NIST SP 800-53 Rev. 5 PE-6(3) — Video Surveillance

What this control requires

The control requires employing video surveillance in defined operational areas, reviewing video recordings at specified intervals, and retaining the recordings for a defined period. The surveillance records activity to detect anomalous events or incidents, with reviews conducted as necessary. Retention of video recordings is subject to organizational policies and legal considerations. This control supports the Video Surveillance Systems capability within the Physical and Environmental Protection family.

In plain English

The control requires employing video surveillance in defined operational areas, reviewing video recordings at specified intervals, and retaining the recordings for a defined period. In practice, this means you can prove you policy 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 Physical and Environmental Protection, the assessor will trace your implementation back to the catalogue reference (Control PE-6(3)) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Policy. Document the trigger, the owner and the cadence.
• Physical. Document the trigger, the owner and the cadence.
• Protection. Document the trigger, the owner and the cadence.
• Environmental. Document the trigger, the owner and the cadence.
• Control. Document the trigger, the owner and the cadence.
• Scope: management, reviews, incidents, records, protection, retention, events, capability.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Video Surveillance.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

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.

• HIPAA (45 CFR Part 164) 164.312(b) — Audit Controls

Related controls in NIST SP 800-53 Rev. 5

• Control PE-13(3) — Automatic Fire Suppression
• Control PE-21 — Electromagnetic Pulse Protection
• Control PL-6 — Security-Related Activity Planning
• Control AU-11 — Audit Record Retention
• Control PE-9(1) — Redundant Cabling
• Control PE-19 — Information Leakage

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control PE-6(3)

Topics: governance risklogging retentionpolicy management