# PE-11 Emergency Power

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

Statement: Provide an uninterruptible power supply to facilitate [Selection (one or more): an orderly shutdown of the system; transition of the system to long-term alternate power] in the event of a primary power source loss.
Guidance: An uninterruptible power supply (UPS) is an electrical system or mechanism that provides emergency power when there is a failure of the main power source. A UPS is typically used to protect computers, data centers, telecommunication equipment, or other electrical equipment where an unexpected power disruption could cause injuries, fatalities, serious mission or business disruption, or loss of data or information. A UPS differs from an emergency power system or backup generator in that the UPS provides near-instantaneous protection from unanticipated power interruptions from the main power source by providing energy stored in batteries, supercapacitors, or flywheels. The battery duration of a UPS is relatively short but provides sufficient time to start a standby power source, such as a backup generator, or properly shut down the system.

## Enhancements (2)
- PE-11(01) Alternate Power Supply — Minimal Operational Capability. Baselines: high
- PE-11(02) Alternate Power Supply — Self-contained
Each enhancement's statement: /api/v1/controls/PE-11?fields=enhancements

## Patterns that use it (1)
- Important (1): SP-002 Server Module

## Clauses by framework (45 frameworks)
- iso_27001_2022: A.7.5, A.7.11. OSA's own, not in NIST's crosswalk: A.7.5
- iso_27002_2022: 7.5, 7.11
- cobit_2019: DSS01, DSS05
- nist_csf_2: PR.IR-02, PR.IR-04. OSA's own, not in NIST's crosswalk: PR.IR-04
- soc2_tsc: A1.2
- bsi_grundschutz: INF.1, INF.2
- anssi: Hygiene.38, SecNumCloud.12.3
- osfi_b13: B-13.2.6
- finma_circular: IV.A(28), IV.E(89)
- bio2: 7.5, 7.11
- rbi_csf: Annex1.3, ITGRCA.18
- fisc: FISC.F2
- hkma_tme1: TME1.5.1
- mlps_2: 8.1.1.8
- dnb_good_practice: DNB.18.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: CTO-10
- cbn_csf: Part10
- sa_js2: JS2-PE
- bot_cyber: Ch2.8
- cpmi_pfmi: CG.RR, PFMI.P17
- eba_ict: 3.4.3
- ecb_croe: CROE.2.3.6, CROE.2.5.2
- ffiec_is: II.C.8
- hipaa_sr: §164.308(a)(7)(ii)(C), §164.310(a)(2)(i)
- iosco_cyber: PROT-5
- sebi_cscrf: PR.PE
- cmmc_2: PE
- nrc_73_54: RG5.71-B-PE
- api_1164: Sec 14
- isae_3402: Clause 4
- hitrust_csf: 08.b, 09.b
- iso_27799: 17.3
- lloyds_ms: PHYS.1
- solvency_ii: EIOPA-ICT-4.5
- csa_ccm_v4: BCR-11, DCS-14
- csa_aicm: BCR-11, DCS-14
- basel_sco60: SCO60.53, SCO60.65
- bssc: NOS-09
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-11
- Clauses only: /api/v1/controls/PE-11?fields=mappings
- Page for people: /controls/pe-11/