Mythos-Readiness Self-Assessment | OSec
Question 0 of 7 0% Complete

Is Your Security Program Ready for the AI Threat Landscape?

The CSA's Mythos-readiness framework identifies 11 Priority Actions every security program needs to address. Answer 7 questions and find out where you stand.

3 minutes 7 questions Instant results

AI-powered attacks don't wait for your quarterly pen test. Find out if your program is built for today's threat speed.

Pillar 1 — Continuous Testing & Coverage
Question 01 / 07  ·  PA 7 · PA 11
How frequently does your organization test its full attack surface — including cloud, web apps, APIs, network infrastructure, and third-party dependencies?
Continuously, with automated testing running at all times
Mythos-Ready · PA 11 Operational
Quarterly scheduled assessments
Partial · PA 7 Cadence Gap
Annually or before major audits
Gap · PA 5 Patch Readiness Risk
Ad hoc — only after incidents or compliance triggers
Critical Gap · PA 7
Pillar 2 — AI Tooling & Agent Adoption
Question 02 / 07  ·  PA 1 · PA 2 · PA 4
Is your security team currently using AI agents or automated tooling to accelerate vulnerability discovery, triage, or incident response?
Yes — AI agents are embedded across our workflows with governance and controls in place
Mythos-Ready · PA 1 + PA 2 + PA 4
We're piloting AI tools in some areas but without formal oversight
Partial · PA 4 Agent Defense Gap
It's on the roadmap but not yet deployed
Critical Gap · PA 2 — Operating at Human Speed
No — our team operates primarily manually
Critical Gap · PA 1 + PA 2
Question 03 / 07  ·  PA 7 · PA 8
How do you confirm your attack surface inventory is accurate and current — including shadow IT, new cloud assets, and third-party dependencies?
Automated, continuous discovery — our inventory updates in real time
Mythos-Ready · PA 7 Full Coverage
Regular manual reviews, updated quarterly
Partial · Gaps Likely Between Cycles
We rely on a periodic audit or import from another tool
Gap · PA 7 Coverage Drift Risk
We don't have a formal asset inventory process
Critical Gap · PA 7
Question 04 / 07  ·  PA 8 · PA 9 · PA 10
How do you know your EDR, SIEM, and WAF are detecting and stopping real-world attacks — not just passing configuration checks?
We run continuous simulated attacks against our controls to validate they work
Mythos-Ready · PA 8 + PA 9
We test controls periodically through red team or purple team exercises
Partial · PA 10 Not Yet Automated
We rely on vendor certifications and audit results
Gap · PA 8 Not Validated Under Real Conditions
We assume they're working if no alerts are firing
Critical Gap · PA 9 + PA 10
Pillar 3 — Patch Velocity & Response Readiness
Question 05 / 07  ·  PA 5 · PA 10 · PA 11
How long does it typically take your team to patch a critical vulnerability after disclosure?
Less than 24 hours
Mythos-Ready · PA 5 + PA 11 Mature
1–7 days
Partial · Manageable Today, Insufficient as AI Patches Land
1–4 weeks
Critical Gap · Window to Exploitation Now Under 24 Hours
More than a month, or no defined SLA
Critical Gap · PA 10 + PA 11
Pillar 4 — Business Risk Visibility & Governance
Question 06 / 07  ·  PA 6
How do you currently communicate security exposure to executive leadership or the board?
We report breach probability and business impact tied to revenue-critical systems
Mythos-Ready · PA 6 Risk Models Updated
We share technical metrics with some business context
Partial · PA 6 Translation Gap
We report on compliance status and audit outcomes only
Gap · Pre-AI Risk Framing
Security reporting to leadership is infrequent or informal
Critical Gap · PA 6
Question 07 / 07  ·  PA 3 · PA 6
If a critical zero-day were disclosed today affecting infrastructure your organization runs, how quickly could your team triage, assess exploitability, and brief your executive team?
Within hours — continuous visibility, pre-built executive reporting, and pre-authorized response playbooks
Mythos-Ready · PA 3 + PA 6 In Place
Within a day — requires some manual analysis and formatting
Partial · PA 6 Partial · PA 3 Not Formalized
Within a week — it's a significant effort across multiple teams
Gap · PA 3 Approval Friction Present
We'd struggle to produce that briefing on short notice
Critical Gap · PA 3 + PA 6

Almost There — One Last Step

Tell us a bit more about yourself to get your full Mythos-Readiness score and personalised Priority Action report.

What This Means

Your Answers at a Glance

See What Incenter Finds That Your Current Tools Miss

Book a 30-minute walkthrough and see real findings from environments like yours.

Book Your Free Consultation →