Disaster Recovery Guide¶
This guide explains how customers should report service disruptions for applications deployed via Game Warden. Prompt, accurate reporting helps Second Front (2F) respond quickly and effectively.
When to report¶
Operational disruptions such as outages, data loss, or critical service degradation that may require recovery procedures.
Common event types:
| Event Type | Description |
|---|---|
| Service Unavailability | The application is completely inaccessible to end-users (e.g., 503 errors, timeouts) due to underlying platform or infrastructure issues. |
| Data Loss or Corruption | Persistent data (databases, object storage) is accidentally deleted, corrupted, or rolled back to an incorrect state. |
| Cloud Region/Zone Outage | A major failure of the underlying hyperscaler IaaS provider (e.g., AWS/Azure) affecting the hosting region or availability zone. |
| Platform Component Failure | Essential PaaS services required for the application to run (e.g., Ingress controller, DNS, authentication services) are non-functional. |
| Malicious Data Destruction | A security compromise (such as ransomware or insider threat) that results in data encryption or deletion, requiring restoration from backups. |
| Resource Exhaustion | The application or platform runs out of critical resources (storage, compute quotas) causing a crash that requires intervention to restore service. |
| Failed Deployment/Upgrade | A platform or application update results in a catastrophic failure where standard rollback procedures fail, requiring a full recovery. |
Important
If you’re not sure which category applies, report the event anyway. Our team will triage and route appropriately.
How to report¶
Notify 2F¶
The below listed options are in priority order to ensure the most rapid response. If the report is not acknowledged or the recommended resource is not available, utilize another option to ensure rapid response.
Report via your customer Slack channel.
Create an Outage Ticket in the Game Warden application. See Submit Support Tickets for more details.
Send an email to devops@secondfront.com.
When reporting a disruption, please include the following details in your communication to 2F:
- Company name
- Brief description of the disruption
- Type of event (Refer to the list above)
- Current impact (i.e., downtime, degraded service)
- Affected application or service
- Contact information so the Security Team can follow up with you quickly
What happens next¶
Once your report is received, the 2F team will:
- Review the information provided.
- Assess the event and initiate disaster recovery (DR) protocols.
- Execute required recovery and/or mitigation steps.
- Provide status updates and next steps via Slack or email.
Responsibility model¶
- Platform-level response (Game Warden infrastructure): Managed by 2F.
- Application-level response (your deployed apps): Managed by your team.
- Some DR controls are partially inheritable, but primary responsibility for application-level security and recovery rests with the customer.