Dehashed

Dehashed is a breach-data search platform that indexes credential leaks and other exposed data. The Guard integration with Dehashed adds breach-search enumeration to your passive OSINT collection runs, allowing your team to identify compromised credentials tied to your assets before attackers can exploit them.

---

Prerequisites

• An active Dehashed account with API access enabled.
• A Dehashed API key.
• The Integrations permission in Guard.

---

Connect Dehashed to Guard

1. In Guard, navigate to Integrations > OSINT > Dehashed.
2. Click Connect.
3. Enter your Dehashed API Key.
4. Click Save. Guard validates the key against the Dehashed API before storing it.

Once the connection is confirmed, Dehashed is available as a passive source in Target-OSINT collection runs.

---

Use Dehashed in a Target-OSINT collection run

1. Navigate to OSINT and start a new Target-OSINT collection run.
2. In the Sources step of the wizard, select Dehashed alongside any other passive sources you want to include (such as Hunter, Lusha, or Apollo).
3. Complete the remaining wizard steps and launch the run.

Guard queries Dehashed for breach data matching the targets defined in the run. Results are ingested and surfaced in the OSINT findings view alongside data from other configured sources.

---

Review breach findings

Dehashed results appear in the OSINT findings view after the collection run completes. Each finding includes the breach data returned by Dehashed and is available for triage and remediation tracking through the standard Guard workflow.

---

Disconnect Dehashed

1. Navigate to Integrations > OSINT > Dehashed.
2. Click Disconnect and confirm the action.

Disconnecting removes the stored API key and prevents Dehashed from being selected in future collection runs. Findings already ingested are not removed.