NIST 800-53 REV 5 • PERSONNEL SECURITY
PS-1 — Policy and Procedures
Develop, document, and disseminate to {{ insert: param, ps-1_prm_1 }}: {{ insert: param, ps-01_odp.03 }} personnel security policy that: Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls; Designate an {{ insert: param, ps-01_odp.04 }} to manage the development, documentation, and dissemination of the personnel security policy and procedures; and Review and update the current personnel security: Policy {{ insert: param, ps-01_odp.05 }} and following {{ insert: param, ps-01_odp.06 }} ; and Procedures {{ insert: param, ps-01_odp.07 }} and following {{ insert: param, ps-01_odp.08 }}.
Supplemental Guidance
Personnel security policy and procedures for the controls in the PS 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 their development. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission level 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 reflecting the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/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 personnel security policy and procedures include, but are not limited to, 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.
Practitioner Notes
You need documented personnel security policies and procedures that cover the entire employee lifecycle — from hiring through termination. These policies govern how you screen, onboard, manage, and offboard people with access to your systems.
Example 1: Write a personnel security policy that covers background checks, access agreements, security training requirements, personnel transfer procedures, and termination checklists. Store it in SharePoint and require annual review and leadership signature.
Example 2: Create a personnel security procedures document that walks HR and IT through each step: how to request a background check, what forms new employees sign, how access is provisioned in Azure AD, and the exact steps to disable accounts and collect equipment when someone leaves.