# NIST800 53 PM-1 — Information Security Program Plan

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist80053_pm1_c311d616c4-nist800-53-pm-1-information-security-program-plan
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST](https://support.icompaas.com/support/solutions/62000112528) › [Program Management](https://support.icompaas.com/support/solutions/folders/f_gen_62000112528_programmanagement)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 53 · Control PM-1 · Priority: critical · Component: Program Management

### What this control covers

Develop and disseminate an organization-wide information security program plan that outlines security requirements, management controls, and common controls. It should assign roles, responsibilities, ensure coordination among entities, and be approved by a senior official. The plan should be reviewed and updated regularly, and protected from unauthorized disclosure and modification. This control supports the Information Security Program Plan capability within the Program Management 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

Use **Cloud Identity** (or Workspace) as the IdP and **IAM** for resource access. Grant roles at the lowest scope (project > folder > org) using **Workload Identity Federation** for CI/CD and **service accounts** for workloads — never download service-account keys when avoidable. Enable **Policy Intelligence** recommenders to right-size privileges and detect dormant identities.

#### Google Workspace

Enforce **2-Step Verification** (preferably hardware keys for admins) for the entire org, set session length to ≤ 12 hours, and disable less-secure-app access. Use **Context-Aware Access** levels to restrict admin sign-in by IP/device posture. Provision and de-provision users via **SCIM** from your HRIS so leavers lose access on day one.

#### GitHub

Require **SSO + SCIM** from your IdP on the organisation; enforce **2FA** org-wide and use **fine-grained PATs** (or, better, GitHub Apps) instead of classic tokens. Restrict **outside collaborators**, require signed commits on protected branches, and use **OIDC** from Actions to short-lived AWS/GCP/Azure credentials rather than stored secrets.

#### Zoho Mail

Make **two-factor authentication** mandatory for all users (TOTP, OneAuth, or YubiKey) in _Admin Console → Security_. Configure **SAML SSO** against your IdP and disable password-based logins for admins. Use **role-based privileges** (Admin / Spam Moderator / Mail Account Admin) and review the _Login history_ report monthly for anomalies.

#### 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

-   `identity_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Information Security Program Plan.

### Quick checklist

-   Access — Management / Information
-   Information — Management / Information
-   Security — Management / Information
-   Review — Management / Information
-   Unauthorized — Management / Information
-   Identity — Management / Information

### Related articles on this site

-   [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)
-   [NIST 800-171 3.1.15 Authorize remote execution of privileged commands and remote access to security-relevant information.](https://support.icompaas.com/support/solutions/articles/62000229250-nist-800-171-3-1-15-authorize-remote-execution-of-privileged-commands-and-remote-access-to-security-r)
-   [CMMC 2.0 AC.3.021 Authorize remote execution of privileged commands and remote access to security-relevant information.](https://support.icompaas.com/support/solutions/articles/62000229416-cmmc-2-0-ac-3-021-authorize-remote-execution-of-privileged-commands-and-remote-access-to-security-rel)
-   [NIST 800-171 3.2.2 Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.](https://support.icompaas.com/support/solutions/articles/62000229266-nist-800-171-3-2-2-ensure-that-personnel-are-trained-to-carry-out-their-assigned-information-security)

## 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.