Web application pentesting
Auth, access control, business logic, session handling, injection paths, file handling, and exposed admin workflows.
offensive security consulting
1H Security
Penetration testing for teams that need exploit-driven findings, clear evidence, and remediation advice that engineers can use.
- Focus
- web, API, cloud, attack surface
- Output
- evidence, exploit paths, fixes
what this is
Practical offensive testing.
1H Security tests the controls that protect real applications and infrastructure. The work is scoped around real attack paths, clear evidence, and fixes your engineers can ship.
services
Where offensive review helps most.
API security testing
Endpoint discovery, object-level authorisation, schema drift, token handling, abuse cases, and integration boundaries.
Cloud edge review
Internet-facing cloud services, IAM assumptions, storage exposure, deployment defaults, and control-plane reachability.
External attack surface
Asset discovery, exposed services, forgotten hosts, risky management paths, and evidence-backed prioritisation.
Architecture-informed testing
Threat-model-led testing for new systems, major releases, and sensitive data flows before they become production incidents.
process
A clear path from scope to exploit chain.
-
01
Set boundaries
Agree objectives, dates, access, test accounts, reporting channel, and production-safety constraints.
-
02
Map the attack surface
Build a working model of exposed systems, roles, trust boundaries, APIs, data flows, and control assumptions.
-
03
Prove reachable risk
Validate exploitability with safe evidence, then chain issues where that changes the practical impact.
-
04
Report for repair
Deliver concise findings with reproduction notes, affected assets, impact, and remediation guidance.
deliverables
Findings your team can act on.
Evidence
Reproduction notes, screenshots where useful, affected routes, payload context, and clear exploit conditions.
Prioritisation
Risk ranked by reachability, business impact, chaining potential, and what an attacker actually gains.
Remediation
Fix guidance written for engineering teams, including validation notes for re-testing critical issues.
principles
Practical, scoped, evidence-led.
- Real exploit paths over scanner noise.
- Clear scope, clean communication, no surprises.
- Production-aware testing that protects availability.
- Reporting written for engineers and decision makers.
- Retesting support for critical fixes.
contact
Bring the target, dates, and constraints.
Send the systems, the outcome you need, and what needs to be true at the end. You will get a practical engagement shape back.
[email protected]