Service package

Authorised Security Verification

Controlled technical verification of attack surface, web/API, hosts, configuration, supply chain and identities — only after payment and documented rights verification.

price after verified scope

Start guided tool Ask a personal question All services

Scope and boundaries

What the entry price covers

Background

Why companies ask for this

Small companies often know that something should be improved, but the first step is unclear. This page turns the topic into a narrow technical start.

Clear first scope

Fixed next step

Documentation for owner and office

Guided automatic start

Connect the right source and receive a visible first result

1. Prepare: The intake phase connects no target system. Active testing is blocked server-side until payment, rights evidence, exact scope, rules of engagement and safe mode are all confirmed.
2. Automatic step: After the complete gate is approved, the run orchestrates selected network, web/API, host, configuration, supply-chain and identity checks and takes findings through discovery, normalisation, correlation, risk, recommendation, evidence, remediation, recheck and history.
3. Result: Only a safe scope and approval plan is produced immediately. An active run remains technically blocked until documented admin approval.
4. Control: A customer checkbox is not authorisation to test. Start only after the matching package is fully paid, an admin has verified documentary rights evidence, the exact target scope is documented, rules of engagement with a test window and emergency contact are approved, and safe mode is confirmed. No DoS, production fuzzing or destructive payloads.

Your first deliverables

Approval matrix for payment, rights, exact scope, rules of engagement and safe mode
Selection of six technical verification modules and their safe boundaries
Ten-stage flow from discovery to automatic recheck and history
Normalised findings with risk, recommendation, evidence and remediation status

Open setup in customer portal

Do not enter passwords, access tokens, API keys, private keys, payment data or confidential documents. Secure access is agreed separately and only when required.

Implementation

How this service starts

1 Short technical audit
Clear output, no hidden full automation.
2 Controlled setup with approval
Clear output, no hidden full automation.
3 Documentation for owner and office
Clear output, no hidden full automation.
4 Monthly operation if useful
Clear output, no hidden full automation.

Request this package

Answer the package-specific questions. We use the details to prepare the right next step.

Name Company Email Phone Website What should improve first? How urgent is it? Which systems or tools are involved?

FAQ

Typical questions

When can an active security verification start?

Only after the matching package is paid in full and an administrator has verified documentary proof of rights, the exact target scope, rules of engagement, the test window, emergency contact and safe mode. The public page itself starts no scan.

What can be checked?

Depending on the approved scope: attack surface and network services, web and API security, host and operating-system vulnerabilities, configuration, cryptography and exposed secrets, dependencies and supply chain, plus identity and access settings.

How are risky checks handled?

Production systems are checked in safe detection mode. Known RCE and memory-related vulnerabilities are normally identified through versions, CVE correlation and non-destructive templates rather than production fuzzing or executing damaging payloads.

What result do we receive?

Normalised and correlated findings with risk, evidence and remediation recommendations, followed by an approved automatic recheck and a traceable history. Any expanded or changed target scope needs a new approval.