SI-1—Policy and Procedures

LI-SaaS

Low

Moderate

High

>Control Description

Develop, document, and disseminate to ⚙organization-defined personnel or roles: (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

[Selection (one or more): Organization-level; Mission/business process-level; System-level] system and information integrity policy that:

Procedures to facilitate the implementation of the system and information integrity policy and the associated system and information integrity controls;

Designate an ⚙organization-defined official to manage the development, documentation, and dissemination of the system and information integrity policy and procedures; and

Review and update the current system and information integrity:

Policy ⚙organization-defined frequency and following ⚙organization-defined events; and

Procedures ⚙organization-defined frequency and following ⚙organization-defined events.

>FedRAMP Baseline Requirements

Parameter Values

at least annually

>Discussion

System and information integrity policy and procedures address the controls in the SI 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 information integrity 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 information integrity 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.