SOOperating StrikeOps
Integrations and data sovereignty
How StrikeOps runs on your own accounts and keys: setting the Anthropic key first, connecting recon and messaging providers, understanding where secrets live, setting daily caps, and pointing encryption at your own AWS KMS key with a kill-switch.
Advanced4 min readprofessional streamUpdated Sat Aug 01 2026 00:00:00 GMT+0000 (Coordinated Universal Time)
Learning objectives
- Explain the bring-your-own model and why the Anthropic key is set first and fails safe.
- Describe where integration secrets live and how per-tenant isolation and daily caps protect spend.
- Enable BYO-KMS by creating a key, adding the grant, and verifying before use.
- Describe the revoke kill-switch behaviour and what full-lock sealing the connection means.
Operating StrikeOps
Available to StrikeOps operators
Operating StrikeOps trains you on the platform itself, so it is reserved for licensed StrikeOps firms and their operators.
- The full Operating StrikeOps track
- Deploy agents, run engagements, and report with the platform
- Unlocks automatically for signed-in operators
Already at a StrikeOps firm? Sign in to unlock.