01 · Discover

A map of your stack, measured from your domain

Discovery starts with what your organisation already shows the world: DNS and mail records, certificates, headers, a rendered page, app stores and job boards. Nobody fills in a spreadsheet first.

  • Signals are matched against 666 technology fingerprints, then profiled into a picture of what runs where.
  • Connect your cloud, identity, device and code tools, and they add what the outside cannot see.
  • The report states what was and was not looked at, and what the profile cannot claim.

Why it matters

You see your technology the way an outsider can, including what your own inventory missed.

Mail records DNS Certificates Software Hardware Cloud services Data tools

02 · Confirm

Every finding graded, and decided by a person

A discovery is only useful if you can tell a fact from a guess. Every finding carries a confidence grade and the alternatives where it could be wrong, and a person decides it before it shapes your scope.

  • Five grades, from confirmed and measured to probable, possible and unverified.
  • Each one explains why an auditor cares and the cheapest way to settle it.
  • Confirm it, correct it, or mark it not yours or out of scope. Every decision is recorded.

Why it matters

Unknown assets come to light, and no guess quietly becomes part of your audit scope.

Technology-stack discovery
#FindingConfidenceConnectorDecision
1Amazon Web ServicesconfirmedAWSConfirmed
2OktameasuredOktaConfirmed
3ZendeskpossibleZendeskTo decide
4SnowflakeprobableSnowflakeTo decide
If not thisBigQuery or Redshift. A job posting names both as past experience.
Why an auditor caresA warehouse holding customer data brings its access and retention into scope.
Cheapest way to settle itAsk the data team lead. One answer closes it.
ConfirmCorrectNot oursOut of scope

03 · Put it to work

From what you run to what you must prove

What you confirm does not sit in a report. It pre-fills your set-up, tells you which connections reach the most requirements, and shows the systems your documents name.

  • Set-up questions arrive with suggested answers, for a person to accept.
  • Connectors are ranked for your scope, from a catalogue of 138 providers across 22 categories.
  • Systems named across your documents are merged into one view, and a system you were expected to name but did not gets flagged.

Why it matters

Technology gaps and potential compliance risks surface on day one, not in the middle of the audit.

Patient PortalProgrammes over it: 3
Systems24Portal API, Okta, Zendesk
Data stores6Patient records, audit logs
Cloud accounts2Production, shared services
Companies relied on11AWS, Okta, Snowflake
Snowflake is named in the Data Protection Policy, p. 9, and nowhere in your set-up.Reconfirm systems
Recommended for your scope
AWAWS
Reaches 260 assessable requirements
Connected
ENMicrosoft Entra ID
Cloud identity and access
Connector shipped
GHGitHub
Code and change control
Not connected

See what your stack already says about you.

Start with a discovery of your own domain. We will walk you through what we found, the frameworks that apply, who would own what, and where your evidence already stands.