# PE-06 Monitoring Physical Access

NIST SP 800-53 control. Family: PE Physical and Environmental Protection. Function: detective. Baselines: low, moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: a. Monitor physical access to the facility where the system resides to detect and respond to physical security incidents; b. Review physical access logs [Assignment: organization-defined frequency] and upon occurrence of [Assignment: organization-defined events or potential indications of events]; and c. Coordinate results of reviews and investigations with the organizational incident response capability.
Guidance: Physical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include the employment of guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help identify suspicious activity, anomalous events, or potential threats. The reviews can be supported by audit logging controls, such as AU-02, if the access logs are part of an automated system. Organizational incident response capabilities include investigations of physical security incidents and responses to the incidents. Incidents include security violations or suspicious physical access activities. Suspicious physical access activities include accesses outside of normal work hours, repeated accesses to areas not normally accessed, accesses for unusual lengths of time, and out-of-sequence accesses.

## Enhancements (4)
- PE-06(01) Intrusion Alarms and Surveillance Equipment. Baselines: moderate, high
- PE-06(02) Automated Intrusion Recognition and Responses
- PE-06(03) Video Surveillance
- PE-06(04) Monitoring Physical Access to Systems. Baselines: high
Each enhancement's statement: /api/v1/controls/PE-06?fields=enhancements

## Patterns that use it (2)
- Important (1): SP-002 Server Module
- Standard (1): SP-023 Industrial Control Systems

## Clauses by framework (55 frameworks)
- iso_27001_2022: A.7.2, A.7.4, A.8.16. OSA's own, not in NIST's crosswalk: A.7.2
- iso_27002_2022: 7.2, 7.4
- cobit_2019: DSS01, DSS05
- pci_dss_v4: 9.2
- nist_csf_2: DE.CM-02, PR.AA-06
- bsi_grundschutz: INF.1, INF.2
- anssi: Hygiene.37, Hygiene.39, SecNumCloud.12.2
- osfi_b13: B-13.3.2, B-13.3.3
- finma_circular: IV.C(66)
- gdpr: Art.32(1)(b), Art.32(1)(d)
- bio2: 7.2, 7.4
- rbi_csf: Annex1.3, ITGRCA.18
- fisc: FISC.F1
- hkma_tme1: TME1.5.1, TME1.11.1, TME1.11.3
- mlps_2: 8.1.1.2, 8.1.1.3, 8.1.10.1
- dnb_good_practice: DNB.21.1, DNB.21.2
- swift_cscf: SWIFT.3.1
- cbb_tm: TM-10
- nca_ecc: 1-11
- qatar_nia: PS
- sama_csf: 3.7
- uae_ia: T6
- bog_cisd: CISD-XIV
- bom_ctrm: 3.5
- cbe_csf: CD-1, CTO-10
- cbn_csf: Part10
- sa_js2: JS2-PE
- bot_cyber: Ch2.8
- cpmi_pfmi: CG.PR
- eba_ict: 3.4.3
- ecb_croe: CROE.2.3.6
- ffiec_is: II.C.8
- hipaa_sr: §164.310(a)(1), §164.310(a)(2)(ii), §164.310(a)(2)(iii)
- iosco_cyber: PROT-5
- sebi_cscrf: PR.PE
- cmmc_2: PE
- nerc_cip: CIP-006-6, CIP-014-3
- nrc_73_54: RG5.71-B-PE
- api_1164: Sec 14
- iaea_nss: Sec 10
- pci_pts: A, I
- fips_140: FIPS 140-3 §7.7
- pci_hsm: 6, 7
- isae_3402: Clause 4
- hitrust_csf: 08.a
- iso_27799: 11.1
- lloyds_ms: PHYS.1
- naic_ds: 4B
- solvency_ii: EIOPA-ICT-4.5
- csa_ccm_v4: DCS-07, DCS-10, DCS-11
- csa_aicm: DCS-07, DCS-10, DCS-11
- ccss_v9: 1.01.1
- basel_sco60: SCO60.62
- bssc: NOS-09
- sec_custody_digital: SEC-CD-08, 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/PE-06
- Clauses only: /api/v1/controls/PE-06?fields=mappings
- Page for people: /controls/pe-06/