Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

An AI compliance audit is less mysterious than its absence from most planning suggests. Someone outside the organization reads what you wrote down, then samples real systems to test whether the organization does what the documents describe. The distance between those two things is where findings come from. ‍ Three different exercises get called an AI audit, and they run differently. Certification against a management standard follows a defined two-stage process.

Three organizations had their production systems compromised by an AI model in April, and found out in late July when the model's developer called them. None of them had detected the activity. One was a security company whose own package scanner was the entry point. ‍ Anthropic published that account on July 30, nine days after OpenAI disclosed a related incident of its own.

The answer changed on a specific date. Until the start of 2026, most organizations were covered for AI losses by silence rather than by grant, because policies neither affirmed nor excluded AI and the question would have been argued at claim time. On January 1, 2026 the standard forms organization introduced generative AI exclusion endorsements for commercial general liability, and carriers began attaching them at renewal. ‍

Security budget requests fail on arithmetic rather than on argument. A finance function asked to approve spending wants the same information it requires from every other proposal, being what it costs, what it returns and over what period. Most security cases supply the first, describe the second qualitatively, and omit the third. ‍ Return on security investment closes that by expressing the benefit as reduced modeled loss rather than as reduced likelihood of an unspecified bad outcome.

AI Security Posture Management arrived as a term before it arrived as a definition. Vendors announced products under the label through 2025 and in volume at RSA Conference 2026, each describing a somewhat different scope, and buyers now evaluate a category whose boundaries depend on who is selling. The lineage is evident, since AI-SPM follows cloud and data security posture management, and the inherited assumptions are where the difficulty starts.

Directors ask for AI risk reporting because oversight failure is personally actionable. Under the Caremark line of cases, a board that cannot demonstrate it monitored a material risk carries exposure of its own, and AI has moved into that category for most enterprises. The request is rarely curiosity about the technology. ‍ The framing determines what belongs in the pack.

NIST AI RMF and ISO/IEC 42001 answer different questions, so the choice is rarely about which one is better. One gives you a risk process your engineering teams can run. The other gives you a management system an auditor can certify. Organizations that treat them as rival options usually pick the wrong one for the problem in front of them. ‍

The EU AI Act reached a turning point this summer, and the headlines got it half right. Obligations for high-risk AI systems were postponed to December 2027 under the Digital Omnibus, adopted in June 2026. The transparency rules under Article 50 were not postponed, and they apply from August 2, 2026. ‍ Enterprises reading spring 2026 guidance are working from a timeline that no longer exists, and enterprises reading the headline about a delay may believe nothing is due.

An annual control assessment produces evidence that a control operated on one day out of three hundred and sixty-five. Sampling narrows it further, since testing twenty-five items from a population of a thousand evidences the control for those twenty-five on that day. The certificate describes a moment and gets read as a year. ‍ Continuous control monitoring closes that interval by testing automatically and often.