Owner
The person or organization able to authorize review of the exact system.
Client readiness / five-minute frame
Start with the decision, not the scanner.
A useful first conversation needs a system owner, a real decision and enough architecture to identify where authority and impact meet.
Bring these five things
Decision
What launch, change, risk acceptance or remediation decision the work must support.
System
A simple architecture or data-flow view, including agents, tools, APIs, identities and third parties.
Impact
The highest credible harm to users, money, data, operations or trust.
Safety contact
A technical contact who can answer scope questions and order an immediate stop.
What happens next
- A short discovery conversation confirms fit and the decision to support.
- Delx Security proposes the smallest sufficient scope and explicit exclusions.
- Data handling, commercial terms and responsibilities are agreed.
- Any active testing waits for accepted Rules of Engagement.
- Delivery ends with evidence, remediation priorities and a verification path.
Begin privately
Do not send credentials, production data, exploit material or confidential architecture in the first email. A secure handling path is agreed only after fit and scope are clear.
Initial contact