cm/controlmapping
Español
Fuentes
Marco

NIST Cybersecurity Framework 2.0

Qué es

Marco voluntario del NIST de resultados de ciberseguridad, publicado en febrero de 2024. Consta de seis funciones (Gobernar, Identificar, Proteger, Detectar, Responder y Recuperar), 22 categorías y 106 subcategorías. Define qué lograr, no cómo: las organizaciones describen su situación actual y adónde quieren llegar mediante perfiles actuales y perfiles objetivo.

Quién lo necesita

Cualquier organización, de cualquier tamaño o sector. Las agencias federales de EE. UU. lo utilizan junto con el Marco de Gestión de Riesgos del NIST, muchos reguladores y aseguradoras lo citan como referencia, y los consejos de administración lo emplean para estructurar los informes de seguridad.

Cómo se evalúa

No existe una certificación ni una auditoría oficial del CSF. Las organizaciones autoevalúan sus perfiles o encargan una evaluación independiente; las afirmaciones de estar "certificado en CSF" no proceden del NIST.

106
Subcategorías
89
Con correspondencia con otro marco
100%
Temas cubiertos (50/50)

Comparativas

Requisitos

Los identificadores y títulos de los requisitos se muestran tal como los publica cada marco, en inglés.

NIST Cybersecurity Framework 2.0 requisitos
IDRequisitoTemasCon correspondencia en
Detect (DE) · 11
DE.AE-02Potentially adverse events are analyzed to better understand associated activitiesDetección de intrusiones, Detección de anomalías10 de 13
DE.AE-03Information is correlated from multiple sourcesRegistro y auditoría, SIEM / SOC10 de 13
DE.AE-04The estimated impact and scope of adverse events are understoodDetección de anomalías9 de 13
DE.AE-06Information on adverse events is provided to authorized staff and toolsSIEM / SOC10 de 13
DE.AE-07Cyber threat intelligence and other contextual information are integrated into the analysisInteligencia de amenazas6 de 13
DE.AE-08Incidents are declared when adverse events meet the defined incident criteriaSIEM / SOC10 de 13
DE.CM-01Networks and network services are monitored to find potentially adverse eventsSeguridad DNS, WAF, Monitoreo cont., Detección de intrusiones11 de 13
DE.CM-02The physical environment is monitored to find potentially adverse eventsSeguridad física8 de 13
DE.CM-03Personnel activity and technology usage are monitored to find potentially adverse eventsMonitoreo cont., Amenaza interna11 de 13
DE.CM-06External service provider activities and services are monitored to find potentially adverse eventsGestión de riesgos de proveedores10 de 13
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse eventsProtección de endpoints, Seguridad del correo electrónico, Monitoreo cont., Detección de anomalías11 de 13
Govern (GV) · 31
GV.OC-01The organizational mission is understood and informs cybersecurity risk managementEntorno empresarial5 de 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 managedCumplimiento10 de 13
GV.OC-04Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicatedEntorno empresarial, Continuidad del negocio8 de 13
GV.OC-05Outcomes, capabilities, and services that the organization depends on are understood and communicatedEntorno empresarial5 de 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 neededCumplimiento10 de 13
GV.PO-01Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforcedPolítica de gobernanza9 de 13
GV.PO-02Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational missionPolítica de gobernanza9 de 13
GV.RM-01Risk management objectives are established and agreed to by organizational stakeholdersGestión de riesgos10 de 13
GV.RM-02Risk appetite and risk tolerance statements are established, communicated, and maintainedGestión de riesgos10 de 13
GV.RM-03Cybersecurity risk management activities and outcomes are included in enterprise risk management processesGestión de riesgos10 de 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 communicatedGestión de riesgos10 de 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 improvingFunciones y responsabilidades9 de 13
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforcedFunciones y responsabilidades9 de 13
GV.RR-03Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policiesFunciones y responsabilidades9 de 13
GV.RR-04Cybersecurity is included in human resources practicesAmenaza interna8 de 13
GV.SC-01A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholdersRiesgo de la cadena de suministro9 de 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 processesRiesgo de la cadena de suministro9 de 13
GV.SC-04Suppliers are known and prioritized by criticalityGestión de riesgos de proveedores10 de 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 partiesRiesgo de la cadena de suministro9 de 13
GV.SC-06Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationshipsGestión de riesgos de proveedores10 de 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 relationshipGestión de riesgos de proveedores10 de 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 cycleRiesgo de la cadena de suministro9 de 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 maintainedGestión de activos13 de 13
ID.AM-02Inventories of software, services, and systems managed by the organization are maintainedGestión de activos13 de 13
ID.AM-03Representations of the organization's authorized network communication and internal and external network data flows are maintainedCortafuegos / Segmentación de red9 de 13
ID.AM-04Inventories of services provided by suppliers are maintainedGestión de activos, Seguridad en la nube13 de 13
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on the missionClasificación de datos9 de 13
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintainedClasificación de datos9 de 13
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cyclesGestión de activos13 de 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 activitiesLecciones aprendidas9 de 13
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improvedRespuesta a incidentes, Planificación de la recuperación12 de 13
ID.RA-01Vulnerabilities in assets are identified, validated, and recordedGestión de vulnerabilidades13 de 13
ID.RA-02Cyber threat intelligence is received from information sharing forums and sourcesInteligencia de amenazas6 de 13
ID.RA-03Internal and external threats to the organization are identified and recordedEvaluación de riesgos, Inteligencia de amenazas10 de 13
ID.RA-04Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recordedEvaluación de riesgos10 de 13
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritizationEvaluación de riesgos10 de 13
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicatedEvaluación de riesgos10 de 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 establishedGestión de vulnerabilidades13 de 13
ID.RA-09The authenticity and integrity of hardware and software are assessed prior to acquisition and useRiesgo de la cadena de suministro9 de 13
ID.RA-10Critical suppliers are assessed prior to acquisitionGestión de riesgos de proveedores10 de 13
Protect (PR) · 22
PR.AA-01Identities and credentials for authorized users, services, and hardware are managed by the organizationControl de acceso11 de 13
PR.AA-02Identities are proofed and bound to credentials based on the context of interactions—0
PR.AA-03Users, services, and hardware are authenticatedAutenticación multifactor, Confianza cero, Seguridad de APIs10 de 13
PR.AA-04Identity assertions are protected, conveyed, and verifiedConfianza cero7 de 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 dutiesControl de acceso, Acceso privilegiado, Confianza cero, Seguridad móvil12 de 13
PR.AA-06Physical access to assets is managed, monitored, and enforced commensurate with riskSeguridad física8 de 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 mindConcienciación y formación10 de 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 mindConcienciación y formación10 de 13
PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protectedCifrado, Protección de datos, DLP11 de 13
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protectedCifrado, Protección de datos, Seguridad del correo electrónico, DLP12 de 13
PR.DS-10The confidentiality, integrity, and availability of data-in-use are protectedProtección de datos, DLP11 de 13
PR.DS-11Backups of data are created, protected, maintained, and testedCopias de seguridad y recuperación11 de 13
PR.IR-01Networks and environments are protected from unauthorized logical access and usageCortafuegos / Segmentación de red, Seguridad web, Confianza cero, Seguridad en la nube, Seguridad DNS, WAF, Seguridad de APIs11 de 13
PR.IR-02The organization's technology assets are protected from environmental threatsSeguridad física8 de 13
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situationsContinuidad del negocio, Recuperación ante desastres10 de 13
PR.IR-04Adequate resource capacity to ensure availability is maintained—0
PR.PS-01Configuration management practices are established and appliedConfiguración segura, Seguridad móvil, Seguridad en la nube12 de 13
PR.PS-02Software is maintained, replaced, and removed commensurate with riskGestión de parches10 de 13
PR.PS-03Hardware is maintained, replaced, and removed commensurate with risk—0
PR.PS-04Log records are generated and made available for continuous monitoringRegistro y auditoría10 de 13
PR.PS-05Installation and execution of unauthorized software are preventedProtección de endpoints10 de 13
PR.PS-06Secure software development practices are integrated, and their performance is monitored throughout the software development life cycleDesarrollo seguro, Seguridad web, Seguridad de APIs8 de 13
Recover (RC) · 8
RC.CO-03Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholdersComunicaciones y restauración8 de 13
RC.CO-04Public updates on incident recovery are shared using approved methods and messagingComunicaciones y restauración8 de 13
RC.RP-01The recovery portion of the incident response plan is executed once initiated from the incident response processPlanificación de la recuperación9 de 13
RC.RP-02Recovery actions are selected, scoped, prioritized, and performedPlanificación de la recuperación, Recuperación ante desastres10 de 13
RC.RP-03The integrity of backups and other restoration assets is verified before using them for restorationCopias de seguridad y recuperación11 de 13
RC.RP-04Critical mission functions and cybersecurity risk management are considered to establish post-incident operational normsContinuidad del negocio8 de 13
RC.RP-05The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmedComunicaciones y restauración, Recuperación ante desastres11 de 13
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related documentation is completedLecciones aprendidas9 de 13
Respond (RS) · 13
RS.AN-03Analysis is performed to establish what has taken place during an incident and the root cause of the incidentAnálisis forense7 de 13
RS.AN-06Actions performed during an investigation are recorded, and the records' integrity and provenance are preservedAnálisis forense7 de 13
RS.AN-07Incident data and metadata are collected, and their integrity and provenance are preservedAnálisis forense7 de 13
RS.AN-08An incident's magnitude is estimated and validated—0
RS.CO-02Internal and external stakeholders are notified of incidentsNotificación12 de 13
RS.CO-03Information is shared with designated internal and external stakeholdersComunicación8 de 13
RS.MA-01The incident response plan is executed in coordination with relevant third parties once an incident is declaredRespuesta a incidentes12 de 13
RS.MA-02Incident reports are triaged and validatedRespuesta a incidentes12 de 13
RS.MA-03Incidents are categorized and prioritizedRespuesta a incidentes12 de 13
RS.MA-04Incidents are escalated or elevated as neededRespuesta a incidentes12 de 13
RS.MA-05The criteria for initiating incident recovery are applied—0
RS.MI-01Incidents are containedMitigación8 de 13
RS.MI-02Incidents are eradicatedMitigación8 de 13

Cobertura del tema

Temas con requisitos de NIST CSF 2.0 asignados (50):