cm/controlmapping
Deutsch
Quellen
Framework

NIST Cybersecurity Framework 2.0

Worum es geht

Das freiwillige Framework des NIST mit Cybersicherheits-Ergebnissen, veröffentlicht im Februar 2024. Es umfasst sechs Funktionen (Govern, Identify, Protect, Detect, Respond, Recover), 22 Kategorien und 106 Unterkategorien. Es legt fest, was erreicht werden soll, nicht wie: Organisationen beschreiben ihren Ist-Zustand und ihren Soll-Zustand als Current und Target Profiles.

Für wen es relevant ist

Jede Organisation, unabhängig von Größe oder Branche. US-Bundesbehörden setzen es zusammen mit dem NIST Risk Management Framework ein, viele Aufsichtsbehörden und Versicherer verweisen darauf, und Geschäftsleitungen nutzen es, um die Sicherheitsberichterstattung zu strukturieren.

So wird geprüft

Es gibt keine offizielle CSF-Zertifizierung oder -Prüfung. Organisationen bewerten ihre Profile selbst oder beauftragen eine unabhängige Bewertung; Behauptungen, „CSF-zertifiziert“ zu sein, stammen nicht vom NIST.

106
Unterkategorien
89
Einem anderen Framework zugeordnet
100%
Abgedeckte Themen (50/50)

Vergleiche

Anforderungen

Anforderungs-IDs und Titel werden so angezeigt, wie jedes Framework sie veröffentlicht, auf Englisch.

NIST Cybersecurity Framework 2.0 Anforderungen
IDAnforderungThemenZugeordnet in
Detect (DE) · 11
DE.AE-02Potentially adverse events are analyzed to better understand associated activitiesAngriffserkennung, Anomalieerkennung10 von 13
DE.AE-03Information is correlated from multiple sourcesProtokollierung & Audit, SIEM / SOC10 von 13
DE.AE-04The estimated impact and scope of adverse events are understoodAnomalieerkennung9 von 13
DE.AE-06Information on adverse events is provided to authorized staff and toolsSIEM / SOC10 von 13
DE.AE-07Cyber threat intelligence and other contextual information are integrated into the analysisThreat Intelligence6 von 13
DE.AE-08Incidents are declared when adverse events meet the defined incident criteriaSIEM / SOC10 von 13
DE.CM-01Networks and network services are monitored to find potentially adverse eventsDNS-Sicherheit, WAF, Kont. Überwachung, Angriffserkennung11 von 13
DE.CM-02The physical environment is monitored to find potentially adverse eventsPhysische Sicherheit8 von 13
DE.CM-03Personnel activity and technology usage are monitored to find potentially adverse eventsKont. Überwachung, Insider-Bedrohungen11 von 13
DE.CM-06External service provider activities and services are monitored to find potentially adverse eventsLieferantenrisikomanagement10 von 13
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse eventsEndpoint-Schutz, E-Mail-Sicherheit, Kont. Überwachung, Anomalieerkennung11 von 13
Govern (GV) · 31
GV.OC-01The organizational mission is understood and informs cybersecurity risk managementGeschäftsumfeld5 von 13
GV.OC-02Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered—0
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managedCompliance10 von 13
GV.OC-04Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicatedGeschäftsumfeld, Business Continuity8 von 13
GV.OC-05Outcomes, capabilities, and services that the organization depends on are understood and communicatedGeschäftsumfeld5 von 13
GV.OV-01Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction—0
GV.OV-02The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks—0
GV.OV-03Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments neededCompliance10 von 13
GV.PO-01Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforcedGovernance-Richtlinie9 von 13
GV.PO-02Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational missionGovernance-Richtlinie9 von 13
GV.RM-01Risk management objectives are established and agreed to by organizational stakeholdersRisikomanagement10 von 13
GV.RM-02Risk appetite and risk tolerance statements are established, communicated, and maintainedRisikomanagement10 von 13
GV.RM-03Cybersecurity risk management activities and outcomes are included in enterprise risk management processesRisikomanagement10 von 13
GV.RM-04Strategic direction that describes appropriate risk response options is established and communicated—0
GV.RM-05Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties—0
GV.RM-06A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicatedRisikomanagement10 von 13
GV.RM-07Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions—0
GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improvingRollen und Verantwortlichkeiten9 von 13
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforcedRollen und Verantwortlichkeiten9 von 13
GV.RR-03Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policiesRollen und Verantwortlichkeiten9 von 13
GV.RR-04Cybersecurity is included in human resources practicesInsider-Bedrohungen8 von 13
GV.SC-01A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholdersLieferkettenrisiko9 von 13
GV.SC-02Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally—0
GV.SC-03Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processesLieferkettenrisiko9 von 13
GV.SC-04Suppliers are known and prioritized by criticalityLieferantenrisikomanagement10 von 13
GV.SC-05Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third partiesLieferkettenrisiko9 von 13
GV.SC-06Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationshipsLieferantenrisikomanagement10 von 13
GV.SC-07The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationshipLieferantenrisikomanagement10 von 13
GV.SC-08Relevant suppliers and other third parties are included in incident planning, response, and recovery activities—0
GV.SC-09Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycleLieferkettenrisiko9 von 13
GV.SC-10Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement—0
Identify (ID) · 21
ID.AM-01Inventories of hardware managed by the organization are maintainedAsset-Management13 von 13
ID.AM-02Inventories of software, services, and systems managed by the organization are maintainedAsset-Management13 von 13
ID.AM-03Representations of the organization's authorized network communication and internal and external network data flows are maintainedFirewall / Netzsegmentierung9 von 13
ID.AM-04Inventories of services provided by suppliers are maintainedAsset-Management, Cloud-Sicherheit13 von 13
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on the missionDatenklassifizierung9 von 13
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintainedDatenklassifizierung9 von 13
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cyclesAsset-Management13 von 13
ID.IM-01Improvements are identified from evaluations—0
ID.IM-02Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties—0
ID.IM-03Improvements are identified from execution of operational processes, procedures, and activitiesErkenntnisse aus Vorfällen9 von 13
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improvedIncident Response, Wiederherstellungsplanung12 von 13
ID.RA-01Vulnerabilities in assets are identified, validated, and recordedSchwachstellenmanagement13 von 13
ID.RA-02Cyber threat intelligence is received from information sharing forums and sourcesThreat Intelligence6 von 13
ID.RA-03Internal and external threats to the organization are identified and recordedRisikobewertung, Threat Intelligence10 von 13
ID.RA-04Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recordedRisikobewertung10 von 13
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritizationRisikobewertung10 von 13
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicatedRisikobewertung10 von 13
ID.RA-07Changes and exceptions are managed, assessed for risk impact, recorded, and tracked—0
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are establishedSchwachstellenmanagement13 von 13
ID.RA-09The authenticity and integrity of hardware and software are assessed prior to acquisition and useLieferkettenrisiko9 von 13
ID.RA-10Critical suppliers are assessed prior to acquisitionLieferantenrisikomanagement10 von 13
Protect (PR) · 22
PR.AA-01Identities and credentials for authorized users, services, and hardware are managed by the organizationZugriffskontrolle11 von 13
PR.AA-02Identities are proofed and bound to credentials based on the context of interactions—0
PR.AA-03Users, services, and hardware are authenticatedMulti-Faktor-Authentifizierung, Zero Trust, API-Sicherheit10 von 13
PR.AA-04Identity assertions are protected, conveyed, and verifiedZero Trust7 von 13
PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of dutiesZugriffskontrolle, Privilegierter Zugriff, Zero Trust, Mobile Security12 von 13
PR.AA-06Physical access to assets is managed, monitored, and enforced commensurate with riskPhysische Sicherheit8 von 13
PR.AT-01Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mindAwareness & Training10 von 13
PR.AT-02Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mindAwareness & Training10 von 13
PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protectedVerschlüsselung, Datenschutz, DLP11 von 13
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protectedVerschlüsselung, Datenschutz, E-Mail-Sicherheit, DLP12 von 13
PR.DS-10The confidentiality, integrity, and availability of data-in-use are protectedDatenschutz, DLP11 von 13
PR.DS-11Backups of data are created, protected, maintained, and testedBackup & Recovery11 von 13
PR.IR-01Networks and environments are protected from unauthorized logical access and usageFirewall / Netzsegmentierung, Webanwendungssicherheit, Zero Trust, Cloud-Sicherheit, DNS-Sicherheit, WAF, API-Sicherheit11 von 13
PR.IR-02The organization's technology assets are protected from environmental threatsPhysische Sicherheit8 von 13
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situationsBusiness Continuity, Disaster Recovery10 von 13
PR.IR-04Adequate resource capacity to ensure availability is maintained—0
PR.PS-01Configuration management practices are established and appliedSichere Konfiguration, Mobile Security, Cloud-Sicherheit12 von 13
PR.PS-02Software is maintained, replaced, and removed commensurate with riskPatch-Management10 von 13
PR.PS-03Hardware is maintained, replaced, and removed commensurate with risk—0
PR.PS-04Log records are generated and made available for continuous monitoringProtokollierung & Audit10 von 13
PR.PS-05Installation and execution of unauthorized software are preventedEndpoint-Schutz10 von 13
PR.PS-06Secure software development practices are integrated, and their performance is monitored throughout the software development life cycleSichere Entwicklung, Webanwendungssicherheit, API-Sicherheit8 von 13
Recover (RC) · 8
RC.CO-03Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholdersKommunikation & Wiederherstellung8 von 13
RC.CO-04Public updates on incident recovery are shared using approved methods and messagingKommunikation & Wiederherstellung8 von 13
RC.RP-01The recovery portion of the incident response plan is executed once initiated from the incident response processWiederherstellungsplanung9 von 13
RC.RP-02Recovery actions are selected, scoped, prioritized, and performedWiederherstellungsplanung, Disaster Recovery10 von 13
RC.RP-03The integrity of backups and other restoration assets is verified before using them for restorationBackup & Recovery11 von 13
RC.RP-04Critical mission functions and cybersecurity risk management are considered to establish post-incident operational normsBusiness Continuity8 von 13
RC.RP-05The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmedKommunikation & Wiederherstellung, Disaster Recovery11 von 13
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related documentation is completedErkenntnisse aus Vorfällen9 von 13
Respond (RS) · 13
RS.AN-03Analysis is performed to establish what has taken place during an incident and the root cause of the incidentForensik7 von 13
RS.AN-06Actions performed during an investigation are recorded, and the records' integrity and provenance are preservedForensik7 von 13
RS.AN-07Incident data and metadata are collected, and their integrity and provenance are preservedForensik7 von 13
RS.AN-08An incident's magnitude is estimated and validated—0
RS.CO-02Internal and external stakeholders are notified of incidentsMeldung12 von 13
RS.CO-03Information is shared with designated internal and external stakeholdersKommunikation8 von 13
RS.MA-01The incident response plan is executed in coordination with relevant third parties once an incident is declaredIncident Response12 von 13
RS.MA-02Incident reports are triaged and validatedIncident Response12 von 13
RS.MA-03Incidents are categorized and prioritizedIncident Response12 von 13
RS.MA-04Incidents are escalated or elevated as neededIncident Response12 von 13
RS.MA-05The criteria for initiating incident recovery are applied—0
RS.MI-01Incidents are containedMitigation8 von 13
RS.MI-02Incidents are eradicatedMitigation8 von 13

Themenabdeckung

Themen mit zugeordneten NIST CSF 2.0-Anforderungen (50):