borghei/Claude-Skills / ra-qm-team/nist-csf-specialist
nist-csf-specialist
VerifiedNIST Cybersecurity Framework 2.0 implementation, assessment, and compliance management. Use for CSF 2.0 gap analysis, cybersecurity risk management, maturity assessment, CSF profiles, and cross-framework compliance mapping.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.8 KB |
| references/assessment-and-roadmap.md | markdown | 7.3 KB |
| references/csf-functions-guide.md | markdown | 21.9 KB |
| references/csf-implementation-playbook.md | markdown | 25.1 KB |
| references/framework-reference.md | markdown | 26.3 KB |
| references/tools-and-troubleshooting.md | markdown | 5.7 KB |
| scripts/csf_control_mapper.py | script | 27.3 KB |
| scripts/csf_maturity_assessor.py | script | 29.1 KB |
references/csf-functions-guide.md
View on GitHub# NIST CSF 2.0 Functions, Categories, and Subcategories — Complete Reference
This reference provides the complete NIST CSF 2.0 taxonomy with implementation guidance, evidence requirements, common assessment questions, and maturity indicators for each function and category.
---
## 1. GOVERN (GV)
**Purpose:** Establish and monitor the organization's cybersecurity risk management strategy, expectations, and policy. GOVERN is the connective tissue that informs how the other five functions are implemented.
### GV.OC — Organizational Context
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| GV.OC-01 | Organizational mission | The organizational mission is understood and informs cybersecurity risk management |
| GV.OC-02 | Internal stakeholders | Internal stakeholders understand and contribute to cybersecurity risk management |
| GV.OC-03 | Legal and regulatory | Legal, regulatory, and contractual requirements are understood and managed |
| GV.OC-04 | Critical objectives | Critical objectives, capabilities, and services are understood and communicated |
| GV.OC-05 | Outcomes and dependencies | Outcomes, dependencies, and requirements are understood for key services |
**Evidence Requirements:**
- Documented organizational mission and cybersecurity alignment statement
- Stakeholder register with cybersecurity interests and expectations
- Regulatory obligations matrix (GDPR, HIPAA, PCI-DSS, SOX, state laws, etc.)
- Critical business process inventory with IT dependencies
- Risk appetite and tolerance documentation approved by leadership
**Assessment Questions:**
1. How is the organizational mission reflected in cybersecurity investment decisions?
2. Which stakeholders have been identified as having cybersecurity interests?
3. Is there a comprehensive catalog of legal and regulatory cybersecurity obligations?
4. How frequently is the regulatory obligations register reviewed and updated?
5. Has risk appetite been formally defined and approved by executive leadership?
**Maturity Indicators:**
| Tier | Indicators |
|------|------------|
| 1 — Partial | Mission exists but no cybersecurity alignment; regulations addressed reactively |
| 2 — Risk Informed | Documented mission alignment; partial regulatory catalog; informal stakeholder awareness |
| 3 — Repeatable | Formal stakeholder mapping; complete regulatory register updated quarterly; risk appetite defined |
| 4 — Adaptive | Dynamic risk appetite; continuous regulatory monitoring; real-time stakeholder engagement |
---
### GV.RM — Risk Management Strategy
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| GV.RM-01 | Risk management objectives | Risk management objectives are established and agreed upon |
| GV.RM-02 | Risk appetite and tolerance | Risk appetite and risk tolerance statements are established and communicated |
| GV.RM-03 | Risk management activities | Activities and outcomes tied to risk appetite/tolerance are determined |
| GV.RM-04 | Strategic direction | Strategic direction describing risk response options is established |
| GV.RM-05 | Lines of communication | Lines of communication for cybersecurity risk management are established |
| GV.RM-06 | Standardized method | A standardized method for calculating, documenting, categorizing risk is established |
| GV.RM-07 | Opportunities | Strategic opportunities (positive risks) are characterized and communicated |
**Evidence Requirements:**
- Cybersecurity risk management strategy document
- Risk appetite statement with quantitative thresholds
- Risk tolerance levels per business unit and asset class
- Risk register with treatment decisions
- Board meeting minutes showing risk posture discussions
- Integration evidence with enterprise risk management
**Assessment Questions:**
1. Is there a formal cybersecurity risk management strategy approved by leadership?
2. Are risk appetite and tolerance quantitatively defined?
3. How is cybersecurity risk integrated with enterprise risk management?
4. How frequently is the risk strategy reviewed and updated?
5. Do investment decisions reference the risk management strategy?
---
### GV.RR — Roles, Responsibilities, and Authorities
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| GV.RR-01 | Leadership accountability | Organizational leadership is responsible and accountable for cybersecurity risk |
| GV.RR-02 | Established roles | Roles, responsibilities, and authorities are established and communicated |
| GV.RR-03 | Adequate resources | Adequate resources are allocated commensurate with cybersecurity risk strategy |
| GV.RR-04 | Cybersecurity in HR | Cybersecurity is included in human resources practices |
**Evidence Requirements:**
- CISO job description and organizational chart showing reporting line
- RACI matrix for cybersecurity functions
- Cybersecurity steering committee charter and meeting minutes
- Budget allocation documents showing cybersecurity investment
- HR policies including cybersecurity responsibilities
- Performance review templates with cybersecurity objectives
**Assessment Questions:**
1. To whom does the CISO report (CEO, CIO, board)?
2. Is there a cybersecurity steering committee with cross-functional representation?
3. Are cybersecurity responsibilities included in all relevant job descriptions?
4. Is cybersecurity performance tracked in executive reviews?
5. Are resources (budget, staff) aligned with identified risk levels?
---
### GV.PO — Policy
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| GV.PO-01 | Cybersecurity policy | A cybersecurity policy based on context and strategy is established |
| GV.PO-02 | Policy review | The cybersecurity policy is reviewed, updated, and communicated |
**Evidence Requirements:**
- Cybersecurity policy document(s) approved by leadership
- Policy hierarchy: Policy > Standards > Procedures > Guidelines
- Policy review schedule and revision history
- Policy distribution and acknowledgment records
- Policy exception management process and log
- Evidence of policy enforcement (disciplinary actions, technical controls)
**Assessment Questions:**
1. Does the cybersecurity policy framework cover all CSF functions?
2. When were policies last reviewed and updated?
3. How are policies communicated to all personnel and third parties?
4. Is there a formal exception management process?
5. How is policy compliance measured and enforced?
---
### GV.OV — Oversight
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| GV.OV-01 | Strategy evaluation | Cybersecurity risk management strategy is reviewed to assess effectiveness |
| GV.OV-02 | Adjusted strategy | The cybersecurity risk management strategy is revised as needed |
| GV.OV-03 | Performance evaluation | Organizational cybersecurity risk management performance is evaluated |
**Evidence Requirements:**
- Board reporting packages with cybersecurity metrics
- KPI/KRI dashboards and trend analysis
- Management review meeting minutes
- Program maturity assessment results
- Remediation tracking for identified deficiencies
- Budget vs actual cybersecurity spending analysis
**Assessment Questions:**
1. How frequently does the board receive cybersecurity risk reports?
2. What KPIs and KRIs are tracked for the cybersecurity program?
3. How are assessment findings tracked to resolution?
4. Is cybersecurity performance benchmarked against peers or standards?
5. How does performance data influence strategy adjustments?
---
### GV.SC — Cybersecurity Supply Chain Risk Management
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| GV.SC-01 | C-SCRM program | A cybersecurity supply chain risk management program is established |
| GV.SC-02 | Roles and processes | Cybersecurity roles and responsibilities for suppliers are established |
| GV.SC-03 | Integrated into risk management | Cybersecurity supply chain risk management is integrated into broader risk management |
| GV.SC-04 | Supplier prioritization | Suppliers are known and prioritized by criticality |
| GV.SC-05 | Contract requirements | Requirements for suppliers and partners include cybersecurity |
| GV.SC-06 | Planning and due diligence | Planning and due diligence are performed to reduce supply chain risks |
| GV.SC-07 | Post-engagement activities | Risks posed by a supplier, partner, or third party are understood and managed post-engagement |
| GV.SC-08 | Supplier monitoring | Relevant suppliers and partners are included in monitoring activities |
| GV.SC-09 | Supply chain practices | Supply chain security practices are integrated into cybersecurity operations |
| GV.SC-10 | Post-acquisition plans | Cybersecurity supply chain risk management plans include provisions for activities after an acquisition |
**Evidence Requirements:**
- C-SCRM policy and procedures
- Supplier tiering methodology and results
- Contracts with cybersecurity requirements (right-to-audit, breach notification, security standards)
- Supplier security assessments (questionnaires, SOC 2 reports, penetration test results)
- SBOM requirements and inventory for critical software
- Supplier incident notification procedures
- Supplier monitoring dashboards or reports
**Assessment Questions:**
1. Is there a formal supplier risk management program covering cybersecurity?
2. How are suppliers tiered by criticality and data access?
3. Do contracts include specific cybersecurity requirements?
4. How frequently are critical suppliers assessed?
5. Is there a process for managing security risks when supplier relationships end?
---
## 2. IDENTIFY (ID)
**Purpose:** Develop organizational understanding to manage cybersecurity risk to systems, assets, data, and capabilities.
### ID.AM — Asset Management
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| ID.AM-01 | Hardware inventories | Inventories of hardware managed by the organization are maintained |
| ID.AM-02 | Software inventories | Inventories of software, services, and systems are maintained |
| ID.AM-03 | Data mapping | Representations of authorized network communication and data flows are maintained |
| ID.AM-04 | External service inventory | Inventories of services provided by suppliers are maintained |
| ID.AM-05 | Assets are prioritized | Assets are prioritized based on classification, criticality, and business value |
| ID.AM-07 | Data classification | Inventories of data and corresponding metadata for designated data types are maintained |
| ID.AM-08 | System dependencies | Systems, hardware, software, services, and data are managed throughout their life cycles |
**Evidence Requirements:**
- Hardware asset inventory (CMDB) with owner, location, criticality
- Software inventory with version, license, end-of-life dates
- Network architecture diagrams with data flows
- Data inventory with classification labels
- Shadow IT discovery scan results
- Asset lifecycle management records
**Assessment Questions:**
1. Is there an automated asset discovery process?
2. How frequently is the asset inventory reconciled?
3. Are all assets classified by criticality and data sensitivity?
4. Are data flows mapped between systems and external parties?
5. Is shadow IT actively discovered and managed?
---
### ID.RA — Risk Assessment
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| ID.RA-01 | Vulnerabilities identified | Vulnerabilities in assets are identified, validated, and recorded |
| ID.RA-02 | Threat intelligence | Cyber threat intelligence is received from information sharing forums and sources |
| ID.RA-03 | Threats identified | Internal and external threats are identified and recorded |
| ID.RA-04 | Impacts identified | Potential impacts and likelihoods of threats exploiting vulnerabilities are identified |
| ID.RA-05 | Threats and vulnerabilities prioritized | Threats, vulnerabilities, likelihoods, and impacts are used to understand risk |
| ID.RA-06 | Risk responses | Risk responses are chosen, prioritized, planned, tracked, and communicated |
| ID.RA-07 | Changes and exceptions | Changes and exceptions are managed, assessed for risk impact |
| ID.RA-08 | Third-party assessment | Processes for receiving, analyzing, and responding to vulnerability disclosures |
| ID.RA-09 | Severity assessment | The authenticity and integrity of hardware and software are assessed prior to acquisition |
| ID.RA-10 | Critical supply chain assessment | Critical suppliers are assessed prior to acquisition |
**Evidence Requirements:**
- Vulnerability scan reports (internal and external)
- Threat intelligence subscription records and integration evidence
- Risk register with likelihood, impact, and treatment decisions
- Risk assessment methodology documentation
- Penetration test results
- Change management records with risk assessment
**Assessment Questions:**
1. What risk assessment methodology is used?
2. How are vulnerability scan results integrated into risk assessment?
3. What threat intelligence sources are consumed?
4. How frequently are risk assessments conducted for critical systems?
5. Is there a formal risk treatment decision process?
---
### ID.IM — Improvement
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| ID.IM-01 | Lessons learned | Improvements are identified from evaluations |
| ID.IM-02 | Improvement implementation | Improvements are identified from security tests, exercises, assessments |
| ID.IM-03 | Plans are implemented | Improvements identified from executing operational processes, procedures, and activities are implemented |
| ID.IM-04 | Communications plan | Incident response plans and other plans are established and improved |
**Evidence Requirements:**
- Post-incident review reports with improvement actions
- Exercise after-action reports
- Improvement action tracker with status
- Program maturity trend data
- Benchmarking results
---
## 3. PROTECT (PR)
**Purpose:** Implement appropriate safeguards to ensure delivery of critical services.
### PR.AA — Identity Management, Authentication, and Access Control
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| PR.AA-01 | Identity management | Identities and credentials for authorized users, services, and hardware are managed |
| PR.AA-02 | Identity proofing | Identities are proofed and bound to credentials based on context of interactions |
| PR.AA-03 | MFA | Users, services, and hardware are authenticated |
| PR.AA-04 | Identity assertions | Identity assertions are protected and verified |
| PR.AA-05 | Access permissions | Access permissions, entitlements, and authorizations are defined and managed |
| PR.AA-06 | Physical access | Physical access to assets is managed, monitored, and enforced |
**Evidence Requirements:**
- Identity governance platform configuration
- MFA enrollment statistics (percent of users with FIDO2, authenticator app, SMS)
- PAM solution configuration and session logs
- Access review records and recertification evidence
- Zero trust architecture documentation
- Physical access control system logs
---
### PR.AT — Awareness and Training
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| PR.AT-01 | Awareness | Personnel are provided awareness and training so they possess the knowledge and skills to perform tasks with cybersecurity risks in mind |
| PR.AT-02 | Privileged users | Individuals in specialized roles are provided with awareness and training |
**Evidence Requirements:**
- Training completion records
- Phishing simulation results and trend data
- Role-based training curriculum documentation
- Developer secure coding training completion
- Training effectiveness assessments
---
### PR.DS — Data Security
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| PR.DS-01 | Data at rest | The confidentiality, integrity, and availability of data-at-rest is protected |
| PR.DS-02 | Data in transit | The confidentiality, integrity, and availability of data-in-transit is protected |
| PR.DS-10 | Data in use | The confidentiality, integrity, and availability of data-in-use is protected |
| PR.DS-11 | Backups | Backups of data are created, protected, maintained, and tested |
**Evidence Requirements:**
- Encryption configurations for databases, file systems, backups
- TLS configurations for all data in transit
- DLP policy configurations and incident reports
- Data classification taxonomy and labeling rules
- Key management procedures and rotation evidence
- Backup integrity test results
---
### PR.PS — Platform Security
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| PR.PS-01 | Configuration management | The configuration of the platform is managed and documented |
| PR.PS-02 | Software maintenance | Software is maintained, replaced, and removed |
| PR.PS-03 | Hardware maintenance | Hardware is maintained, replaced, and removed |
| PR.PS-04 | Log management | Log records are generated and made available for monitoring |
| PR.PS-05 | Unauthorized installation | Installation and execution of unauthorized software is prevented |
| PR.PS-06 | Secure development | Secure software development practices are integrated |
**Evidence Requirements:**
- CIS Benchmark compliance scan results
- Patch management reports with SLA compliance
- Configuration management tool deployment evidence
- Golden image documentation and update process
- Application allowlisting configuration
- SDLC documentation with security gates
---
### PR.IR — Technology Infrastructure Resilience
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| PR.IR-01 | Redundancy | Networks and environments are protected for resilience |
| PR.IR-02 | Capacity | Technology assets are managed for availability |
| PR.IR-03 | Failover | Mechanisms exist to achieve resilience requirements in normal and adverse situations |
| PR.IR-04 | Recovery | Adequate resource capacity to ensure availability is maintained |
**Evidence Requirements:**
- Architecture diagrams showing redundancy
- RPO/RTO documentation per system tier
- Failover test results and metrics
- Capacity monitoring dashboards and alert configurations
- DR test results and lessons learned
- Backup restoration test records
---
## 4. DETECT (DE)
**Purpose:** Identify the occurrence of cybersecurity events in a timely manner.
### DE.CM — Continuous Monitoring
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| DE.CM-01 | Network monitoring | Networks and network services are monitored to find potentially adverse events |
| DE.CM-02 | Physical monitoring | The physical environment is monitored for adverse events |
| DE.CM-03 | Personnel activity | Personnel activity and technology usage are monitored |
| DE.CM-06 | External provider monitoring | External service provider activities and services are monitored |
| DE.CM-09 | Hardware and software | Computing hardware and software, runtime environments, and their data are monitored |
**Evidence Requirements:**
- SIEM deployment scope and log source inventory
- IDS/IPS deployment and tuning records
- EDR/XDR deployment coverage statistics
- Network monitoring tool configurations
- SOC operational documentation (playbooks, escalation procedures)
- UEBA deployment and baseline documentation
---
### DE.AE — Adverse Event Analysis
**Subcategories:**
| ID | Subcategory | Description |
|---|---|---|
| DE.AE-02 | Event analysis | Potentially adverse events are analyzed to better understand associated activities |
| DE.AE-03 | Event correlation | Events are correlated from multiple sources and sensors |
| DE.AE-04 | Impact estimation | The estimated impact and scope of adverse events is understood |
| DE.AE-06 | Information on events | Information on adverse events is provided to authorized staff and tools |
| DE.AE-07 | Threat intelligence integration | Cyber threat intelligence and other contextual information are integrated into analysis |
| DE.AE-08 | Declared incidents | Incidents are declared when adverse events meet the defined incident criteria |
**Evidence Requirements:**
- MITRE ATT&CK detection coverage matrix
- Threat hunting reports and outcomes
- SOAR playbook documentation
- Detection efficacy metrics (true positive rate, MTTD)
- Alert triage SOP
- Correlation rule documentation
---
## 5. RESPOND (RS)
**Purpose:** Take action regarding detected cybersecurity incidents to contain impact.
### RS.MA — Incident Management
**Evidence Requirements:**
- Incident response plan (annually tested)
- Incident classification and severity matrix
- Escalation procedures and contact lists
- Tabletop exercise and simulation reports
- On-call rotation schedules
- Incident management tool configuration
### RS.AN — Incident Analysis
**Evidence Requirements:**
- Forensic toolkit inventory and maintenance records
- Evidence handling and chain of custody procedures
- Root cause analysis reports
- Forensic analyst training certifications
- External forensic retainer agreements
### RS.CO — Incident Response Reporting and Communication
**Evidence Requirements:**
- Communication plan templates (internal, regulatory, public, affected parties)
- Regulatory notification timeline reference
- Legal counsel review of notification templates
- Communication log from past incidents
- Media spokesperson designation
### RS.MI — Incident Mitigation
**Evidence Requirements:**
- Containment playbooks per incident type (ransomware, breach, insider, DDoS)
- Containment action documentation
- Eradication verification procedures
- Post-containment monitoring procedures
- Recovery initiation criteria
---
## 6. RECOVER (RC)
**Purpose:** Maintain plans for resilience and restore capabilities impaired during cybersecurity incidents.
### RC.RP — Incident Recovery Plan Execution
**Evidence Requirements:**
- Recovery prioritization matrix by system tier
- Backup verification and restore test results
- Golden image library for system rebuild
- Post-recovery validation checklists
- Business owner sign-off procedures
### RC.CO — Incident Recovery Communication
**Evidence Requirements:**
- Recovery status communication templates
- Customer FAQ templates for significant incidents
- Post-incident summary report template
- Stakeholder communication logs from past recoveries
- Corrective action communication records
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |