>_ETESTING consultancy

Your systems are being tested.
The question is — by whom?

Scanners probe your infrastructure every day and nobody sends you the results. An authorized test does — scoped individually, run by hand, and delivered with a written report and an included retest.

Request a scoping call See what we test

// services

Six service lines

Pick one, or combine them. Scope is agreed in writing before any testing begins.

Penetration testing

Adversarial simulation against a defined scope.

A structured attempt to exploit real weaknesses in your environment before an attacker does — reconnaissance, enumeration, exploitation, post-exploitation — constrained by an agreed scope and rules of engagement. Findings are risk-rated and ordered by what to fix first.

  • External and internal network testing
  • Web application testing
  • API and microservices testing
  • Cloud environment review (AWS, Azure, GCP)
  • Assumed-breach and lateral movement scenarios

Vulnerability assessment

Breadth across the estate, with the false positives removed.

Authenticated and unauthenticated scanning across your estate, then manual triage so you get a list you can act on rather than a thousand-page tool export. Useful as a baseline before a first penetration test, or on a recurring cycle.

  • Authenticated and unauthenticated scanning
  • Manual validation of every reported issue
  • Patch and configuration gap analysis
  • Recurring quarterly or monthly cycles

Web and mobile application audits

Source-aware testing against OWASP ASVS and MASVS.

Deep testing of a single application, including the logic that scanners cannot reach: authentication flows, authorization boundaries, session handling and business logic abuse. Grey-box where you can share credentials and architecture notes.

  • Authentication and session management
  • Broken access control and privilege escalation
  • Business logic abuse cases
  • Android and iOS client and storage review
  • Secrets exposure and hardcoded credential checks

Phishing simulation

Measuring how your people respond, without naming and shaming.

Controlled campaigns run against agreed groups, with reporting on click rates, credential submission and — more usefully — how quickly someone reported it. Results come back aggregated, with training recommendations rather than a list of names.

  • Credential harvesting and attachment campaigns
  • Pretext development based on public footprint
  • Report-rate and response-time measurement
  • Aggregated results with awareness recommendations

Smart contract audits

Manual review of on-chain logic before it becomes immutable.

Line-by-line review of EVM-compatible contracts against known vulnerability classes and the logic specific to your protocol. Deployed code cannot be patched, so findings are delivered before mainnet with a re-review once fixes are in.

  • Reentrancy, access control and upgrade patterns
  • Arithmetic and rounding edge cases
  • Oracle dependency and price manipulation paths
  • Gas griefing and denial-of-service conditions
  • Token standard compliance (ERC-20, 721, 1155)
  • Deployment, ownership and key management review

Compliance readiness

Evidence your auditor will accept, gathered before the audit.

Gap assessment and testing evidence mapped to the control frameworks you are being measured against, so the technical requirements are already satisfied when the auditor arrives. This is preparation and evidence, not certification.

  • SOC 2 technical control readiness
  • ISO 27001 Annex A gap assessment
  • PCI DSS segmentation and scope validation
  • Remediation tracking through to re-test

// how it works

Four phases, no surprises

You know the cost, the window and the deliverable before testing starts. Nothing is touched outside the agreed scope.

Phase 01

Scope

A call to agree targets, testing window, rules of engagement and emergency contacts. You get a fixed price and a written authorization to sign.

Phase 02

Test

Hands-on testing within the window. Critical findings are reported the same day rather than held back for the report.

Phase 03

Report

A technical report with reproduction steps and evidence, plus a short executive summary. Followed by a call to walk your engineers through it.

Phase 04

Retest

Once fixes are deployed, the affected findings are tested again and the report is reissued. Included in the original price.

// about

Who does the testing

Engagements are principal-led. The person who scopes your test is the person who runs it and the person who walks your engineers through the report — no junior handoff, no report nobody can explain on a call.

Where a scope calls for a specialism outside that, certified associates are brought in and named to you before work starts. You always know who is testing your systems.

Testing follows published methodology — PTES, OWASP ASVS and MASVS — so findings can be mapped against a standard rather than a private checklist.

OSCP CEH AWS Security Specialty
Engagements delivered
120+
Years in offensive security
7
Sectors
Fintech, SaaS, healthcare, logistics, Web3
Delivery
Principal-led
Typical window
5–20 working days
Report turnaround
5 working days
Retest
Included

Testing is only carried out against systems you own or hold documented authorization to test. A signed authorization letter naming the in-scope assets is required before any engagement begins — no exceptions, including for demonstrations.

// contact

Request a scope

Tell us roughly what you want tested and you will get a scope and fixed price back, usually within one working day.

Or email info@etestingconsultancy101.com directly. Please do not include credentials, exploit detail or sensitive findings in a first email.