Service · Penetration Testing
You define the scope. We test it properly.
Conventional VAPT across web applications, mobile applications, and thick clients. Every exploit path validated by hand before it's written down, priced by what's actually in scope — never by how many days it takes.
How it's priced
Fixed-fee per scope
- Quoted against the assets in scope, agreed before testing starts
- No man-day billing — the price doesn't change if testing runs long
- One retest included, to confirm each fix actually closed the gap
What's covered
One engagement, six surfaces.
Most products aren't just a website. We test the surfaces attackers actually reach — together, in a single scoped engagement.
Web applications
Authenticated and unauthenticated testing for access-control gaps, business-logic flaws, and injection-class issues across customer and admin-facing apps.
Mobile applications
Static and dynamic analysis of the app plus the APIs it talks to, including certificate-pinning and anti-tampering bypass attempts on iOS and Android.
Thick clients
Binary and traffic analysis of installed desktop software — local storage, memory, IPC, and the protocols it uses to reach your servers.
Network — internal & external
Perimeter testing against your external footprint, and internal testing for segmentation gaps and lateral movement paths.
Host security
Hardening review and vulnerability assessment of individual servers and endpoints against recognised benchmarks.
Active Directory
Privilege-escalation paths, misconfigured GPOs, Kerberos abuse, and lateral movement across your AD environment.
Why fixed-fee
Man-day billing rewards time. We'd rather be rewarded for coverage.
Billing by the day gives a tester every incentive to stop once the clock runs out, not once the scope is actually covered. We quote the scope once, in full, before testing starts — so slower testing on a hard target doesn't cost you more, and thorough testing on a simple one doesn't cost you less than it should.
How it runs
Five stages, the same way every time.
The same process regardless of target — because a report you can trust starts with a process you can describe.
Scope
We agree the exact assets, roles, and rules of engagement in writing before any request is sent.
Test
Manual exploitation against the agreed scope, with automation used to widen coverage, not replace judgment.
Score
Every finding rated under CVSS v3.1, so a Critical means the same thing in every report we send.
Report
Evidence, reproduction steps, and remediation guidance a developer can act on without a follow-up call.
Retest
We verify each fix against the original proof of concept before we call anything resolved.
Inside the report
Built to be read by your engineers, not just filed by your auditor.
Every Ikigai Security report follows the same structure, in our own formal report template:
- Plain-language executive summary for stakeholders who won't read the technical detail
- Each finding scored under CVSS v3.1, with the vector string shown alongside the number
- Step-by-step reproduction and evidence for every finding — screenshots, requests, and responses
- Remediation guidance specific to your stack, not a generic OWASP link
- A retest section confirming which findings are closed, and which remain open
Who this is for
Teams that need a real answer, not a satisfied checkbox.
Penetration Testing is our flagship engagement — the one most of our government, financial, and healthcare clients start with.
Ahead of an audit
You need an annual or periodic pentest on file — and would rather it hold up under real scrutiny than just satisfy a checkbox.
Before a launch
A new application or major release is going live, and you want it tested against real exploitation before customers or regulators find the gaps.
After a near miss
Something was almost exploited, and you need a full, evidence-backed picture of what else is exposed before it happens again.