{"data":{"id":"PS-01","name":"Policy and Procedures","family":"PS","family_name":"Personnel Security","withdrawn":false,"description":"a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:\n1. [Selection (one or more): Organization-level; Mission/business process-level; System-level] personnel security policy that:\n(a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n(b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n2. Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls;\nb. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the personnel security policy and procedures; and\nc. Review and update the current personnel security:\n1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and\n2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].","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.","enhancements":[],"baseline_low":true,"baseline_moderate":true,"baseline_high":true,"nist_800_53":{"rev5":{"id":"PS-01","name":"Policy and Procedures","description":"a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]:\n1. [Selection (one or more): Organization-level; Mission/business process-level; System-level] personnel security policy that:\n(a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n(b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n2. Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls;\nb. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the personnel security policy and procedures; and\nc. Review and update the current personnel security:\n1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and\n2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].","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":["PM-09","PS-08","SI-12"],"baseline_low":true,"baseline_moderate":true,"baseline_high":true,"baseline_privacy":false,"new_in_rev5":false,"changes_from_rev4":"Title changed from 'Personnel Security Policy and Procedures' Requires the selection (one or more) of organization-level; mission/business process-level; system-level personnel security policies Adds text requiring consistency with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines Requires the designation of a specific official to manage the development, documentation, and dissemination of the personnel security policy and procedures New parameters require update to policy and procedures as a result of specified events in addition to specified frequency Discussion amplifies the need for policy and procedures for risk management, and to help provide security and privacy assurance"}},"compliance_mappings":{"iso_27001_2022":["5.2","5.3","7.5","A.5.1","A.5.2","A.5.4","A.5.31","A.5.36","A.5.37"],"iso_27002_2022":["5.1","5.2"],"cobit_2019":["APO07"],"pci_dss_v4":["12.1"],"nist_csf_2":["GV.OC-03","GV.OV-01","GV.PO-01","GV.PO-02","GV.RR-02","GV.RR-04","GV.SC-03","ID.IM-01","ID.IM-02","ID.IM-03"],"cis_controls_v8":[],"soc2_tsc":["CC1.1","CC1.1-POF1","CC1.1-POF3","CC1.2-POF1","CC1.4","CC1.4-POF1","CC1.4-POF2","CC1.4-POF3","CC2.2-POF1","CC2.2-POF3","CC2.2-POF7","CC3.3-POF1","CC5.3","CC5.3-POF1","CC5.3-POF6","CC7.2-POF1","P1.1-POF5"],"finos_ccc":[],"iso_42001_2023":["A.3.2","A.4.6"],"iec_62443":[],"asd_e8":[],"nis2":["Art. 21(2)(i)"],"apra_cps_234":["Para 18"],"mas_trm":[],"pra_op_resilience":["SS1/21-5.1"],"bsi_grundschutz":["ORP.2"],"anssi":["Hygiene.2","Hygiene.7","SecNumCloud.6.1","SecNumCloud.8.1"],"osfi_b13":["B-13.1.1"],"finma_circular":["IV.A(23)","IV.B.a(48)"],"gdpr":["Art.32(4)","Art.39(1)(b)","Rec.78"],"dora":["Art.5(4)"],"bio2":["5.1","5.2"],"rbi_csf":["Annex1.23","ITGRCA.24"],"fisc":["FISC.O8"],"lgpd_bcb":["BCB.Art.2","LGPD.Art.47"],"hkma_tme1":["TME1.2.5"],"mlps_2":[],"dnb_good_practice":["DNB.1.2","DNB.5.1","DNB.8.1","DNB.8.4"],"cra":[],"swift_cscf":[],"nca_ecc":["1-3","1-4","1-9"],"qatar_nia":["HR"],"sama_csf":["1.2","1.5","1.7"],"uae_ia":["T3","T5"],"bog_cisd":["CISD-XV"],"bom_ctrm":["1.2","3.8"],"cbe_csf":["GOV-2"],"cbn_csf":["Part1.2","Part9"],"popia":["s19"],"sa_js2":["JS2-8.6"],"bcbs_239":["Principle 1"],"bot_cyber":["Ch7.2"],"cpmi_pfmi":["CG.GOV","PFMI.P2"],"eba_ict":["3.4.1"],"ecb_croe":["CROE.2.1.2","CROE.2.3.2"],"ffiec_is":["I.B","II.C.1","II.C.7"],"hipaa_sr":["§164.308(a)(1)(ii)(C)","§164.308(a)(2)","§164.308(a)(3)(i)","§164.316(a)"],"iosco_cyber":["GOV-1","GOV-4"],"nydfs_500":["500.3","500.10"],"sebi_cscrf":["GV.RR"],"cmmc_2":["PS"],"nerc_cip":["CIP-004-7"],"nrc_73_54":["RG5.71-C-PS"],"tsa_psd":[],"ieee_1686":[],"ferc_cip":[],"doe_c2m2":["WORKFORCE"],"api_1164":["Sec 13"],"awia":["AWWA Sec 8"],"iaea_nss":["Sec 9"],"pci_pts":[],"fips_140":[],"cbest":[],"tiber_eu":[],"pci_hsm":["1"],"common_criteria":[],"isae_3402":["Clause 9"],"fca_sysc_13":["SYSC 13.6.1","SYSC 13.6.3","SYSC 13.6.4"],"fda_21_cfr_11":["§11.10(i)"],"fda_cyber":[],"hitrust_csf":["02.a","04.a"],"iso_27799":["5.1","6.1","6.2","7.1"],"lloyds_ms":["MS8.2"],"naic_ds":["4-personnel"],"nhs_dspt":["NDG-2.3"],"pra_ss1_23":["P2.1","P2.4"],"solvency_ii":["Art.41(3)","Art.42","DR.258"],"owasp_masvs_v2":[],"csa_ccm_v4":["CEK-02","HRS-01","HRS-07","HRS-09"],"csa_aicm":["CEK-02","GRC-13","HRS-01","HRS-07","HRS-09","HRS-15"],"ccss_v9":[],"mica":[],"basel_sco60":["SCO60.60"],"bssc":["GSP-04"],"sec_custody_digital":["SEC-CD-01","SEC-CD-19"],"dpdpa":[]},"attack_techniques":[],"metadata":{"last_reviewed":"2026-10-03","review_notes":"2026-10-03: iso_27001_2022 5.2, 7.5, A.5.31, A.5.36, A.5.37 added from NIST's SP 800-53 Rev 5 to ISO/IEC 27001:2022 crosswalk (OLIR entry 155), which OSA's mapping now takes as its base. 2026-10-03: nist_csf_2 GV.OC-03, GV.OV-01, GV.PO-01, GV.PO-02, GV.SC-03, ID.IM-01, ID.IM-02, ID.IM-03 added from NIST's CSF 2.0 to SP 800-53 Rev 5.2.0 crosswalk (OLIR entry 186), which OSA's mapping now takes as its base.","mapping_status":"complete"},"function":"preventative","used_by_patterns":["SP-014","SP-018","SP-036"]}}