Application pentesting & security projects

Tell us what
needs a closer look.

Need a pentest before a release or customer review? Start here. We also take on cloud, AI, infrastructure, and specialist security work.

What happens next

Let's work out the scope.

You don't need a test plan to get in touch. Tell us a little about the project and any deadline. We'll ask for the details we need.

  1. 01We read your enquiry and come back with questions.
  2. 02Together, we work out what to test and what access it needs.
  3. 03If the project fits, we send a written scope, schedule and quote.
  4. 04We agree on confidentiality, authorization and safety rules before access.

Prefer email? contact@balhence.com

See what the report looks like: read the fictional sample.

Want to prepare a little more? Draft a web or API test brief. It stays in your browser until you choose to send it.

Sending this form doesn't authorize a test. Scope, permissions, safety rules, schedule, and terms must be agreed in writing first.

Just the basics for now. Fields marked * are required. Please don't send credentials or private findings.

Leave out passwords, API keys, customer data, private findings, and confidential diagrams. We'll agree on a secure way to share those later.

Optional preparation

Useful things to have in mind.

No extra homework required. These are the questions we usually start with.

01 / SYSTEMS

What is involved?

Products, infrastructure, AI systems, devices, code, or the processes around them.

02 / PEOPLE

Who owns the work?

The technical lead, system owners, decision-makers, and anyone needed to approve access.

03 / CONSTRAINTS

What should we know?

Deadlines, sensitive environments, operational limits, and work already underway.

04 / OUTCOME

What do you need from the work?

A report for a customer, help with a release, a list of fixes, or an answer to a security question.