Research depth. Clear assessments. Human accountability.

About Balhence

Balhence is a researcher-led offensive security company helping product teams test web applications, APIs, SaaS and AI systems with controlled proof and human-validated evidence.

Company direction

From one assessment to a validated security loop

Balhence is building toward a repeatable model that starts with a baseline assessment, keeps scope and evidence structured, and rechecks selected high-risk paths as products change.

Delivery today remains specialist-led. Automation can support approved research, repeatable checks and evidence organization; it does not expand authorization or replace human validation.

Explore recurring attack-path validation or read the public testing and client-data standards.

Specialist-led assessments

Coverage shaped around your system.

A web application, an API, a cloud environment, and an AI agent expose different trust boundaries. We design coverage around the system, its users, and the decisions the assessment needs to support.

The person who helps define the scope stays involved in the technical work, evidence review, and handover. Your team can discuss a finding with someone who understands how it was investigated.

Balhence works across penetration testing, security research, code review, and defensive engineering. When a project requires specialist expertise or equipment beyond that scope, we say so before making a commitment and agree on the right support.

Why Balhence exists

Security research applied to decisions your team must make.

A list of scanner results is not the same as understanding how a product could be compromised. Useful testing needs curiosity, controlled proof, and enough product context to separate a real risk from noise.

Balhence brings that research mindset into a defined assessment: agree on the boundary, investigate how the system behaves, validate what matters, and explain the result in terms engineers and decision-makers can use.

Private submission archive / snapshot 8 Nov 2026

Research breadth, summarized without exposing programs.

A private body of coordinated-disclosure work informs how Balhence approaches authorization, identity, workflow, server-side and AI trust boundaries.

1,100+Documented reports in private submission archives
690+Explicitly labeled Critical or High
120+Explicitly labeled Critical
3Coordinated-disclosure platforms represented

What the archive covers

  • Authorization, privilege, and tenant isolation
  • Authentication, recovery, sessions, and identity
  • Injection, code execution, and server-side request boundaries
  • AI agents, tools, and automation trust boundaries
  • Business logic and workflow integrity
  • Secrets, private data, and unintended exposure

How to read these numbers

The public figures are a conservative rounded roll-up of unique, structurally recognized report documents across three private submission archives. Templates, reserved records, low-structure artifacts, ambiguous severity labels, and unlabeled reports are not used to increase the displayed severity totals.

They do not claim that every report was accepted, paid, resolved, or retained at the stored severity. Program and target identities, report titles, reproduction details, credentials, and evidence remain private. The themes are non-exclusive and are not presented as a category distribution.

Review our testing and data standards
Working standards

The basics we don't skip.

01 / SCOPE

Permission comes first.

Systems, access, methods, data handling, contacts, and stop conditions are agreed before work starts.

02 / PROOF

Show the evidence.

A plausible tool result isn't enough. We check findings and changes before asking your team to act on them.

03 / CARE

Use the smallest safe check.

Controlled accounts and synthetic records help us answer the question without touching more data than necessary.

04 / HANDOFF

Make time for questions.

The handover includes a walkthrough and whatever validation or re-testing is agreed in your scope.

How we use AI

Useful tools.
Our responsibility.

We use AI for research, analysis, code, and documentation where it helps the work. Your approval determines which tools and data we can use. Human review stays part of the process.

Where AI fits

  • Researching technologies and organizing approved project context
  • Connecting observations across code, configuration, and workflows
  • Helping review threats, controls, and detection coverage
  • Developing custom defensive tools and repeatable checks
  • Organizing redacted evidence with traceable sources
  • Drafting documentation, remediation options, and handover notes

What people own

  • The scope, permissions, and safety of each action
  • Architecture decisions and the tradeoffs behind them
  • Validation of findings and review of generated code
  • The meaning of the evidence and its business impact
  • Recommendations, priorities, and quality of delivery
  • Checking fixes and deliverables against the agreed requirements
Your data and AI

AI use is documented in the scope and rules of engagement. No public model receives client credentials, tokens, customer records, source code, or unredacted vulnerability evidence unless the client explicitly approves the provider, purpose, and processing terms. No model autonomously tests production.

Read how we use AI in testing

Penetration testing methodology and working standards

We use recognized references to organize coverage and explain the limits of an assessment. The methods used depend on the systems and the agreed scope.

These are methodology references, not certifications or endorsements. Every reported finding is reviewed by a person, and the report identifies what was checked, excluded, or left unverified.

For features you build with models or agents, see AI and LLM penetration testing.

Balhence / Santulan

Security has to work with your product.

The name Balhence comes from santulan, meaning balance. Your team has releases to ship, customers to support, and data to protect. Security advice needs to account for all of that.

A recommendation that ignores the way your team works is unlikely to stick. We'll explain the risk, talk through the tradeoffs, and help you choose a fix you can maintain.

Before you choose

Take a look at the work.

Our sample penetration test report uses fictional systems and findings to show the format. For other projects, we'll agree on the deliverable and how to check it before starting.

Work you can inspect

  • A detailed sample report for penetration testing
  • Methods and deliverables matched to the engagement
  • Clear scope, exclusions, and safety controls
  • Published AI-use and client-data guardrails
  • Practical handover and agreed validation checks
  • Direct access to the person responsible for delivery

Clear expectations

  • The work covers the systems and outcomes we agree on
  • Results reflect the version and access available during the work
  • Every reported issue is checked by a person
  • No assessment can guarantee that every vulnerability has been found
  • Your auditor or reviewer decides whether deliverables meet their needs
  • Testing starts only after written authorization

Publication and evidence standards

Balhence publishes buyer guides to help teams plan assessments and understand deliverables. Organization bylines link to this approach, while archived research keeps its original byline and publication context. A guide describes how to prepare for a service; it does not establish an individual's certification or a client's results.

  • Sources and dates: methodology and regulatory references link to the responsible publishers. Publication dates identify the original article; modification dates reflect substantive content changes.
  • Examples: worksheets and the sample report use fictional systems and findings. They demonstrate scope and report format, not client outcomes.
  • Research: Nine first-person field notes in the Bug Bounty Archive anonymize private controlled research. Ten historical articles retain their original technical substance and publication dates; modification dates disclose the editorial wording updates made for this first-party Balhence archive.
  • Corrections: send a page URL, the statement, and a supporting source to contact@balhence.com. Please exclude credentials and confidential findings.

Start with the penetration testing guides or compare assessment types and their limits.

Working together

You won't have to keep starting over.

The person who scopes the project stays involved in technical decisions, evidence review, and the handover. You can ask questions with the context already in place.

  1. 01
    Direct communicationTalk to someone who understands your goals and the work underway.
  2. 02
    A realistic scheduleWe accept work only when we can support the agreed timeline.
  3. 03
    The right mix of skillsWe shape the approach around your problem and agree on specialist support when needed.
Rules of engagement
AUTHORIZEDROE-01

What we agree before starting.

The systems, methods, data handling, and checks that define the work.

scope: systems + workflows
methods: research / review / build
data: approved handling only
result: validated deliverables
  • Named business and technical contacts
  • Permissions and boundaries documented
  • Evidence handling agreed
The practice in brief

Balhence at a glance

A concise public profile of Balhence
PracticeBalhence
SpecialismPenetration testing, security research, code review, and defensive engineering
Core coverageWeb applications, APIs, SaaS products, AI and LLM applications, cloud environments, and networks
Working modelRemote, scoped engagements that begin only after written authorization and agreed rules of engagement
Who we work withProduct, engineering, technology, and security teams
MarketsRemote engagements for India and US teams
Contactcontact@balhence.com
Talk to us about your assessment

What are you building, and what do you need to know?

Tell us about the system, what prompted the test, and when you need answers. A rough description is enough to start defining the boundary.