Habr•November 2, 2026•🇷🇺Translated from Russian

How EVRAZ Built Effective Information Security Processes Without Draconian Restrictions

EVRAZ operates one of the smallest information security teams in its industry yet achieves strong results, including more than 92 percent compliance in the latest external audit and high maturity scores against sector benchmarks.

Andrey Nuykin, head of the Information Security Department, oversees protection for over one thousand developers, tens of thousands of users, industrial systems, and numerous IT contractors. The team deliberately avoids heavy-handed prohibitions, preferring negotiated requirements and extended rollout periods instead of sudden restrictions.

Gradual rollout of security controls

Security involvement begins at the project request stage and continues through technical specification, architecture design, development, and production handover. An internal instruction detailing requirements for all information systems is available to project managers and IT staff. Every project receives an assigned leader from EvrazTekhnika, the company’s in-house IT provider.

Architecture diagrams must be submitted for review. Internet-facing services require intermediate servers in a DMZ with explicitly defined data flows. Once architecture is approved, static code analysis is embedded in the DevOps pipeline. Failed scans block the pipeline until vulnerabilities are fixed or marked as false positives under controlled conditions.

From development to production

Before moving to pilot operation, the security team verifies that agreed controls remain in place. A system passport is then prepared, documenting ownership, criticality, accounts, roles, certificates, and data categories. All operational units must sign off before the system enters full production.

After deployment, the monitoring center receives events, performs correlation, and issues tickets for vulnerability remediation and incident response.

Handling developer resistance and AI-generated tools

Developers once resisted implementing WAF and DDoS protection on a public service, claiming performance impact. After the team temporarily disabled the WAF during a platform migration, the same developers requested its return within three weeks due to a surge in unwanted bot traffic.

A separate incident involved a business-unit employee who built an AI-assisted internal dashboard that grew popular among managers. A quick pre-meeting assessment by the security team revealed multiple exploitable flaws. The employee was persuaded not to expose the service externally and was directed to rebuild it under proper IT governance.

The department now works to extend established review processes to cover widespread use of generative AI tools by non-developers, focusing on data leakage risks and uncontrolled code rather than blanket prohibitions.

Related articles

Habr•Policy & Regulation

I Know but Cannot Tell: The Forensic Expert's Struggle to Share Real Cases Under NDA Constraints

A cybersecurity journalist reflects on the inherent difficulties of writing about digital and financial forensics while bound by strict confidentiality agreements. The article explores how verifying financial documents involves far more than spotting Photoshop alterations, raising questions about data origin, accuracy, interpretation, and the validity of conclusions drawn by examiners. Automated verification systems often produce conflicting results because they assess different aspects of a document, yet lack transparent justification for their verdicts. Attempts to anonymize cases, obtain client consent, or use synthetic data each carry limitations that can still lead to identification or fail to demonstrate actual expertise. The author recounts collaborating with an AI to draft the piece, only to realize the meta-discussion about the inability to publish real cases itself became the only publishable story. Ultimately, the piece highlights the tension between the professional desire to share knowledge and the contractual and ethical barriers that prevent meaningful disclosure in the field of forensic analysis.

Habr•Policy & Regulation

Three Hypotheses on Information Security Risk Assessment: Where Automation Truly Saves Time at Avito

Avito expert Irina Sozinova details how the company tested automation in its risk assessment process after scaling issues emerged with thousands of risks in the GRC system. The team formulated and piloted three hypotheses focused on automating typical risks, eliminating manual team preparation, and validating data to reduce InfoSec workload. Results showed a 16% drop in total risks registered, zero preparation time for teams, and improved coverage and context quality, though overall expert time savings were partially offset by new post-processing tasks. The pilot confirmed that automation works best on repeatable scenarios with stable data sources rather than promising immediate proportional time cuts. Avito plans to complete automation of context collection and finding classification this year to expand risk assessments across the company next year.

Habr•Policy & Regulation

Integrating OAuth 2.0 with PDP Architectures Without Modifying Core Authorization Engines

The article explores how to combine OAuth 2.0 delegated access with traditional PEP/PDP authorization systems. It proposes an OAuth-aware PDP layer that translates access tokens into standard PDP checks while preserving the original PDP implementation. Three main use cases are analyzed: stored user grants, tenant-level administrative grants, and scopes carried directly inside tokens. The design relies on synthetic subjects such as u+c and t+c pairs, ephemeral policies for token-embedded scopes, and optional OAuth-aware PAP components. Special attention is given to token contents, policy storage via PAP, and the need for deterministic subject identifiers. The approach supports both classic scope models and structured RAR-style authorizations while maintaining separation between OAuth grants and subject permissions.

Habr•Policy & Regulation

Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks

The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.