Provide the capability of shutting off power to [organization-defined] in emergency situations;
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill PE-10_emergency-shutoff --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of PE 10 Emergency Shutoff?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-pe-10-emergency-shutoff)More formats (shields.io, HTML) on the badges page.
---
name: "PE-10_emergency-shutoff"
description: "Provide the capability of shutting off power to [organization-defined] in emergency situations;"
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- pe-10
- pe
tech_stack:
- any
cwe_ids: []
chains_with:
- PE-15
prerequisites: []
severity_boost:
PE-15: "Chain with PE-15 for comprehensive security coverage"
---
# PE-10 Emergency Shutoff
## High-Level Description
**Family:** Physical and Environmental Protection (PE)
**Framework:** NIST SP 800-53 Rev 5
Emergency power shutoff primarily applies to organizational facilities that contain concentrations of system resources, including data centers, mainframe computer rooms, server rooms, and areas with computer-controlled machinery.
## What to Check
- [ ] Verify PE-10 Emergency Shutoff is documented in SSP
- [ ] Validate all 3 control requirements are implemented
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for PE-10
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for PE-10 implementation details. Verify the organization has documented how this control is satisfied.
### Step 2: Validate Implementation
```
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
```
### Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
## Tools
| Tool | Purpose | Usage |
| ------------- | --------------------------------- | ----- |
| Manual Review | Documentation and interview-based | N/A |
## Remediation Guide
### Control Statement
Provide the capability of shutting off power to [organization-defined] in emergency situations;
Place emergency shutoff switches or devices in [organization-defined] to facilitate access for authorized personnel; and
Protect emergency power shutoff capability from unauthorized activation.
### Implementation Guidance
Emergency power shutoff primarily applies to organizational facilities that contain concentrations of system resources, including data centers, mainframe computer rooms, server rooms, and areas with computer-controlled machinery.
## Risk Assessment
| Finding | Severity | Impact |
| --------------------------------------- | -------- | ------------------------------------------------ |
| PE-10 Emergency Shutoff not implemented | Medium | Physical and Environmental Protection |
| PE-10 partially implemented | Low | Incomplete Physical and Environmental Protection |
## CWE Categories
| CWE ID | Title |
| ------ | --------------------- |
| N/A | No direct CWE mapping |
## References
- [NIST SP 800-53 Rev 5 - PE-10](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=pe-10)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)
## Checklist
- [ ] Control documented in SSP
- [ ] Implementation evidence collected
- [ ] Operating effectiveness validated
- [ ] Continuous monitoring in place
- [ ] Related controls (PE-15) reviewed
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!