Patching processes were designed around a trickle of findings on a monthly cycle, because finding vulnerabilities was the scarce activity. That balance has changed. AI now finds flaws in real software at a scale no team could match, the same capability turns published fixes into working exploits cheaply, and disclosures have risen sharply. The constraint has therefore moved from finding to verifying, prioritising and fixing. This chapter shows how defenders use AI to find and fix flaws in their own code, prioritise exposure, delegate patch decisions in advance, and absorb the resulting patch wave without exhausting the people who approve each change.
The chapter is responsible for two Categories of NIST CSF 2.0 (19, NIST, 2024). ID.RA Risk Assessment asks that vulnerabilities are identified, validated and recorded (ID.RA-01), that threats, likelihoods and impacts inform the prioritisation of risk (ID.RA-05), that risk responses are planned and tracked (ID.RA-06), and that vulnerability disclosures are handled (ID.RA-08). PR.PS Platform Security asks that software is maintained commensurate with risk (PR.PS-02) and that secure development practices are integrated throughout the life cycle (PR.PS-06). Chapter 10 covers the threat-modelling side of ID.RA; this chapter covers its vulnerability side, through the three focus areas of the NIST Cyber AI Profile (20, NIST, 2025).
It builds on two earlier conclusions. AI Governance, Chapter 24, held that patch decisions must be delegated in advance, because a weekly change advisory board cannot sit in the path of known-exploited vulnerabilities, and that patch velocity belongs in management reporting (72, Nordqvist, 2026). AI Platform and Security, Chapter 18, made patch velocity the first commitment against AI-enabled adversaries and concluded that human verification is the bottleneck of AI-enabled defence (73, Nordqvist, 2026). This chapter answers what both left open: how to absorb a patch wave in which every published fix also tells an adversary where to look.
Primary topics explored
- What the evidence shows
- AI review in the delivery pipeline
- The verification bottleneck
- Prioritisation signals
- Delegated patch decisions and patch velocity
- Disclosure and reporting
About AI Red Team
AI Red Team is Book 4 of The Transformed Architecture. It shows how large European enterprises and public authorities put artificial intelligence to work as an active part of cyber defence: AI-assisted red teaming and adversary emulation, red teaming of AI systems themselves, the AI-assisted security operations centre, detection engineering, threat intelligence, incident response and purple teaming, all under a lawful mandate and with evidence a supervisor can inspect.
It builds on the conclusions of Architecture as Code, AI Governance and AI Platform and Security.
CISOs, SOC leads, red and blue team practitioners, security architects, AI architects and technical decision-makers.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 11: Vulnerability Discovery and Exposure Management at Machine Speed in AI Red Team gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Identify” and is one of 32 drawn from the manuscript.