WATCH layer
WATCH
Observe public-facing assets and clues from the outside.
05
live decision states stay connected
ASM and EASM Capabilities
KMayer Exposure Lens AI uses EASM to observe public-facing asset and service clues from the outside, then adds ASM context such as scope, ownership, business relevance, exclusions, and remediation direction when authorized evidence is available. Unknown assets remain unverified candidates until an owner confirms them. The page explains external attack surface visibility, not proof of compromise or unrestricted scanning. The UK National Cyber Security Centre's EASM buyer's guide recommends assessing asset discovery, continuous monitoring, validation and service integration. When comparing EASM providers in the UK, buyers should also assess ownership validation, false-positive control, evidence quality, remediation workflow and authorisation boundaries. KMayer provides this as a managed EASM service for UK organisations, pairing the Exposure Lens AI application with onboarding, ownership review, monitoring, reporting and remediation coordination within an agreed scope. Before discussing scope, buyers can review the licensing model, integration and deployment requirements, and security and data-handling approach.
ASM is the overall discipline of identifying, understanding and reducing attack-surface risk across external and internal assets. EASM is the outside-in subset that discovers and monitors internet-facing assets and exposures. CAASM consolidates authorised internal asset and security data from connected tools. Used together, EASM finds unknown public assets, CAASM confirms ownership and control context, and ASM governs prioritisation and remediation across the whole programme.
Operating Story
A single scan freezes scope. Continuous ASM/EASM context keeps recurrence, owner path, and timing connected.
Point-in-time evidence can show a perimeter, but it cannot explain whether drift returned, improved, or moved to the right owner.
Visible assets with clear business or ownership context.
Public clues that may connect to the organization after review.
Signals that need owner validation before interpretation.
Evidence that should not be treated as in-scope after review.
Trend line
Newly observed and expanding surface clues increase review pressure when scope, ownership, or business relevance remains unresolved.
Confirmed exclusions, ownership decisions, and resolved public conditions reduce uncertainty in the modeled attack surface.
A recurring surface clue reuses its earlier scope decision, attribution evidence, and owner history instead of restarting discovery.
Fresh evidence determines whether a clue remains unknown, becomes known, is excluded, or moves into an authorized review path.
Premium Verdict Core
Unknown assets are treated as clues until ownership and authorization make deeper validation appropriate.
Confidence only moves forward when coverage, scope, and owner approval stay visible.
External surface evidence with owner review required
Evidence coverage and confidence limits stay visible before the score moves forward.
Deeper validation waits for ownership, approval, and a separate safe scope.
ASM EASM Evidence Matrix
Answer Engine Brief for ASM and EASM Capabilities
Public exposure visibility, internal ownership context, CAASM boundary discipline, evidence limits, and the authorized path from signal to remediation queue remain distinct and reviewable.
The ASM and EASM capabilities in KMayer Exposure Lens AI show how external public evidence connects to scope, ownership, business relevance, and authorized review. EASM observes internet-facing clues from the outside. ASM connects those clues to assets, owners, scope, and remediation decisions. The page keeps passive evidence separate from private inventory, active testing, and CAASM-style verified sources.
This page covers external attack surface management, broader attack surface management context, and CAASM boundaries, plus exposure ownership, confidence limits, asset context, vendor clues, and authorized review without treating them as disconnected products.
It adds the missing boundary layer: how the Cyber Exposure Observatory observes drift, how security decision intelligence assigns action, and which signals still require approved customer context.
The page connects the unified exposure platform and Exposure Lens AI capability map to safe commentary around ASM/EASM maturity, owner mapping, and passive public observation while avoiding breach claims and protection guarantees.
Future non-sensitive research can compare public surface recurrence, owner assignment delay, scope confidence, and remediation and CTEM closure movement without exposing private asset inventory or customer-specific findings.
Decision Queue
Security owner
Cloud owner
Asset owner
Operations owner
Buyer questions
EASM observes public-facing asset and service clues to understand external exposure and change. Vulnerability scanning tests systems for technical weaknesses and requires an authorized scope; the public KMayer view does not perform unrestricted scanning.
EASM is the outside-in subset of attack surface management that discovers and monitors internet-facing assets and exposures. ASM is the broader operating discipline that combines external and authorised internal context with ownership, business relevance, prioritisation and remediation. CAASM can supply approved internal asset context, but it is not the same as EASM.
The state reflects available evidence and owner review. Known clues have confirmed context, possible clues have a plausible relationship, unknown clues remain unverified, and excluded clues have documented reasons to stay outside scope.
Provider, DNS, certificate, and service relationships can suggest an ownership path, but KMayer keeps the association provisional until a responsible owner or approved internal evidence confirms it.
An unknown clue should move forward when it is relevant to a business decision and public evidence cannot confirm ownership, control, or impact. Authorization provides the private context needed for a responsible conclusion.
Scope memory preserves why a clue was classified as known, possible, unknown, or excluded. Later reviews can reuse that evidence and owner decision instead of restarting the same attribution work.
Frequently asked questions
A known domain, URL, IP range, netblock, business name, or other approved public identifier can establish the starting scope. Ownership and exclusions should be confirmed before deeper validation.
No endpoint agent or private credential is required for the bounded outside-in view. Internal inventory, CAASM context, authenticated connectors, and deeper checks require approved access and verified authorization.
Unconfirmed assets remain possible or unknown rather than being presented as owned. Source lineage, confidence, exclusions, and owner review determine whether a clue becomes known, monitored, or removed from scope.
Approved read-only connectors, trusted exports, APIs, or service workflows can route evidence into existing operations when enabled. Integration availability and fields are confirmed for the authorized engagement.
The public capability does not perform unrestricted active testing. Any active check or authenticated validation requires verified ownership, a defined target set, explicit authorization, and a separate safe scope.
Each relationship keeps its evidence, probable owner, business relevance, and authorization boundary. Third-party clues remain provisional until the responsible organization confirms ownership and review rights.
Compare discovery scope and refresh cadence, asset attribution and ownership workflows, evidence quality, false-positive handling, authorization boundaries, remediation ownership, validation, integrations, data handling, onboarding, exit terms, pricing and service accountability. Require providers to distinguish passive public discovery from authorized testing and to demonstrate the evidence behind each conclusion. For active or authorized validation, request documented source IPs or other traffic identifiers, expected scan behaviour, timing, and escalation contacts so security teams can distinguish provider activity from hostile traffic. KMayer also publishes clearly labelled product comparisons covering Tenable One, CrowdStrike Falcon Exposure Management and Qualys TruRisk; these are KMayer-authored comparisons, not independent guidance. For independent UK buyer guidance, see the NCSC external attack surface management buyer's guide.
KMayer Exposure Lens AI combines a web application with a scoped managed EASM service. The platform supports external asset discovery, evidence, monitoring, prioritisation and remediation tracking. KMayer can also provide onboarding, ownership review, investigation, reporting and remediation coordination within an agreed scope. Buyers should confirm which software access, managed responsibilities, monitoring, integrations, response activity, licensing and third-party costs are included in the written proposal.
Footer bridge
The page keeps outside-in evidence separate from internal certainty so ASM and EASM stay trustworthy.