Start with a clear assessment brief.

Share your organization, contact details and area of interest. We will use your request to discuss scope and next steps. No testing begins through this form.

Prepare your enquiry

Describe your organization and select the relevant services.
Review the authorization notice and confirm each acknowledgement.
Review the prepared email, then send it from your email service.

Assessment enquiry

Company name

Contact name

Phone or email

Services neededSelect all that apply

Web Application Penetration TestingMobile Application Security TestingCloud Security AssessmentCybersecurity Consulting

Security testing authorization and responsibility

Notice version: 2026-11-10.1

Before you confirm

Testing risks and preparation

Even agreed testing can trigger alerts, reduced performance, service interruption or unexpected data changes. Clients should prepare backups and recovery, coordinate with relevant parties and supply accurate asset and authorization information. If you do not accept testing risks, you may discuss advisory needs without requesting tests.

Responsibilities and limits of liability

Clients are responsible for the accuracy and lawfulness of the authority, asset ownership and information they provide. Losses or claims arising from false authorization, missing third-party permission or a client breach are addressed under applicable law and the agreement. Risk allocation, recoverable losses and liability limits must be separately agreed in the formal contract, to the extent permitted by law. This notice does not exclude liability that cannot lawfully be excluded or permit unlawful, unauthorized or out-of-scope activity. Testing cannot guarantee discovery of every vulnerability or absolute security.

Read the full authorization notice

1.Authority and third-party permission
You must own the proposed systems or hold express authority from their owner. Employment alone does not confer authority to approve testing. Cloud platforms, hosting providers, suppliers and other third-party assets require the relevant permissions. We may request evidence and decline or suspend services if authority cannot be verified.
2.Written testing scope
Before testing, authorized representatives of both parties must sign a service agreement and testing authorization covering domains, IPs, applications and environments, permitted methods and exclusions, testing windows, source addresses, third-party permissions, emergency contacts and stop conditions. Unlisted assets and activities are excluded. Refusal, withdrawal or changes to authorization require the affected testing to pause pending written confirmation.
3.Testing risks and preparation
Even agreed testing can trigger alerts, reduced performance, service interruption or unexpected data changes. Clients should prepare backups and recovery, coordinate with relevant parties and supply accurate asset and authorization information. If you do not accept testing risks, you may discuss advisory needs without requesting tests.
4.Responsibilities and limits of liability
Clients are responsible for the accuracy and lawfulness of the authority, asset ownership and information they provide. Losses or claims arising from false authorization, missing third-party permission or a client breach are addressed under applicable law and the agreement. Risk allocation, recoverable losses and liability limits must be separately agreed in the formal contract, to the extent permitted by law. This notice does not exclude liability that cannot lawfully be excluded or permit unlawful, unauthorized or out-of-scope activity. Testing cannot guarantee discovery of every vulnerability or absolute security.
5.Information use and confidentiality
Company, contact person and contact details are used to discuss this request and retain request confirmation records. A configured external form provider also receives the submission. Do not submit passwords, keys or vulnerability details. Before testing, both parties must separately agree confidentiality, data access, retention, deletion and incident handling requirements.

I will request testing only for assets I lawfully own or am expressly authorized to test, and will provide authorization and required third-party permissions before testing. Without that authority, this is an advisory enquiry only and I am not requesting testing.

I have read this notice and agree that scanning or vulnerability verification may begin only after formal written authorization takes effect and only within its agreed scope. This submission is not testing authorization.

I understand the testing risks and responsibilities above, agree to define both parties’ responsibilities in the formal contract, and agree to use of my submission for this enquiry and its confirmation records.

Caution Include only the information needed for initial contact. Exchange credentials, sensitive architecture and vulnerability details through an agreed channel after confidentiality arrangements are in place.

Review and send your enquiry

Your request includes the selected services and acknowledgement record. Sending an enquiry does not authorize testing.

Complete the required fields and acknowledge the authorization notice before continuing. You must send the request from your email app. You can also email an enquiry directly to the address on this page.

You send the request from your email app. We use your information to discuss this enquiry and retain its confirmation records.

How the engagement proceeds

1
Contact and verification
Discuss your needs and verify the representative’s authority, asset ownership and required third-party permissions.
2
Written agreement
Sign confidentiality, service and testing authorization documents covering scope, timing, risks, responsibilities and stop conditions.
3
Authorized testing
Test only after written authorization takes effect, within its scope, then provide findings and recommendations.

Contact us directly

Email: service@onexasset.comSend email