Join our Newsletter — 33% off our NHI Course
Home› Guides› NIST CSF 2.0 Community Profiles Catalogue Guide: Sector…
Regulatory Map Regulations & Frameworks

NIST CSF 2.0 Community Profiles Catalogue Guide: Sector Profiles and How to Use Them

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 12 min read
On this page

NIST and industry bodies now publish a growing list of CSF 2.0 Community Profiles, and most organisations do not know which one applies to them or how to turn it into a target state. This page is a catalogue: it lists the Community Profiles that NIST links from its CSF 2.0 profiles page, shows their publication status as checked on 27 October 2026, and explains how a member organisation adopts one. It does not re-teach the CSF Core, the Tiers or the method for writing your own Organizational Profile; the NIST CSF 2.0 Guide covers those. It is written for security architects, GRC leads and sector associations choosing a baseline. Status line: CSF 2.0 is a voluntary framework, several profiles listed here are still drafts, and statuses change as NIST finalises documents.

Key takeaways

  • A Community Profile is a shared baseline, not a regulation. NIST describes it as a baseline of CSF outcomes created and published to address shared interests and goals across a number of organisations, which members can adopt as or into their own Target Profile.
  • Status varies widely. SP 800-61 Rev. 3 (incident response) and IR 8374 Rev. 1 (ransomware) are final; the manufacturing (IR 8183 Rev. 2), genomic data (IR 8467), O-RAN (IR 8623) and Cyber AI (IR 8596) profiles were drafts when checked.
  • Not every profile is written by NIST. The NIST list includes profiles from the Cyber Risk Institute (financial sector), the Cloud Security Alliance, CableLabs and telecommunications groups.
  • Profiles say what matters most, not how to configure it. The draft NIST guide to creating Community Profiles (CSWP 32) says a profile at minimum sets priorities for CSF outcomes and gives a rationale; implementation detail comes from informative references.
  • Identity outcomes need translation for machines and agents. PR.AA-01 already covers identities and credentials for "users, services, and hardware"; a sector profile's PR.AA priorities should be applied to service accounts, API keys and AI agents, not only to staff.

Regulations and frameworks at a glance

The table lists the CSF 2.0 Community Profiles linked from the NIST CSF 2.0 profiles page, with the status shown on the NIST CSRC publication page where one exists. Where the NIST profiles page gives no publication number, the column says "see publisher".

ProfilePublisherDocumentStatus (checked 27 Oct 2026)Typical audience
Incident Response Recommendations and ConsiderationsNISTSP 800-61 Rev. 3Final, April 2025; supersedes Rev. 2 (2012)Any organisation with an IR capability
Ransomware Risk ManagementNISTIR 8374 Rev. 1Final, June 2026; supersedes the CSF 1.1 version (2022)Any organisation
Manufacturing ProfileNISTIR 8183 Rev. 2Initial public draft, September 2025; comments closed 17 November 2025Manufacturers, OT owners
Genomic Data Cybersecurity and Privacy Frameworks ProfileNISTIR 8467Second public draft, December 2024Genomic sequencing, research, healthcare
Federal Agency O-RAN DeploymentNISTIR 8623Initial public draft, September 2026; comments due 2 November 2026US federal agencies deploying Open RAN
Cyber AI ProfileNIST (with MITRE authors)IR 8596Initial preliminary draft, December 2025; comments closed 30 January 2026Organisations building, using or defending against AI
Transit, Foundational PNT, SemiconductorNISTSee NIST profiles pageCheck the linked page before useTransit operators, PNT users, chip makers
Financial Sector Profile; Financial Sector Cloud Services ProfileCyber Risk InstituteSee publisherCheck publisherBanks, insurers, financial services
Cloud Security Community ProfileCloud Security AllianceSee publisherCheck publisherCloud providers and customers
Internet Routing ProfileCableLabsSee publisherCheck publisherNetwork operators
Telecommunications Sector Profile v1.0 and v2.0Industry groups listed by NISTSee publisherCheck publisherTelecoms operators

Older CSF 1.1 profiles remain in the NCCoE archive of example Community Profiles, including liquefied natural gas (IR 8406), hybrid satellite networks (IR 8441), electric vehicle extreme fast charging (IR 8473), the smart grid profile (TN 2051) and profiles from the Cybersecurity Coalition and the IRS Security Summit. They are still useful as content but map to CSF 1.1 identifiers, so expect to remap categories (CSF 2.0 has 22 Categories and 106 Subcategories, against 23 and 108 in CSF 1.1, according to the IR 8183 Rev. 2 page).

Scope: who and what is covered

Community Profiles sit between the generic CSF Core and an individual organisation's Organizational Profile.

  • Developers and owners: CSWP 32 names trade associations, non-profits, government agencies, advisory committees and information sharing organisations as typical owners. They need sector expertise and the ability to convene experts.
  • Participants: operational and security experts who shape priorities and ideally champion the profile once published.
  • Member organisations: use the profile to inform executive decisions, benchmark their current state, set Target Profiles and allocate resources.
  • NCCoE: publishes example Community Profiles and supporting resources.

Scope differs by profile. Threat profiles (ransomware, incident response) apply across sectors. Sector profiles (manufacturing, financial, telecoms) assume a sector's systems and regulators. Technology profiles (O-RAN, PNT, cloud, Cyber AI) follow a technology wherever it is deployed. Many organisations should combine one sector profile with one or two threat or technology profiles.

Choosing your profile set

If you areStart withAdd
A manufacturer with OTIR 8183 Rev. 2 (draft) or Rev. 1 if you need a final textIR 8374 Rev. 1; SP 800-61 Rev. 3
A US bank or insurerCRI Financial Sector ProfileCRI cloud services profile; IR 8374 Rev. 1
A SaaS or cloud providerCSA Cloud Security Community ProfileSP 800-61 Rev. 3; IR 8596 for AI features
A healthcare or genomics organisationIR 8467 (draft)IR 8374 Rev. 1
Any organisation deploying AI agentsYour sector profileIR 8596 Cyber AI Profile (draft)

Key obligations

A Community Profile creates no legal duty on its own. Obligations arise only when a regulator, contract or internal policy adopts one. What a profile does specify, according to CSWP 32, is:

  • Priorities: a priority level for each relevant CSF 2.0 outcome, as a ranking or a scale such as Low, Moderate, High.
  • Rationale: why each outcome matters to that community, tied to its threats and challenges.
  • Informative references: mappings to standards and guidance the community already uses.
  • Optional material: considerations, implementation examples and notes. There is no required format.

For a member organisation, adoption means three concrete commitments: record which profile and version you adopted and why, express its priorities as your Target Profile (or a documented subset of it), and measure your Current Profile against it. Where a profile's outcome does not apply, document the exclusion and the reason, because that record is what an auditor or regulator will ask for.

Timeline and current status

DateEvent
26 February 2024CSF 2.0 released with quick-start guides, including SP 1301 (Organizational Profiles, final) and CSWP 32 (Community Profiles, initial public draft; comments to 3 May 2024)
December 2024IR 8467 genomic data profile second public draft
April 2025SP 800-61 Rev. 3 final, as a CSF 2.0 Community Profile
September 2025IR 8183 Rev. 2 manufacturing profile initial public draft
December 2025IR 8596 Cyber AI Profile initial preliminary draft
11 June 2026IR 8374 Rev. 1 ransomware profile final; IR 8374 (2022) withdrawn
September 2026IR 8623 O-RAN profile initial public draft; comments due 2 November 2026

Drafts can change materially before final publication. If you adopt a draft, pin the exact version (for example "IR 8183 Rev. 2 ipd, September 2025") in your Target Profile and schedule a review when the final appears.

Enforcement and penalties

There are none from NIST. CSF 2.0 and its Community Profiles are voluntary guidance. Exposure comes indirectly:

  • Regulatory adoption: a supervisor or sector body may reference a profile in examination or membership expectations. The financial sector CRI Profile is the most prominent example of a sector profile used in supervisory conversations; see the NIST CSF Financial Sector CRI Profile Guide and the FFIEC Cybersecurity Guidance Guide.
  • Contracts: customers and federal agencies may require attestation against a named profile.
  • Negligence arguments: after an incident, failing to meet a sector baseline that peers widely adopted is hard to defend.

What it means for AI agents and non-human identities

Most profiles were written with people and devices in mind, yet the CSF 2.0 identity outcomes explicitly include services. Translate priorities as follows.

CSF 2.0 outcomeWordingNHI and agent interpretation
ID.AM-02Inventories of software, services, and systems are maintainedInventory service accounts, workload identities, API keys and agents with an owner for each
PR.AA-01Identities and credentials for authorized users, services, and hardware are managedLifecycle for machine credentials: issuance, rotation, revocation, decommissioning
PR.AA-03Users, services, and hardware are authenticatedPrefer federated workload identity and short-lived tokens over static secrets
PR.AA-05Access permissions are managed with least privilege and separation of dutiesScope agent tool permissions and OAuth grants; review entitlements of automation
PR.PS-04Log records are generated and made available for continuous monitoringLog each agent action against a distinct identity, not a shared key
DE.CM-09Computing hardware and software, runtime environments, and their data are monitoredBaseline service account and agent behaviour; alert on new resources or hours

The draft Cyber AI Profile organises AI concerns into three focus areas: securing AI system components, AI-enabled cyber defence, and thwarting AI-enabled attacks. Overlay it on your sector profile rather than treating it as a replacement. See the NIST Cyber AI Profile Guide and the Agentic AI Identity Guide. For the ransomware profile, credential theft from service accounts is a common path to domain-wide encryption; the NIST IR 8374 Rev 1 Ransomware Risk Management Profile Guide covers that profile in depth.

Compliance steps

  1. Select: pick one sector profile and the threat or technology profiles that match your exposure, using the tables above. Record the document number, version and status.
  2. Read the rationale, not only the priorities: the rationale tells you which threats the community assumed. If your threat model differs, adjust and document why.
  3. Merge into one Target Profile: where two profiles rate the same Subcategory differently, take the higher priority. Use the SP 1301 Organizational Profile template structure to hold the result.
  4. Assess the Current Profile: rate each in-scope Subcategory against evidence. Include machine and agent identities in PR.AA and ID.AM scoring from the start.
  5. Prioritise gaps: rank by the profile's priority and your risk register. High-priority gaps get funded actions with owners and dates.
  6. Pilot on one business unit: test the assessment method and evidence requests before rolling out, then refine.
  7. Report: show leadership the gap profile against the community baseline; peers' adoption makes it a credible benchmark.
  8. Maintain: watch the NIST profiles page and publisher sites. When a draft becomes final, or a profile is superseded (as IR 8374 was), re-baseline. If an update causes confusion, you can roll back to the pinned prior version until the change is assessed.

If you are building a Community Profile

Sector associations and ISACs sometimes find no profile fits their members. CSWP 32 describes a four-phase lifecycle with communication running through every phase:

  • Plan: identify the audience, set scope, choose participants, identify community-specific references and decide what to include.
  • Develop: identify community priorities, align them with CSF outcomes, draft the profile, gather community feedback and announce the final version.
  • Use: coordinate how the profile is applied across and within member organisations and assess the community's current state.
  • Maintain: measure impact, monitor for feedback and change, update as needed, and retire the profile when it is no longer useful.

Before starting, check the NIST list and the NCCoE archive: extending an existing profile with a sector annex is usually cheaper than a new one, and it keeps members comparable with peers in adjacent sectors. Include machine identity and AI agent considerations in the Develop phase, since retrofitting them after publication means a new version.

Metrics

  • Percentage of high-priority profile Subcategories at target.
  • Number of open gaps against the adopted profile, by priority, over time.
  • Percentage of machine identities in inventory with a named owner (ID.AM-02, PR.AA-01).
  • Age of the adopted profile version against the latest published version.
  • Time from a profile's final publication to your re-baseline.

Common failure patterns

  • Adopting a draft as if final: drafts change; the unpinned version you assessed against may not exist next year.
  • Copying priorities without rationale: a manufacturing profile's priorities assume OT; an IT-only subsidiary inherits irrelevant targets.
  • Human-only identity scoring: PR.AA marked "met" because staff have MFA, while service accounts use static passwords that never rotate.
  • Using CSF 1.1 profiles with CSF 2.0 IDs: category identifiers changed, so mappings silently break.
  • Profile as shelfware: no Current Profile assessment, so no gap list and no funded actions.

Practitioner checklist

  • Identify your sector, threat and technology profiles from the NIST CSF 2.0 profiles page.
  • Record the exact document number, version and status for each adopted profile.
  • Read each profile's rationale and note assumptions that do not fit you.
  • Merge priorities into one Target Profile, taking the higher priority where they conflict.
  • Assess the Current Profile with evidence, including NHIs and AI agents under ID.AM and PR.AA.
  • Document excluded outcomes with reasons.
  • Fund high-priority gaps with owners and dates.
  • Re-check status of draft profiles at least quarterly and re-baseline on final publication.
  • Report the gap profile to leadership against the community baseline.

Standards and references

Related NHI Mgmt Group resources: NIST CSF 2.0 Guide · NIST Cyber AI Profile Guide · NIST IR 8374 Rev 1 Ransomware Risk Management Profile Guide · NIST CSF Financial Sector CRI Profile Guide · NHI Governance Maturity Model. This guide summarises the NIST CSF 2.0 Community Profiles catalogue and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.