NIST SP 1353: How AI Helps Map Cybersecurity Risk

NIST SP 1353 is an initial public draft showing how generative AI could help organisations analyse, plan, implement and monitor progress against the NIST Cybersecurity Framework (CSF) 2.0. Published on 19 August 2026, it focuses on structured prompts for reviewing governance, drafting a current-state profile and drafting a target-state profile. It does not certify controls, replace a security assessment or turn an AI output into evidence. The public comment period closes on 15 October 2026.

This is an educational analysis, not cybersecurity, compliance or legal advice. Validate the draft and any resulting decisions with qualified security professionals.

What NIST SP 1353 actually is

NIST SP 1353 is a Quick-Start Guide for Using Artificial Intelligence (AI) for CSF Analysis and Reporting. It is an initial public draft, not a final standard or certification scheme.

NIST gives it two purposes: provide structured AI prompts for creating CSF-related artefacts, and describe the current state of prompt engineering for CSF implementation and analysis. The guide uses simulated documents for a fictitious company and three notional use cases.

NIST’s key caveat is that these examples illustrate a possible approach and are not prescriptive assessment or assurance methodologies. NIST is seeking comments on the guide and its prompts, not on the fictional documents.

How CSF 2.0 profiles work

The NIST Cybersecurity Framework 2.0 gives organisations a common structure for managing cybersecurity risk. A profile connects that structure to a specific organisation.

• A current-state profile describes the organisation’s present position against relevant CSF outcomes, using policies, processes and evidence.
• A target-state profile describes the outcomes it wants to reach in light of its mission, stakeholders, requirements and risk landscape.

SP 1353 uses AI to help draft this bridge from unstructured material. The model may sort, map and summarise documents; the organisation still owns the scope, evidence and risk judgement.

The three use cases in the draft

Use case	What the AI-assisted workflow drafts	What people still decide
Governance review	A review of policy, strategy and risk governance against CSF 2.0 outcomes	Whether documents reflect how risk is actually owned and managed
Current-state profile	A mapping of artefacts and interview notes, with assumptions and observed gaps	Which claims are supported by current evidence
Target-state profile	A draft of desired outcomes using internal and industry references	Whether the target is realistic, prioritised and tied to business goals

The useful pattern is not “ask a chatbot for a security score”. It is “give a model a defined body of material and ask for a reviewable document that exposes assumptions and missing evidence”.

Where AI can help—and where it cannot

Cybersecurity programmes contain policies, audit reports, architecture diagrams, risk registers, interviews, supplier questionnaires and incident reviews. A language model can create a first structured pass across that material.

A controlled workflow could ask it to:

1. extract claims from a policy or interview note;
2. map each claim to a candidate CSF outcome;
3. preserve the source passage;
4. label each item as evidence, assumption, open question or contradiction;
5. identify missing artefacts or interviews;
6. produce a draft profile for a named reviewer.

This can reduce the cost of finding and organising information. It may reveal that a policy describes access reviews while the evidence pack contains no recent review record. But a fluent sentence is not proof that a control operates, and a missing sentence is not proof that it does not.

NIST’s announcement says the guide is not intended to provide AI best practices or cybersecurity guidelines, although it marks specific precautions in places. The model cannot independently establish whether evidence is authentic and complete, whether a control operates effectively, whether a gap is material, whether sensitive data may be sent to a provider, or whether someone should accept residual risk. Those are governance decisions.

A safer way to use the prompts

Start with a narrow workflow, not “audit our cybersecurity”. Define:

• the business unit, system or process in scope;
• the CSF version and profile template;
• the documents and interview notes the model may access;
• the owner, date and sensitivity of each source;
• the required output fields;
• the reviewer who must approve, reject or correct each finding.

Separate source-backed evidence, model interpretation, assumption and missing evidence in the output. Preserve references so a reviewer can move from a claim back to its supporting document, interview or system record.

Data handling is part of the design. Minimise context, remove unnecessary personal or confidential information, define retention and access rules, log the prompt and model version, and test whether untrusted source material can manipulate the workflow. A document that contains instructions for a model is data to analyse, not automatically an instruction to follow.

From draft to decision

1. Set scope and ownership

Name the process, systems, business owner and security reviewer. Record whether the exercise is for a gap inventory, current-state profile, target-state discussion or formal-assessment preparation.

2. Build an evidence pack

Collect only material needed for that scope. Give each item a source name, date, owner and sensitivity classification. Treat interviews as reports that need corroboration, not automatic proof.

3. Run a reproducible first pass

Ask for mappings, quotations, assumptions, gaps and questions in a fixed schema. Record the prompt, model, input set and output date.

4. Review, validate and track change

Security practitioners check the mapping; process and system owners confirm whether the practice exists. Compare important findings with logs, tickets, configuration records, test results, contracts or other authoritative evidence. Store the approved version, review date, owners and follow-up actions, then rerun the workflow when a defined change or review trigger occurs.

What this means for AI assistants in security teams

SP 1353 points to a practical role for AI in cybersecurity: a governed assistant that helps people navigate company knowledge and repeatable analysis, rather than an autonomous authority that silently approves risk.

An assistant may retrieve approved documents, produce a draft mapping, show the evidence behind a claim and route uncertainty to a human. It should not broaden its own access, invent missing controls, make high-impact changes or turn an unreviewed draft into a compliance statement.

Permissions, source freshness, audit logs, escalation paths and correction processes matter more than model novelty.

What happens next

NIST published SP 1353 as an initial public draft on 19 August 2026. Comments are open until 15 October 2026 at 11:59 p.m. Feedback should address the quick-start guide and supplied AI prompts; the fictional organisational documents are illustrative.

The draft’s contribution is concrete: prompts are attached to familiar CSF work products. Its limitation is equally concrete: it does not remove the need for evidence, security expertise or accountable approval.

FAQ

Is NIST SP 1353 a final standard?

No. It is an initial public draft of a CSF 2.0 quick-start guide. Comments close on 15 October 2026.

Does SP 1353 certify an organisation’s cybersecurity?

No. NIST says the use cases are possible approaches, not prescriptive assessment or assurance methodologies.

What is a current-state profile?

It is a structured description of an organisation’s present position against relevant CSF 2.0 outcomes. SP 1353 shows how AI could help draft the mapping while documenting assumptions and observed gaps.

Can a company paste all its security documents into a public AI model?

Not by default. The choice depends on the model, contract, data classification, access controls, retention settings and organisational policy. Minimise data and obtain security and legal review before using sensitive material.

What should a small team try first?

Choose one bounded process, keep a human reviewer, preserve source references and compare the AI-assisted result with a manual baseline before expanding the workflow.

Sources

• NIST SP 1353: Quick-Start Guide for Using AI for CSF Analysis and Reporting
• NIST: Seeking Public Comment on Using AI for CSF 2.0 Analysis and Reporting
• NIST Cybersecurity Framework 2.0
• NIST AI Risk Management Framework

If your organisation is turning AI experiments into governed assistants for company knowledge and repeatable security workflows, explore Botchi. For an independent conversation about the use case, evidence and implementation path, contact SignorCrypto.