- Tested: the compromised data was tested to determine if it is live/active;
- Sample: the compromised data was posted to prove its validity;
- Keylogged or Phished: the compromised data was entered into a fictitious websiteor extracted through software designed to steal PII;
- 3rd Party Breach: the compromised data was exposed as part of a company’s internal data breach or on a 3rd party Website;
- Accidental Exposure: the compromised data was accidentally shared on a Web, social media, or Peer-to Peer site;
- Malicious / Doxed: the compromised data was intentionally broadcast to expose PII.
Identified method used to capture/ steal data: how was the data stolen or compromised?
Have more questions?
Was this article helpful?
Provide feedback for the Documentation team!
Browse this section
- Compromise Data Spike
- Dark Web ID Data Integrity
- CSS Compromise Type
- I see fake emails (false positives). Why is this important?
- How are the stolen or exposed credentials found on the Dark Web ID?
- What is the Dark Web?
- What does password criteria mean?
- Some of this data is old and includes employees that are no longer working for us. Doesn’t this mean we are not at risk?
- Identified method used to capture/ steal data: how was the data stolen or compromised?
- Does the identification of my organization’s exposed credentials mean we are being targeted by hackers?
- See more