ambacti
Explore workflows

SECURITY INVENTORY · Workflow idea

Understand your public domain footprint and keep reconnaissance in scope.

For a domain the organization owns or is explicitly authorized to assess, collect passive subdomain and public DNS information and prepare a structured report for the security team. Keep the target scope documented, avoid active probing or exploitation, treat records as time-sensitive clues rather than proof of a vulnerability, restrict report access, and require a qualified owner to validate findings before remediation.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
An authorized security review begins
Produces
A dated domain inventory and DNS summary with validation notes and security-owner review status.
Category
Commerce

01 / The starting point

A clear request.
A useful direction.

A verified domain, written assessment scope, and approved report recipients

“Review public domain records without crossing into unapproved testing or exposing sensitive findings.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps a security team gather public subdomain and DNS records into a report for an authorized review.

  1. Verify domain ownership and written scope

    Confirm the exact domains and records the reviewer is authorized to examine.

  2. Collect passive public records

    Gather subdomain and DNS details only for the approved target scope.

  3. Prepare a dated, source-linked report

    Record when information was observed and distinguish missing data from a negative finding.

  4. Validate potential issues with an owner

    Check records and possible misconfigurations with the responsible system administrator.

  5. Approve any follow-up security action

    Require a qualified owner to authorize additional testing or a configuration change.

03 / The result

Something useful.
Something to build on.

A dated domain inventory and DNS summary with validation notes and security-owner review status.

AmbactiWorkflow folio · 5 steps

Review an authorized domain inventory

Commerce · Example outcome

The handoff

A dated domain inventory and DNS summary with validation notes and security-owner review status.

Keep in mind

Public records can be stale, incomplete, or misinterpreted, and security details can create risk if widely shared. Restrict the review to owned or approved domains, keep it passive, verify records with the system owner, and do not treat a report as authorization for further testing.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Record approved domains and assessment purpose

Keep target scope, authorization, and review contacts documented and current.

Keep collection passive and proportionate

Do not expand into probing, exploitation, or unrelated domains without separate approval.

Protect reports and recipient lists

Limit security inventory access to people responsible for the assessed environment.

Set validation and remediation ownership

Assign a security owner to verify findings and approve corrective actions.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗