Agent-ready workflow · cloud
Cloud and DNS Ownership
Connect DNS, certificates, cloud services, repositories, and ownership evidence while rejecting shared infrastructure.
Entry contract
Enter with artifacts, leave with evidence.
Use when
- wildcard scope
- dangling CNAME
- cloud edge
- unknown certificate
- new subdomain
Prerequisites
- scope roots
- passive discovery allowed
- ownership criteria
MCP retrieval
Agents can search this workflow, retrieve the complete graph, or request one stage through the read-only Vulns.co MCP connector.
Build the passive asset graph
Join DNS, certificates, nameservers, ASNs, repositories, and source references.
Inputs
- approved roots
Outputs
- asset graph
- provenance edges
- Evidence gate
- Every edge names its source and observation date.
- Negative control
- Shared CDN and hosting edges are labeled shared, not owned.
- Stop condition
- Stop at uncertain ownership.
Resolve and classify services
Record current DNS chains, HTTP behavior, TLS identity, and provider-specific signatures.
Inputs
- candidate assets
Outputs
- live service map
- dangling candidates
- Evidence gate
- A dangling candidate has both current DNS evidence and a provider state signal.
- Negative control
- A known active service on the same provider establishes normal behavior.
- Stop condition
- No provider claim or resource creation without explicit permission.
Confirm program ownership
Compare current program scope, organization references, certificate names, and application linkage.
Inputs
- candidate asset
- scope snapshot
Outputs
- ownership decision
- ambiguity queue
- Evidence gate
- An asset is in scope by current source, not merely related infrastructure.
- Negative control
- Lookalike and third-party service domains remain excluded.
- Stop condition
- Ask the program when ownership remains ambiguous.
Validate the minimal provider state
Use passive or provider-documented non-claiming checks and preserve exact signatures.
Inputs
- owned dangling candidate
Outputs
- minimal takeover evidence
- Evidence gate
- The report distinguishes dangling configuration from proven claimability.
- Negative control
- Active provider resource does not show the dangling signature.
- Stop condition
- Do not register, claim, or serve content unless expressly authorized.
Related methods
Continue with the right depth.
Sources