Skip to content

Runbook: CDN/Hosting Compromise

Security SpecialistOperations & StrategyDevops

Stub runbook. Customize with your CDN and hosting provider details.

Quick Reference

FieldValue
Typical SeverityP1
Primary ResponderInfrastructure SME
Last Updated[Date]
Owner[Name]

Identification

Symptoms

  • Malicious files being served
  • File hashes don't match expected
  • Unauthorized access in provider logs

Confirm Compromise

  • Compare served files to known good source
  • Check CDN/hosting access logs

Immediate Actions

  1. Purge CDN cache
  2. Take down site or redirect to maintenance page
  3. Rotate all access credentials
  4. Review access logs for unauthorized activity

Mitigation

  1. Redeploy from verified source (git, not existing infra)
  2. Verify deployment matches expected
  3. Enable additional access controls
  4. Set up file integrity monitoring

Prevention

  • Limit hosting/CDN admin access
  • Enable 2FA on all accounts
  • Use subresource integrity (SRI)
  • Implement Content Security Policy (CSP)
  • Regular access audits

Related