Security Event Response

This is a Hermes-native security-event-response workflow skill.

Why This Exists

security-event-response exists because an event had no owner: security-safety-review and application-threat-model review a design before it ships, and a CVE, a committed secret, or a license question was answered by onboarding, review, or an achievements lane with no containment order at all.

First Steps

• Classify the event and state its exposure window before proposing any step.
• For a leaked secret, order the rotation and its observed rejection before any history rewrite.

Do Not Use When