+Separation of Duties (SoD)
|
Separation of Duties (SoD)
Description
Mechanisms exist to implement and maintain Separation of Duties (SoD) to prevent potential inappropriate activity without collusion.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Documented / assigned Separation of Duties (SoD)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Documented / assigned Separation of Duties (SoD)
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Documented / assigned Separation of Duties (SoD)
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Documented / assigned Separation of Duties (SoD)
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Documented / assigned Separation of Duties (SoD)
SCR-CMM
Level 0 Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 Performed Informally
Human Resources Security (HRS) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with HRS domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Personnel management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ The Human Resources (HR) department provides guidance on secure HR practices for hiring, retaining and terminating employees, contractors and other personnel that work on behalf of the organization.
Level 2 Planned Tracked
Human Resources Security (HRS) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with HRS domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with HRS domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with HRS domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Personnel management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Personnel management is decentralized at a localized/regionalized function, where there are non-standardized methods to govern personnel matters across the organization. ▪ Localized HR practices are implemented for hiring, managing, training, investigating and terminating employees, contractors and other personnel that work on behalf of the organization. ▪ The HR department, in conjunction with IT and/or cybersecurity personnel, implements and maintains Separation of Duties (SoD) to prevent potential malevolent activity without collusion.
Level 3 Well Defined
Human Resources Security (HRS) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with HRS domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with HRS domain capabilities are well-documented and kept current by process owners. ▪ A Human Resources (HR) team, or similar function, is appropriately staffed and supported to implement and maintain HRS domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of human resources security operations (e.g., personnel management software solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with HRS domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to implement and maintain Separation of Duties (SoD) to prevent potential inappropriate activity without collusion.
Level 4 Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
1. Resumen
1.1 Referencias
1.2 Requisitos identificados
1.3 Regulaciones relacionadas
2. Requisitos identificados
Requisitos
| Fuente |
Requisito |
3. Regulaciones relacionadas
Regulaciones
| Fuente |
Regulación |
|
EULAW
|
Artículo 2 Elementos generales de las políticas, procedimientos, protocolos y herramientas en materia de seguridad de las TIC
-
|
|
EULAW
|
Artículo 17 Gestión de cambios en las TIC
-
|
|
EULAW
|
Artículo 21 Control de acceso
Artículo 21
Dentro de su control de los derechos de gestión de accesos, las entidades financieras elaborarán, documentarán y aplicarán una política que incluya todos los aspectos siguientes:
a)
la asignación de derechos de acceso a los activos de TIC sobre la base de los principios de «necesidad de conocer», «necesidad de uso» y «mínimo privilegio», también para el acceso a distancia y de emergencia;
b)
la separación de funciones con el fin de impedir el acceso injustificado a datos esenciales o la asignación de combinaciones de derechos de acceso que puedan utilizarse para eludir los controles;
c)
una disposición sobre responsabilidad de los usuarios que limite en la medida de lo posible el uso de cuentas de usuario genéricas y compartidas y garantice que, en todo momento, los usuarios sean identificables cuando realicen acciones en los sistemas de TIC;
d)
una disposición sobre las restricciones de acceso a los activos de TIC que establezca controles y herramientas para impedir el acceso no autorizado;
e)
procedimientos de gestión de cuentas para la concesión, modificación o revocación de derechos de acceso en relación con las cuentas de usuario y las cuentas genéricas, incluidas las cuentas de administrador genéricas, que incluyan disposiciones sobre todos los aspectos siguientes:
i)
asignación de funciones y responsabilidades para la concesión, revisión y revocación de los derechos de acceso,
ii)
asignación de acceso privilegiado, de emergencia y de administrador sobre la base del principio de «necesidad de uso» o con carácter ad hoc para todos los sistemas de TIC,
iii)
retirada de los derechos de acceso sin demora indebida al término de la relación laboral o cuando el acceso ya no sea necesario,
iv)
actualización de los derechos de acceso cuando se requiera introducir cambios y al menos una vez al año para todos los sistemas de TIC que no sustenten funciones esenciales o importantes y al menos cada seis meses para los sistemas de TIC que sustenten funciones esenciales o importantes;
f)
métodos de autenticación, incluidos todos los aspectos siguientes:
i)
el uso de métodos de autenticación que sean acordes con la clasificación establecida de conformidad con el artículo 8, apartado 1, del Reglamento (UE) 2022/2554 y con el perfil de riesgo general de los activos de TIC, y que tengan en cuenta las prácticas punteras,
ii)
el uso de métodos de autenticación sólidos de conformidad con las prácticas y técnicas punteras para el acceso a distancia a la red de la entidad financiera, el acceso privilegiado y el acceso a los activos de TIC que sustenten funciones esenciales o importantes o a los activos de TIC que sean de acceso público;
g)
medidas de control del acceso físico que incluyan lo siguiente:
i)
la identificación y el registro de las personas físicas autorizadas a acceder a los locales, los centros de datos y las zonas sensibles designadas determinadas por la entidad financiera en los que se encuentren los activos de TIC y de información,
ii)
la concesión de derechos de acceso físico a los activos de TIC esenciales únicamente a las personas autorizadas, de conformidad con los principios de «necesidad de conocer» y «mínimo privilegio» y con carácter ad hoc,
iii)
el seguimiento del acceso físico a los locales, los centros de datos y las zonas sensibles designadas determinadas por la entidad financiera en los que se encuentren los activos de TIC, los activos de información o ambos,
iv)
la revisión de los derechos de acceso físico para garantizar la rápida revocación de los derechos que no sean necesarios.
A efectos de la letra e), inciso i), las entidades financieras establecerán el período de conservación teniendo en cuenta los objetivos empresariales y de seguridad de la información, los motivos por los que se consigna el hecho de que se trate en los registros y los resultados de la evaluación del riesgo relacionado con las TIC.
A efectos de la letra e), inciso ii), las entidades financieras utilizarán, en la medida de lo posible, cuentas específicas para la realización de tareas administrativas en los sistemas de TIC. Cuando sea factible y adecuado, las entidades financieras implementarán soluciones automatizadas para la gestión del acceso privilegiado.
A efectos de la letra g), inciso i), la identificación y el registro serán acordes con la importancia de los locales, los centros de datos y las zonas sensibles designadas y con el carácter esencial de las operaciones que se realicen en ellos o los sistemas de TIC que se encuentren en ellos.
A efectos de la letra g), inciso iii), el seguimiento será acorde con la clasificación establecida de conformidad con el artículo 8, apartado 1, del Reglamento (UE) 2022/2554 y con el carácter esencial de la zona a la que se acceda.
|
|
EULAW
|
Artículo 28 Gobernanza y organización
-
|
Incidencias vinculadas
Vínculos
| Tipo de vínculo |
Incidencia |
|
is related to
|
Annual |
|
is related to
|
relative Control Weighting = 08 |
|
is related to
|
Process |
|
is related to
|
Protect |
|
is related to
|
SCRM Focus Tier 1 STRATEGIC |
|
is related to
|
SCRM Focus Tier 2 OPERATIONAL |
|
blocks
|
Excessive or Unauthorized Privilege |
|
blocks
|
Unauthorized Access |
|
blocks
|
Loss, Theft or Damage of Assets |
|
blocks
|
Unauthorized Modification / Loss of System Integrity |
|
blocks
|
Unauthorized Retention / Inability to Dispose of Data |
|
blocks
|
Business / Service Interruption |
|
blocks
|
Data Loss / Integrity Compromise |
|
blocks
|
Reduced Operational Productivity |
|
blocks
|
System / Data Compromise (Technical Vector) |
|
blocks
|
System / Data Compromise (Non-Technical Vector) |
|
blocks
|
Revenue Loss |
|
blocks
|
Contractual Default / Termination |
|
blocks
|
Loss of Competitive Advantage |
|
blocks
|
Reputational Harm / Loss of Stakeholder Trust |
|
blocks
|
Regulatory / Legal / Contractual Financial Liability |
|
blocks
|
Exposure from Unaddressed Vulnerabilities |
|
blocks
|
System / Service Compromise |
|
blocks
|
Failure to Support Business / Mission Objectives |
|
blocks
|
Unaddressed Security / Compliance Exposure |
|
blocks
|
Unperformed / Unowned Control Responsibilities |
|
blocks
|
Uncontrolled Internal Security / Privacy Exposure |
|
blocks
|
Uncontrolled Third-Party Security / Privacy Exposure |
|
blocks
|
Lack of oversight of internal controls |
|
blocks
|
Lack of oversight of third-party controls |
|
blocks
|
Harm from Illegal, Abusive or Unsafe Content / Conduct |
|
blocks
|
Loss of Investigative / Evidentiary Capability |
|
blocks
|
Delayed Containment / Increased Incident Impact |
|
blocks
|
Incident Persistence / Recurrence |
|
blocks
|
Incident Response / Recovery Cost |
|
blocks
|
Lack of a security-minded workforce |
|
blocks
|
Third-Party Cybersecurity Compromise / Exposure |
|
blocks
|
Third-Party Physical Security Disruption / Exposure |
|
blocks
|
Sub-Tier / Fourth-Party Supply Chain Exposure |
|
blocks
|
Third-Party Legal / Compliance Exposure |
|
blocks
|
Harm from Unauthorized / Unintended Product or Service Use |
|
blocks
|
Third-Party Dependency Failure |
|
is related to
|
relative Control Weighting = 07 |
|
is related to
|
People |
|
is related to
|
SCRM Focus Tier 3 TACTICAL |
|
blocks
|
OS Credential Dumping |
|
blocks
|
LSASS Memory |
|
blocks
|
Security Account Manager |
|
blocks
|
NTDS |
|
blocks
|
LSA Secrets |
|
blocks
|
Cached Domain Credentials |
|
blocks
|
DCSync |
|
blocks
|
Proc Filesystem |
|
blocks
|
/etc/passwd and /etc/shadow |
|
blocks
|
Remote Services |
|
blocks
|
Remote Desktop Protocol |
|
blocks
|
SMB/Windows Admin Shares |
|
blocks
|
Distributed Component Object Model |
|
blocks
|
SSH |
|
blocks
|
Windows Remote Management |
|
blocks
|
Cloud Services |
|
blocks
|
Windows Management Instrumentation |
|
blocks
|
Scheduled Task/Job |
|
blocks
|
At |
|
blocks
|
Cron |
|
blocks
|
Scheduled Task |
|
blocks
|
Systemd Timers |
|
blocks
|
Container Orchestration Job |
|
blocks
|
Process Injection |
|
blocks
|
Ptrace System Calls |
|
blocks
|
Web Portal Capture |
|
blocks
|
Command and Scripting Interpreter |
|
blocks
|
PowerShell |
|
blocks
|
Network Device CLI |
|
blocks
|
Indicator Removal |
|
blocks
|
Clear Command History |
|
blocks
|
Clear Network Connection History and Configurations |
|
blocks
|
Clear Mailbox Data |
|
blocks
|
Clear Persistence |
|
blocks
|
Software Deployment Tools |
|
blocks
|
Valid Accounts |
|
blocks
|
Default Accounts |
|
blocks
|
Domain Accounts |
|
blocks
|
Local Accounts |
|
blocks
|
Cloud Accounts |
|
blocks
|
Cloud Account |
|
blocks
|
Account Manipulation |
|
blocks
|
Additional Cloud Credentials |
|
blocks
|
Additional Email Delegate Permissions |
|
blocks
|
Additional Cloud Roles |
|
blocks
|
SSH Authorized Keys |
|
blocks
|
Device Registration |
|
blocks
|
Additional Local or Domain Groups |
|
blocks
|
Brute Force |
|
blocks
|
Password Guessing |
|
blocks
|
Password Cracking |
|
blocks
|
Password Spraying |
|
blocks
|
Credential Stuffing |
|
blocks
|
Access Token Manipulation |
|
blocks
|
Token Impersonation/Theft |
|
blocks
|
Create Process with Token |
|
blocks
|
Make and Impersonate Token |
|
blocks
|
SID-History Injection |
|
blocks
|
Create Account |
|
blocks
|
Local Account |
|
blocks
|
Domain Account |
|
blocks
|
Cloud Account |
|
blocks
|
Browser Session Hijacking |
|
blocks
|
Exploit Public-Facing Application |
|
blocks
|
BITS Jobs |
|
blocks
|
Exploitation of Remote Services |
|
blocks
|
Data from Information Repositories |
|
blocks
|
Confluence |
|
blocks
|
Sharepoint |
|
blocks
|
Code Repositories |
|
blocks
|
Customer Relationship Management Software |
|
blocks
|
System Binary Proxy Execution |
|
blocks
|
Msiexec |
|
blocks
|
File and Directory Permissions Modification |
|
blocks
|
Windows Permissions |
|
blocks
|
Linux and Mac Permissions |
|
blocks
|
Domain or Tenant Policy Modification |
|
blocks
|
Service Stop |
|
blocks
|
Firmware Corruption |
|
blocks
|
Server Software Component |
|
blocks
|
Transport Agent |
|
blocks
|
Web Shell |
|
blocks
|
Terminal Services DLL |
|
blocks
|
Implant Internal Image |
|
blocks
|
Steal Application Access Token |
|
blocks
|
Data from Cloud Storage |
|
blocks
|
Transfer Data to Cloud Account |
|
blocks
|
Cloud Service Dashboard |
|
blocks
|
Pre-OS Boot |
|
blocks
|
System Firmware |
|
blocks
|
Bootkit |
|
blocks
|
TFTP Boot |
|
blocks
|
Create or Modify System Process |
|
blocks
|
Launch Agent |
|
blocks
|
Systemd Service |
|
blocks
|
Windows Service |
|
blocks
|
Launch Daemon |
|
blocks
|
Container Service |
|
blocks
|
Windows Management Instrumentation Event Subscription |
|
blocks
|
Winlogon Helper DLL |
|
blocks
|
Kernel Modules and Extensions |
|
blocks
|
Shortcut Modification |
|
blocks
|
Print Processors |
|
blocks
|
XDG Autostart Entries |
|
blocks
|
Abuse Elevation Control Mechanism |
|
blocks
|
Bypass User Account Control |
|
blocks
|
Sudo and Sudo Caching |
|
blocks
|
TCC Manipulation |
|
blocks
|
Use Alternate Authentication Material |
|
blocks
|
Pass the Hash |
|
blocks
|
Pass the Ticket |
|
blocks
|
Unsecured Credentials |
|
blocks
|
Credentials In Files |
|
blocks
|
Credentials in Registry |
|
blocks
|
Group Policy Preferences |
|
blocks
|
Container API |
|
blocks
|
Modify Authentication Process |
|
blocks
|
Domain Controller Authentication |
|
blocks
|
Pluggable Authentication Modules |
|
blocks
|
Network Device Authentication |
|
blocks
|
Reversible Encryption |
|
blocks
|
Conditional Access Policies |
|
blocks
|
Steal or Forge Kerberos Tickets |
|
blocks
|
Golden Ticket |
|
blocks
|
Silver Ticket |
|
blocks
|
Kerberoasting |
|
blocks
|
Inter-Process Communication |
|
blocks
|
Component Object Model |
|
blocks
|
Remote Service Session Hijacking |
|
blocks
|
SSH Hijacking |
|
blocks
|
RDP Hijacking |
|
blocks
|
System Services |
|
blocks
|
Launchctl |
|
blocks
|
Service Execution |
|
blocks
|
Hijack Execution Flow |
|
blocks
|
Dylib Hijacking |
|
blocks
|
Executable Installer File Permissions Weakness |
|
blocks
|
Path Interception by PATH Environment Variable |
|
blocks
|
Path Interception by Search Order Hijacking |
|
blocks
|
Path Interception by Unquoted Path |
|
blocks
|
Services File Permissions Weakness |
|
blocks
|
COR_PROFILER |
|
blocks
|
Modify Cloud Compute Infrastructure |
|
blocks
|
Create Snapshot |
|
blocks
|
Create Cloud Instance |
|
blocks
|
Delete Cloud Instance |
|
blocks
|
Cloud Infrastructure Discovery |
|
blocks
|
Network Boundary Bridging |
|
blocks
|
Network Address Translation Traversal |
|
blocks
|
Modify System Image |
|
blocks
|
Patch System Image |
|
blocks
|
Downgrade System Image |
|
blocks
|
Forge Web Credentials |
|
blocks
|
Container Administration Command |
|
blocks
|
Escape to Host |
|
blocks
|
Cloud Storage Object Discovery |
|
blocks
|
Financial Theft |
|
blocks
|
Loss of Accountability / Attribution |
|
blocks
|
Unauthorized Privilege Elevation |
|
blocks
|
Fraud / Theft / Direct Financial Loss |
|
blocks
|
Loss of Data Integrity |
|
blocks
|
Drought & Water Shortage |
|
blocks
|
Earthquakes |
|
blocks
|
Fire & Wildfires |
|
blocks
|
Floods |
|
blocks
|
Hurricanes & Tropical Storms |
|
blocks
|
Landslides & Debris Flow |
|
blocks
|
Pandemic (Disease) Outbreaks |
|
blocks
|
Severe Weather |
|
blocks
|
Space Weather |
|
blocks
|
Thunderstorms & Lightning |
|
blocks
|
Tornadoes |
|
blocks
|
Tsunamis |
|
blocks
|
Volcanoes |
|
blocks
|
Winter Storms & Extreme Cold |
|
blocks
|
Malicious Cyber Activity |
|
blocks
|
Dysfunctional Management Practices |
|
blocks
|
Human Error |
|
blocks
|
Technical / Mechanical Failure |
|
blocks
|
Statutory / Regulatory / Contractual Change |
|
blocks
|
Fraud, Corruption and/or Intentional Criminal Conduct |
|
blocks
|
Conflict of Interest (COI) / Undue Influence / Insider Misconduct |
|
blocks
|
Economic Shock / Market Disruption |
|
blocks
|
Workforce Shortage / Loss of Critical Skills / Labor Disruption |
|
blocks
|
OIS-04.01B |
|
blocks
|
OIS-04.02B |
|
blocks
|
OIS-04.04B |
|
blocks
|
OIS-04.01AC |
|
blocks
|
IAM-01.02B |
|
blocks
|
DEV-03.01B |
|
blocks
|
PSS-08.02B |
|
blocks
|
Loss of Accountability / Attribution |
|
blocks
|
Unauthorized Privilege Elevation |
|
blocks
|
Fraud / Theft / Direct Financial Loss |
|
blocks
|
Loss of Data Integrity |
|
blocks
|
Drought & Water Shortage |
|
blocks
|
Earthquakes |
|
blocks
|
Fire & Wildfires |
|
blocks
|
Floods |
|
blocks
|
Hurricanes & Tropical Storms |
|
blocks
|
Landslides & Debris Flow |
|
blocks
|
Pandemic (Disease) Outbreaks |
|
blocks
|
Severe Weather |
|
blocks
|
Space Weather |
|
blocks
|
Thunderstorms & Lightning |
|
blocks
|
Tornadoes |
|
blocks
|
Tsunamis |
|
blocks
|
Volcanoes |
|
blocks
|
Winter Storms & Extreme Cold |
|
blocks
|
Malicious Cyber Activity |
|
blocks
|
Dysfunctional Management Practices |
|
blocks
|
Human Error |
|
blocks
|
Technical / Mechanical Failure |
|
blocks
|
Statutory / Regulatory / Contractual Change |
|
blocks
|
Fraud, Corruption and/or Intentional Criminal Conduct |
|
blocks
|
Conflict of Interest (COI) / Undue Influence / Insider Misconduct |
|
blocks
|
Economic Shock / Market Disruption |
|
blocks
|
Workforce Shortage / Loss of Critical Skills / Labor Disruption |
|
blocks
|
OIS-04.01B |
|
blocks
|
OIS-04.02B |
|
blocks
|
OIS-04.04B |
|
blocks
|
OIS-04.01AC |
|
blocks
|
IAM-01.02B |
|
blocks
|
DEV-03.01B |
|
blocks
|
PSS-08.02B |
|
is blocked by
|
HRS-14 Separation of Duties (SoD) – Assessment Procedure |
|
blocks
|
AC-05 Separation of Duties |
|
blocks
|
AC-05 [M] Separation of Duties |
|
blocks
|
AC-05 [H] Separation of Duties |
|
blocks
|
03.01.04 Separation of Duties |
|
blocks
|
PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of … |
- Secure Controls Framework -
"The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.
The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.
Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.
The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/
Terms & Conditions
The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.
|