Skip to content

security: add a runbook for responding to a compromised admin key #464

Description

@Idaonoli

Scope

SECURITY.md covers vulnerability disclosure, but there's no operational runbook for an issuer whose admin key is compromised — which contracts have an upgrade path that could help, which don't and would need a full redeploy, and what circuit-breaker/pause actions are available as an immediate stopgap.

Acceptance criteria

  • Add a compromised-admin-key runbook to SECURITY.md or a new docs/incident-response.md, covering immediate mitigation (freeze/pause) and longer-term recovery per contract

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave programcomplexity: mediumModerate scope, some contract/domain knowledge helpfuldocumentationImprovements or additions to documentationhelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions