Skip to main content

EASM — getting started

EASM maps everything your organization exposes to the internet — subdomains, servers, open ports, web apps — and turns it into prioritized findings with fixes. It is non-intrusive: it observes and infers, and never sends an exploit payload. (Active payload testing is the separate DAST module.)

There's nothing to install and no access to grant. You give us your domains; we do the rest.

The flow​

Add your domains  →  Run scan  →  Review findings  →  Answer them  →  Rescan confirms

1. Add your domains​

List the domains you own (e.g. acme.com, www.acme.com, shop.acme.com). These are the roots we discover from — we'll find the subdomains, addresses, services, and exposed ports under them. Add or remove domains any time.

2. Run a scan​

Click Run scan. It runs asynchronously; a progress bar shows the current stage and live asset/finding counts. A scan takes a while (discovery + enrichment across your whole surface). You can run one EASM scan per 14 days by default.

3. Review the findings​

Each finding comes with a plain-language description, the risk, and exactly four remediation steps — no vague filler. Severity is computed, not copied: the base CVSS is raised for actively-exploited issues (CISA KEV) or high exploit-probability (EPSS), and lowered for shared/third-party infrastructure, with every step of that reasoning recorded.

The default view shows real signal only — technology inventory is hidden, false positives are filtered, and duplicates are merged. Findings group by issue: one problem across many hosts is a single row with the affected assets and a "5 of 20 remaining" rollup; anything that persists across scans is flagged recurring.

4. Answer the findings​

For each finding, record an answer: In Progress, Resolved, Accepted Risk, or False Positive. A false positive or accepted risk can suppress the whole class so it doesn't nag you on future scans.

5. Rescan validates your answers​

Run another scan after you've remediated. The engine reconciles your answers against reality and reports the outcome: confirmed fixed, regressed (the fix didn't hold), still open, newly found. Anything you marked Resolved closes once the scan no longer sees it; an untriaged fix auto-closes after two clean scans. This is how a rescan proves the work, rather than trusting a checkbox.

What you don't have to do​

  • No agents, no installs, no credentials.
  • No picking scanners or tuning — one scan runs the full pipeline.
  • No chasing third-party noise — infrastructure you don't own is de-prioritized automatically.

Next​

  • Want active payload testing of the web apps EASM found? See the DAST guide — it runs on the surface EASM discovers.
  • Integrating EASM into your own portal? See the API Usage Guide.