Selector Best Practices
SpyCloud Investigations is a flexible, analyst-driven solution. This guide outlines how to effectively use selectors to accelerate workflows, uncover hidden links, and avoid false assumptions when querying SpyCloud’s breach, infostealer, phishing, and combolist datasets.
🔒 Privacy-Protected Selectors
These selectors are SHA-1 hashed before ingestion. You may submit them in plaintext — SpyCloud will hash them automatically.
- Bank account number
- Credit card number
- Social Security Number (SSN)
- Passport number
- National ID
- Driver’s license number
👤 Identity Selector Best Practices
Email
Use full email addresses (e.g., [email protected]) for targeted identity investigations.
Email Username
Search just the portion before @ (e.g., jane.doe) to find reuse across domains.
Username
Run usernames across multiple selectors to detect reuse.
Common usernames may return a large, noisy set.
Social Handle
Uncover cross-platform reuse of handles (e.g., Telegram, Instagram, LinkedIn).
Phone Number
Try multiple formats — with/without country codes. Also test as a password or username.
Name
Use naming patterns (e.g., jdoe, john.doe) to build likely selectors.
For ambiguous identities, request an analyst investigation.
🧠 Investigative Techniques – Moniker Reuse Strategy
🌐 Domain Selector Types
🖥️ Infrastructure Selector Types
📅 Date Filter Best Practices
Summary
SpyCloud Investigations gives analysts powerful, flexible tools — and selectors are at the heart of it.
To get the most value:
- Understand which selectors are hashed
- Think like your adversary: humans reuse data across platforms
- Use pivots across selector types to uncover connections
Need help refining a strategy or resolving ambiguous data?
Use Analyst Credits for expert-guided investigations.
Updated 3 months ago