# PS-02 Position Risk Designation

NIST SP 800-53 control. Family: PS Personnel Security. Function: preventative. Baselines: low, moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: a. Assign a risk designation to all organizational positions; b. Establish screening criteria for individuals filling those positions; and c. Review and update position risk designations [Assignment: organization-defined frequency].
Guidance: Position risk designations reflect Office of Personnel Management (OPM) policy and guidance. Proper position designation is the foundation of an effective and consistent suitability and personnel security program. The Position Designation System (PDS) assesses the duties and responsibilities of a position to determine the degree of potential damage to the efficiency or integrity of the service due to misconduct of an incumbent of a position and establishes the risk level of that position. The PDS assessment also determines if the duties and responsibilities of the position present the potential for position incumbents to bring about a material adverse effect on national security and the degree of that potential effect, which establishes the sensitivity level of a position. The results of the assessment determine what level of investigation is conducted for a position. Risk designations can guide and inform the types of authorizations that individuals receive when accessing organizational information and information systems. Position screening criteria include explicit information security role appointment requirements. Parts 1400 and 731 of Title 5, Code of Federal Regulations, establish the requirements for organizations to evaluate relevant covered positions for a position sensitivity and position risk designation commensurate with the duties and responsibilities of those positions.

## Patterns that use it (1)
- Important (1): SP-014 Awareness and Training Pattern

## Clauses by framework (56 frameworks)
- iso_27002_2022: 5.2
- cobit_2019: APO07
- nist_csf_2: GV.RR-02, GV.RR-04. OSA's own, not in NIST's crosswalk: GV.RR-02, GV.RR-04
- soc2_tsc: CC1.2, CC1.2-POF1, CC1.3, CC1.4-POF2, CC1.5, CC5.3
- iso_42001_2023: A.3.2
- nis2: Art. 21(2)(i)
- apra_cps_234: Para 18
- pra_op_resilience: SS1/21-5.1, SS2/21-17.1
- bsi_grundschutz: ORP.2
- anssi: Hygiene.7, Hygiene.15, SecNumCloud.8.1
- osfi_b13: B-13.1.1
- finma_circular: IV.B.a(48), IV.B.c(54)
- gdpr: Art.32(4)
- dora: Art.5(4)
- bio2: 5.2
- rbi_csf: Annex1.8
- fisc: FISC.O8
- lgpd_bcb: LGPD.Art.47
- dnb_good_practice: DNB.7.1, DNB.8.1, DNB.8.3
- nca_ecc: 1-9
- qatar_nia: HR
- sama_csf: 1.5, 1.7
- uae_ia: T5
- bog_cisd: CISD-XV
- bom_ctrm: 1.2, 3.8
- cbe_csf: CD-1, GOV-2
- cbn_csf: Part1.2, Part9
- sa_js2: JS2-8.6
- bcbs_239: Principle 1
- bot_cyber: Ch7.2
- cpmi_pfmi: CG.GOV
- ecb_croe: CROE.2.1.2, CROE.2.3.2
- ffiec_is: I.B, II.C.7, II.C.7(a), II.C.7(c)
- hipaa_sr: §164.308(a)(3)(i), §164.308(a)(3)(ii)(A), §164.308(a)(3)(ii)(B)
- iosco_cyber: GOV-4
- nydfs_500: 500.10
- sebi_cscrf: GV.RR
- cmmc_2: PS
- nerc_cip: CIP-004-7
- nrc_73_54: RG5.71-C-PS
- doe_c2m2: WORKFORCE
- api_1164: Sec 13
- awia: AWWA Sec 8
- iaea_nss: Sec 9
- pci_hsm: 1
- isae_3402: Clause 9
- fca_sysc_13: SYSC 13.6.1, SYSC 13.6.2, SYSC 13.6.4
- fda_21_cfr_11: §11.10(i)
- hitrust_csf: 02.a
- iso_27799: 6.2, 7.1
- naic_ds: 4-personnel
- pra_ss1_23: P2.2, P2.4
- solvency_ii: Art.42
- mica: Art.34(1), Art.54(1)
- basel_sco60: SCO60.60
- bssc: GSP-04
OSA's mapping for nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/PS-02
- Clauses only: /api/v1/controls/PS-02?fields=mappings
- Page for people: /controls/ps-02/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.