Documentation · 9 / 12
Security tools: map, Deep Scan, report, board
The tools of the team for looking at a company from outside. Behind a login.
Domain map
Enter a domain. The map finds subdomains from public sources and DNS, resolves their addresses and networks, and makes one ordinary web request per host. The drawing connects host, address and network. The table lists each host with its systems and observations.
A map usually takes less than two minutes.
Host check
From the map, a single host can be checked in more depth. This needs the confirmation that the owner agrees. The result is a short report in English or German, as HTML or PDF.
Deep Scan
A Deep Scan analyses up to ten web hosts of the domain: headers, redirects, cookies and page source; TLS and certificates; DNS and mail records; a port scan of common service ports; known vulnerabilities and misconfigurations. It runs for 15 to 30 minutes.
The scan is non-intrusive: no exploitation, no password guessing, no fuzzing and no load tests.
Permission
Active checks start only after the user confirms that the owner has given permission. The confirmation is logged and printed in the report.
The report
About 40 pages: summary with score and grade, findings by severity with evidence and fix, TLS, headers, network, DNS and e-mail, technology, the mapping to NIS2 Article 21, ISO 27001 Annex A and GDPR Article 32, a plan in phases and the method.
The report is available as HTML and as PDF on light or dark paper. It is written in English.
Findings board
Every scanned domain is a project with its own board. The findings are cards in five columns: Open, In progress, Fixed to verify, Verified and Accepted risk. A card is moved by drag and drop or inside the card. Every change is stored with time, person and note.
A new Deep Scan updates the board by itself: new findings appear in Open, findings that are gone move to Verified, and findings that return after a fix go back to Open.
Use cases
Look at a prospect before the first call
- Open Tools.
- Enter the domain and start the map.
- Read the hosts, networks and observations.
- Use the facts in the call.
Run a Deep Scan for a customer
- Get the permission of the owner.
- Create the map of the domain.
- Start the Deep Scan and confirm the permission.
- Wait 15 to 30 minutes.
- Open the report and send the PDF.
Track the fixing of findings
- Open the board of the project.
- Move each card as the work proceeds.
- Run a new Deep Scan after the fixes.
- Check which cards the scan moved to Verified.
User stories
- As a consultant, I want a map of a domain in two minutes, so that I am prepared for the first call.
- As a customer, I want a report with evidence and a fix for each finding, so that my team knows what to do.
- As a project lead, I want to see the status of every finding, so that I can report progress.
- As an auditor, I want to see when a status changed and who changed it, so that the process can be traced.
Updated: