30 or 60 minutes / confirmed by email

Request a security scoping call

Tell us what you are planning and offer one or two times that work for you. This is a call request, not an instant booking: Balhence confirms the agreed slot by email.

A useful first conversation

Bring the goal. We will shape the questions.

You do not need a finished scope. A short description of the system, why the work matters now, and any deadline is enough to start.

  1. 01You send preferred times in your local time zone.
  2. 02We reply by email to confirm a mutually available slot.
  3. 03On the call, we discuss boundaries, access, timing, and the evidence you need.
  4. 04If the project fits, a written scope and quote follow separately.
No test is authorized by this call request.

Testing begins only after scope, permissions, safety rules, schedule, and terms are agreed in writing.

Prefer email? Write to contact@balhence.com.

This form requests a time; it does not reserve one. Fields marked * are required. Please do not send credentials, private findings, customer data, or confidential diagrams.

We try to detect this from your browser. Check it before sending.

Both times are interpreted in the editable time zone above. They are preferences, not reserved availability.

A high-level description is enough. We will agree on a secure channel before requesting sensitive material.

Optional preparation

Four details make the call more useful

A rough answer is fine. No sensitive evidence is needed at this stage.

01 / SYSTEM

What are we discussing?

A web app, API, SaaS product, AI feature, cloud environment, network, or another approved system.

02 / REASON

Why now?

A release, customer request, audit, recurring assurance plan, or a specific security question.

03 / TIMING

What is the real deadline?

The date the report or decision is needed, not only the preferred week for testing.

04 / OUTCOME

What should the work produce?

A remediation-ready report, compliance evidence, attack-path validation, or release assurance.