Controlled accounts
Use dedicated test identities, synthetic records and agreed tenant boundaries where practical.
This page states the operating standards behind a Balhence engagement. The signed scope and agreement remain controlling for a specific project.
No testing begins from a form submission or an informal request. The parties first agree the systems, environments, identities, methods, schedule, evidence handling, escalation contacts and stop conditions in writing.
Third-party assets require permission from their owner. A change in scope, environment or safety conditions pauses the affected work until the boundary is confirmed again.
Evidence should prove the issue without creating unnecessary impact.
Use dedicated test identities, synthetic records and agreed tenant boundaries where practical.
Set testing windows, request limits, prohibited actions and an escalation route before execution.
Stop when the agreed evidence establishes realistic impact; do not collect unrelated data.
Use the agreed contact path when a confirmed issue needs attention before the report is complete.
The project agreement identifies what material is needed, how it can be transferred, who can access it, where it may be processed and when it should be deleted or returned.
AI may support approved research, analysis, code, tooling and documentation. Its use does not expand authorization, remove a safety gate or turn an observation into a delivered finding.
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 the detailed human-validation approach.
A candidate observation is checked before it asks your team to act.
Confirm the behavior in the agreed environment with clean controls where practical.
Explain realistic impact, affected roles or tenants, preconditions and known limits.
Provide useful reproduction steps and redact secrets or unrelated data.
Record the tested version and whether the issue is fixed, partial, open or not re-tested.
See the format in the fictional sample report.
Balhence does not describe itself as certified, 24/7 monitored, vulnerability-free or guaranteed to find every issue. An assessment reflects the agreed scope, access, environment and time available.
Framework references explain methodology; they are not certifications or endorsements. A report can support an audit or customer review, but the relevant reviewer decides whether it meets their requirement.
Use the published security.txt contact and guidance. Do not include passwords, private keys, session tokens or unrelated personal data in the first message.
For questions about a proposed engagement, contact contact@balhence.com or send a scoped enquiry.