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.

01 Signals

The signals we read

The signals we read
SignalWhat it revealsHow we handle it
Client-side source exposure (guide)Public source maps, reconstructed front-end source, configuration files such as .env and .git/configConfig 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 domainsChecked for verified domains; secret values masked
Breach and credential exposureYour domains and addresses in known breach recordsReported with masked values
Certificate transparency (guide)Every certificate issued for your names, including hosts you forgotFeeds discovery and change tracking
Subdomain-takeover fingerprints (guide)DNS records pointing at services nobody has claimedReviewed by the team before it reaches you
Public code referencesYour domains, keys or internal names in public repositoriesReviewed and reported with masked values
02 Severity

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.

How we rate client-side source exposure
What was exposedSeverityAction
Private keys, access or refresh tokens, provider API secrets, credentials in URLs, session-bearing tokensCriticalRotate now
Reconstructable application sourceHighRemediate the exposure
Source maps that reveal paths and build layout onlyMediumRestrict publication
Public configuration values, hashes and identifiersReviewReview in context
03 Evidence handling

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.

04 The team's part

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.

05 FAQ

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.