Start with a domain and its scope
Establish the domain or asset you are reviewing, who is responsible for it and the boundaries of your authorization. Then use the connected pillars to inspect its public footprint.
The homepage demonstrates this workflow with illustrative domains and animated findings. Its animation timing is separate from monitoring or assessment cadence.
Seven connected pillars
- DNS — Records, configuration and domain dependencies. Read the guide
- Infrastructure — Internet-facing hosts, networks and hosting signals. Read the guide
- Web & HTTP — Website behaviour, security headers and configuration. Read the guide
- TLS & Certificates — Encryption, certificate validity and transparency records. Read the guide
- Email Security — SPF, DKIM and DMARC configuration. Read the guide
- Domain Registration — Registration details, expiry and lifecycle signals. Read the guide
- Exposed Services — Reachable ports, detected services and exposure findings. Read the guide
Observe. Compare. Explain. Review.
- Observe: retain the asset, collection time, method and resulting evidence.
- Compare: examine the current observation alongside earlier evidence.
- Explain: connect the finding to its context, affected service and remaining uncertainty.
- Review: assign follow-up, plan remediation and compare a retest with the intended result.
Monitoring and change
A change is a reason to review the evidence. Check timestamps and distinguish a successful observation from a collection failure. An unavailable response does not, on its own, prove that a service has been removed.
ARIEMA Veritas
Use CVE intelligence to inform investigation and authorized validation planning. Confirm the asset, permission, scope and conditions before active validation. The website’s Veritas scene is an explainer and does not run a test.
Connected destinations
Native destination support covers Slack, Microsoft Teams, Jira, Linear, ServiceNow, Splunk, Microsoft Sentinel, Datadog, Webhook and Email.
Plan which finding, asset, evidence and workflow update each destination should receive. Before relying on a delivery path, confirm the receiver accepted the expected information.