SC-1 System and Communications Protection Policy and Procedures (L) (M) (H)

NIST 800-53 (r4) Control:

The organization:

(a) Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]:

(1) A system and communications protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and

(2) Procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls; and

(b) Reviews and updates the current:

(1) System and communications protection policy [FedRAMP Assignment: (L)(M) at least every three (3) years; (H) at least annually]; and

(2) System and communications protection procedures [FedRAMP Assignment: (L)(M) at least annually; (H) at least annually or whenever a significant change occurs].

NIST 800-53 (r4) Supplemental Guidance:

Supplemental Guidance: The United States Computer Emergency Readiness Team (US-CERT) generates security alerts and advisories to maintain situational awareness across the federal government. Security directives are issued by OMB or other designated organizations with the responsibility and authority to issue such directives. Compliance to security directives is essential due to the critical nature of many of these directives and the potential immediate adverse effects

on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be implemented in a timely manner. External organizations include, for example, external mission/business partners, supply chain partners, external service providers, and other peer/supporting organizations. Related control: SI-2.

References: NIST Special Publication 800-40.

NIST 800-53 (r5) Discussion:

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.

38North Guidance:

Meets Minimum Requirement:

• Develop, document, and disseminate SC policies and procedures.

• SC policies and procedures must address:

  • • • All SC controls contained in the SC family including guidelines and processes for cryptography, PKI certificate lifecycle management, boundary protection, DNS, etc.

      • Policy must include: purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance.

• Review, approve, and update (when a review indicates updates are required) documented SC policies (at least every three (3) years for FedRAMP Moderate and at least annually for FedRAMP High) and procedures at least annually or if there is a major change in the environment.

Best Practice:

• Disseminate policies and procedures to only personnel with SC roles or responsibilities.

• Ensure that the responsible party reviews, approves and signs the SC policy and procedures.

Unofficial FedRAMP Guidance:

• TBD

Assessment Evidence:

• Versioned SC policies and procedures documents with last update, last approval date, and approver.

• Approval by management within the last year or as a result of a major change in the environment, whichever occurred most recently.

CSP Implementation Tips:

• Amazon Web Services (AWS): TBD

• Microsoft Azure: TBD

• Google Cloud Platform: TBD