Calculator Inputs
Enter your current breach-readiness values. Higher percentages improve readiness. Lower detection and containment hours improve their normalized scores.
Example Data Table
| Scenario | IR Plan | MFA | Backup | MTTD | MTTC | Example Score | Tier |
|---|---|---|---|---|---|---|---|
| Small team with limited testing | 55% | 60% | 70% | 48 hrs | 120 hrs | 58.40% | Needs Improvement |
| Growing SaaS organization | 70% | 80% | 85% | 24 hrs | 48 hrs | 75.60% | Moderate |
| Highly mature regulated enterprise | 92% | 98% | 97% | 6 hrs | 12 hrs | 91.10% | Strong |
Formula Used
This calculator converts every input into a normalized 0 to 100 readiness score, then combines them with weighted importance.
Tabletop Score = min((Tabletop Exercises ÷ 4) × 100, 100)
Detection Score = max(0, 100 − min((MTTD Hours ÷ 72) × 100, 100))
Containment Score = max(0, 100 − min((MTTC Hours ÷ 168) × 100, 100))
Overall Readiness = weighted average of plan, testing, recovery, identity, encryption, logging, training, vendor oversight, data inventory, detection, containment, notification, and crisis readiness.
Weights: IR Plan 12%, Tabletop 8%, Backup 10%, MFA 8%, Encryption 8%, Logging 10%, Training 8%, Vendor Review 7%, Data Inventory 7%, Detection 8%, Containment 8%, Notification 7%, Crisis Readiness 7%.
How to Use This Calculator
- Enter the current percentage coverage for each governance, technical, and response control.
- Enter the average number of annual tabletop exercises completed by your team.
- Provide realistic detection and containment times in hours using recent exercises or incidents.
- Click Calculate Readiness to view the score, category breakdown, weakest controls, and next actions.
- Use the CSV or PDF buttons to save your assessment for audits, planning, or management reporting.
FAQs
1. What does the readiness score represent?
It estimates how prepared your organization is to detect, contain, communicate, and recover from a data breach using weighted operational and technical measures.
2. Why do lower hours improve the score?
Fast detection and containment reduce breach impact. The calculator rewards lower response times because shorter delays usually mean less exposure and lower recovery cost.
3. How often should tabletop exercises be run?
Quarterly exercises are a strong baseline. High-risk environments may practice more often, especially after major architecture changes, regulatory changes, or significant incident findings.
4. Can this score replace a formal audit?
No. It is a planning and benchmarking tool. Formal audits, penetration tests, legal reviews, and control validation still provide deeper evidence and assurance.
5. What is a good target score?
Many teams aim for 85% or higher. Your ideal target depends on data sensitivity, legal exposure, business continuity needs, and customer expectations.
6. Should vendor readiness really affect breach readiness?
Yes. Third parties often store data, process transactions, or provide technical access. Weak supplier controls can delay evidence collection, notice timing, and containment.
7. Why include legal and PR readiness?
Breach response is not only technical. Public communication, customer notices, insurer engagement, and regulatory deadlines can influence damage, trust, and legal outcomes.
8. How should I improve a low score?
Start with the lowest-scoring controls, then fix foundational gaps first: response planning, logging, backup testing, detection tuning, supplier oversight, and notification workflows.