Topic
FSTEC Order 117
Proving Vulnerability Management Works: MTTR Metrics, Maturity Models, and Real-World Testing
Vulnerabilities & Exploits
Building the Foundation of Digital Trust: Why Identity Security Remains Undervalued
Policy & Regulation
Why Vulnerability Management Specialists Must Master Compliance: Closing All CVEs but Leaving admin:admin
Policy & RegulationAsset Management as the Foundation of Vulnerability Management: Unknown Assets Cannot Be Protected
The article explains that asset management forms the essential base for any effective vulnerability management program, as organizations cannot protect systems they do not know exist. It details multiple data sources including SIEM, NTA/NDR, Active Directory, CMDB, virtualization platforms, and cloud APIs that must be combined to build a complete inventory. Key record fields such as asset criticality, responsible owner, and last successful scan date are highlighted as critical for prioritization and SLA compliance. The piece examines new Russian regulations including FSTEC Order No. 117 and Federal Law No. 58-FZ that mandate accurate asset inventories to meet monthly scanning and 24-hour critical patch requirements. International frameworks such as CIS Controls v8.1, NIST CSF 2.0, and ISO/IEC 27001:2022 are compared, emphasizing lifecycle management and reaction processes for unauthorized assets. Emerging asset types including cloud resources, SaaS services, AI systems, containers, and IoT devices are discussed as expanding the attack surface faster than organizations can track.
Aligning AI Adoption Maturity with AI Security Using CMMI and Russian Regulatory Requirements
Organizations frequently operate at mismatched maturity levels between AI implementation and AI security controls, creating significant gaps that lead to incidents and regulatory violations. The analysis maps both dimensions onto the five-level CMMI scale, showing how adoption often outpaces protection and highlighting the risks of Shadow AI, uncontrolled agents, and non-compliance. Key frameworks including OWASP AIMA, Google SAIF, NIST AI RMF, and MITRE ATLAS are aligned to CMMI levels L1 through L5. Russian requirements under FSTEC Order No. 117, effective March 2026, introduce mandatory controls for trusted AI technologies, data handling, and statistical response validation that activate precisely at the L2-to-L3 transition. The article details predictable organizational states from denial to managed agentic systems and provides a practical matrix linking each CMMI level to minimum security requirements and specific Russian compliance anchors such as GOST R 56939-2024 and ISO/IEC 42001.