Building the Foundation of Digital Trust: Why Identity Security Remains Undervalued
Identity Security is one of the most underestimated foundations of cybersecurity. Behind the routine request to “give a person access” lies a company’s decision to trust an individual with its information and to allow work with specific documents and systems. This requires understanding what the person must do, which data they need, and when their permissions should end.
Significant investments in protection tools can still leave a dismissed employee with access to confidential documents while a new hire waits for access to a critical system. The topic clearly shows how deeply IT and information security functions intersect. The same directory services, sign-on mechanisms, and access management tools both enable applications and protect company information.
Price of Errors in Access Management
The 2026 Identity Conf presented research by Indid and the Identity Club. The survey covered 200 organizations with at least 100 employees that already use at least one Identity Security solution. 43.5% of respondents reported errors in manual rights assignment that temporarily gave outsiders access to confidential data. 33.5% noted access remaining for dismissed employees. These figures reflect the participants’ own organizations and cannot be extrapolated to the entire Russian market, yet they illustrate where problems arise: personnel changes do not always reach information-system settings.
The reverse side of the problem is equally costly. Before IdM implementation, account creation at Lamoda Tech could take three days. Warehouse staff need access on the morning of their first working day. Such delays affect core business processes and helped justify investment in Identity Security.
Designing Protection Together with Business Processes
In August 2026 NIST introduced the Human-Centered Cybersecurity concept. The authors recommend considering people’s needs, capabilities, and limitations when developing policies, processes, and technologies. For Identity Security this approach should cover the entire path from the decision on permissions to task execution. A manager asked to review an employee’s rights may see only obscure technical role names; the request format must therefore provide clear business explanations.
Economics of the Project Across the Full Lifecycle
Project evaluation must distinguish waiting time from labor costs. Three days until access is granted does not equal three days of continuous administrator work. The freed time of an employee does not automatically become an economic benefit; the actual change in their work must be measured. Separate evaluation of operational improvement and risk reduction is advised. Measurable indicators include task completion time and labor costs, while expected losses are assessed through scenarios and documented assumptions.
What to consider in the project:
- Data to verify: implementation and maintenance costs, labor for surveys, integrations, support, rights reviews, and audit evidence preparation.
- Load on business processes: access waiting time, task execution, login and recovery success rates, approval errors, support tickets, and manual exceptions.
- Residual business risk: unacceptable action scenarios, potential damage, and actual ability to detect and terminate dangerous access.
From Human Trust to System Permissions
Determining who needs access begins with relationships between people. Employment or contractor agreements define the work, conditions, and responsibilities. These legally formalized relations must serve as the basis for granting information and system access. Architectural frameworks such as TOGAF help describe business functions, yet the model must accurately reflect each employee’s and external contractor’s real working tasks. Contract, position, and instructions alone do not explain which data require access; commercial secrets, medical confidentiality, attorney-client privilege, and personal data rules must be mapped to concrete actions and resources.
Keeping Permissions Aligned with Company Changes
After initial configuration, business tasks change, contracts end, and new applications appear. Identity Security is therefore a set of processes forming a managed lifecycle with feedback at three levels: rapid restriction of dangerous access, periodic review of actual permissions, and revision of system-wide rules. These processes align with NIST SP 800-53 Rev. 5 controls AC-2, AC-6(7), AU-6, and IR-4, as well as NIST SP 800-137 for continuous monitoring. Russian FSTEC Order No. 117 (points 48 and 49) and GOST R 59547-2021 provide additional reference points for commercial organizations.
Linking Business Permissions to Application Rights
Centralized access management requires that decisions on permissions are correctly executed in every application. Failed integration attempts have shown that attributes and detailed rights configured only inside an application cannot be managed through API. Pre-project surveys must therefore trace the path from agreed business actions to their execution in each specific application. IGA combines organizational governance with system administration, while IdM links HR data to accounts, assigns and revokes rights, and reconciles results against approved permissions. RBAC and ABAC models, described in GOST R 59383-2021, translate business roles into technical permissions. Integrations must be maintained as the landscape evolves; implementation in a mid-sized company typically takes 10–12 months according to Solar estimates.
Assembling a Trust Environment from Domestic Solutions
The Russian market already offers mature domestic products covering IdM, Credential Management, Access Management (including SSO and PAM), and governance functions. The FICAM reference model from GSA illustrates how identity management, electronic credentials, and access control integrate with overall governance and information resources. Organizations can adapt this model to their own infrastructure and regulatory requirements.
Related articles
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.
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.
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.
Russian Court Convicts Former IT Director for Unauthorized Access to Huawei Storage After Moving Servers Offsite
A former IT director at an Omsk manufacturing plant was found guilty under Part 3 of Article 272 of the Russian Criminal Code for blocking and modifying data on a Huawei Dorado 3000 v6 storage array after relocating the entire server infrastructure to a privately rented office. The court relied heavily on detailed logs from the Huawei system that recorded the exact sequence of disk removals, reinsertions in altered order, and the shutdown command, even after the administrator attempted to delete portions of the event journal. The incident occurred on the same day new management took over, causing immediate loss of access to corporate email, 1C systems, design software, and shared network resources. Despite the defendant's claims that he was preparing the array for cloud backup and that a script had frozen, the court rejected the explanation based on audit concealment, lack of notification to owners, and post-incident behavior. The ruling imposed a 400,000-ruble fine and a one-year ban on computer-information work involving protected secrets, while leaving a civil claim for 18.27 million rubles in recovery costs for separate proceedings. The case highlights how storage-array logs can serve as decisive forensic evidence and underscores the legal risks of retaining physical or logical access after employment ends.