Cyber readiness is an organization’s demonstrated ability to detect, decide, coordinate, and communicate during a live cyber incident. It shows up in how people behave under pressure. It can be observed, it decays over time, and it belongs to the team the organization has today.
It is a Tuesday in late September at a regional property and casualty carrier. The company is deep in talks for its January 1 reinsurance renewal. Around lunch the claims platform slows down, then starts to fail. By 2 p.m. the broker portal is down and policyholder data is inside the blast radius.
Two questions arrive 20 minutes apart. One comes from the state insurance department. The other comes from the lead reinsurer, who would like an answer before the renewal is priced.
Everyone in that building prices other people’s risk for a living. No underwriter at this carrier would write a commercial property policy on the applicant’s description of its own sprinkler system. The underwriter wants the inspection report. Yet the reinsurer is asking how ready the carrier is for its own incident. The best evidence on hand is a plan, a training completion rate, and last year’s tabletop summary.
The distance between what the carrier can describe and what it has watched its own people do is the subject of this guide.
What Is Cyber Readiness?
Cyber readiness is the ability to run a coordinated response while the incident is still unfolding. It includes detection and escalation inside the security team. It covers decisions outside security too: when Legal joins, who talks to the regulator, and what the CFO can approve at 4 p.m. without a board vote.
A disclosure belongs here. Reflex Security sells an incident simulation platform that competes with the annual tabletop, so the company has a stake in this distinction. The survey figures below come from third-party sources, and the links let readers check them.
Readiness involves the whole organization, yet most organizations measure it with the audit file. Ask for evidence of cyber readiness and the usual answer is a stack of documents. The stack holds a versioned incident response plan, a signed attestation, a training completion rate, and last year’s exercise report.
Sygnia’s 2026 CISO Survey asked 600 senior security decision-makers about their incident response. 99% have a formal incident response plan. Only about one in three rated the core parts of that response as highly effective. Tabletop exercises came in at 32%, documented plans at 33%, and defined roles and escalation paths at 34%.
Most of the market tests because someone requires proof. Reflex CEO Marlow Bryant estimates that 200,000 to 300,000 organizations worldwide test their incident response plans for that reason. He lays out the math in sizing the requirement. The documents prove that the organization prepared. They do not prove that it can respond.
Cyber Readiness vs. Cyber Resilience: What’s the Difference?
Readiness is a capability. Resilience is an outcome. An organization builds the first and finds out about the second, usually during an incident it did not choose.
The difference matters because it changes what gets measured and who answers for it. Resilience shows up as restored services, retained customers, and contained losses. Those numbers mostly arrive after the incident.
Readiness has to be tested before the incident. Someone has to build a situation where the team can visibly fail. When a board deck uses the two words as synonyms, everyone watches the outcome and nobody owns the capability.
The World Economic Forum’s Global Cybersecurity Outlook 2026 treats resilience as bigger than any one security team. It calls collective cyber resilience “both an economic and a societal imperative.” It also reports that 65% of large companies name third-party and supply chain weaknesses as their greatest barrier to resilience. That fits the carrier. Its outcome depends on brokers, adjusters, vendors, and a reinsurer. Its readiness depends on whether the people in the room can make decisions that hold up.
Dimension | Cyber readiness | Cyber resilience | How to check it |
What it describes | People and the decisions they make in sequence | The business and the services it must maintain | Ask whether the subject is a team or a service |
When it becomes observable | Before and during an incident | During and after disruption | Exercise records for readiness; recovery records for resilience |
What demonstrates it | Timestamped behavior during an unfamiliar scenario | Restored operations, retained customers, and contained loss | Decision evidence for readiness; operational outcomes for resilience |
What weakens it | Turnover, reorganizations, leadership changes, and long testing gaps | Unmapped dependencies and untested recovery paths | Repeated exercises and recovery tests |
Who owns it | The CISO with Legal, Communications, and Operations | The board and operating executives | Exercise ownership and recovery-plan accountability |
What Does Cyber Attack Readiness Look Like in Practice?
Cyber attack readiness looks like a chain of small, specific decisions, each with a name and a time attached. Back to the carrier.
At 2:11 p.m. the head of claims operations has to choose. He can keep a degraded platform up for adjusters already mid-file, or take it down and lose the afternoon.
At 2:26 p.m. the general counsel decides whether the exposed policyholder data is a cybersecurity event the carrier must report. She has partial forensics and the reinsurer’s email in her inbox. That decision can start a clock. The NAIC Insurance Data Security Model Law is in force in 28 jurisdictions. It gives an insurer no more than 72 hours from that determination to notify its home-state insurance commissioner. Some states changed the window when they adopted it.
At 2:40 p.m. someone has to tell 300 brokers something true. Readiness is whether those three people have worked together before today. It is whether the general counsel knows she can act without waiting for the claims head. It is whether the communications lead has wording that Legal will approve before 2:52 p.m. The plan lists all three titles. That part was never the problem.
Watch an exercise closely and the failures are rarely technical. In the Sygnia survey, 90% of respondents expect trouble coordinating key stakeholders during an attack. 89% report limited executive or board involvement in incident response readiness.
Traditional tabletops hide this because nobody ever fails one. The scenario waits politely while the group talks, so hesitation costs nothing and nobody writes it down. Real attackers do not wait. In early 2024 a finance employee at Arup’s Hong Kong office joined a video call with deepfake versions of the company’s CFO and colleagues. The employee then made 15 transfers totaling about US$25 million. The test is whether people make sound decisions while the situation keeps moving.
How to Conduct a Cyber Security Readiness Assessment
A cyber security readiness assessment is useful only if it answers questions about behavior. Five questions do most of the work. A document cannot answer any of them.
Who decided, and when. The plan names a decision owner. The assessment records who actually made the call, how long it took, and what information they had at the time.
What the functions outside security did. Legal, Communications, Claims, and Finance all have parts to play. When a function stays silent, record the silence as a finding.
Where the response stalled. Every response reaches a point where the next step is unclear and the room goes quiet. Name that point, record the time, and check whether it matches the stall from the last exercise.
What changed since the last run. One assessment is a snapshot. The same scenario run twice gives a trend, and a trend is much better evidence of improvement. Plot it over time, like any security metric worth showing a board.
What survives the meeting. A summary slide preserves a memory. Timestamped decisions, named owners, and a record of how the scenario actually unfolded preserve evidence.
This is where the control frameworks run out. ISO/IEC 27001:2022 lists five incident management controls in Annex A, from A.5.24 (planning and preparation) through A.5.28 (collection of evidence). Clause 6.1.3 requires an organization to compare its controls against Annex A and justify every exclusion in its Statement of Applicability.
Taken together, those five controls describe preparation well. None of them asks for evidence that a named executive made a sound call within 15 minutes on partial forensics. The closest the standard comes is A.5.30, ICT readiness for business continuity, which calls for that readiness to be planned, implemented, maintained, and tested. Proving that systems can fail over is still different from watching the general counsel decide under pressure. An auditor can confirm that the process exists without ever seeing the behavior it should produce.
A cyber attack readiness assessment and a cyber resilience readiness assessment answer different questions, so run them as separate engagements. Maturity levels, scoring scales, and peer benchmarks are a separate discipline again, with their own methods. The buyer’s question is simpler: does the assessment describe what participants did, or only what the documents say?
From Compliance on Paper to Readiness Under Pressure
The same survey holds the number that should end the argument. In Sygnia’s results, 73% of senior security decision-makers say they would not be fully ready to execute under pressure if a significant attack hit tomorrow. 99% have a formal plan.
Sygnia draws that contrast itself. Side by side, the two numbers describe a market that renews the paperwork every year while the ability to respond decays between exercises. It also explains why everybody wants a tabletop now. Boards, insurers, and regulators all started asking for proof at about the same time.
Moving from paper to pressure changes what counts as done. Done no longer means the exercise was held and the report was filed. Done means someone watched the response, named the stall, and scheduled the same scenario for next quarter. The repeat run shows whether the stall moved.
Back at the carrier, this is the evidence the reinsurer was really asking for. Underwriters trust an inspection report over a self-description because someone watched the system work. Readiness evidence earns trust the same way.
How Reflex Security Tests Real-World Cyber Readiness
Those five questions set a bar that most exercise formats cannot clear. The rest of this section describes the Reflex platform. The definition of readiness above holds whether or not an organization uses it.
Requirement: the scenario has to move when the team stalls, or hesitation leaves no trace. In Reflex, the Adaptive Adversary Engine responds to each decision the team makes instead of following a fixed script. When participants put off a decision, the adversary uses the delay. The stall becomes an event with a timestamp.
Reflex builds a profile of the organization from its domain using open-source intelligence. One-Click Scenario Generation then offers five scenario options tailored to that organization, and the build takes minutes. AI agents play executives, employees, customers, journalists, regulators, vendors, and the attacker. A typical exercise runs about an hour. That is short enough to put the general counsel, the head of claims, and security into one incident, much like an executive crisis rehearsal.
Requirement: something has to survive the meeting and answer those five questions in writing. Reflex generates an After Action Report (AAR) when the exercise ends. Each finding traces back to a timestamped decision in the Investigation Console and maps to MITRE ATT&CK. The report records who decided what, when, and where the response went quiet.
That record supports readiness conversations with regulators, underwriters, and board committees. Run the same scenario two quarters apart and the organization has a trend line instead of another one-off report.
One scenario built from an organization’s own environment shows what its people do in the first 10 minutes.
See what your team does under real pressure.
Put your readiness to the test. Sixty minutes, your real environment, no slides.
Book A demo
Frequently Asked Questions
Can a cyber readiness assessment be run internally?
Yes. The hard part is letting the team fail in front of its own leadership. A facilitator who reports to that leadership often finds that difficult. Options include borrowing a facilitator from another function, bringing in a third party, or using a platform that records behavior rather than agreement.
What should a board ask to test cyber readiness?
Three questions, and none of them is about the plan. When did a named executive last make a live call in an unfamiliar scenario? Where did the response go quiet, and did that point move by the next run? What record shows it? An answer that points to a document is answering a different question.
Is a maturity score the same as cyber readiness?
No. A maturity score describes how well processes are defined and how consistently they run. Readiness describes what people do while an incident is still unfolding. A mature program can still have a team that has not practiced together in a year, so keep scoring and behavioral evidence in separate engagements.
Does a cyber insurance questionnaire measure readiness?
It measures controls and paperwork, which an underwriter can check from a distance. Questionnaires typically ask whether the organization has an incident response plan and whether it tests the plan. Neither question shows how the general counsel behaved at 2:26 p.m. Answer the form honestly, and keep the evidence it never asked for. The next renewal or the next claim may ask for it.
Can a small organization be cyber ready without a dedicated security team?
Yes, and the definition stays the same. What changes is the roster. The same decisions land on fewer people, and one of them is usually the operations lead rather than a CISO. The exercise should rehearse the handoffs the organization actually has. Five people who have practiced together will beat a twenty-person plan that has never been run.
Does a red team engagement or a cyber range prove readiness?
Each proves part of it. A red team tests whether controls and analysts detect an adversary moving through the environment. A cyber range tests individual technical skill. Neither one usually puts the general counsel, communications, and operating executives into the same exercise, and that is where coordination failures show up. Run them alongside readiness exercises as complements.
References
International Organization for Standardization. (2022). ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection: Information security management systems: Requirements (clause 6.1.3; Annex A, A.5.24 to A.5.28 and A.5.30). International Organization for Standardization.https://www.iso.org/standard/27001
Sygnia. (2026). CISO survey 2026. Sygnia. https://www.sygnia.co/guides-and-tools/ciso-survey-2026/
World Economic Forum. (2026). Global cybersecurity outlook 2026. World Economic Forum. https://www.weforum.org/publications/global-cybersecurity-outlook-2026/
Black Hat MEA. (2026). How connected ecosystems test incident response plans. Black Hat MEA Insights. https://insights.blackhatmea.com/how-connected-ecosystems-test-incident-response-plans/
Prakash, P. (2024, May 17). A deepfake “CFO” tricked the British design firm behind the Sydney Opera House in $25 million scam. Fortune. https://fortune.com/europe/2024/05/17/arup-deepfake-fraud-scam-victim-hong-kong-25-million-cfo/
National Association of Insurance Commissioners. (2026). NAIC Insurance Data Security Model Law (government affairs brief). https://content.naic.org/sites/default/files/government-affairs-brief-data-security-model-law.pdf
Sygnia. (2026, April). Sygnia released the 2026 CISO survey: The state of incident response readiness. Sygnia. https://www.sygnia.co/press-release/sygnia-released-ciso-survey-2026/
RadarFirst. (n.d.). Understanding the NAIC Insurance Data Security Model Law. RadarFirst. https://www.radarfirst.com/guide/understanding-the-naic-insurance-data-security-model-law/
