# PS-04 Personnel Termination

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

Statement: Upon termination of individual employment: a. Disable system access within [Assignment: organization-defined time period]; b. Terminate or revoke any authenticators and credentials associated with the individual; c. Conduct exit interviews that include a discussion of [Assignment: organization-defined information security topics]; d. Retrieve all security-related organizational system-related property; and e. Retain access to organizational information and systems formerly controlled by terminated individual.
Guidance: System property includes hardware authentication tokens, system administration technical manuals, keys, identification cards, and building passes. Exit interviews ensure that terminated individuals understand the security constraints imposed by being former employees and that proper accountability is achieved for system-related property. Security topics at exit interviews include reminding individuals of nondisclosure agreements and potential limitations on future employment. Exit interviews may not always be possible for some individuals, including in cases related to the unavailability of supervisors, illnesses, or job abandonment. Exit interviews are important for individuals with security clearances. The timely execution of termination actions is essential for individuals who have been terminated for cause. In certain situations, organizations consider disabling the system accounts of individuals who are being terminated prior to the individuals being notified.

## Enhancements (2)
- PS-04(01) Post-employment Requirements
- PS-04(02) Automated Actions. Baselines: high
Each enhancement's statement: /api/v1/controls/PS-04?fields=enhancements

## Patterns that use it (5)
- Critical (1): SP-044 SaaS Identity Lifecycle Management
- Important (1): SP-037 Privileged User Management
- Standard (3): SP-014 Awareness and Training Pattern; SP-031 Security Monitoring and Response; SP-036 Incident Response

## Clauses by framework (53 frameworks)
- iso_27001_2022: A.5.11, A.6.5
- iso_27002_2022: 5.11, 6.5
- nist_csf_2: GV.RR-04. OSA's own, not in NIST's crosswalk: GV.RR-04
- cis_controls_v8: CIS 6.2, CIS 15.7
- soc2_tsc: CC1.5
- iso_42001_2023: A.3.2
- nis2: Art. 21(2)(i)
- bsi_grundschutz: ORP.2
- anssi: Hygiene.7, Hygiene.32, SecNumCloud.8.4
- osfi_b13: B-13.1.1, B-13.3.2
- finma_circular: IV.B.d(59), IV.B.d(60)
- gdpr: Art.29, Art.32(1)(b)
- dora: Art.9(4)(c)
- bio2: 5.11, 6.5
- rbi_csf: Annex1.8, ITGRCA.19
- fisc: FISC.O8
- lgpd_bcb: LGPD.Art.47
- hkma_tme1: TME1.8.1
- mlps_2: 8.1.8.1
- dnb_good_practice: DNB.8.5
- swift_cscf: SWIFT.5.2
- cbb_tm: TM-6
- nca_ecc: 1-9
- qatar_nia: HR
- sama_csf: 1.7
- uae_ia: T5
- bog_cisd: CISD-XV
- bom_ctrm: 3.8
- cbe_csf: CD-1, GOV-2
- cbn_csf: Part9
- sa_js2: JS2-8.6
- bot_cyber: Ch7.2
- ecb_croe: CROE.2.3.2
- ffiec_is: II.C.7
- hipaa_sr: §164.308(a)(3)(i), §164.308(a)(3)(ii)(C)
- iosco_cyber: GOV-4
- nydfs_500: 500.7
- cmmc_2: PS
- nerc_cip: CIP-004-7
- nrc_73_54: RG5.71-C-PS
- doe_c2m2: WORKFORCE
- api_1164: Sec 13
- iaea_nss: Sec 9
- fca_sysc_13: SYSC 13.6.4
- hitrust_csf: 02.c
- iso_27799: 7.3, 8.3
- lloyds_ms: MS8.3
- naic_ds: 4-access, 4-personnel, 4B
- nhs_dspt: NDG-4.2
- csa_ccm_v4: HRS-05, HRS-06, IAM-07
- csa_aicm: HRS-05, HRS-06, IAM-07
- ccss_v9: 1.04.1, 1.04.2, 1.06.2
- sec_custody_digital: SEC-CD-16
OSA's mapping for iso_27001_2022 and 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-04
- Clauses only: /api/v1/controls/PS-04?fields=mappings
- Page for people: /controls/ps-04/
- 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.