Skip to content

Applying NIST CSF 2.0 to AI systems and AI tools

By Sam Rivera, Founder, SentinelPanda · November 7, 2026 · 4 min read · NIST CSF

The Cybersecurity Framework was written to outlast specific technologies. AI is the biggest test of that design so far, and it passes, provided your profile says something about AI.

Why a technology-neutral framework fits

NIST CSF 2.0 describes outcomes, what a well-run cybersecurity programme achieves, rather than technologies or controls. That makes it a natural home for AI security. Managing access permissions with least privilege and separation of duties reads the same whether the subject is an employee, a service account or an AI agent.

The practical way to apply it is through profiles. A current profile records which outcomes you achieve today; a target profile records where you intend to be. Adding AI to both is how AI security becomes part of the programme rather than a side project.

Govern: decide before you deploy

The Govern function, new in CSF 2.0, is where AI security mostly begins. Organisational context (GV.OC) should reflect how AI is used across the business. Roles, responsibilities and authorities (GV.RR) should name who approves AI tools and who owns the risk. Policy (GV.PO) holds the rules for staff: approved tools, permitted data, review of AI-generated output.

Cybersecurity supply chain risk management (GV.SC) carries most of the weight, because most AI is bought rather than built. Assess, contract and monitor AI vendors like any critical supplier, with specific attention to data retention, training use and subprocessors.

Identify: inventory the AI

The asset management outcomes cover the inventory gap AI creates. Software, services and systems (ID.AM-02) should include AI tools and the AI features enabled inside existing services. Services provided by suppliers (ID.AM-04) should include the AI APIs your products call. The data inventory (ID.AM-07) should show which data types reach which models. Risk assessment (ID.RA) then starts from an accurate picture, including AI-specific threats such as prompt injection and model abuse.

Protect: identity, data and secure development

Identity management, authentication and access control (PR.AA) applies to AI integrations: distinct identities, least privilege under PR.AA-05, and strong authentication on the accounts staff use. The data security outcomes cover data at rest, in transit and in use (PR.DS-01, PR.DS-02, PR.DS-10), and in use is where the prompt sits.

If you build AI features, platform security includes integrating secure software development practices (PR.PS-06). NIST SP 800-218A extends the Secure Software Development Framework with practices for generative AI and dual-use foundation models, and is a useful reference for what those practices are. Awareness and training (PR.AT) should cover AI use and AI-enabled social engineering.

Detect, Respond, Recover

Continuous monitoring (DE.CM) should include the activity of AI-driven systems, attributable to an identity, and adverse event analysis (DE.AE) should know what abnormal looks like for them: unusual data volumes, unexpected tool calls, access outside normal patterns.

Incident management (RS.MA) and incident analysis (RS.AN) need playbooks for AI-specific events: sensitive data entered into an unapproved tool, an agent manipulated through injected instructions, a vendor incident that exposes your prompts and outputs. Recovery (RC) should include the ability to switch off an AI integration quickly without taking down the service around it.

Where the AI RMF takes over

The CSF protects systems and data. It does not assess whether an AI system is valid and reliable, fair, explainable or privacy-enhanced; those are trustworthiness characteristics in the NIST AI Risk Management Framework (NIST AI 100-1). The AI RMF and its Generative AI Profile (NIST AI 600-1) address them through four functions of their own: Govern, Map, Measure and Manage.

The two frameworks are complementary by design, and their Govern functions overlap on purpose. One governance structure, one inventory and one risk register serving both is the efficient arrangement. NIST is also developing a CSF profile focused on AI; check its current status before citing it in a programme document.

The short version

  • Add AI to your current and target profiles, not to a separate project.
  • Use Govern for the decisions: who approves AI tools, under which policy, on which supplier terms.
  • Inventory AI tools, AI features and AI APIs as assets and supplier services.
  • Apply PR.AA and PR.DS to integrations and prompts, and PR.PS-06 to anything you build.
  • Monitor AI-driven activity, and write incident playbooks for AI-specific events.
  • Use the AI RMF for the trustworthiness questions the CSF does not ask.
NIST CSF 2.0 core functions NIST AI RMF NIST CSF supply chain risk AI security risks across frameworks

Run your compliance program in one workspace.