NIST 800-53 REV 5 • SYSTEM AND SERVICES ACQUISITION
SA-1 — Policy and Procedures
Develop, document, and disseminate to {{ insert: param, sa-1_prm_1 }}: {{ insert: param, sa-01_odp.03 }} system and services acquisition policy that: Procedures to facilitate the implementation of the system and services acquisition policy and the associated system and services acquisition controls; Designate an {{ insert: param, sa-01_odp.04 }} to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures; and Review and update the current system and services acquisition: Policy {{ insert: param, sa-01_odp.05 }} and following {{ insert: param, sa-01_odp.06 }} ; and Procedures {{ insert: param, sa-01_odp.07 }} and following {{ insert: param, sa-01_odp.08 }}.
Supplemental Guidance
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.
Practitioner Notes
You need documented policies and procedures for how your organization acquires systems and services with security built into the process. Buying or building systems without security requirements leads to expensive retrofits later.
Example 1: Write an acquisition security policy that requires security requirements to be included in all RFPs, contracts, and service agreements. Define minimum security standards vendors must meet (encryption, access controls, audit logging) and include them as evaluation criteria in procurement decisions.
Example 2: Create procurement procedures that include a security review checkpoint. Before any IT purchase over a defined threshold, the CISO or security team must review the vendor's security posture, the product's security features, and the data it will handle. No purchase order without a signed security review form.