White-team control should: 1. Immediately pause or stop the affected exercise activity—treat it as **scope drift** and do not make a silent scope change. 2. Preserve safety: do not alter production, use real credentials, contact real targets, or cross the synthetic-data boundary. 3. Notify the exercise lead and authorizing authority, then log the stop with the time, authority, scope reference, trigger, evidence, limitations, and accountable owner. 4. Hand the observation to independent adjudi...
Pro scans all 17 files and shows the line behind each finding
Scanned 9/24/2026
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill cyber-exercise-control --agent claude-codeInstalls 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 automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-cyber-exercise-control-agent-skills-standard)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
White-team control should:
1. Immediately pause or stop the affected exercise activity—treat it as **scope drift** and do not make a silent scope change.
2. Preserve safety: do not alter production, use real credentials, contact real targets, or cross the synthetic-data boundary.
3. Notify the exercise lead and authorizing authority, then log the stop with the time, authority, scope reference, trigger, evidence, limitations, and accountable owner.
4. Hand the observation to independent adjudication; white-team control must not self-adjudicate the result.
5. Restart only after fresh authorization and runtime safety gates are confirmed and a recorded restart decision exists. Otherwise, terminate the live activity and use an offline inject.
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!
