This workflow creates a privacy-reduced incident queue from Enterprise dark-web records. FullHunt supplies evidence. Password reset, session revocation, user notification, and case closure happen in your identity and incident-response systems.

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
Do not test returned credentials against an account or system. Do not copy raw passwords into logs, tickets, chat, or state files.

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

  1. Match the reduced email identifier to an active identity through an access-controlled internal process.
  2. Confirm whether the returned breach source and date are relevant to the identity.
  3. Apply your identity policy, such as password reset, session revocation, multifactor-authentication review, or credential rotation.
  4. Record the action and owner in the incident system without copying raw credential values.
  5. Close the case only after the identity control confirms the required action.
The first run reports every returned record as new. Set 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.