What happens before, during, and after your Hound test.
Schedule the test and provide the domain you want tested. We’ll provide a code to add as a DNS record to verify you control the domain. Create dedicated test accounts in your application for the roles you want covered. Send us the test account credentials for Hound to use during the test.
Hound builds a working model of your application’s roles, workflows, and trust boundaries as it tests. Evidence shapes what it tests next. Every reported finding is independently verified. Guardrails restrict state-changing operations to approved test accounts and resources.
Your report includes verified findings, supporting evidence, test coverage, limitations, and remediation guidance.
When fixes are ready, schedule a retest. Hound retests every issue from your original report and reports each as fixed, open, or inconclusive.