Start the scoping interview
Begin with a concise description of the system and the business outcome. The boundary can be refined before a fee or testing window is agreed.
Scope an assessmentCONTACT-ROUTE
A useful first contact starts with the right context.
Instead of a generic inbox, each request starts in the route designed for it. That captures the useful context, keeps secrets and evidence out of a public channel, and places the request in human review.
01
A new assessment
The scoping interview asks about the objective, assets, roles, access model, environment, third parties, and safety constraints. Its answers are stored as a draft. They are not an invitation, proposal, or authority to test.
What to prepare
A high-level asset list, role and tenant counts, preferred access model, target date, third-party ownership, and prohibited actions.
What not to submit
Do not place passwords, access tokens, findings, sensitive code, or exploitation evidence in a public channel. A protected exchange is agreed only after review.
02
An active engagement or urgent stop
Questions about work already underway belong with the people and channels named in the statement of work and rules of engagement. An urgent stop request should go to the contact designated for that scenario, not the public intake route.
03
Joining as a tester
Membership is by invitation, not an open jobs board. The careers page explains the experience and work evidence that matter, while the partnership page describes assignment and accountability.
The introduction path
See what is reviewed before an invitation and how fit is assessed.
Read the careers pathThe partnership model
Review adoption, transparency, and quality-control principles without repeating the full terms here.
Review the partnership modelNEXT DECISION
Have a system that needs assessment?
The scoping interview creates a structured draft for human review. It sends no message or commitment automatically.
Start scoping