Platform · Exposure intelligence
Exposure intelligence: what attackers learn without touching you
Exposure intelligence collects what is publicly knowable about your organization that an attacker could use: leaked credentials, exposed source code, forgotten hostnames and dangling records. It is the indirect half of our philosophy, and most testing providers leave it out.
The signals we read
| Signal | What it reveals | How we handle it |
|---|---|---|
| Client-side source exposure (guide) | Public source maps, reconstructed front-end source, configuration files such as .env and .git/config | Config files count only when the content matches a real configuration file. Secret values are masked; full evidence stays private. |
| Infostealer exposure (guide) | Credentials and sessions stolen from infected devices and tied to your domains | Checked for verified domains; secret values masked |
| Breach and credential exposure | Your domains and addresses in known breach records | Reported with masked values |
| Certificate transparency (guide) | Every certificate issued for your names, including hosts you forgot | Feeds discovery and change tracking |
| Subdomain-takeover fingerprints (guide) | DNS records pointing at services nobody has claimed | Reviewed by the team before it reaches you |
| Public code references | Your domains, keys or internal names in public repositories | Reviewed and reported with masked values |
How we rate client-side source exposure
Not everything a source map reveals is equally dangerous. Severity follows what was exposed, and each finding carries a clear action.
| What was exposed | Severity | Action |
|---|---|---|
| Private keys, access or refresh tokens, provider API secrets, credentials in URLs, session-bearing tokens | Critical | Rotate now |
| Reconstructable application source | High | Remediate the exposure |
| Source maps that reveal paths and build layout only | Medium | Restrict publication |
| Public configuration values, hashes and identifiers | Review | Review in context |
Sensitive evidence stays private
Full reconstructed source and secret values never appear in reports, notifications, logs or dashboards. They are kept in private storage, outside anything served to the web, and can be retrieved only by authorized users of your organization. What you see in a finding is masked.
What our team adds
A leaked key or a dangling record needs context: is it live, what does it unlock, who needs to act? The team confirms what matters, tells you what to rotate or remove first, and checks again after you act.
Questions about exposure intelligence
Which domains can you check?
Only domains you have verified. Exposure intelligence starts from your verified assets.
What happens when you find a live secret?
It is flagged for immediate rotation, with the secret masked in every report and notification, and the team follows up with you.
Does this run continuously?
Yes. It is part of continuous coverage, within your plan.
Find it before an attacker does.
Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.
Facts on this page verified 11 November 2026.