Skip to main content

OPS-01: Security Operations Policy

OPS 10 — Critical Govern

Mechanisms exist to establish a formal, documented security operations policy that: (1) Conveys executive management's intent; (2) Provides organizational direction and expected behaviors; (3) Is reviewed at least annually; and (4) Is updated, as necessary, to adapt to evolving risks, threats and other changes that affect the organization.

Code reused: In SCF 2025.4 and earlier, OPS-01 was Operations Security. That control is now OPS-02.

Control Question: Does the organization establish a formal, documented security operations policy that: (1) Conveys executive management's intent; (2) Provides organizational direction and expected behaviors; (3) Is reviewed at least annually; and (4) Is updated, as necessary, to adapt to evolving risks, threats and other changes that affect the organization?

EMEA (2)
Framework Mapping Values
EMEA EU EBA GL/2019/04 3.4.1.30(d)
EMEA LUX CCSF 20/750 2020 3.4.1-30.d

Capability Maturity Model

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

Security Operations (OPS) 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 OPS domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with OPS 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 OPS domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Security operations management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Security operations management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.

Level 3 — Well Defined

Security Operations (OPS) 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 OPS 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 OPS domain capabilities are well-documented and kept current by process owners. ▪ A Security Operations Center (SOC), or similar function, is appropriately staffed and supported to implement and maintain OPS domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of security operations management (e.g., SIEM solution and EDR/XDR tools). ▪ 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 OPS 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). ▪ Cybersecurity personnel create “run books,” or SOPs, to capture operational knowledge in documentation form for critical business functions and/or for sensitive/regulated obligations.

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.

Assessment Objectives

  1. OPS-01_A01 a formal, documented security operations policy is approved by executive management, or a formally delegated authority, and conveys executive management's intent for security operations.
  2. OPS-01_A02 the security operations policy provides organizational direction and states the behaviors expected of personnel and other applicable parties with respect to security operations.
  3. OPS-01_A03 the current version of the security operations policy is communicated to, and accessible by, the personnel and other applicable parties who are expected to comply with it.
  4. OPS-01_A04 the security operations policy is reviewed at least annually.
  5. OPS-01_A05 the security operations policy is updated, as necessary, in response to changes in risks, threats, business practices and/or statutory, regulatory and contractual obligations that affect the organization.

Evidence Requirements

E-GOV-01.28 Security Operations Policy

Documented evidence of a security operations policy.

Security, Compliance & Resilience Governance

Technology Recommendations

Micro/Small

  • ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
  • Executive-approved written policy with documented annual review

Small

  • ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
  • Executive-approved written policy with documented annual review
  • Policy acknowledgement tracking (e.g., HR onboarding records)

Medium

  • ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
  • GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.) for policy lifecycle management
  • Documented annual policy review with version control

Large

  • ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
  • GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.) for policy lifecycle management
  • Policy governance committee with formal annual review and approval workflow
  • Automated policy attestation and acknowledgement tracking

Enterprise

  • Steering committee
  • ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
  • Enterprise GRC platform (e.g., Cyturus, Archer, MetricStream, ServiceNow IRM) for policy lifecycle management
  • Automated policy attestation, exception tracking and change history
  • Annual executive approval and board-level reporting

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.