# NIST800 53 PS-2 — Position Risk Designation

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist80053_ps2_7866279220-nist800-53-ps-2-position-risk-designation
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST](https://support.icompaas.com/support/solutions/62000112528) › [Personnel Security](https://support.icompaas.com/support/solutions/folders/f_gen_62000112528_personnelsecurity)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 53 · Control PS-2 · Priority: high · Component: Personnel Security

### What this control covers

Assign a risk designation to all organizational positions, establishing screening criteria for individuals in these positions. Regularly review and update these designations to ensure they remain accurate and consistent with organizational needs. The risk designation process assesses the potential impact of a position on organizational integrity and security, guiding access to sensitive information and systems. This control supports the Governance capability within the Personnel Security family.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

**VM Manager** (OS patch + config management) and **Artifact Registry vulnerability scanning** integrate with Cloud Build to block vulnerable images.

#### GitHub

**Dependabot** security updates + version updates, plus **CodeQL** for SAST and a renovate bot for major-version drift management.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.

Signed policy or standard documents the safeguard. Focus: Position Risk Designation.

### Quick checklist

-   Policy — Management / Information
-   Access — Management / Information
-   Information — Management / Information
-   Process — Management / Information
-   Security — Management / Information
-   Review — Management / Information

### Related articles on this site

-   [NIST 800-171 3.11.1 Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the assoc](https://support.icompaas.com/support/solutions/articles/62000229327-nist-800-171-3-11-1-periodically-assess-the-risk-to-organizational-operations-including-mission-fun)
-   [CMMC 2.0 RM.2.141 Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associa](https://support.icompaas.com/support/solutions/articles/62000229660-cmmc-2-0-rm-2-141-periodically-assess-the-risk-to-organizational-operations-including-mission-funct)
-   [Ensure Access Review is Set Up for External Users in Azure AD Privileged Identity Management (PIM](https://support.icompaas.com/support/solutions/articles/62000229788-ensure-access-review-is-set-up-for-external-users-in-azure-ad-privileged-identity-management-pim)
-   [Ensure an Organizational EC2 Tag Policy Has Been Created](https://support.icompaas.com/support/solutions/articles/62000233962-ensure-an-organizational-ec2-tag-policy-has-been-created)

## Related compliance guidance

- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): How the 800-53 catalogue, baselines and the Risk Management Framework fit together, and which controls take the most work in the cloud.
- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If the driver is a DoD or federal contract handling CUI, 800-171 (and CMMC) is the scope you actually need.
