Contacts With Groups & Associations

Description

Mechanisms exist to establish contact with selected groups and associations within the security, compliance and resilience communities to:
(1) Facilitate ongoing cybersecurity and data protection education and training for organizational personnel;
(2) Maintain currency with recommended cybersecurity and data protection practices, techniques and technologies; and
(3) Share current cybersecurity and/or data protection-related information including threats, vulnerabilities and incidents.

Possible Solutions & Considerations

Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2

∙ ISACA chapters (https://www.isaca.org)
∙ ISC2 chapters (https://www.isc2.org)
∙ IAPP chapters (https://iapp.org)
∙ CISA free resources and advisories (https://www.cisa.gov)
∙ SANS reading room, vendor security blogs

Small Business (10-49 staff) / BLS Firm Size Classes 3-4

Medium Business (50-249 staff) / BLS Firm Size Classes 5-6

∙ ISACA chapters (https://www.isaca.org)
∙ ISC2 chapters (https://www.isc2.org)
∙ IAPP chapters (https://iapp.org)
∙ CISA advisories and threat alerts (https://www.cisa.gov)
∙ Sector-specific ISAC membership

Large Business (250-999 staff) / BLS Firm Size Classes 7-8

∙ ISACA chapters (https://www.isaca.org)
∙ ISC2 chapters (https://www.isc2.org)
∙ IAPP chapters (https://iapp.org)
∙ Sector ISAC active membership (e.g., FS-ISAC, H-ISAC)
∙ CISA Cyber Information Sharing program
∙ InfraGard membership (https://www.infragard.org)

Enterprise (> 1,000 staff) / BLS Firm Size Class 9

∙ ISACA enterprise membership (https://www.isaca.org)
∙ ISC2 enterprise programs (https://www.isc2.org)
∙ IAPP enterprise membership (https://iapp.org)
∙ Sector ISAC leadership participation
∙ InfraGard and CISA partnership programs
∙ Sector-specific policy engagement (FS-ISAC, NTIA, etc.)

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

SCR-CMM Level 1 criteria definitions are not available for this control:
▪ A reasonable person would conclude this control requires a structured process.
▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 Planned Tracked

Cybersecurity & Data Protection Governance (GOV) 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 GOV domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with GOV 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 GOV domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Governance-related controls are primarily administrative and preventative in nature (e.g., policies, standards, procedures & guidelines).
▪ No formal Governance, Risk & Compliance (GRC) team exists. GRC roles are assigned to existing IT and/or cybersecurity personnel.
▪ Cybersecurity and data privacy personnel identify and maintain contact information for local, regional and national cybersecurity / data privacy groups and associations.

Level 3 Well Defined

Cybersecurity & Data Protection Governance (GOV) 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 GOV 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 GOV domain capabilities are well-documented and kept current by process owners.
▪ The entity's GRC team, or similar function, is appropriately staffed and supported to implement and maintain GOV 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).
▪ Technology is leveraged to enhance the efficiency and accuracy of governance, risk management and compliance operations (e.g., GRC platform).
▪ An implemented and operational capability exists to establish contact with selected groups and associations within the security, compliance and resilience communities to:
(1) Facilitate ongoing cybersecurity and data protection education and training for organizational personnel;
(2) Maintain currency with recommended cybersecurity and data protection practices, techniques and technologies; and
(3) Share current cybersecurity and/or data protection-related information including threats, vulnerabilities and incidents.

Level 4 Quantitatively Controlled

Cybersecurity & Data Protection Governance (GOV) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational.
▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 Continuously Improving

1. Overview

Summary	Standard

1.1 References

1.2 Identified Requirements

1.3 Related Regulations

2. Identified Requirements

Requirements
Source	Requirement

3. Related Regulations

Regulations
Source	Regulation
DORA	DORA Ch. VI Art. 45 1. 1. Financial entities may exchange amongst themselves cyber threat information and intelligence, including indicators of compromise, tactics, techniques, and procedures, cyber security alerts and configuration tools, to the extent that such information and intelligence sharing: (a) aims to enhance the digital operational resilience of financial entities, in particular through raising awareness in relation to cyber threats, limiting or impeding the cyber threats’ ability to spread, supporting defence capabilities, threat detection techniques, mitigation strategies or response and recovery stages; (b) takes places within trusted communities of financial entities; (c) is implemented through information-sharing arrangements that protect the potentially sensitive nature of the information shared, and that are governed by rules of conduct in full respect of business confidentiality, protection of personal data in accordance with Regulation (EU) 2016/679 and guidelines on competition policy.
DORA	DORA Ch. VI Art. 45 2. 2. For the purpose of paragraph 1, point (c), the information-sharing arrangements shall define the conditions for participation and, where appropriate, shall set out the details on the involvement of public authorities and the capacity in which they may be associated to the information-sharing arrangements, on the involvement of ICT third-party service providers, and on operational elements, including the use of dedicated IT platforms.

Linked Issues

Issuelinks
Linktype	Issue
is related to	Annual
is related to	relative Control Weighting = 07
is related to	Process
is related to	Govern
is related to	SCRM Focus Tier 1 STRATEGIC
is related to	SCRM Focus Tier 2 OPERATIONAL
blocks	Information loss / corruption or system compromise due to technical attack
blocks	Information loss / corruption or system compromise due to non‐technical attack
blocks	Loss of revenue
blocks	Cancelled contract
blocks	Diminished competitive advantage
blocks	Diminished reputation
blocks	Fines and judgements
blocks	Unmitigated vulnerabilities
blocks	System compromise
blocks	Inability to support business processes
blocks	Incorrect controls scoping
blocks	Lack of roles & responsibilities
blocks	Inadequate internal practices
blocks	Inadequate third-party practices
blocks	Lack of oversight of internal controls
blocks	Lack of oversight of third-party controls
blocks	Illegal content or abusive action
blocks	Inability to investigate / prosecute incidents
blocks	Improper response to incidents
blocks	Ineffective remediation actions
blocks	Expense associated with managing a loss event
blocks	Inability to maintain situational awareness
blocks	Lack of a security-minded workforce
blocks	Third-party cybersecurity exposure
blocks	Third-party physical security exposure
blocks	Third-party supply chain relationships, visibility and controls
blocks	Third-party compliance / legal exposure
blocks	Use of product / service
blocks	Reliance on the third-party

Secure Controls Framework -
The Secure Controls Framework® (SCF)

"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.