SA-1 System and Service Acquisition (L) (M) (H)

NIST SP 800-53 (r4) Control:

The organization:

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

1. A system and services acquisition 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 services acquisition policy and associated system and services acquisition controls; and

b. Reviews and updates the current:

1. System and services acquisition policy [FedRAMP Assignment: (L)(M) at least every 3 years; (H) at least annually]]; and

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

NIST 800-53 (r4) Supplemental Guidance:

This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the SA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. Related control: PM-9.

NIST 800-53 (r5) Discussion:

System and services acquisition policy and procedures address the controls in the SA 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 services acquisition 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 services acquisition policy and procedures include assessment or audit findings, security incidents or breaches, or changes in 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 SA policies and procedures.

  • SA policies and procedures must address:

    • All SA controls contained in the SA family including guidelines and processes for resource allocation, the organization's system development lifecycle, IT acquisition process (to include hardware and software services), engineering and development practices, 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 SA policies and procedures at least annually or if there is a major change in the environment.

    • For Low and Moderate systems, policies may be on a three year review cycle.

Best Practice:

• • None.

Unofficial FedRAMP Guidance:

• • None.

Assessment Evidence:

• • SA policies and procedures documents with last update, last approval date, and approver most commonly found in a ‘revision table’.

  • 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:

• 1. None.