ASM FAQs
Clear answers before you evaluate.
Understand discovery, ownership, coverage and deployment. Confirm the scope and terms that apply to your organization.

Understanding ASM
ClearSkies Attack Surface Monitoring (ASM) helps security teams discover their internet-facing assets, verify ownership, prioritize exposures and track remediation within an agreed scope.
Inventory-based scanning generally starts from known, authorized targets. ASM helps discover publicly visible candidates that may be missing from that scope, then reviews ownership and exposure. It complements vulnerability scanning, penetration testing and internal inventory controls.
ASM addresses unknown external assets, disputed ownership, poorly contextualized findings and exposure without remediation accountability. It is designed for organizations whose public footprint changes through cloud projects, contractors, acquisitions or shared services.
Yes. Standalone ASM supports discovery, attribution, contextual prioritization, findings management and reporting, with supported workflow destinations and exports. Native iISOC correlation is a separate deployment and licensing choice.
Yes. Existing ClearSkies iISOC customers can adopt the native ASM add-on directly, subject to the applicable licensing and deployment configuration. A standalone ASM purchase is not a prerequisite.
Discovery & authorization
ASM searches outward from customer-authorized root domains using external observations such as certificate transparency, passive DNS, registration records and publicly observable service information. A pre-existing asset inventory is not required to begin discovery.
Multiple signals contribute to a recorded confidence decision, including certificate lineage, DNS relationships, registration data, technical fingerprints and reputation. Ownership evidence and disputed cases can be reviewed; similarity alone should not establish responsibility.
The outside-in discovery and assessment model is agentless and unauthenticated. It does not require internal system credentials. Customer-provided business and ownership context may still be needed to validate attribution and prioritize findings.
Active assessment requires confirmed attribution and explicit customer-approved testing scope. A confidence score is not permission to scan. Agree entities, root domains, exclusions, allowed techniques, provider restrictions and escalation contacts before active testing.
The standalone outside-in model does not scan inside internal or OT networks. It can provide context on externally reachable entry points within scope. Internal and industrial-system coverage requires other controls or separately defined integrations.
Risk & coverage
The documented approach considers CVSS severity, EPSS exploitation probability, CISA Known Exploited Vulnerabilities information and asset business context where applicable. Inspect the individual inputs and the reasoning behind priority during evaluation.
Yes. Authorized outside-in assessment can include externally observable issues such as exposed management interfaces, storage exposure, TLS weaknesses and email-domain protection gaps. Agreed scope defines which checks are performed.
Coverage can include domain-related credential exposure, breach mentions, brand abuse and access-broker signals within the agreed package and source coverage. Confirm monitored domains, permitted sources, evidence handling and entitlements in your proposal.
Named supplier observations and relevant supplied SBOM/component information can be included where contracted. Agree entities, data sources, permissions and entitlements. A supplier relationship or public discoverability does not itself authorize active testing.
Findings follow a defined lifecycle with ownership, tracked actions, time-to-fix targets and risk acceptance with expiry. Supported Jira, Teams, Slack and email workflows depend on configuration. Customers remain responsible for system changes unless contracted services establish another arrangement.
Adoption & operations
ASM is licensed on monitored in-scope subdomains within authorized root-domain scope. The current proposal defines counting rules, allowances, coverage, retention and service terms. MSSP pool allocation and partner terms are agreed separately.
Discuss the current evaluation options with the ClearSkies team. Duration, eligibility, authorized scope, permitted activities, deliverables and commercial terms are agreed before an evaluation begins.
Agree a baseline and review ownership evidence, verified unknown assets, permitted exposure examples, priority inputs and a finding’s workflow. Set success criteria before starting. A short evaluation is not a guarantee of measured long-term risk reduction.
The outside-in model avoids agent deployment, but useful coverage still depends on scope authorization, ownership review, configuration and customer participation. Agree onboarding milestones for your environment rather than assuming a universal completion time.
Native ASM reports external asset and finding context to TDIR. Other available add-ons provide their signals independently. TDIR can correlate relevant evidence around shared entities, subject to licensing, deployment and configuration.
Standalone ASM does not automatically include TDIR, AI-SecOps Autonomous Analyst or Active Defense. Investigation and response functions require the relevant licensed and configured capabilities, supported controls, permissions and approved operational policies.
Confirm hosting, processing, retention, deletion and access controls for your deployment in the agreement. Dark web material can include sensitive personal data, so the permitted collection scope and handling requirements should also be agreed.
Your next step
Have a question about your environment?
Discuss your footprint, deployment route and evaluation objectives with the ClearSkies team.
