Look outside your organisation and you can see the signals: domains, mail settings, certificates. Cyber Health Score brings those signals together, so there's a clear place to start.

First, add a domain you control and verify ownership. That sets the boundary. An authorised assessment can then check supported public signals and record what it actually found. Discovery alone doesn't grant permission.

Take email security. DNS carries the instructions. SPF names permitted senders; DKIM supports signed mail; DMARC sets a policy for failures. If a selector is missing, you get an explainable finding, with its limits.

Here, a completed assessment scores sixty-eight. Confidence is partial, and you can see when the evidence was captured. Some checks weren't available. A number on its own never tells you the whole risk story.

The inventory separates verified assets from discovery candidates. Sankofa, the history view, separates recorded observations from reconstructed ones. You can follow the evidence over time without pretending the gaps are filled.

Now look at this DKIM finding. The owner assigned it, recorded the next step, and ran a recheck. The issue was still detected, so it stays open. That's an honest remediation trail.

Atlas shows the fictional supplier inside a trust lens. Select it, and Missions carries that context into an investigation. The relationship helps you ask a better question; it doesn't authorise a supplier scan.

A declaration isn't a reviewed claim. A reviewed claim isn't a certificate. Here, the supplier review couldn't be created, so trust claims and Verifier stay empty. The product keeps that boundary visible.

Observe the signal. Understand the evidence. Decide what matters. Act, then check again. Cyber Health Score gives teams a more accountable way to share what they know.