Brand & domains
Open-web leaks & secrets
We spot the source code, secrets, storage buckets, container images and pastes that expose parts of your organisation outside your systems. Open-web leak monitoring spots the source code, secrets, storage buckets, container images and pastes that expose parts of your organisation outside your systems.
The problem
An API token in a public repository, an open storage bucket, a container image embedding a configuration, a forgotten paste: these leaks involve no attack. They stay visible for months, and attackers’ engines find them before your teams. Continuous collection of repositories, registries, buckets and pastes finds them first.
Client area preview
What you see
Fictional data, for illustration only: no client, no real data.
What you get: this screen in your client area, refreshed at every synchronisation, with CSV and JSON export.
- 01
Each exposed item: repository, bucket, image, paste, with its location and first-seen date
- 02
The type of secret detected and its apparent validity, never shown in clear by default
- 03
The status: to revoke, revoked, false positive, with the owner
How it works
Our answer in three steps
VesperID searches the open web for your domains, keywords, repositories and cloud spaces, tells the exploitable secret from the false positive, and tells you what to revoke, what to close and who to notify.
- 01
You declare domains, keywords, code repositories (a GitHub organisation or one repository) and cloud spaces to watch.
- 02
Continuous collection scans public repositories, image registries, exposed buckets and paste sites; the platform detects your secret patterns and internal names in them.
- 03
An analyst verifies the exposure, discards samples and public data, and writes the remediation.
Where this data comes from
Leaks come from the continuous collection of public code repositories, container image registries, exposed buckets and paste sites; VesperID searches them for your secret patterns, your domains and your internal names.
Our sources in detailCross analyses
What the platform computes on top
This service’s data is crossed with the others’: here are the analyses that come out of it, all visible in the client area.
Discover the platform- 01
Prioritisation
A still-valid secret in a public repository ranks above an old configuration file: severity, freshness and asset criticality rank the queue.
- 02
Hardening playbook
Revoking the secret, removing the content, checking for use: the “exposure hardening” playbook lists the steps in order.
What you receive
Open-web leaks & secrets
- 01
Alert per exposed secret or space, with the expected action
- 02
Inventory of open exposures, exportable
- 03
Revocation procedure fitted to the secret type
- 04
Monthly follow-up of exposures by team or project
Frequently asked questions
Do you see our private repositories?
No. We only reach what is public. A private repository exposed by mistake becomes visible to everyone, us included; that is exactly what we detect.
What do you do with a secret you find?
We keep its type, its location and its date; the value is not stored and can only be viewed on demand, after re-authentication.
Do you detect leaks from our own contractors?
Yes, if you declare their domains or keywords; ransomware leak-site monitoring covers them too.
Request an exposure assessment.
One hour with an analyst, not a demo: what already circulates about your organisation, what to monitor, what is better left alone. Reply within one working day.
No public price list: bespoke offering, written proposal after scoping.