From MTTD and MTTR to Real Value: How to Organize SOC Metrics Effectively
Anatoly Antipov, who leads the L1 analyst group in a small in-house SOC of up to eight people, describes how classic time-based metrics often produce the opposite of their intended effect. Many leaders start the day reviewing dashboards built around MTTD, MTTR, and similar indicators recommended by NIST SP 800-61. These numbers look clean in quarterly reports, yet they frequently hide shallow investigations and growing technical debt.
The SANS SOC Survey highlights the same pattern: when speed and volume become the only targets, analysts begin optimizing for the metric instead of security outcomes. One documented case showed a simple script automatically moving new alerts into the “in progress” state to keep MTTA numbers green while real cases sat untouched for hours.
To address this, the team introduced a strict five-level verdict matrix. The categories are TP.Ext for confirmed external attacks, TP.Int for internal policy violations, BP for authorized testing activity, FP for legitimate business or IT actions, and FP.SOC for problems inside detection content, parsing, or filtering logic. This classification makes it immediately visible where the SOC is generating value and where it is accumulating its own technical debt.
The weekly report was rebuilt around three focused blocks. The first shows overall alert volume, closure rates, backlog, and shift workload distribution. The second breaks alerts down by the new verdict matrix so managers can see whether rising false positives stem from business changes or from SIEM and SOAR content issues. The third block lists real confirmed incidents together with concrete effort indicators such as emails sent, EDR scans launched, and indicators blocked.
Every week a sample of closed alerts from each analyst undergoes quality review. Reviewers check whether the verdict is correct, whether actions are fully documented, whether sufficient artifacts are attached, and whether FP.SOC items include clear recommendations for rule improvement. The process prevents analysts from being rated solely on speed.
The changes demonstrate that Mean Time metrics remain useful when paired with quality controls, transparent verdicts, and regular audits. Without these additions, small SOC teams risk turning into expensive click farms that look efficient on dashboards while actual risk reduction quietly declines.
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.