K05 assurance architecture
Authority and mission boundary is explicit
Direct answer
Every automated protection action and any external mission support is traceable to a competent authority, named asset scope, allowed effects, prohibited outcomes, duration, stop conditions, and review route.
Evidence boundary. These records describe architecture, control relationships, test requirements, and legal-source status. They do not certify a facility, authorize a mission, prove deployment, or replace current facility-specific engineering and legal review.
Claim
Every automated protection action and any external mission support is traceable to a competent authority, named asset scope, allowed effects, prohibited outcomes, duration, stop conditions, and review route.
Argument
Speed is useful only after authority and consequence boundaries are established; technical access must not create its own mandate.
Evidence requirements
- signed authority record
- asset and identity scope
- allowed-action matrix
- prohibited outcomes
- deconfliction record
- expiry and revocation evidence
- review and appeal path
Assurance defeaters
- missing authority
- expired approval
- ambiguous asset ownership
- unresolved jurisdiction
- action outside approved effect envelope
Hazards
- unauthorized access
- third-party impact
- mission conflict
- unreviewed escalation
Recovery objectives
- automatic action stop on authority failure
- preserve signed decision state
- restore least-privilege baseline
Site-tailoring questions
- operator and licensee roles
- government mission authority
- third-party service boundaries
- jurisdiction and contract
Sources and record
Expanding Capabilities to Combat Transnational Cyber-Enabled Crime · 10 CFR Part 73 Subpart J — Security Requirements at Commercial Nuclear Plants