What PE-12 emergency lighting requires and why assessors check it
If an SP 800-53 assessment is coming and PE-12 is in your system's baseline, the question is whether the facility housing the system has automatic emergency lighting that switches on during a power outage or other disruption and covers emergency exits and evacuation routes. SP 800-53B allocates PE-12 to the low, moderate and high baselines, so every federal or FedRAMP-aligned system in scope will be tested on it. The risk behind the control is practical: if the lights fail with the power, people cannot leave the building safely, and staff who must reach racks, consoles or shutdown equipment during an event may be unable to do so. Assessors look for a working capability, not a plan on paper, so confirm early who in your organization owns the lighting, which battery or generator supply feeds it, and when the system was last tested.
What makes PE-12 hard is ownership. The control sits in the physical plant, and facilities or building management usually controls the fixtures, batteries and test schedules, while the IT team owns the system and its evidence. IT screenshots or monitoring dashboards alone will not satisfy an assessor who asks for emergency lighting documentation, test records and a walk-through of exits and evacuation routes. The practical step is a written request to facilities for the lighting inventory, the most recent test records and the evacuation route drawings, followed by a site walk with an interviewer ready to speak with the person responsible for emergency lighting and planning. Ask the building owner which parts of the facility are covered if your system is hosted in a shared or colocated space.
PE-12 has one control enhancement, and no SP 800-53B baseline allocates it, so the baseline obligation is the base control. The control connects to CP-2 (contingency plan) and CP-7 (alternate processing site), because an outage that drives staff out of the building is also a contingency event that your recovery plan should anticipate. Check that your contingency plan references the facility lighting and evacuation behavior, and that the scenarios you exercise include a loss of power at the site. Confirm the exact enhancement wording and assessment objects in the NIST CPRT catalog entry for PE-12 before you build the evidence list.
Which facilities, systems and teams fall under PE-12 scope
PE-12 applies to the physical facility that houses the system, not to the system alone. Scope follows where the components sit, which baseline the system is categorized under, and who controls the building, the power and the emergency lighting on any given day.
The facility housing the system
PE-12 reaches the facility where the system resides, whether that is a dedicated data center, a server room, or an office floor holding a few racks or endpoints that process system data. Start with a list of every location that holds system components, including backup media and network closets. For each one, confirm whether emergency lighting covers the exits and evacuation routes that people would use to leave during an outage. Illustrative case: a server room on an upper floor may depend on a stairwell that the building's lighting does not cover.
Baseline applicability
PE-12 is allocated to the low, moderate and high baselines, so it applies to any system categorized at those impact levels. It is not part of the privacy baseline, so a privacy-only assessment does not test it. Confirm the system's impact categorization before scoping, because a system moved from low to moderate changes which PE controls the assessor will examine. Record the baseline choice and any tailoring decision in the security plan so the scope is traceable.
Facilities and building management
The facilities team or building management company usually owns the emergency lighting fixtures, their battery or generator backing, and their inspection schedule. They decide whether lighting covers the paths the system's staff would use. Ask facilities for the current test log, the fixture map, and the written responsibilities for repair. Without a named owner in facilities, the emergency lighting control has no one to answer the assessor's interview questions.
IT operations and system owners
IT operations owns the system's dependence on the facility. They know which racks, network closets and storage arrays would lose service during an outage, and which exits staff must use to reach them safely. They should document the emergency lighting in the contingency and evacuation planning that the system owner maintains. Ask IT operations to confirm that the list of covered locations matches the current asset inventory.
Colocation and cloud data center providers
When the system runs in a colocation facility or a cloud provider's data center, the organization may inherit emergency lighting from the provider rather than operating it directly. That inheritance must be documented. Review the provider's contract, security addendum or shared responsibility documentation for language on emergency lighting, testing and evidence. Request the provider's most recent test records or attestation summaries, and confirm with the provider which of those records it will share during an assessment.
Contingency planning links
PE-12 is related to CP-2 and CP-7, so emergency lighting is part of the broader contingency picture. Lighting matters during an outage that also halts power to the system, because staff may need to shut down equipment or leave the building in the dark. Check that the contingency plan names the facility's emergency lighting as part of the evacuation and recovery steps, and that the plan has been exercised with the facilities team present.
How an assessor tests PE-12 emergency lighting
This table maps the four SP 800-53A determination statements for PE-12 to the examine, interview and test methods an assessor uses, the evidence each one requests, and the findings that most often appear. Read it as a checklist of what to have ready before an assessment begins.
| Assessment element | What the assessor does | Evidence to prepare | Common finding |
|---|---|---|---|
| Policy and procedures (examine) | Reads the physical and environmental protection policy and the procedures that address emergency lighting, and checks that they cover the facility housing the system. | Approved PE policy and procedures naming an owner, a review cycle and the emergency lighting section. | Procedures exist but never mention emergency lighting, or the review date has lapsed. |
| Emergency lighting documentation (examine) | Compares the documented lighting design against the facility and confirms that the lighting is automatic and activates during a power outage or disruption. | Lighting design or inventory, battery or generator backup details, and a floor plan marking emergency exits and evacuation routes. | Documentation describes the fixtures but not the exits or routes they must cover. |
| Test records (examine) | Reviews emergency lighting test records to confirm that testing happens and that results are recorded and acted on. | Dated test logs with the tester's name, the fixtures tested, pass or fail results and corrective actions. | No defined test cadence, or gaps in the logs with no explanation. |
| Responsible personnel (interview) | Interviews the staff who own emergency lighting and facility planning to confirm their responsibilities and how they plan for outages. | Role assignments, contact lists and a short description of how facilities staff respond to a power loss. | Staff cannot name who maintains the lighting or who approves repairs. |
| Lighting mechanisms (test) | Observes or tests the emergency lighting mechanisms to confirm they activate and illuminate the exits and evacuation routes. | Results of a supervised activation test, photographs or a walkthrough record, and repair tickets for any failed units. | Lighting does not cover a route, such as a corridor between the server room and an exit, or a unit has failed and was not replaced. |
Implementing emergency lighting for a system facility
This sequence turns the PE-12 requirement into a verified state: a confirmed facility owner, mapped exits and evacuation routes, working battery-backed fixtures, a repeatable test schedule and records that an assessor can examine. Each step produces an artifact that feeds the next.
Confirm the facility and its owner
Identify the building, floor or room that houses the system, and the party that controls it, such as the organization, a colocation provider or a landlord. Where a third party controls the space, record which emergency lighting responsibilities sit with that party and which stay with your organization. The output is a short facility scope statement naming the owner, the address and the systems inside the boundary. Confirm this before any survey, because a lighting test that covers the wrong space produces evidence that does not support the control.
Survey exits and evacuation routes
Walk every route that people would use to leave the facility and the rooms that hold the system, and mark each emergency exit, stairwell, corridor and assembly path on a current floor plan. Note where the existing lighting does not reach. The output is a route map that lists each exit and evacuation path, its location on the plan and the fixtures that serve it. An assessor will compare this map against the facility as it actually is, so the survey should be dated and signed by the person who performed it.
Verify or install automatic battery-backed fixtures
Check each mapped route against the fixtures in place. For every fixture, confirm that it switches on automatically when primary power is lost, that it has a battery or equivalent backup, and that its coverage matches the route map. Where gaps exist, the facility owner or a licensed electrical contractor installs the missing units, following local fire and electrical codes. The output is an installation or verification record for each fixture, with location, model, and the date it was confirmed working. Keep the manufacturer documentation with the record.
Define the test schedule and record format
Set a recurring test schedule for the emergency lighting and write it into the physical and environmental protection procedures. Define what a test covers, such as a simulated outage at each route, the observed result for every fixture and the person who witnessed it. Confirm the required frequency with the facility owner and the policy your organization has adopted, because NIST does not set the interval for you. The output is a test log template with fields for date, route, fixture, result, tester and corrective action.
Assign responsibility for testing and records
Name one accountable owner for emergency lighting in the facility, and a backup, and record who performs each test and who reviews the results. Where a colocation provider or landlord runs the tests, put that duty in the contract or service agreement and keep the provider's reports as evidence. Assessors interview these people, so their roles should match the procedures. The output is a responsibility matrix that is approved by the control owner and kept with the physical and environmental protection documentation.
Run tests and sign the test log
Carry out tests on the defined schedule, using a simulated power loss or the facility's approved test method. Record the result for each fixture on the log, including any that failed to light, failed to hold charge or left a route uncovered. Have the tester and the reviewer sign each log entry. The output is a signed test log for each cycle, which is the evidence an assessor examines to see that the lighting works in practice and is maintained over time.
Tie test failures to the POA&M
When a fixture or route fails a test, open a corrective action with an owner and a target date, and record it in the plan of action and milestones for the system if the failure affects the control. Track it until a retest confirms the fix, then attach the retest result to the entry. The output is a closed POA&M item that shows the failure, the repair and the verification. Assessors look for this loop because it shows that failures are found and resolved rather than left open.
Package the evidence for assessment
Gather the route map, installation and verification records, test logs, responsibility matrix and POA&M entries into one folder mapped to the four determination statements in the assessment procedure for PE-12. Check that each document is dated, signed where required and matches the current facility. The output is an evidence package that the control owner can hand to an independent assessor. Your implementation partner can prepare this package, but the organization owns the control and the assessor issues any findings.
How emergency lighting connects to power and contingency planning
PE-12 only works if it is designed alongside the other power-related controls in the physical and environmental family and the contingency planning family. Emergency lighting is the part of the outage plan that keeps people able to move and act. The uninterruptible power supply under PE-11 keeps servers and network gear running long enough to shut down in an orderly way, and the emergency shutoff under PE-10 lets authorized staff cut power to equipment quickly in a hazard. Neither of those decisions answers a basic question: can staff reach the racks, find the exits and leave safely when mains power fails? Lighting is usually supplied from its own circuit or battery units, separate from the computing load, so it can fail independently of the UPS. Confirm with your facilities team which circuits feed the lighting, how long the battery units run, and whether any shutoff under PE-10 would also de-energize lighting on the evacuation route.
CP-2 (contingency plan) and CP-7 (alternate processing site) are the places where PE-12 becomes operational. A contingency plan for a facility outage should name who moves people out, who controls access to the room while power is down, and how staff continue to reach the site or an alternate location. Emergency lighting is part of that sequence because a plan that assumes staff can reach the server room in the dark is not a plan. Ask the operator of the plan to walk the outage scenario, including people movement and any access controls under PE-2 and PE-3 that depend on electronic door locks. If doors fail closed or badge readers lose power, staff may be unable to enter or leave, so the plan should state the fallback.
For evidence, the lighting test should show the lights activating on loss of mains power, not only that the fixtures work on a bench. Record a controlled interruption of the supply to the facility or to the relevant panel, with the time the mains was removed, the time the emergency lights came on, the duration they stayed lit, and the exit and evacuation routes they covered. Keep the record with the emergency lighting test records that assessors examine under PE-12, and link it to the CP-2 plan exercise and any lessons recorded for CP-4 testing. An assessor will look for the link between the test, the plan and the facility layout, so a clear route map and a dated log matter as much as the test itself.
Evidence that passes a PE-12 review
An assessor testing PE-12 looks for documents that show emergency lighting is designed, placed, tested and maintained, not just installed. The cards below cover the artifacts an examiner asks for and the routine that keeps each one current between assessments. The organization owns these records; an implementation partner can help structure them, and only an independent assessor concludes whether they meet the control.
Physical and environmental protection policy and procedures
The PE policy and the procedures beneath it should name emergency lighting explicitly, state who owns the capability, and say how it is tested and repaired. Assessors examine these documents first, because PE-12 asks for a documented capability and the procedures that operate it. Check that the policy names the facility and the system it protects, that the procedures refer to real test steps, and that the revision history shows a review date. Tie each procedure to a named role so the document does not go stale when staff change.
Emergency lighting documentation and floor plans
Keep a current inventory of emergency luminaires, exit signs and their coverage, with a floor plan marking each fixture and every emergency exit and evacuation route in the facility housing the system. Assessors compare the plan against the physical space, so a plan that predates a room change will fail. Record the fixture make, installation date and circuit or battery source for each unit. Reconcile the plan at each walkthrough and after any renovation or tenant change.
Dated test records of activation on power loss
PE-12 is only shown to work when there is evidence it activates during an outage or disruption. Keep dated test records for each functional test, showing the fixture or zone tested, the simulated loss, the observed result, the duration reached, and the tester's name. Record failures with the corrective action and the retest date. Ask whoever runs the tests to state the test interval in the procedure, then schedule the next test on a shared calendar with a sign-off by the facility owner.
Maintenance and battery replacement records
Battery-backed fixtures degrade, so assessors look for service history: inspections, battery replacement, lamp or driver repairs and the vendor or technician who performed them. Each entry should show the date, the unit identifier, the part replaced and the next due date. Keep warranty and service contracts with these records so a reviewer can see who is responsible for upkeep. Confirm with the manufacturer the battery service life and recommended replacement schedule for your fixtures, since those figures vary by product.
Link to contingency plans
PE-12 is related to CP-2 and CP-7 in the catalog, so emergency lighting should appear in the contingency plan's description of how people and systems respond to a facility outage. Check that the contingency plan references the lighting test records, names the alternate site or shutdown sequence if lighting fails, and assigns responsibility for evacuation guidance. Assessors often trace a finding across both families, so a cross-reference in each document saves rework during the assessment.
Recurring test calendar and sign-off
The practice that keeps every other artifact current is a single calendar that lists each test, inspection and document review with an owner and a due date. Each completed item needs a signature from the facility owner or security lead and a link to the record it produced. Review the calendar at least once a year and after any power or lighting change, and keep a record of who approved the revised schedule. Ask your implementation partner or auditor to confirm the interval your assessor expects before you finalize it.
What meeting PE-12 costs in money and effort
This table breaks down the cost components of meeting PE-12 emergency lighting, showing who is paid, whether each cost is one-time or recurring, and what drives it up or down. Use it to build a request for quote and to see where a facility survey and testing schedule will shape the budget. No prices or durations are given because none are supplied for this topic, so confirm each figure in writing with your contractor and your own facility.
| Cost component | Who is paid | One-time or recurring | What drives it and what to ask for |
|---|---|---|---|
| Emergency lighting fixtures and battery backup | Electrical contractor or lighting supplier | One-time, with replacement later | Number of fixtures, number of routes and exits, and battery type. Ask for fixture count, battery runtime stated by the manufacturer, and whether the quote covers exit signage. |
| Installation by licensed electricians | Licensed electrical contractor | One-time | Facility size, ceiling and wiring access, and whether work happens in a live data center. Ask for a site survey, permits included or excluded, and after-hours labor rates. |
| Functional testing of emergency lighting | Facility team or electrical contractor | Recurring | Testing frequency set in your own procedures, number of fixtures, and whether tests need downtime coordination. Ask for a test schedule, test procedure, and how records are returned to you. |
| Battery maintenance and replacement | Facility team or electrical contractor | Recurring, with periodic replacement | Battery age, operating environment, and test results. Older batteries that fail tests raise replacement cost. Ask for battery age records and a replacement plan tied to test results. |
| Documentation upkeep | Internal compliance or implementation partner | Recurring | Number of test records, how they are stored, and how often the PE policy and procedures are reviewed. Ask who maintains test logs and how evidence is retrieved for an assessor. |
| Assessor time for sampling | Independent assessor, paid by the organization | Recurring at each assessment cycle | Number of facilities in scope, number of routes sampled, and availability of records. Clean, dated test records usually shorten sampling. Ask the assessor for the sample plan before fieldwork. |
Who owns PE-12 and what an implementation partner can prepare
The organization owns PE-12 in full. Emergency lighting is a facility asset, so the facilities team owns the fixtures, their power source, their maintenance contracts and their testing schedule. The IT and security team owns the link between that facility control and the system it protects, including which rooms, exits and evacuation routes are in scope and how the records are kept for assessors.
- Fixtures and power: Confirm that automatic emergency lighting covers the emergency exits and evacuation routes in the facility housing the system, and that it activates on a power loss or disruption.
- Testing and maintenance: Run the scheduled functional tests, log the results and arrange repairs when a unit fails.
- Records: Keep emergency lighting documentation and test records that an examiner can read without help from the people who created them.
- Policy alignment: Make sure the physical and environmental protection policy and procedures name who is responsible for emergency lighting.
- Interviews: Make sure the named owners can explain the arrangement, because assessors interview the people responsible.
Before any outside party starts, check that the list of exits, routes and test records matches what the facility actually has.
An implementation partner such as DeployOpen prepares the systems, documents and evidence that an assessor will examine. The partner does not own the lighting, does not decide whether the control is met and does not issue assessment results. Its work is preparation: organizing what the organization already does into a form an independent assessor can test against the SP 800-53A procedure.
- Evidence package: Assemble the policy references, emergency lighting documentation and test records into a single, indexed package mapped to the PE-12 determination statements.
- Route mapping: Prepare a map of emergency exits and evacuation routes in the facility, reconciled with the lighting layout provided by the facilities team.
- Test log templates: Provide templates that record each functional test, the person who ran it, the result and the corrective action.
- POA&M entries: Draft plan of action and milestones entries for any gaps, so the organization can track remediation to closure.
- Contractor coordination: Coordinate with the electrical contractor that installs, repairs or certifies the emergency lighting, so their reports reach the evidence package.
Ask any partner to put the preparation scope, deliverables and handover in writing before work starts.
The independent assessor, not the organization and not the implementation partner, decides whether PE-12 is satisfied. SP 800-53A gives the assessor four determination statements for PE-12, assessed through the examine, interview and test methods. The assessor examines documents, interviews the responsible personnel and tests the lighting mechanisms, then records findings in an assessment report.
- Examine: Review the physical and environmental protection policy, procedures, emergency lighting documentation, test records and the exit and route layout.
- Interview: Speak with personnel responsible for emergency lighting and for facility planning.
- Test: Observe the mechanisms that provide emergency lighting, usually by simulating a power disruption in a controlled manner.
- Report: Issue the assessment report with findings. Only the assessor's report counts as the assessment result.
- Independence: Confirm that the assessor is independent of the team that prepared the evidence.
Confirm with the organization's authorizing official or contract owner which assessor is acceptable and what the assessment scope requires.
Where PE-12 evidence usually falls short
Most PE-12 findings are not about missing lights. They come from evidence that cannot be shown to an assessor: unmarked routes, undocumented tests, and provider responsibilities nobody confirmed. Each card below names one gap and the check that closes it before an assessor arrives.
Routes missing from floor plans
PE-12 covers emergency exits and evacuation routes within the facility, so the assessor will expect those routes to be identifiable on documentation. If the floor plan does not mark exits, paths to them, and the lights that cover them, the coverage claim cannot be checked. Compare the plan against a walkthrough of the room housing the system. Close it by marking every exit and evacuation route on the current floor plan and tying each route to the lighting circuit that serves it.
Tests recorded only verbally
A facilities manager who says the lights were checked is not evidence. Assessors look for test records that name the date, the person, the fixtures or circuits tested, and the result, which is the form the examine method for emergency lighting test records calls for. Verbal confirmation also leaves no trail to show what was fixed. Close it by requiring a written or system-generated test record for every emergency lighting test, retained with the other PE documentation.
Lights tested without a simulated outage
Pressing a test button on a fixture does not show that the emergency lighting activates when the main supply fails. The test method in SP 800-53A Rev. 5 expects mechanisms that support the emergency lighting capability to be tested, and an outage-style test is the closest match. Confirm which tests simulate loss of normal power and which only check battery or lamp status. Close it by scheduling a documented test that removes normal power to the area and confirms the lights take over along the defined routes.
Colocation provider evidence not requested
When the system sits in a colocation or hosted facility, the emergency lighting belongs to the provider, but the organization still needs to show PE-12 is met. Many teams never ask the provider for test records or outage test results, so the gap appears only at assessment time. Check what the contract and service description commit the provider to, and whether reports can be requested. Close it by adding a request for emergency lighting test records and the most recent outage test result to the provider's audit evidence list.
Test failures absent from the POA&M
When an emergency lighting test fails, the failure is a control weakness that should be tracked until fixed. If failed tests are repaired but never entered in the plan of action and milestones, the assessor sees a known gap with no record of ownership, due date or closure. Link each failed PE-12 test to a POA&M entry with a named owner. Close it by logging every failed emergency lighting test as a POA&M item and recording the closing test that proves the repair.
Common questions about PE-12 emergency lighting
What does emergency lighting for PE-12 cost, and what drives the price?
The cost depends on the facility, not on the control text, so no fixed figure applies. Most spend goes to the lighting hardware itself, including battery or self-contained fixtures, and to electrical work where new circuits or fixtures are needed. Recurring costs include battery replacement, periodic testing labor and maintenance contracts. Costs rise with the size of the floor area, the number of exits and evacuation routes, building age and how much wiring must change. Ask any contractor for a quote that lists fixtures, installation, testing and recurring maintenance as separate lines, and confirm which items the facility owner's electrical contractor or building services team will supply.
How long does it take to get emergency lighting ready for an assessment?
There is no fixed duration because it depends on facility condition. A building with existing emergency fixtures that are documented and tested may need only records and a test cycle. A facility that lacks coverage for exits or evacuation routes may need design, procurement, electrical work and inspection before any test evidence exists. Lead times for fixtures and permits, along with access windows for work in an occupied or live data center, often set the schedule. Ask for a written plan that sequences the site survey, remediation, testing and evidence collection, and confirm local code and inspection requirements with the building authority.
Can our own facilities team implement PE-12 without an outside partner?
Often yes, provided the team has electrical competence, knows the building's egress design and can keep records that an assessor will accept. The organization owns PE-12 and must be able to show that emergency lighting is in place, maintained and tested. Internal teams commonly handle the survey, test scheduling and record keeping, while licensed electricians handle installation and any code-required inspections. An outside partner can help with the gap analysis, documentation templates and evidence preparation, but it does not certify the control. An independent assessor reviews the results and issues any report.
What should we ask a partner before hiring one for emergency lighting work?
Ask for a written scope that names the facilities covered, the exits and evacuation routes in each, and the deliverables. Confirm whether the partner prepares evidence only or also manages installation through licensed trades. Ask how the partner documents the current state, what test records it will produce, and how it hands over policy and procedure material for PE-1. Clarify who holds permits, who pays subcontractors and how changes to scope are priced. Confirm that the partner understands that assessors, not the partner, issue any report. Request references you can verify independently.
Does a colocation provider's facility automatically satisfy PE-12 for our system?
Not automatically. PE-12 applies to the facility housing the system, so the provider's emergency lighting may cover the building, but the organization still needs to know it applies to the spaces where its equipment sits and the routes staff would use. Review the provider's documented emergency lighting, test records and any third-party assessment reports it can share, and confirm these cover the relevant hall or cage. Contract terms should set out what evidence the provider supplies and how often. Where the provider's evidence is incomplete, the organization must document the gap in its own risk management and assess it.
How often should emergency lighting be tested to meet PE-12?
The control requires the lighting to be employed and maintained, but the test interval is set by the organization's own defined policy and by local fire and building codes, which may specify frequency and duration. Assessors look for a defined interval, records showing the tests happened, and evidence that failed fixtures were repaired. Ask the facility owner or local authority which intervals apply, then write them into your procedures. Keep test logs with dates, results, the tester's name and corrective actions so they can be produced during an assessment.
How DeployOpen prepares PE-12 evidence for a system
DeployOpen scopes PE-12 under a written, fixed-scope agreement that names the facility, the systems it houses, the emergency lighting circuits and fixtures in scope, and the people who will sign off on the evidence. Before work starts, the client and DeployOpen agree which emergency exits and evacuation routes count as in scope, who maintains the lighting and who owns each test. The client keeps ownership of the control itself: the lighting must be installed, maintained and tested by the organization or its facilities contractor. DeployOpen's role is to prepare the documents and evidence that let an assessor check that work, drawing on the four determination statements in SP 800-53A for PE-12.
For a typical engagement, DeployOpen prepares a route map that marks each emergency exit and evacuation path against the lighting fixtures that cover it, a test template for periodic functional tests of the lighting under a simulated power loss, and an evidence package that indexes the policy and procedures, maintenance records, test records and documentation an assessor will examine. The test template records the date, tester, fixtures checked, observed result and corrective action, so that each test can be traced to a finding. Where the client uses contractors for electrical or facilities work, DeployOpen can review what those contractors deliver and help the client request matching records, but the contractor and the client remain responsible for the work itself.
Quotes follow from the written scope. DeployOpen does not publish a price list, so the proposal will reflect the number of buildings and routes, the state of existing fixtures and documentation, and how much of the evidence the client wants packaged. Clients should ask for the deliverables, the handover format, and which items the client must supply, such as floor plans and facilities records. DeployOpen does not issue audit reports, attestations or certifications. An independent assessor or certification body makes that determination, so the agreement should state what evidence will be handed to the assessor and who presents it.
