Lion Cipher Lab

Read Amass output: map an org's attack surface and spot the assets nobody remembers

Why it matters

Running a recon tool is the easy half. Anyone can paste a domain after `amass enum` and watch names scroll past. The half that pays is what happens next: someone hands you three hundred discovered hostnames and asks 'so what does this tell us?' A tool prints a list; a person reads an attack surface. Buried in that list — every single time, on every real organisation — are the things nobody remembers owning: the staging box from a project that shipped in 2019, the marketing subdomain still pointing at a SaaS trial that lapsed, the analytics server a data scientist spun up in a cloud account…

What you'll learn

Steps in this lab

  1. The scenario, and the data you are here to read
  2. How to read ONE line: name, resolution, owner, source
  3. Group by owner: separate what you host from what a third party hosts
  4. Finding #1 — the forgotten staging/dev host nobody remembers
  5. Finding #2 — the dangling CNAME: a subdomain-takeover waiting to happen
  6. Finding #3 — the wildcard artifact: three phantom hosts, one IP
  7. Finding #4 — the shadow-IT asset in a cloud nobody claims
  8. WHEN the output IS the finding — and WHEN you must probe further
  9. Turn the list into a triage: what we own, what's exposed, what to investigate first
  10. Do it better — the habits that separate a reader from a lister

Open the full interactive lab →