01
Intake
Twenty questions cover the legal name, the footprint you actually own, the people you approve for monitoring, and who receives each report.
For client organizations
Answer the questions. Monitoring starts when the domain checks out.
A client buys an engagement, completes one scripted intake, and publishes a DNS record that proves they control the primary domain. Weekday collection then runs on its own. It is passive and outside-in: no scans, no logins, no exploit tests. An executive is watched only if you list them and approve them.
02
Domain check
You add one DNS TXT record. The tenant stays off until a public resolver can see it. A form submission alone does not start collection.
03
It runs
Daily, weekly, and monthly jobs use the same engine that already builds the reports. Mail goes out automatically, or waits in a review queue if you asked for that.
What arrives
- Leadership daily, TLP:AMBER, on weekdays after the data run.
- Analyst daily, TLP:AMBER, with the work queue.
- Weekly executive one-pager, TLP:GREEN, the morning after the week ends.
- Monthly leadership brief, TLP:AMBER.
What we will not do
- No port scans, no authenticated logins, no exploit tests.
- No executive monitoring unless that person is listed and marked approved, with a named approver.
- No API keys on this form. A sharing-community key stays in a file outside the application, one client at a time.