Web applications
Authentication, permissions, session handling, and the business logic behind your important user journeys.
Penetration testing
Focused, manual testing for the systems your business depends on. We agree the scope, test real attack paths, and give your team evidence it can act on.
01 / COVERAGE
Select the surfaces that matter. We turn that inventory into an agreed test plan with explicit exclusions.
Authentication, permissions, session handling, and the business logic behind your important user journeys.
Object and function access, tenant boundaries, data exposure, and the way services trust one another.
Agreed iOS and Android builds, their backend APIs, sensitive local storage, and client-side trust assumptions.
The authorized accounts and services: identity permissions, exposed resources, configuration, and routes between workloads.
Internal or external networks, exposed services, segmentation, and management interfaces within the agreed boundaries.
Include the CRM, support, identity, and payment integrations that carry sensitive data or privileged actions.
Follow the connection. Examine the application. Understand where privileges change.
INSPECTION FOCUS / 01
TLS encrypts traffic in transit. Review how peers are authenticated, where encryption terminates, and how the receiving service checks access.
INSPECTION FOCUS / 02
Examine local storage, sessions, permissions, and service calls within the agreed scope. The app sandbox separates application resources; backend authorization remains a separate check.
INSPECTION FOCUS / 03
System services and the kernel operate across distinct privilege boundaries. Inspect the interfaces included in scope: app access does not grant kernel or root privileges.
The agreed scope determines which layers are tested.
02 / HOW IT WORKS
Agree assets, environments, objectives, test dates, access, exclusions, and operational limits. Written authorization is in place before testing starts.
Researchers combine manual testing with supporting tools, verify findings, and document the conditions needed to reproduce them. Urgent findings follow the agreed escalation route.
An executive summary explains business risk. Technical findings give your engineers evidence, affected assets, severity reasoning, and remediation guidance.
Retesting checks the agreed fixes against the original findings. The retest window, coverage, and any additional work are defined in your engagement agreement.
03 / GET READY
A useful brief lets us scope the work accurately. Share an overview first; we agree a secure route for credentials and sensitive material.
The commercial model is agreed before testing. Pay-On-Catch is available only for eligible PTaaS engagements explicitly agreed in writing; validation rules and pricing are part of that agreement.
Sources & further reading
Tell us what needs testing and when. We will help you define a practical engagement.