Requirements
- Enterprise access with the Dark Web Monitoring module
- A monitored company domain
- An approved retention and access policy for credential-exposure data
- Python 3.10 or later with
requests
Evidence sources
The two endpoints use different filter names and response envelopes. The collector normalizes both without retaining
password, hashed_password, address, phone, IP address, or other unnecessary fields.
Run the collector
collect_credential_exposure.py
Response procedure
- Match the reduced email identifier to an active identity through an access-controlled internal process.
- Confirm whether the returned breach source and date are relevant to the identity.
- Apply your identity policy, such as password reset, session revocation, multifactor-authentication review, or credential rotation.
- Record the action and owner in the incident system without copying raw credential values.
- Close the case only after the identity control confirms the required action.
FULLHUNT_BASELINE_ONLY=1 to create state without generating an initial incident backlog.
Data handling
- Encrypt state and incident records at rest and restrict access by job role.
- Retain stable FullHunt record IDs and source dates for evidence lineage.
- Define deletion windows for resolved records and departed users.
- Avoid storing the full API response unless a documented legal or incident-response need requires it.
- Treat an empty query result as
not returned, not proof that no credential exposure exists.
