Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

NIST SP 800-53 Learning Center

PE-18 — Location of System Components

Read the official control and assessment content, then use the separately labeled Bare Metal Cyber perspective to connect the requirement to implementation, evidence, and sustained operation.

1Enhancements
1Parameters
1Baseline memberships
3Assessment methods

PE — Physical and Environmental Protection · NIST SP 800-53 Release 5.2.0

High
Official NIST control content

Control statement

Position system components within the facility to minimize potential damage from [Organization-defined: physical and environmental hazards] and to minimize the opportunity for unauthorized access.

Official NIST discussion

Discussion

Physical and environmental hazards include floods, fires, tornadoes, earthquakes, hurricanes, terrorism, vandalism, an electromagnetic pulse, electrical interference, and other forms of incoming electromagnetic radiation. Organizations consider the location of entry points where unauthorized individuals, while not being granted access, might nonetheless be near systems. Such proximity can increase the risk of unauthorized access to organizational communications using wireless packet sniffers or microphones, or unauthorized disclosure of information.

Official OSCAL parameters

Organization-defined parameters

These values must be resolved through the organization’s tailoring and governance process. Bracketed parameter references in the control text identify where a decision is required.

physical and environmental hazardsphysical and environmental hazards that could result in potential damage to system components within the facility are defined;
Original Bare Metal Cyber perspective

From control text to operational evidence

Use Location of System Components as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to physical access, facility protection, environmental safeguards, and visitor accountability.

Implementation workflow

  • Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
  • Resolve each organization-defined parameter before declaring the control implemented.
  • Document how the implementation satisfies every clause of the official control statement.
  • Collect evidence as a normal byproduct of operation rather than only before an assessment.
  • Review exceptions, changes, and monitoring results on a risk-based cadence.

Evidence examples

  • badge and visitor logs
  • physical access reviews
  • facility diagrams and sensor records
  • environmental and power test results

Common failure patterns

  • logical security assumptions invalidated by physical access
  • tailgating and visitor exceptions normalized
  • critical infrastructure not included in access reviews
  • environmental alarms not integrated into response

Questions practitioners should ask

  • What risk decision is this control intended to support in this system?
  • Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
  • Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
  • What event or threshold requires the implementation to be reviewed or changed?
Official NIST SP 800-53A content

Assessment objectives and methods

Show the assessment objective

system components are positioned within the facility to minimize potential damage from [Organization-defined: physical and environmental hazards] and to minimize the opportunity for unauthorized access.

Examine

  • Physical and environmental protection policy
  • procedures addressing the positioning of system components
  • documentation providing the location and position of system components within the facility
  • locations housing system components within the facility
  • list of physical and environmental hazards with the potential to damage system components within the facility
  • system security plan
  • other relevant documents or records

Interview

  • Organizational personnel with responsibilities for positioning system components
  • organizational personnel with information security responsibilities

Test

  • Organizational processes for positioning system components
Official relationships

Related controls

These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.

Official NIST enhancements

Control enhancements

Enhancements add specificity, strength, or scope to the base control. Baseline badges show explicit selections in the official SP 800-53B OSCAL profiles.

Official NIST control enhancement

PE-18(1) — Facility Site

Withdrawn

This enhancement is marked withdrawn in the official OSCAL catalog. Related-control metadata below may identify where its intent was incorporated.

Source record

Authoritative sources