AGENT SKILL

performing-nist-csf-maturity-assessment

Conduct a NIST Cybersecurity Framework (CSF) 2.0 maturity assessment across the six core Functions (Govern, Identify, Protect, Detect, Respond, Recover), scoring organizational posture against the four Implementation Tiers (Partial, Risk-Informed, Repeatable, Adaptive) and producing an improvement roadmap. Use when benchmarking an organization's cybersecurity program maturity or preparing a CSF-based gap analysis and remediation plan.

适用职业产品经理
License 许可
Apache-2.0
最近更新
2026-08-31
Stars
★ 3.6w
Forks
4.4k

01 前言 Front Matter

name
performing-nist-csf-maturity-assessment
tags
[ "compliance", "governance", "nist", "csf", "maturity-assessment", "risk-management" ]
author
mahipal
domain
cybersecurity
license
Apache-2.0
version
1.0
nist_csf
[ "GV.OC-01", "GV.RM-01", "GV.PO-01", "ID.RA-01", "GV.OV-01" ]
subdomain
compliance-governance
description
Conduct a NIST Cybersecurity Framework (CSF) 2.0 maturity assessment across the six core Functions (Govern, Identify, Protect, Detect, Respond, Recover), scoring organizational posture against the four Implementation Tiers (Partial, Risk-Informed, Repeatable, Adaptive) and producing an improvement roadmap. Use when benchmarking an organization's cybersecurity program maturity or preparing a CSF-based gap analysis and remediation plan.
mitre_attack
[ "T1078", "T1530", "T1685.002" ]

02 资源文件 7

03 SKILL.md 正文

Performing NIST CSF Maturity Assessment

Overview

The NIST Cybersecurity Framework (CSF) 2.0, released in February 2024, provides a comprehensive taxonomy for managing cybersecurity risk through six core Functions: Govern, Identify, Protect, Detect, Respond, and Recover. This skill covers conducting a maturity assessment against the CSF, using the four Implementation Tiers (Partial, Risk-Informed, Repeatable, Adaptive) to measure organizational cybersecurity posture and create improvement roadmaps.

When to Use

  • When conducting security assessments that involve performing nist csf maturity assessment
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Understanding of cybersecurity risk management principles
  • Access to NIST CSF 2.0 documentation and reference tool
  • Knowledge of organizational IT/OT environment and security controls
  • Stakeholder access across business units for assessment interviews

Core Concepts

CSF 2.0 Functions (6 Functions, 22 Categories)

Function Code Categories Purpose
Govern GV 6 Establish and monitor cybersecurity risk management strategy
Identify ID 3 Determine current cybersecurity risk to the organization
Protect PR 5 Implement safeguards to prevent or reduce risk
Detect DE 2 Find and analyze possible cybersecurity attacks
Respond RS 4 Take action regarding detected cybersecurity incidents
Recover RC 2 Restore capabilities impaired by cybersecurity incidents

Govern Function (New in CSF 2.0)

  • GV.OC: Organizational Context
  • GV.RM: Risk Management Strategy
  • GV.RR: Roles, Responsibilities, and Authorities
  • GV.PO: Policy
  • GV.OV: Oversight
  • GV.SC: Cybersecurity Supply Chain Risk Management

Implementation Tiers

Tier Name Description
Tier 1 Partial Ad hoc, reactive; limited awareness of cybersecurity risk
Tier 2 Risk-Informed Risk-aware but not organization-wide; approved but may not be policy
Tier 3 Repeatable Formal policies; consistently implemented; regularly updated
Tier 4 Adaptive Continuous improvement; real-time risk response; lessons learned integrated

Workflow

Phase 1: Scoping and Preparation (Weeks 1-2)

  1. Define assessment scope (enterprise-wide vs. business unit)
  2. Identify stakeholders and schedule interviews
  3. Gather existing documentation (policies, procedures, architecture diagrams)
  4. Customize CSF Profile for organizational context
  5. Select assessment methodology (self-assessment, facilitated, third-party)

Phase 2: Current State Assessment (Weeks 3-6)

  1. Assess each CSF Category and Subcategory against Implementation Tiers
  2. For each subcategory, evaluate:
    • Policy/documentation maturity
    • Implementation completeness
    • Automation level
    • Measurement and metrics
    • Continuous improvement evidence
  3. Score using tier criteria (1-4 scale)
  4. Document evidence supporting each tier rating
  5. Identify strengths, gaps, and improvement areas

Phase 3: Target State Definition (Weeks 7-8)

  1. Define target tier for each Function based on:
    • Risk appetite and tolerance
    • Industry requirements and benchmarks
    • Regulatory obligations
    • Available resources and budget
  2. Create Target Profile documenting desired maturity state
  3. Validate target state with executive leadership

Phase 4: Gap Analysis and Roadmap (Weeks 9-12)

  1. Compare Current Profile to Target Profile
  2. Prioritize gaps based on risk reduction potential
  3. Develop improvement roadmap with:
    • Short-term quick wins (0-3 months)
    • Medium-term improvements (3-12 months)
    • Long-term strategic initiatives (12-24 months)
  4. Estimate resource requirements for each initiative
  5. Assign ownership and timelines

Phase 5: Implementation and Reassessment (Ongoing)

  1. Execute improvement roadmap initiatives
  2. Track progress against milestones
  3. Conduct periodic reassessments (annually recommended)
  4. Report maturity progress to leadership
  5. Adjust roadmap based on evolving threats and business changes

Key Artifacts

  • CSF Current Profile (by Function/Category/Subcategory)
  • CSF Target Profile
  • Gap Analysis Report
  • Maturity Assessment Scorecard
  • Improvement Roadmap with Priorities
  • Executive Summary and Dashboard

Common Pitfalls

  • Assessing technology only without evaluating governance and people
  • Setting unrealistic target tiers without resource commitment
  • Treating assessment as one-time rather than continuous process
  • Ignoring the new Govern function in CSF 2.0
  • Not aligning CSF assessment with existing compliance requirements (ISO 27001, SOC 2)

References

04 同仓库更多 Skills

mukul975
mukul975/Anthropic-Cybersecurity-Skills

verifying-build-provenance-with-slsa-sigstore

Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI/CD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.

Skill与智能体开发
★ 3.6w
mukul975
mukul975/Anthropic-Cybersecurity-Skills

validating-tpm-measured-boot-attestation

Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote/tpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware/kernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.

Skill与智能体开发
★ 3.6w
mukul975
mukul975/Anthropic-Cybersecurity-Skills

validating-backup-integrity-for-recovery

Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable/air-gapped backups for silent corruption or tampering.

测试与质量Skill与智能体开发
★ 3.6w
mukul975
mukul975/Anthropic-Cybersecurity-Skills

triaging-windows-with-kape

Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment/triage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.

Skill与智能体开发
★ 3.6w
mukul975
mukul975/Anthropic-Cybersecurity-Skills

triaging-vulnerabilities-with-ssvc-framework

Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track/Track*/Attend/Act decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.

Skill与智能体开发
★ 3.6w
mukul975
mukul975/Anthropic-Cybersecurity-Skills

triaging-security-incident

Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM/EDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.

Skill与智能体开发
★ 3.6w