Understanding Your Exposure Score

How your 0–100 exposure score is calculated across five attack surfaces.

·5 min read

What the score means

Your exposure score runs from 0 (severe exposure across multiple surfaces) to 100 (no detectable exposure). It's calculated as a weighted average of five surface scores.

The score is not a security rating — it's an exposure indicator. A low score means your business data is more accessible to unauthorised parties than it should be.

How it's calculated

Each surface is scored independently (0–100), then combined using these weights:

  • File Sharing: 30% — publicly shared files, external access grants
  • Credentials: 25% — employee emails found in breach databases
  • AI Tool Access: 25% — shadow AI tools with OAuth access to company data
  • Email Security: 10% — SPF, DKIM, DMARC configuration
  • External Surface: 10% — subdomains, SSL certificates, DNS

Within each surface, findings are weighted by severity: critical findings have 10× the impact of low findings.

Severity levels

  • Critical: immediate action required — breached credentials with recent exposure, publicly shared sensitive files, or missing email authentication allowing spoofing
  • High: address this week — older breached credentials, broad OAuth scopes on AI tools, or weak email security configuration
  • Medium: address this month — external shares without expiry, medium-risk AI tool access, or partial email security
  • Low: address when convenient — informational findings, minor configuration improvements

Correlated risks

Governably connects findings across surfaces to identify compound risks. For example:

  • An employee with breached credentials who also granted an AI tool access to company files
  • No DMARC policy combined with breached employee emails (high phishing risk)
  • A publicly shared file owned by an employee with breached credentials

Correlated risks are typically rated one severity level higher than their individual components.

Improving your score

  1. Fix critical findings first: use the remediation plan (Starter plan) for prioritised steps with direct admin console links
  2. Connect more integrations: scanning all five surfaces gives you a complete picture
  3. Govern your AI tools: approve, flag, or block discovered tools (Growth plan)
  4. Re-scan regularly: monthly at minimum, weekly for active remediation