Start with a short email.
Write from your organization's address with a few plain facts. We take it from there in private.
What to include.
The email button fills in these headings for you. Answer each in a line or two.
Leave sensitive details out of the first email. No network ranges, hostnames, credentials, findings or names of people outside your organization. We ask for those later, over the channel you choose.
- Organization
- The legal name of the organization that would engage us.
- Your role
- Your title and whether you would own the engagement.
- What is in scope
- Systems, sites or teams in broad terms. No addresses, hostnames or credentials yet.
- Target dates
- When you need testing to start and any deadline it answers to.
- Who can authorize testing
- The role that can sign authority for the systems in scope.
- Preferred secure channel
- How you would like to continue once we have replied.
-
Acknowledge
A person at Bendings replies to confirm we have your message and tells you who will handle it.
-
Mutual NDA
Both sides sign a non-disclosure agreement before anything specific about your environment is shared.
-
Scoping conversation
The engagement lead talks through objectives, scope, constraints and the framework your regulator or board uses.
-
Written proposal
You receive the proposed scope, approach, team, schedule and fees in writing, for your review.
-
Signed authorization and rules of engagement
The system owner signs authority to test. Rules of engagement name who can stop the work and how.
-
Kickoff
The team meets your contacts, confirms windows and escalation paths, and testing begins inside the agreed rules.
Found a vulnerability in something of ours? Please follow the disclosure policy instead of this inquiry route.
Email engage@bendings.com