← Controls / SC

SC-01 Policy and Procedures

System and Communications Protection

Low Moderate High

Description

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): Organization-level; Mission/business process-level; System-level] system and communications protection policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the system and communications protection policy and the associated system and communications protection controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the system and communications protection policy and procedures; and c. Review and update the current system and communications protection: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].

Supplemental Guidance

System and communications protection policy and procedures address the controls in the SC family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and communications protection policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and communications protection policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.

Changes from Rev 4

Title changed from 'System and Communications Protection Policy and Procedures' Requires the selection (one or more) of organization-level; mission/business process-level; system-level system and communications protection policies Adds text requiring consistency with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines Requires the designation of a specific official to manage the development, documentation, and dissemination of the system and communications protection policy and procedures New parameters require update to policy and procedures as a result of specified events in addition to specified frequency Discussion amplifies the need for policy and procedures for risk management, and to help provide security and privacy assurance

Patterns that use this control (1)

Grouped by the emphasis each pattern gives it.

Compliance Mappings

ISO 27001:2022

5.25.37.5A.5.1A.5.2A.5.4A.5.31A.5.36A.5.37

ISO 27002:2022

5.1

NIST CSF 2.0

GV.OC-03GV.OV-01GV.PO-01GV.PO-02GV.SC-03ID.IM-01ID.IM-02ID.IM-03

SOC 2 TSC

CC1.2-POF1CC1.4-POF1CC2.2CC2.2-POF1CC2.2-POF7CC3.2CC5.1CC5.2CC5.3CC5.3-POF1CC5.3-POF6CC6.1CC6.1-POF2CC6.1-POF5CC6.6CC6.6-POF1CC6.6-POF2CC6.6-POF3CC7.2-POF1P1.1-POF5

PCI DSS v4.0.1

12.1

CSA CCM v4

CEK-01IVS-01

CSA AICM v1

CEK-01I&S-01

ANSSI

Hygiene.2Hygiene.23RGS.1.3SecNumCloud.6.1SecNumCloud.14.1

FINMA Circular 2023/1

IV.A(23)IV.B.d(59)IV.D(78)

OSFI B-13

B-13.1.3B-13.3.2

EU GDPR

Art.5(1)(f)Art.32(1)(a)Art.32(1)(b)

EU DORA

Art.9(1)Art.9(4)(a)

BIO2

5.1

RBI CSF

Annex1.4ITGRCA.16

LGPD + BCB 4893

BCB.Art.2

HKMA TM-E-1

TME1.2.5

DNB Good Practice

DNB.1.2

SAMA CSF

1.2

NCA ECC

1-32-5

UAE IA

T3T8

CBB TM

TM-8

Qatar NIA

CS

CBN CSF

Part1.3

BoG CISD

CISD-VI

POPIA

s19

IOSCO Cyber Resilience

GOV-1

FFIEC IS

II.C.1

NYDFS 500

500.3

HIPAA Security Rule

§164.312(e)(1)§164.316(a)

EBA ICT Guidelines

3.4.1

SEBI CSCRF

PR.NS

BOT Cyber Resilience

Ch2.4

CMMC 2.0

SC

Solvency II

Art.41(3)DR.266

Lloyd's Minimum Standards

MS8.2

HITRUST CSF v11

04.a09.e

ISO 27799

5.1

MiCA

Art.62(7)

ISO 17799 (legacy)

10.8.115.1.1

COBIT 4.1 (legacy)

DS5.2PC5