• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team
Interactive Quiz

Cybersecurity Maturity Assessment

Answer 20 questions to discover your organization's cybersecurity maturity level and receive a personalized improvement roadmap.

Question 1 of 205%
0 answered20 remaining
Technology

How often do you conduct vulnerability assessments?

Prefer to talk through your security needs? Request a risk review

Jump to question:

What the assessment measures

Twenty questions across five areas. Each question describes four stages, from ad hoc to fully embedded, so you can see what the next step up looks like.

Governance (6 questions)

Who owns security, whether policies are written and kept current, how risk is assessed, how vendors are vetted, how data is classified and how compliance obligations are tracked. Weak governance tends to show up later as controls that exist on paper but nobody checks.

Technology (7 questions)

Vulnerability assessment, privileged access, backups, cloud security, multi-factor authentication, encryption and mobile devices. These are the controls attackers test first, so gaps here usually carry the most immediate risk.

People (1 question)

How staff are trained to spot phishing and social engineering. Because this area has a single question, its percentage moves in big steps. Treat it as a signal rather than a precise measure.

Processes (3 questions)

Incident response planning, patching and disaster recovery. These decide how quickly you recover when something does go wrong, and whether the recovery is rehearsed or improvised.

Detection (3 questions)

Network monitoring, insider threat detection and logging. Without these, an intrusion can run for a long time before anyone notices, and there may be no record to investigate afterwards.

How to get an honest result

  1. Answer for the whole organization

    Pick the option that is true everywhere, not for your best-run system. If MFA covers email but not the VPN, the honest answer is the lower one.
  2. When torn, choose the lower option

    If you would struggle to show evidence for an answer, such as a dated test report or a review record, score it one step down. The result is more useful when it errs on the side of caution.
  3. Bring a second view

    Ask someone from IT operations and someone from the business to answer separately, then compare. Disagreements are often the most useful finding.
  4. Save and share the result

    Your answers stay in this browser so you can return to them. Use Share Results to send the page to colleagues, then retake it after each round of improvements.

How to read your level

The total of your answers places you in a band. The area breakdown then shows where that total comes from, which is usually more useful than the level itself.

Level 1, Initial (20 to 35 points)

Security depends on individuals rather than process. Start with the basics that block the most common attacks: MFA everywhere, tested backups kept offline or immutable, a patching routine and a short written incident plan.

Level 2, Developing (36 to 55 points)

Some good controls exist but coverage is uneven. The priority is consistency: extend what works to every system, write down owners, and start testing plans rather than just having them.

Level 3, Defined (56 to 70 points)

Processes are standard and most critical controls are in place. Gains now come from monitoring, measurement and rehearsal: centralized logging, regular tabletop exercises and risk reviews that feed decisions.

Level 4, Managed (71 to 80 points)

Controls are measured and reviewed. Keep it that way with independent testing, such as a penetration test, and by checking that answers still hold after staff changes, acquisitions or new cloud services.

A strong total can hide one weak area. If Detection or Processes sits well below the rest, an attacker who gets past your preventive controls may go unnoticed, or recovery may take far longer than it should. Fix the weakest area before polishing the strongest.

Turning the result into a plan

Take the recommendations list and give each item an owner and a target date. Group them into a first 90 days of quick, high-impact fixes, such as enforcing MFA on remaining systems or testing a backup restore, and a longer program for items that need budget or new tools.

Share the result with leadership in plain terms: the current level, the two or three areas holding it back, and what it would take to move up one level. A single page with that information usually gets a better hearing than a long list of technical findings.

If you want help, our team can validate the answers with evidence, map them to the framework you need, and build the roadmap with you through a security risk assessment or an ongoing virtual CISO engagement. Related self-checks include the ransomware readiness checklist and the incident response preparedness checklist.

Maturity Assessment: Frequently Asked Questions

How is the maturity score calculated?

Each of the 20 questions has four answers worth 1 to 4 points, so totals run from 20 to 80. The total sets your maturity level, and each area shows the share of available points you scored in it. Any question answered with one of the two lowest options adds a recommendation, tagged High or Medium impact.

Which framework is this based on?

It is a quick self-assessment, not a formal framework audit. The questions cover the same ground as the NIST Cybersecurity Framework 2.0 functions (Govern, Identify, Protect, Detect, Respond and Recover) and the common controls that ISO/IEC 27001, SOC 2 and cyber insurers ask about, so the result is a reasonable starting point for any of them.

Is my data sent anywhere?

No. Your answers are saved in your own browser so you can come back to them. Nothing is submitted unless you choose to contact us.

Which recommendations should we tackle first?

Start with High impact items that reduce the chance of a breach or speed recovery: multi-factor authentication, privileged access, backups, patching and an incident response plan. Then work through governance items, which make the technical fixes stick.

How often should we retake the assessment?

Quarterly works well for teams actively improving, and at least once a year otherwise. Retake it after major changes such as a merger, a move to a new cloud platform or a change in who runs IT.

Can a self-assessment replace an independent review?

No. It shows where you think you stand. An independent assessment tests whether controls actually work, which matters for auditors, insurers, customers and boards. Use this result to scope that review so it focuses on the areas that need it.

Get an independent view of your maturity

We will check your answers against evidence and turn the gaps into a prioritized roadmap your team can deliver.