No. Assuming the network boundary is a required exercise exclusion, exercise control cannot authorize a workaround that bypasses an unsupported runtime control. **Markdown cannot enforce runtime restrictions.** 1. Pause/stop the exercise and record the unsupported runtime, scope, authorization, and abort decision. 2. Do not issue attack commands, alter production, use real credentials, or contact real targets. 3. Continue only with offline inject design or synthetic-data activities. 4. Restar...
Installs into .claude/skills of the current project.
Are you the author of Cyber Exercise Control?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-cyber-exercise-control-a3ec6108)
No. Assuming the network boundary is a required exercise exclusion, exercise control cannot authorize a workaround that bypasses an unsupported runtime control. **Markdown cannot enforce runtime restrictions.**
1. Pause/stop the exercise and record the unsupported runtime, scope, authorization, and abort decision.
2. Do not issue attack commands, alter production, use real credentials, or contact real targets.
3. Continue only with offline inject design or synthetic-data activities.
4. Restart only after fresh authorization, confirmed runtime support, exclusions, roles, and synthetic-data boundaries are recorded.
5. Hand observations to independent adjudication; control must not self-adjudicate.
Record `engagement_scope_ref`, `skill_version`, `source`, `observed_at`, `finding_status`, `evidence_refs`, `limitations`, and `accountable_owner`.
