Application pentesting & security projects

Request a penetration test

To request a penetration test, share the application or system, the main user roles, and your deadline. Balhence replies with scoping questions, then a written proposal covering scope, effort, exclusions, deliverables, and any re-test. No testing begins without written authorization.

Start your enquiry Prefer email?
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.

Working remotely from India or with a US team? Include your time zone, review date, and any tester-location or evidence-handling restrictions so we can confirm whether the proposed engagement fits.

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

What to include in your pentest enquiry

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.

What happens after your penetration test request?

  • A scoping conversation to confirm systems, roles, tenants, integrations, access, and deadline.
  • A written proposal with coverage, effort, exclusions, deliverables, and any re-test.
  • Agreed authorization, data-handling terms, and rules of engagement before testing.
  • A test window confirmed against scope, readiness, and availability.

We work remotely with US teams. Agree business-hours overlap for scoping and escalation, and discuss NDA or MSA terms before the engagement. See US delivery details.

Prefer to sketch the scope first? Build your scope, browse testing services, or review a sample penetration testing report.