| Key Takeaways |
| 74% of cybersecurity incidents trace back to unknown or unmanaged assets. Organizations have on average 30% more external assets than documented, creating a persistent blind spot that traditional vulnerability scanners cannot address. |
| The ASM market reached $1.03 billion in 2025, growing at 21–29% CAGR depending on the analyst, driven by cloud migration, shadow IT proliferation, and regulatory mandates (DORA, NIS 2, PCI DSS 4.0). |
| Mandiant ASM leads on threat intelligence integration; CyCognito pioneers zero-input AI-driven discovery; Censys excels in internet-wide data depth; Detectify leverages crowdsourced vulnerability research; Randori (IBM) uniquely combines ASM with continuous automated red teaming (CART). |
| Only 43% of organizations use dedicated ASM tools, yet 76% have suffered a cyberattack through an exposed asset. The gap between incident attribution and budget allocation is the risk that ASM closes. |
| Ten ASM-specific KRIs with progress-bar thresholds connect external asset visibility directly to your risk register, risk appetite statement, and board reporting cadence. |
| A three-stage activation roadmap (Discover, Integrate, Operationalize) ensures ASM output feeds your ERM framework rather than generating dashboards nobody acts on. |
Your organization’s attack surface is not what you think it is. Research consistently shows that the average enterprise has 30% more external-facing assets than its asset inventory documents.
Forgotten subdomains, orphaned cloud instances, shadow IT deployments, acquired company infrastructure, third-party integrations—these are the assets that attackers find first because defenders do not know they exist.
74% of cybersecurity incidents now trace back to unknown or unmanaged assets, according to Trend Micro’s 2025 global study of over 2,000 cybersecurity leaders.
Attack Surface Management (ASM) tools exist to close that visibility gap. They continuously discover, map, and monitor an organization’s externally facing digital footprint from the attacker’s perspective—without requiring seed lists, IP ranges, or agent deployments.
The ASM market reached $1.03 billion in 2025 (Fortune Business Insights), growing at 21% CAGR. Gartner now classifies External Attack Surface Management (EASM) as a distinct market category, separate from vulnerability management and threat intelligence.
This guide compares five leading ASM platforms: Mandiant ASM (Google Cloud, threat-intelligence-led), CyCognito (AI-driven zero-input discovery), Censys (internet-wide data and research-grade scanning), Detectify (crowdsourced vulnerability testing), and Randori (IBM, ASM + continuous automated red teaming).
Each is evaluated through an enterprise risk management lens, scored against eight criteria mapped to NIST CSF 2.0 and ISO 27001, and connected to KRIs that translate ASM output into board-ready risk intelligence.

Figure 1: ASM market growth by vertical segment, 2023–2029 (Fortune Business Insights / Straits Research estimates)
Attack Surface Management as a Risk Control, Not a Dashboard
Under ISO 31000, ASM is a risk treatment that addresses a specific control gap: the failure to maintain an accurate, real-time inventory of externally facing assets. Without that inventory, every downstream control—vulnerability scanning, penetration testing, patch management—operates on incomplete information. You cannot protect what you cannot see.
Under NIST CSF 2.0, ASM maps directly to ID.AM (Asset Management): “Assets that enable the organization’s critical functions are identified and managed.”
It also supports ID.RA (Risk Assessment) by surfacing exposures that feeding into risk assessments, and DE.CM (Continuous Monitoring) by providing real-time change detection on the external perimeter.
Under ISO 27001:2022, ASM supports Annex A controls A.5.9 (Inventory of information assets), A.8.8 (Management of technical vulnerabilities), and A.5.23 (Information security for use of cloud services).
The business case is stark. Verizon’s 2025 DBIR reports that vulnerability exploitation now accounts for 20% of all initial access vectors, up from 15% the prior year.
Yet only 43% of organizations use dedicated ASM tools to manage their external exposure. The mismatch between where breaches originate and where security budgets are allocated is the gap that ASM fills.
For risk managers, framing ASM as a control that reduces the risk appetite breach—rather than a dashboard to look at—is critical to securing budget.
| Metric | Value / Source |
| Incidents from unknown/unmanaged assets | 74% (Trend Micro 2025 global study) |
| Organizations attacked via exposed asset | 76% reported a cyberattack (ESG/Trend Micro 2024) |
| Average undocumented external assets | 30% more than inventoried (industry surveys) |
| ASM market size (2025) | $1.03B (Fortune Business Insights) |
| ASM market CAGR | 21–29% depending on analyst scope |
| Orgs using dedicated ASM tools | 43% (Trend Micro 2025) |
| Orgs with no continuous ASM process | 55% (Trend Micro 2025) |
| Budget allocated to attack surface risk | 27% average of security budget (Trend Micro) |
| Vuln exploitation as initial access vector | 20%, up from 15% (Verizon DBIR 2025) |
| Attack surface grew in past year | 62% of organizations (ESG Research) |

Figure 2: 74% of incidents stem from unmanaged assets, yet only 27% of budget addresses attack surface risk (Trend Micro 2025)
Eight Evaluation Criteria for ASM Platforms
Structure your ASM tool selection as a formal risk assessment. The eight criteria below map to NIST CSF 2.0 functions and ISO 27001 Annex A controls.
Weight each criterion based on your organization’s risk profile and present results to your three lines model governance structure.
| # | Criterion | What It Measures | Standards Mapping |
| 1 | Asset Discovery Depth | Automated discovery of domains, subdomains, IPs, cloud instances, APIs, certificates without seed input | NIST ID.AM; ISO 27001 A.5.9 |
| 2 | Vulnerability Detection | Ability to identify exposures, misconfigurations, and exploitable flaws on discovered assets | NIST ID.RA; ISO 27001 A.8.8 |
| 3 | Cloud & Multi-Cloud Coverage | AWS, Azure, GCP asset discovery; container registries; serverless; IaC misconfigurations | NIST PR.DS; ISO 27001 A.5.23, A.8.9 |
| 4 | Threat Intelligence Integration | Enrichment with threat feeds, exploit intelligence, and attacker TTP context | NIST ID.RA; ISO 27001 A.5.7 |
| 5 | API & SIEM Integration | Bidirectional API, native SIEM/SOAR connectors, ITSM ticket creation | NIST DE.CM; ISO 27001 A.8.15, A.8.16 |
| 6 | Compliance Mapping | PCI DSS 4.0 external scanning, DORA, NIS 2, SOC 2, ISO 27001 reporting packs | NIST GV.OC; ISO 27001 A.5.35 |
| 7 | Ease of Deployment | Zero-input setup, time to first discovery, ongoing maintenance requirements | NIST PR.PT; ISO 27001 A.8.9 |
| 8 | Cost Efficiency | Per-asset pricing, annual license model, ROI relative to reduced shadow IT risk | ISO 31000 cost-benefit analysis |
Head-to-Head: Five ASM Platforms Compared
Scores use a 1–5 scale (5 = best-in-class). Ratings reflect Gartner Peer Insights, G2 reviews, vendor documentation, published case studies, and Forrester analysis.
The five platforms represent distinct approaches: threat-intelligence-led (Mandiant), AI-driven autonomous discovery (CyCognito), internet-scale data (Censys), crowdsourced vulnerability testing (Detectify), and ASM + red teaming (Randori/IBM).
| Criterion | Mandiant ASM | CyCognito | Censys | Detectify | Randori (IBM) |
| Asset Discovery | 5 – Deep + threat-enriched | 5 – Zero-input AI | 5 – Internet-wide data | 4 – Domain-focused | 4 – Attacker perspective |
| Vuln Detection | 4 – Enriched by threat intel | 5 – Automated testing | 4 – Exposure identification | 5 – Crowdsourced payloads | 4 – CART validation |
| Cloud Coverage | 4 – Multi-cloud discovery | 5 – AWS/Azure/GCP deep | 4 – Cloud certificate/IP | 3 – Limited cloud depth | 4 – Cloud perimeter |
| Threat Intel | 5 – Mandiant Intel (elite) | 4 – AI-driven context | 3 – Research-grade data | 3 – Hacker community | 4 – IBM X-Force intel |
| API/SIEM Integration | 4 – Chronicle + API | 4 – REST API + SIEM | 5 – Open API + Splunk | 3 – API + webhook | 4 – QRadar native + API |
| Compliance | 4 – Regulatory mapping | 4 – PCI, SOC 2, HIPAA | 3 – Basic reporting | 3 – Basic compliance | 3 – IBM compliance packs |
| Deployment | 3 – Enterprise onboarding | 5 – Zero-input, SaaS | 4 – SaaS console | 5 – SaaS, instant setup | 3 – Enterprise onboarding |
| Cost Efficiency | 3 – Enterprise pricing | 3 – Enterprise pricing | 4 – Tiered pricing | 5 – Mid-market accessible | 3 – IBM enterprise pricing |

Figure 3: Cleveland dot-plot comparison of 5 ASM platforms across 8 evaluation criteria (1–5 scale)
Mandiant ASM (Google Cloud): Threat-Intelligence-Led Discovery
Mandiant Advantage Attack Surface Management, now part of Google Cloud, is the platform for organizations that want their attack surface discovery informed by world-class threat intelligence.
Mandiant’s ASM maps your external footprint and enriches every discovered asset with intelligence on whether it has been targeted, exploited, or is associated with active threat campaigns.
The integration with Google Chronicle SIEM enables real-time correlation between external exposure and internal detection events.
For risk managers, this means ASM findings arrive with threat context already attached—reducing the triage burden and accelerating the path from discovery to risk register entry.
The trade-off: enterprise pricing and onboarding complexity. Best for large enterprises with mature security operations who need threat-intelligence-enriched attack surface visibility.
CyCognito: AI-Driven Zero-Input Discovery
CyCognito pioneered the zero-input approach to ASM: provide your organization name, and the platform uses AI and machine learning to autonomously discover your entire external attack surface—subsidiaries, cloud infrastructure, third-party connections, and shadow IT—without seed lists or IP ranges.
The platform then classifies assets by business criticality and runs automated security tests to validate exploitability.
CyCognito’s strength is breadth: it finds assets that other tools miss because it mimics how a sophisticated attacker would map your organization.
For third-party risk management, CyCognito can map subsidiary and vendor attack surfaces. The limitation: enterprise pricing puts it out of reach for SMBs.
Best for organizations with complex, distributed digital footprints (multi-subsidiary, multi-cloud, heavy M&A activity).
Censys: Internet-Scale Data and Research-Grade Scanning
Censys emerged from academic research at the University of Michigan into internet-wide scanning.
The platform maintains a continuously updated map of every device and service connected to the internet, giving Censys ASM an unmatched data foundation.
The platform discovers external assets, identifies exposures (open ports, misconfigurations, expired certificates), and provides change detection alerts. Censys’s open API powers many third-party threat intelligence platforms.
For risk managers, Censys excels at answering the question: “What can anyone on the internet see about our organization right now?”
The platform integrates natively with Splunk, and its tiered pricing makes it accessible across market segments.
The limitation: less automated vulnerability testing than CyCognito or Detectify. Best for organizations that value data depth and want to build custom risk monitoring workflows on a robust API.
Detectify: Crowdsourced Vulnerability Research Meets ASM
Detectify combines continuous asset discovery with automated vulnerability scanning powered by a crowdsourced community of ethical hackers.
The key differentiator is the continuous feed of new vulnerability checks contributed by researchers—meaning Detectify tests for the latest attack techniques faster than platforms relying solely on CVE databases.
The platform is built for web-focused attack surfaces: domains, subdomains, web applications, and APIs. Setup is instant (SaaS, no infrastructure), and pricing is accessible for mid-market organizations.
The limitation: narrower scope than Mandiant or CyCognito for deep infrastructure and cloud-native discovery. Best for web-heavy organizations (SaaS companies, e-commerce, media) that need fast, continuous scanning with crowdsourced vulnerability intelligence and compliance reporting.
Randori (IBM): ASM Plus Continuous Automated Red Teaming
Randori, acquired by IBM in 2022, uniquely combines attack surface management with Continuous Automated Red Teaming (CART). While other ASM tools discover and monitor, Randori goes further by automatically attempting to exploit discovered exposures—proving which ones are truly exploitable in your environment, not just theoretically vulnerable.
Randori Recon maps your external footprint; CART validates it through automated attack simulation. The native integration with IBM Security QRadar enables bidirectional data flow between ASM findings and SIEM/XDR detection.
For risk managers, this combination provides the strongest evidence base for risk treatment decisions: you know not just what is exposed, but what is exploitable and what your controls failed to detect.
The limitation: IBM enterprise licensing and integration complexity. Best for enterprises already in the IBM security ecosystem (QRadar, Guardium) who want unified ASM, red teaming, and detection validation.
Key Risk Indicators for Attack Surface Management Programs
ASM dashboards generate operational data. KRIs generate risk data. The ten indicators below transform ASM output into structured risk intelligence for your risk committee.
Each is classified as leading or lagging and calibrated against industry benchmarks. Integrate these into your KRI dashboard with automated escalation at the red threshold.
| KRI | Type | Amber Threshold | Red Threshold | Data Source |
| Asset discovery coverage (%) | Leading | <95% | <90% | ASM platform vs. CMDB reconciliation |
| Unknown/undocumented asset ratio | Leading | >5% | >10% | ASM discovery vs. inventory delta |
| Mean time to discover new asset (hours) | Leading | >24 hrs | >72 hrs | ASM platform discovery log |
| Critical exposures on external perimeter (count) | Leading | >10 | >25 | ASM platform findings |
| Shadow IT instances detected | Leading | >10 | >25 | ASM discovery + cloud CASB |
| Certificate expiry monitoring (%) | Leading | <95% tracked | <90% tracked | ASM certificate inventory |
| Exposure remediation within SLA (%) | Lagging | <90% | <80% | ASM platform + ITSM tickets |
| Cloud asset visibility (%) | Leading | <90% | <80% | ASM vs. cloud provider inventory |
| Third-party connection risk coverage (%) | Leading | <85% | <75% | ASM + TPRM platform cross-ref |
| Board reporting cadence (reports/year) | Leading | <4 | <2 | Board pack delivery log |

Figure 4: KRI performance dashboard with RAG status bars for attack surface management program monitoring
Mapping ASM Capabilities to Control Frameworks
Every ASM capability should trace to a control standard. The mapping below covers NIST CSF 2.0, ISO 27001:2022, and NIST SP 800-53 Rev. 5.
Use this table to demonstrate control coverage during internal audit reviews and compliance risk assessments.
| ASM Capability | NIST CSF 2.0 | ISO 27001:2022 Annex A | NIST SP 800-53 Rev. 5 |
| Automated asset discovery | ID.AM (Asset Management) | A.5.9 (Inventory of assets) | CM-8 (System Component Inventory) |
| Exposure identification | ID.RA (Risk Assessment) | A.8.8 (Technical vulnerability mgmt) | RA-5 (Vulnerability Monitoring) |
| Cloud asset visibility | ID.AM (Asset Management) | A.5.23 (Cloud info security) | CM-8, RA-5 (cloud component) |
| Continuous change detection | DE.CM (Continuous Monitoring) | A.8.16 (Monitoring activities) | SI-4 (System Monitoring) |
| Certificate monitoring | PR.DS (Data Security) | A.5.14 (Information transfer) | SC-12 (Cryptographic Key Mgmt) |
| Threat intelligence enrichment | ID.RA (Risk Assessment) | A.5.7 (Threat intelligence) | RA-3, SI-5 (Security Alerts) |
| Compliance reporting | GV.OC (Organizational Context) | A.5.35 (Independent review) | CA-7 (Continuous Monitoring) |
| Automated red teaming (CART) | DE.CM + RS.AN (Analysis) | A.8.8 + A.5.36 (Compliance) | CA-8 (Penetration Testing) |
Architecture Decision Guide: Matching the Platform to Your Risk Profile
Selecting an ASM platform is a risk treatment decision. The table below matches organization profiles to recommended platforms based on risk appetite, infrastructure complexity, regulatory requirements, and existing security stack.
| Organization Profile | Recommended Platform | Why This Fits | Risk Consideration |
| Enterprise with mature SOC, needs threat-enriched ASM | Mandiant ASM | Elite threat intelligence enrichment; Chronicle SIEM integration; deep exposure context | Enterprise pricing; onboarding complexity; best value with Google Cloud ecosystem |
| Complex multi-subsidiary org, heavy M&A, distributed digital footprint | CyCognito | Zero-input discovery finds assets across subsidiaries, cloud, third parties; AI-driven criticality classification | Enterprise pricing; may surface overwhelming volume of findings without proper triage process |
| Data-driven security team wanting API-first ASM and custom workflows | Censys | Internet-scale data; robust API; Splunk integration; tiered pricing; research-grade scanning | Less automated vuln testing; supplement with Detectify or pentest platform for exploitation validation |
| Web-focused org (SaaS, e-commerce) needing fast, continuous scanning | Detectify | Crowdsourced vulnerability research; instant SaaS setup; mid-market pricing; web/API focus | Narrower infrastructure scope; pair with Censys or Mandiant for deep cloud/network discovery |
| IBM security ecosystem; needs ASM + automated red teaming validation | Randori (IBM) | ASM + CART in one platform; QRadar/Guardium native integration; proves exploitability, not just exposure | IBM enterprise licensing; integration complexity; best value within existing IBM security stack |
Three-Stage Activation Roadmap: Discover, Integrate, Operationalize
Deploying an ASM tool without connecting it to your risk management process creates a discovery engine with no action engine.
The activation roadmap below ensures ASM findings flow into your ERM framework and drive measurable risk reduction from the first week.
| Stage | Actions | Deliverables | Success Metrics |
| Weeks 1–4: Discover & Baseline | 1. Deploy ASM platform (zero-input for CyCognito/Detectify; configure for Mandiant/Censys/Randori). 2. Run initial full discovery against all known domains and subsidiaries. 3. Reconcile ASM findings against CMDB/asset inventory to identify delta. 4. Classify discovered assets by criticality tier (crown jewels, standard, low-value). 5. Document all unknown/shadow assets for remediation or formal acceptance. | ASM discovery baseline report; CMDB reconciliation delta; Asset criticality classification; Shadow IT inventory; Initial exposure snapshot | 95%+ asset coverage; Unknown asset delta quantified; 100% of crown-jewel assets tagged; Shadow IT count documented; Zero critical exposures unacknowledged |
| Weeks 5–8: Integrate & Prioritize | 1. Integrate ASM findings with SIEM (Splunk, Chronicle, QRadar) for real-time correlation. 2. Connect ASM to ITSM (ServiceNow/JIRA) for automated ticket creation on critical exposures. 3. Build KRI dashboard (10 KRIs from this article). 4. Map top 20 critical exposures to risk register entries. 5. Establish remediation SLAs by severity: Critical=48h, High=7d, Medium=30d. | SIEM integration playbook; ITSM ticket workflow; KRI dashboard (live); Risk register mapping document; Remediation SLA matrix | SIEM correlation active; 100% of critical findings in ITSM; KRI dashboard reviewed weekly; Top 20 exposures in risk register; SLAs defined and communicated |
| Weeks 9–12: Operationalize & Report | 1. Deliver first monthly attack surface risk report to risk committee. 2. Conduct a tabletop exercise: unknown asset exploitation scenario. 3. Schedule weekly ASM review meetings with SOC and IT operations. 4. Enable continuous monitoring alerts for new asset discovery and exposure changes. 5. Align ASM KRIs with board risk reporting pack. | Monthly risk committee report; Tabletop after-action report; Weekly review cadence; Continuous monitoring alert rules; Board reporting template with ASM KRIs | Monthly report on schedule; Tabletop completed with documented findings; Weekly reviews established; Continuous alerts <1hr for critical changes; ASM KRIs in board pack |
Oversights That Undermine ASM Programs
ASM programs fail more often from governance and integration gaps than from platform deficiencies.
The oversights below are drawn from risk control self-assessments and post-deployment reviews across organizations that invested in ASM but never translated discovery into risk reduction.
| Oversight | Why It Happens | How to Fix It |
| Running ASM but never reconciling with CMDB | ASM discovery treated as standalone; no feedback loop to asset management | Schedule monthly CMDB reconciliation. Track unknown asset delta as a KRI. Assign ownership for every discovered asset within 72 hours. |
| Discovering thousands of assets but prioritizing none | No criticality classification; treating all exposures equally | Classify assets by business criticality tier. Focus remediation SLAs on crown-jewel assets first. Use risk-based prioritization (CVSS + threat intel + asset value). |
| Shadow IT detected but nobody accountable | Shadow IT findings routed to security team only; no business-unit ownership | Route shadow IT findings to business-unit risk owners. Require formal accept/remediate decision within 7 days. Track shadow IT count as a leading KRI. |
| ASM findings disconnected from risk register | ASM output stays in the security dashboard; no GRC linkage | Map top 20 critical exposures to risk register entries monthly. Report attack surface exposure as a risk metric in board packs, not just a security metric. |
| Certificate monitoring is someone else’s problem | Certificate management split between IT ops, DevOps, and security | Centralize certificate visibility in the ASM platform. Set automated alerts for certificates expiring within 30 days. Track certificate monitoring coverage as a KRI. |
| ASM covers external perimeter only, ignoring cloud | Platform configured for domain/IP scanning; cloud instances not included | Extend ASM scope to all cloud providers (AWS, Azure, GCP). Include container registries and serverless functions. Reconcile ASM cloud findings with CSPM tools. |
| No continuous monitoring—just periodic scans | ASM platform deployed but continuous alerting not configured | Enable real-time change detection for new assets, open ports, and certificate changes. Set alerting thresholds: critical changes notify SOC within 1 hour. |
| M&A due diligence skips attack surface review | Acquired company’s external assets not scanned before integration | Run ASM discovery on acquisition targets during due diligence. Document attack surface risk as part of the M&A risk assessment. Budget for remediation post-close. |
Looking Ahead: ASM Trends for 2026–2028
The ASM category is evolving rapidly. Three structural trends will reshape how organizations buy and operationalize attack surface management over the next three years.
Convergence with CTEM and exposure management. Gartner’s Continuous Threat Exposure Management (CTEM) framework positions ASM as one component of a broader exposure management discipline that includes validation (pentesting, red teaming), prioritization, and mobilization (remediation).
Mandiant and CyCognito already position against CTEM. Expect Censys, Detectify, and Randori to follow. Risk managers should evaluate ASM tools based on how they integrate with their broader risk management lifecycle, not as standalone discovery engines.
AI-driven autonomous discovery and triage. CyCognito’s zero-input model is the direction the market is moving. Large language models are being applied to automate asset classification, exposure triage, and remediation guidance.
Risk managers should conduct an AI risk assessment on AI-augmented ASM tools—particularly around false-positive rates, asset misclassification risk, and the reliability of automated criticality scoring.
Regulatory mandates accelerating adoption. DORA requires financial entities to “identify, on a continuous basis, all sources of ICT risk.” NIS 2 mandates asset identification and vulnerability management for essential entities.
PCI DSS 4.0 requires continuous monitoring of the cardholder data environment. These mandates effectively require ASM capability, even if they do not name the category explicitly. Organizations that frame ASM investment as regulatory compliance cost—quantified through scenario analysis—will secure budget more effectively than those positioning it as a discretionary security enhancement.
Ready to close the visibility gap in your risk program? Visit riskpublishing.com/services for risk assessment frameworks, KRI dashboard templates, and ERM consulting. See our cybersecurity KRI guide for a broader perspective, or explore our IT risk management process to start integrating ASM findings into your risk framework today.
References
1. Trend Micro: 74% of Cybersecurity Incidents Due to Unmanaged Assets — Global study of 2,000+ cybersecurity leaders; 74% incident rate from unknown assets.
2. Fortune Business Insights: Attack Surface Management Market Size 2025–2034 — Market size $1.03B in 2025; 21% CAGR projections.
3. Straits Research: ASM Market Forecast 2025–2033 — Alternative estimate: $1.79B in 2025; 27.7% CAGR to $12.69B by 2033.
4. Verizon 2025 Data Breach Investigations Report — Vulnerability exploitation as 20% of initial access vectors, up from 15%.
5. Gartner: External Attack Surface Management Market Reviews — EASM market classification; vendor peer insights and ratings.
6. NIST Cybersecurity Framework 2.0 — ID.AM, ID.RA, DE.CM functions for attack surface management activities.
7. ISO/IEC 27001:2022 — Annex A controls A.5.9 (Inventory), A.8.8 (Technical vulnerabilities), A.5.23 (Cloud).
8. NIST SP 800-53 Rev. 5 — CM-8 (System Component Inventory), RA-5 (Vulnerability Monitoring).
9. EU Digital Operational Resilience Act (DORA) — ICT risk identification and continuous monitoring requirements for financial entities.
10. NIS 2 Directive (EU 2022/2555) — Asset identification and vulnerability management mandates for essential entities.
11. IBM Acquires Randori for Attack Surface Management — Randori acquisition; ASM + CART integration with QRadar.
12. Gartner: Continuous Threat Exposure Management (CTEM) — CTEM framework positioning ASM within continuous exposure management.
13. ISO 31000:2018 Risk Management Guidelines — Risk treatment cost-benefit framework for ASM investment justification.
14. PCI DSS 4.0 Requirements — Continuous monitoring and external scanning requirements for cardholder data environment.

Chris Ekai is a Risk Management expert with over 10 years of experience in the field. He has a Master’s(MSc) degree in Risk Management from University of Portsmouth and is a CPA and Finance professional. He currently works as a Content Manager at Risk Publishing, writing about Enterprise Risk Management, Business Continuity Management and Project Management.
