Exploit Hound: what it collects and how
For the MSP technician or analyst who onboards a customer into Exploit Hound: the hosted platform and the single agent that runs as onsite probe or OS client (outbound TLS 443, nothing inbound), the collection methods grouped by what they do to the customer's systems (reach out, read configuration, only listen) and what each needs, why assets must be confirmed and authorized before anything is assessed, and how to report coverage gaps as unassessed rather than clean.
- Level
- Intermediate
- Length
- About 45 minutes
- Contents
- 3 lessons · 1 video · final exam
- Status
- Published · updated 2 Oct 2026
- Exploit Hound
Skills you'll practise
- Describe the split between the hosted platform and the collectors that run in the customer's network, including the connection direction
- Sort Exploit Hound's collection methods into those that send traffic, those that read configuration and those that only listen, and state what each needs
- Set up scope so that only confirmed, authorized assets are assessed, and refuse targets the customer cannot authorize
- Read deployment and coverage information and report gaps as unassessed rather than as clean
- Say which capabilities the site labels Beta and where to check their current status
Course outline
- 1.Exploit Hound: what it collects and howVideo · 2 min
- 2.Hosted platform, local collectionLesson · 15 min
- 3.Reach out, read, or only listenLesson · 15 min
- 4.Authorization, scope and coverage gapsLesson · 15 min
- 5.Exploit Hound: what it collects and how: knowledge checkKnowledge check · 17 questions
- 6.Final exam8 questions · passing it completes the course, so people who already know the material can test out
Sources it draws on
The lessons and questions are written from these references, so learners can go back to the original.
- Exploit Hound: home (Discover, Prioritize, Act, Verify; how the exposure picture is built)
- Exploit Hound: platform overview (architecture, scoring, attack paths, identity, ticketing, alerting, verification, exceptions)
- Exploit Hound: What we scan (collection methods, what each needs and cannot determine)
- Exploit Hound: Integrations and their status (GA, Beta, Not Built)
- Exploit Hound: Trust center (architecture, tenant isolation, secrets, access, AI handling, audit)
- Exploit Hound: Service status (what the status page covers)
- Exploit Hound: Product tour (twelve console screens on demonstration data)
See it with your own jobs and topics
Tell us about your team and we'll walk you through setup, from choosing jobs to your first skills check.