Back to catalog
SEA-07.3SEASecure Engineering & Architecture
Fail Safe
Description
Mechanisms exist to implement fail-safe procedures when failure conditions occur.
Cross-Mappings
6 paths across 3 frameworks
Cross-Mappings
NIST 800-531 mapping
SI-17
1.00
- Secure Controls Framework · 2026.2 · scf_strm · equivalent
CCI3 mappings
CCI-002773
1.00
- Secure Controls Framework · 2026.2 · scf_strm · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
CCI-002774
1.00
- Secure Controls Framework · 2026.2 · scf_strm · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
CCI-002775
1.00
- Secure Controls Framework · 2026.2 · scf_strm · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
STIG2 mappings
SV-205221r987708_ruleThe DNS server implementation must follow procedures to re-role a secondary name server as the master name server should the master name server permanently lose functionality.
1.00
- Secure Controls Framework · 2026.2 · scf_strm · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
- DISA · 4 · disa_xccdf · related
SV-214199r612370_ruleThe DNS server implementation must follow procedures to re-role a secondary name server as the master name server should the master name server permanently lose functionality.
1.00
- Secure Controls Framework · 2026.2 · scf_strm · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
- DISA · 2 · disa_xccdf · related
Control mappings provided by the Secure Controls Framework (SCF).
SCF
Powered by the Secure Controls Framework
The control catalog, cross-mappings, and STRM relationship data shown here are provided by the Secure Controls Framework (SCF), 2026.2. Every mapping is credited to SCF as the methodology, with the SCF reference and version stored alongside it.
© SCF Council, LLC. Secure Controls Framework content is free and shown here with attribution. securecontrolsframework.com · About SCF on STIGViewer