PS-1—Policy and Procedures
>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] personnel security policy that:
Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls;
Designate an ⚙organization-defined official to manage the development, documentation, and dissemination of the personnel security policy and procedures; and
Review and update the current personnel security:
Policy ⚙organization-defined frequency and following ⚙organization-defined events; and
Procedures ⚙organization-defined frequency and following ⚙organization-defined events.
>DoD Impact Level Requirements
FedRAMP Parameter Values
PS-1 (c) (1) [at least annually] PS-1 (c) (2) [at least annually] [significant changes]
>Discussion
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.
>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •Who is designated as the official responsible for personnel security policies and procedures?
- •How does the organization coordinate personnel security policies with HR, security, and legal teams?
- •What is the review frequency for personnel security policies, and what events trigger updates?
- •How are personnel security procedures disseminated to managers, HR staff, and security personnel?
- •What governance exists for ensuring personnel security policies align with organizational risk tolerance?
Technical Implementation:
- •What systems or tools manage personnel security policies and procedures?
- •How are personnel security policy documents distributed and acknowledged?
- •What integration exists between personnel security tools and HR systems?
Evidence & Documentation:
- •Provide the current personnel security policy document with version history.
- •Provide documentation showing the designated official responsible for personnel security.
- •Provide evidence of policy review and updates within the required frequency.
- •Provide records showing dissemination of procedures to HR and security personnel.
- •Provide documentation of coordination between personnel security, HR, and legal teams.
Ask AI
Configure your API key to use AI features.