Emergency Lighting

To meet the FedRAMP Moderate emergency lighting requirement, you must deploy and maintain automatic emergency lighting that turns on during a power outage or disruption and illuminates emergency exits and evacuation routes in the facility where the system is hosted. Prove it works through documented testing, maintenance, and facility walkdowns tied to your system boundary. (NIST Special Publication 800-53 Revision 5)

Key takeaways:

• Automatic activation is mandatory; flashlights and ad-hoc procedures do not satisfy PE-12. (NIST Special Publication 800-53 Revision 5)
• Coverage must include emergency exits and evacuation routes, not only data hall aisles. (NIST Special Publication 800-53 Revision 5)
• Auditors will expect evidence of maintenance and functional tests, plus boundary-scoped documentation for each applicable site. (NIST Special Publication 800-53 Revision 5)

Emergency lighting is a physical security and life-safety control that FedRAMP assessors treat as both a facility requirement and a systems requirement. Under NIST SP 800-53 Rev. 5 PE-12, your obligation is straightforward: your hosting facility must have automatic emergency lighting that activates during a power disruption and provides lighting along emergency exits and evacuation routes. (NIST Special Publication 800-53 Revision 5)

For a CCO or GRC lead, the hard part is rarely buying lights. The hard part is scoping: determining which facilities are “within the system boundary,” translating building-level life-safety features into control evidence, and creating a repeatable operating rhythm (tests, maintenance, exceptions, and records retention). This page focuses on rapid operationalization: what to confirm with the landlord or colocation provider, what to demand from a third party data center, what your internal facilities team must document, and what artifacts an assessor will accept.

If you run in multiple sites (HQ office, network rooms, data centers, logistics spaces), treat PE-12 as a site-by-site control with site-specific evidence. If a third party operates the facility, your job becomes a due diligence and contract-evidence problem, not a wrench-and-ladder problem.

Regulatory text

Requirement (PE-12): “Employ and maintain automatic emergency lighting for the system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility.” (NIST Special Publication 800-53 Revision 5)

What the operator must do:

1. Employ emergency lighting that is automatic (it activates during an outage/disruption without human intervention). (NIST Special Publication 800-53 Revision 5)
2. Maintain it so it remains operational over time (planned maintenance and corrective repair). (NIST Special Publication 800-53 Revision 5)
3. Ensure lighting covers emergency exits and evacuation routes in the facility supporting the system (not just equipment areas). (NIST Special Publication 800-53 Revision 5)

There are no enforcement case sources provided for this requirement, so this page focuses on assessment expectations and operational risk.

Plain-English interpretation (what PE-12 means in practice)

If power fails, people must still be able to safely exit the parts of the building that support your FedRAMP system. PE-12 expects a built-in, automatically triggered lighting capability that makes egress routes and exit doors visible long enough to evacuate in an orderly way. (NIST Special Publication 800-53 Revision 5)

For compliance, your proof must show two things:

• Design/coverage: the relevant routes and exits are covered by emergency lighting. (NIST Special Publication 800-53 Revision 5)
• Operations: you keep it working through maintenance and testing, and you can produce records. (NIST Special Publication 800-53 Revision 5)

Who it applies to (entity and operational context)

PE-12 applies when you operate or inherit physical facilities that support the information system in scope for FedRAMP Moderate, including:

• Cloud Service Providers (CSPs): data centers, colocation cages/suites, offices with production administration workstations, network POPs, storage rooms holding in-scope media, or any facility space inside the system boundary. (NIST Special Publication 800-53 Revision 5)
• Federal agencies: agency facilities hosting or operating components of the in-scope system. (NIST Special Publication 800-53 Revision 5)

Scoping decision points (practical)

Treat emergency lighting as in scope when any of the following are true:

• The space houses system components (servers, network gear, security appliances) for the in-scope system.
• The space is used for privileged administration of the system (for example, an operations room).
• The space stores in-scope media or backups.

Treat it as inherited when the building is managed by a third party (landlord, colocation provider, data center operator). You still need evidence and you still own the risk.

What you actually need to do (step-by-step)

Step 1: Define the “facility” and map the egress routes

• Identify each physical site supporting the in-scope system. Create a short “site register” with address, owner/operator, and what in-scope assets/functions exist there.
• For each site, obtain or create a simple floor plan highlighting:
  • In-scope spaces (data room, cage, network room, ops area).
  • Emergency exits serving those spaces.
  • Evacuation routes from those spaces to exits. (NIST Special Publication 800-53 Revision 5)

Operator tip: Assessors commonly ask, “Show me the route.” A marked-up plan plus a short walkthrough script makes this easy.

Step 2: Confirm emergency lighting is automatic and outage-triggered

• Validate that emergency lights activate on power loss/disruption automatically. (NIST Special Publication 800-53 Revision 5)
• Capture evidence that the fixtures are not just normal lights connected to a generator circuit with manual switching. If the building relies on centralized emergency power plus automatic transfer, document how that results in automatic illumination for egress.

If a third party runs the site, request their statement of how emergency lighting activates and what components provide it (for example, battery-backed fixtures, inverter systems, or emergency circuits).

Step 3: Verify coverage meets the requirement (exits + evacuation routes)

• Perform a walkdown from in-scope spaces to exits.
• Confirm emergency fixtures are present and reasonably placed to illuminate:
  • Corridor turns and intersections
  • Stairwells
  • Exit doors and exit signage
  • Any path from the in-scope area to the exit discharge (as applicable to the facility layout) (NIST Special Publication 800-53 Revision 5)

Document gaps as findings. Create work orders or third-party tickets for remediation.

Step 4: Put maintenance and testing into an operating rhythm

PE-12 requires you to maintain emergency lighting. (NIST Special Publication 800-53 Revision 5) Translate that into:

• A maintenance procedure (who does it, what “pass/fail” means, how issues are escalated).
• A testing plan (functional checks, battery health checks where applicable, and post-change validation after electrical work).
• A repair process with timelines defined by your internal risk appetite and facilities SLAs (avoid hard numeric commitments unless you can meet them).

If the facility is operated by a third party:

• Require maintenance and test records as part of your due diligence package.
• Add contract language or an MSA/SOC addendum requiring the provider to supply records upon request and notify you of impairments affecting egress lighting in your areas.

Step 5: Tie it to your FedRAMP documentation set

• Update the SSP/control narrative for PE-12 to specify:
  • Which sites are in scope
  • Whether emergency lighting is provider-managed (inherited) or customer-managed
  • Where evidence is stored and who is accountable for requests during assessment (NIST Special Publication 800-53 Revision 5)
• Maintain a site-by-site evidence folder so an assessor can sample a location and get everything quickly.

Step 6: Validate after changes

Trigger re-validation when:

• You move cages/suites or expand into new space.
• Construction changes egress routes.
• Electrical work, generator work, or UPS/inverter changes occur.
• You onboard a new data center/colocation provider.

A lightweight “post-change PE-12 check” prevents the common drift where floor plans and routes become stale.

Required evidence and artifacts to retain

Keep artifacts per site. Aim for assessor-ready packages:

Coverage and design

• Marked-up floor plan showing in-scope areas, evacuation routes, and emergency exits. (NIST Special Publication 800-53 Revision 5)
• Photo log of emergency fixtures and exit routes relevant to the in-scope areas (include location notes).
• Statement of responsibility matrix (RACI) showing who maintains emergency lighting (internal facilities vs third party).

Operations and maintenance

• Emergency lighting maintenance/testing procedure.
• Maintenance logs or inspection records (from your facilities team or third party).
• Work orders and repair tickets for failed fixtures, plus closure evidence.
• Change management records that show re-checks after layout/electrical changes.

Third-party due diligence (if inherited)

• Contract clauses or service descriptions indicating emergency lighting is provided and maintained by the facility operator.
• Attestations or compliance letters from the facility operator specifically addressing emergency lighting for exits/routes.

Common exam/audit questions and hangups

Expect these lines of inquiry:

• “Which facilities are in your system boundary, and which routes/exits apply?” Assessors want boundary clarity, not a generic building claim.
• “Show me evidence that lighting activates automatically during an outage.” (NIST Special Publication 800-53 Revision 5)
• “How do you know routes and exits are covered, not just your data hall?” (NIST Special Publication 800-53 Revision 5)
• “Show maintenance/testing records and how you handle failures.” (NIST Special Publication 800-53 Revision 5)
• “If this is inherited from a colocation provider, where is the evidence and who reviews it?”

Hangups that slow audits:

• Evidence is building-wide but not mapped to the in-scope area.
• You have a policy but no logs, tickets, or records of actual testing/repair.
• The provider gives generic facility brochures instead of inspection/maintenance artifacts.

Frequent implementation mistakes (and how to avoid them)

1. Relying on portable flashlights or phone lights. PE-12 calls for automatic emergency lighting, not a manual workaround. (NIST Special Publication 800-53 Revision 5)
   Fix: Document installed emergency fixtures or an automatic emergency power system that lights the egress path.

2. Documenting only the data hall. The requirement explicitly includes emergency exits and evacuation routes. (NIST Special Publication 800-53 Revision 5)
   Fix: Walk the full path from your in-scope area to the exit and capture it on the floor plan.

3. Assuming the landlord “has it handled” with no evidence. Inheritance does not remove your need to prove compliance.
   Fix: Add evidence requests to your third-party oversight checklist and renew them on your review cadence.

4. Stale routes after renovations or cage moves. Egress changes break your documentation first, then your actual coverage.
   Fix: Add PE-12 to your facilities change checklist and require a new marked-up plan after changes.

Enforcement context and risk implications

No public enforcement case sources were provided for PE-12. Operationally, treat emergency lighting as a control that reduces:

• Life safety risk during evacuations.
• Business interruption risk when outages coincide with incidents requiring evacuation.
• Assessment risk because PE controls are commonly validated through site walkthroughs and evidence sampling. (NIST Special Publication 800-53 Revision 5)

If you are heavily dependent on third party data centers, PE-12 also becomes a third-party risk management issue: you need contractual access to evidence and a defined path for impairment notifications.

Practical 30/60/90-day execution plan

First 30 days (stabilize scope and evidence requests)

• Build the site register for all in-scope facilities.
• Identify which sites are third party operated and send an evidence request for emergency lighting maintenance/testing records.
• Perform at least one internal walkdown for a representative site and create the marked-up floor plan template you will reuse.
• Draft the PE-12 procedure (who owns it, where records go, what triggers re-validation).

Days 31–60 (close gaps and formalize operations)

• Complete walkdowns (or remote validations with the provider) for each in-scope site.
• Open remediation tickets for coverage gaps, failed fixtures, or missing documentation.
• Update SSP narratives and your control evidence index so PE-12 can be produced on demand. (NIST Special Publication 800-53 Revision 5)
• Add PE-12 checkpoints to facilities change management and third-party review checklists.

Days 61–90 (prove repeatability)

• Run your first full cycle of maintenance/testing documentation collection (internal or provider-supplied).
• Conduct a tabletop “audit pull” where someone unfamiliar with the site attempts to retrieve PE-12 evidence within a short window.
• Normalize exceptions: if a site cannot provide records, escalate through third-party risk governance and document compensating actions (extra walkdowns, contract updates, or alternative facility selection).

Where Daydream fits (practical, non-disruptive)

If you manage multiple facilities and third parties, Daydream can serve as the system of record for PE-12 by tracking site scoping, assigning evidence requests to facility operators as third parties, and keeping walkthrough artifacts, tickets, and SSP mappings in one place for assessor pulls.

Frequently Asked Questions

Does emergency lighting have to be inside the data center room itself?

PE-12 requires coverage for emergency exits and evacuation routes within the facility supporting the system. If the route from your in-scope area includes corridors, stairwells, or antechambers, those segments need coverage too. (NIST Special Publication 800-53 Revision 5)

We’re in a colocation facility. Can we inherit this control?

Yes, the colocation provider can operate and maintain emergency lighting, but you still need evidence. Get maintenance/testing records and document which parts are inherited versus customer-managed in your control narrative. (NIST Special Publication 800-53 Revision 5)

What evidence is most persuasive to assessors?

A marked-up floor plan tied to your system boundary, a short photo log of the egress route, and recent maintenance/testing records. Pair those with a clear owner and a process for handling failures. (NIST Special Publication 800-53 Revision 5)

What counts as “automatic” activation?

Automatic means the lighting activates upon a power outage or disruption without a person taking action. If activation depends on manual switching or staff intervention, it will be hard to defend as compliant with PE-12. (NIST Special Publication 800-53 Revision 5)

How do we handle multi-tenant buildings where we don’t control common areas?

Treat common-area emergency lighting as inherited and collect the landlord or facility operator’s records for those areas. Your responsibility is to ensure the evacuation route from your in-scope space to the exit is covered and maintained, even if you do not own the fixtures. (NIST Special Publication 800-53 Revision 5)

What if a fixture fails between scheduled inspections?

Document the detection path (walkthroughs, staff reporting, provider monitoring) and the repair ticket workflow. PE-12 is about maintenance over time, so show that failures are tracked to closure and that risk is managed while repairs are pending. (NIST Special Publication 800-53 Revision 5)