Aligning AI Adoption Maturity with AI Security Using CMMI and Russian Regulatory Requirements
Organizations today operate simultaneously in two distinct dimensions of artificial intelligence: the depth of AI integration into business processes and the maturity of security controls protecting those systems. These two maturity levels rarely align, and the resulting gap is responsible for most security incidents and regulatory findings rather than the mere fact of using AI.
To make the misalignment visible, both axes are mapped onto the five-level CMMI scale. Level L1 represents initial, unpredictable processes; L2 covers managed processes at the project level; L3 introduces organization-wide defined standards; L4 adds quantitative management through metrics; and L5 focuses on continuous optimization.
Under this unified scale, typical adoption follows the Gartner progression from awareness to enterprise transformation, while security maturity is assessed using OWASP AIMA across eight domains including Governance, Data Management, and Operations. The mapping reveals that many organizations reach L3 in adoption while remaining at L1 or L2 in security, leaving them exposed to Shadow AI and violations of mandatory requirements.
FSTEC Order No. 117, effective from March 2026, replaces earlier rules and introduces explicit obligations in paragraphs 60 and 61. These require the use of trusted AI technologies, prohibition on transferring restricted data to model developers, statistical criteria for response accuracy, and controls on query formats. The obligations activate when systems move from pilot to production use, exactly at the L2-to-L3 transition.
Additional Russian anchors include GOST R 56939-2024 for secure development, GOST R 59276-2020 for trust mechanisms, and the new P NST 1046-2026 standard for AI in critical information infrastructure. International references such as Google SAIF, NIST AI RMF, and MITRE ATLAS supply supporting risk maps and attack catalogs that fit within the same CMMI framework.
The practical states organizations pass through include denial of AI use, widespread uncontrolled Shadow AI, LLM controls that leave agentic systems exposed, and finally managed agentic environments with least-privilege tool access and continuous red-teaming. The recommended approach is to ensure security maturity matches or slightly exceeds adoption maturity at every level to avoid both operational risk and regulatory non-compliance.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.