NIST SP 800-53 Rev. 5·Control PM-6·high·Component: Program Management

What this control requires

Develop, monitor, and report on the results of performance measures for information security and privacy programs to assess the effectiveness and efficiency of controls, aligning them with the organization's risk tolerance. This control supports the Performance Measurement System capability within the Program Management family.
— NIST SP 800-53 Rev. 5, Control PM-6

In plain English

Develop, monitor, and report on the results of performance measures for information security and privacy programs to assess the effectiveness and efficiency of controls, aligning them with the organization's risk tolerance. In practice, this means you can prove you information management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Program Management, the assessor will trace your implementation back to the catalogue reference (Control PM-6) and look for objective evidence on the latest two assessment cycles.

How to implement

Secure Development

Pipeline. Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

Branch protection. Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Logging Monitoring

AWS. Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation.

Azure. Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR.

GCP. Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM.

Operational checklist

  • Information. Document the trigger, the owner and the cadence.
  • Security. Document the trigger, the owner and the cadence.
  • Review. Document the trigger, the owner and the cadence.
  • Monitor. Document the trigger, the owner and the cadence.
  • System. Document the trigger, the owner and the cadence.
  • Scope: management, information, privacy, organization, system, controls, monitor, review.

Evidence to collect

  • Code Repo Scan. Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports.

Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Measures Of Performance.

Common pitfalls

  • CI security checks set to warn-only; the merge button is faster than the security feedback.
  • Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in NIST SP 800-53 Rev. 5

References

Topics: governance risksecure developmentcode review testingdevsecopslogging monitoring