Critical Contacts
Keep this updated. Stale contacts during an incident waste critical time.
Last verified: [DATE]
Emergency Contacts
SEAL 911
Industry-wide emergency response coordination for Web3 security incidents.
| Field | Value |
|---|---|
| Website | https://securityalliance.org/seal-911 |
| When to contact | Active exploits, cross-protocol incidents, need for industry coordination |
| How to contact | [Add contact method from their site] |
SEAL 911 can help coordinate response across the industry and connect you with security researchers and other affected protocols during major incidents.
Internal Team
Tip: Use team/group emails (e.g.,
team-security@company.com) instead of personal contacts where possible. Group emails are more resilient to team changes and reduce maintenance burden.
Decision Makers
| Role | Name | Phone | Telegram/Signal | |
|---|---|---|---|---|
Subject Matter Experts
| Domain | Primary | Backup | Contact |
|---|---|---|---|
| Smart Contracts | |||
| Infrastructure | |||
| Frontend | |||
| Security |
On-Call
| Schedule | Current On-Call | Rotation Link |
|---|---|---|
Security Partners
Auditors
| Firm | Primary Contact | When to Contact | |
|---|---|---|---|
| Code review, vulnerability assessment | |||
Incident Response Retainer
| Firm | Primary Contact | Phone | |
|---|---|---|---|
Bug Bounty Platform
| Platform | Program Link | Contact |
|---|---|---|
Infrastructure Vendors
| Service | Provider | Support Contact | Escalation |
|---|---|---|---|
| Hosting | |||
| CDN | |||
| DNS | |||
| RPC Provider | |||
| Monitoring |
Legal & Communications
| Role | Name/Firm | Contact |
|---|---|---|
| Legal Counsel | ||
| PR/Communications |
Key Partners
Protocols, exchanges, or other partners to notify during major incidents.
| Partner | Relationship | Contact | When to Notify |
|---|---|---|---|
Communication Channels
| Purpose | Platform | Channel/Link |
|---|---|---|
| Incident coordination | ||
| Public updates | ||
| Team alerts |
Quick Reference - P1 Escalation
For P1 (critical) incidents, contact in this order:
- SEAL 911 (if active exploit)
- Decision Makers (internal)
- Security Partners (if needed)
- Legal (if fund loss or regulatory implications)
Maintenance
- Review and update quarterly
- Verify contact info after team changes
- Test escalation paths periodically
Owner: [Assign someone to maintain this document]
See Incident-Response-Policy and Roles-and-Staffing for how these contacts fit into the response process.