Pentest Pricing

6 pentests / month. Rathnakara (OSCP) leads every pentest engagement. Book ahead.

Penetration testing plans

Essentials Plan

When someone is evaluating you

74,999 + taxes
1 Scope Included 1 scope = 1 application type, internal and external network included. The exact boundary of each type is published further down this page, in the scope counter. Add further scopes for INR 44,999 each, 6 business days per scope. There is no scope cap on this plan. The Compliance Plan is for when you need the SOC 2 or ISO 27001 evidence, not for more scopes.
Pick one: AI, web app, API, Android, iOS, desktop, cloud, IoT, internal network, or external network. One target, tested thoroughly.
+1 Scope at INR 44,999 A scope is 6 business days, 5 days of testing and 1 day writing the report. One scope is 6 business days and two is 12. For more than that we confirm the schedule when we scope the work.
No cap on scopes. The first scope carries the engagement setup, so each one after it is INR 44,999 rather than 74,999, and is still tested in full.
Report in 6 Business Days A business day is Monday to Friday; the weekend is our quality buffer and is not counted against your timeline, and Indian public holidays fall outside the count. Of each scope's 6 days, 5 are testing and 1 is writing the report, so the report is produced inside the window rather than after it. The scope row above shows how the total grows when you add scopes.
Kick-off to the v1.0 report. The clock starts once access is verified, so waiting on access never comes out of your testing time.
OWASP Top 10 + PTES Methodology, Investor-Ready Report Industry-standard OWASP Top 10 + PTES (Penetration Testing Execution Standard) methodology. Authentication and access control are inside that baseline: OWASP Top 10:2025 lists them as A07 Authentication Failures and A01 Broken Access Control. Coverage starts here because this is where the lowest-hanging findings are, and there is little value in running advanced work against an application whose baseline has not been verified yet. Deliverable is a full technical report with reproduction steps, fix guidance and risk ratings, plus a 2-page executive summary written for the reader who is not a security specialist. Findings carry their OWASP Top 10:2025 category.
Manual exploitation, authentication and access-control coverage. Technical report for engineering + 2-page executive summary for investors and enterprise clients.
6 Hours of Founder-led Security Consulting 6 consulting hours included with the Essentials Plan, usable within 6 months from pentest kickoff. Use during the engagement (remediation pairing, scope clarification) or anytime in the 6-month window (architecture review, threat modeling, compliance Q&A).
Use anytime within 6 months from pentest kickoff. Architecture questions, remediation pairing, compliance prep, threat modeling. Both founders available. Extra hours, if you want them, are INR 3,500 each.
1 Full Retest within One Month After you fix the findings in v1.0, we retest every one of them to confirm the fixes are effective. One month from v1.0 is the outer bound; we go sooner once your fixes are in. Completes in 1-3 business days on our side. Report v2.0 is issued at retest close.
One month from the v1.0 report is the outer bound, not a wait: tell us when your fixes are in and we go sooner. No extra charge. Your report closes "remediated", not "open".
Monthly External Attack Surface Scan An automated external attack surface scan of your domain, run monthly, consolidated into unique issues and reviewed by a founder before it reaches you. It covers the internet-facing half only: it does not reach inside your network or behind authentication. Useful for answering a security questionnaire with something current rather than something from the engagement. The window is set in your SOW.
Every month we scan what you expose to the internet and email you the report. A founder reads it before it is sent. Free for every customer who has bought a plan, no extra charge.

Best Suited For: An enterprise customer, an investor, or an acquirer has asked for a pentest report. Someone is evaluating you before they buy, invest or acquire, and the essential pentest has to be done and handed over.

Get an Essentials Plan Quote Understand scoping
Most Popular

Compliance Plan

When a certificate is on the line

1,79,999 + taxes
1 Scope + 1 Extra Scope Included Internal network counts as a scope too: one scope covers a single Active Directory domain, up to 256 live hosts and up to 3 segmentation boundaries. Larger estates or multi-forest environments are quoted as a custom proposal. 2 scopes total = 2 targets tested (1 base + 1 extra included in the Compliance Plan price). E.g., web app + API, or Android app + iOS app. Each platform counts as a separate scope. Add more scopes for INR 74,999 each, and 6 business days each. On a tight deadline, ask us. Tell us the date and we will confirm the schedule when we scope the work. Scheduling changes the timeline, never the price.
Test your web app + API together, or any two targets. Most startups have at least two attack surfaces.
+1 Scope at INR 74,999 The 2 included scopes are 12 business days. A scope is 6 business days, 5 days of testing and 1 day writing the report. Adding scopes changes the schedule, never the per-scope price, and we confirm the schedule when we scope the work.
No cap on scopes. Each additional scope is priced below the per-scope rate of the two included, and gets its own findings section with the same control mapping.
Report in 12 Business Days A business day is Monday to Friday; the weekend is our quality buffer and is not counted against your timeline, and Indian public holidays fall outside the count. Of each scope's 6 days, 5 are testing and 1 is writing the report, so the report is produced inside the window rather than after it. The scope row above shows how the total grows when you add scopes.
Two scopes at 6 business days each, tested in sequence, with one consolidated report at the end.
OWASP Top 10 + PTES, plus WSTG v4.2 Test Cases, Auditor-Ready Report OWASP Top 10 + PTES is the baseline on both plans, and the Compliance Plan adds systematic coverage from the OWASP Web Security Testing Guide v4.2, the current release. The difference is category coverage versus test-case coverage: the Top 10 names ten categories of weakness, while WSTG sets out the individual tests that establish whether each one is present. In practice that means testing is driven by WSTG test cases, and a finding cites the test case it came from where one maps, so an auditor can see what was actually executed rather than which categories were considered. Findings that come from business-logic or configuration work carry their CWE and OWASP category instead, because no single WSTG case produced them. The Compliance Plan also carries Real-world Attack Simulation (listed at the bottom of this card), and reports include full SOC 2 / ISO 27001 mapping per finding.
Systematic WSTG test cases on top of the OWASP Top 10 + PTES baseline. Manual exploitation, business logic, auth coverage. Control-mapped technical + executive report your auditor can use as evidence.
12 Hours of Founder-led Security Consulting 12 consulting hours included with the Compliance Plan, usable within 12 months from pentest kickoff. 2Γ— the Essentials Plan allocation. Use during the pentest, the retest window, or anytime in the 12-month window.
Use anytime within 12 months from pentest kickoff. Architecture review, compliance prep, threat modeling, remediation pairing, incident readiness. Both founders available. Extra hours, if you want them, are INR 3,500 each.
1 Full Retest within One Month After you fix the findings in v1.0, we retest every one of them to confirm the fixes are effective. One month from v1.0 is the outer bound; we go sooner once your fixes are in. Completes in 1-3 business days on our side. Report v2.0 is issued at retest close.
One month from the v1.0 report is the outer bound, not a wait: tell us when your fixes are in and we go sooner. No extra charge. Your report closes "remediated", not "open".
Monthly External Attack Surface Scan An automated external attack surface scan of your domain, run monthly, consolidated into unique issues and reviewed by a founder before it reaches you. It covers the internet-facing half only: it does not reach inside your network or behind authentication. Useful for answering a security questionnaire with something current rather than something from the engagement, or an annual platform submission. The window is set in your SOW.
Every month we scan what you expose to the internet and email you the report. A founder reads it before it is sent. Free for every customer who has bought a plan, no extra charge.
SOC 2 + ISO 27001 Compliance Mapping Compliance mapping ties each finding to SOC 2 Trust Services Criteria and ISO 27001 Annex A controls. Structured for SOC 2 Type 1, Type 2, and ISO 27001 internal + external audits.
Compliance Plan only. Every finding mapped to SOC 2 Trust Services Criteria + ISO 27001 Annex A controls. Your auditor can use the report as direct evidence.
Letter of Attestation for Compliance Auditors Letter of Attestation is a standard deliverable on every Compliance Plan engagement. Signed by Rathnakara GN (OSCP) as Lead Penetration Tester. References the methodology used, the engagement window, and the ISO 27001:2022 Annex A controls that penetration testing supports as audit evidence (A.8.8 management of technical vulnerabilities + A.8.29 security testing in development and acceptance). Structured as first-piece-of-evidence for ISO 27001 audits and customer security questionnaires. Does not contain technical findings or vulnerability detail. Not a certification or accreditation of overall security posture.
Compliance Plan only. One-page PDF signed by our Lead Penetration Tester (OSCP). References ISO 27001:2022 Annex A.8.8 + A.8.29 and the engagement window. Send it to auditors, enterprise customers, and procurement without re-cutting the report.
Real-world Attack Simulation Beyond OWASP Top 10 baseline. Includes chained exploits (one finding amplifying another), privilege escalation, lateral movement, and business logic flaws specific to your application (payment race conditions, IDOR in financial flows, tenant-isolation gaps). The OWASP baseline is pattern-based and can be tested against a defined checklist. Business logic cannot: a race condition in your billing flow is only a finding once we understand what the flow is supposed to do, who is allowed to do it, and where your tenant boundaries sit. That understanding is work that happens before the testing does, which is why this sits on the longer plan rather than the baseline.
Compliance Plan only. Beyond OWASP/PTES baseline: chained exploits, privilege escalation, lateral movement, and business logic abuse specific to your application.

Best Suited For: You are getting certified for the first time, or renewing a certificate you already hold. The work is matched to what that certificate requires: control mapping per finding, audit-grade evidence and a Letter of Attestation.

Get a Compliance Plan Quote Understand scoping

Plan terms effective 13 October 2026. The INR price is the one that binds; USD and EUR are indicative. Tax and currency conversion are covered in the FAQ below.

One scope is one thing we test, not one company. A web app, the API behind it and an Android build are three. Each needs a different kind of testing, which is why each is counted separately.

What brings you here?

Optional. It decides which plan fits, not what you pay for testing.

Evaluating: a customer, investor or acquirer asked for a report. Certificate: certifying for the first time, or renewing. Platform programme: Amazon, Shopify or Microsoft is gating you.

Tick what you want tested

One tick per target. Two of the same kind, say two web apps, is two scopes: tick it once and tell us below.

Nothing ticked yet. Most SaaS startups land on two: the web app and the API behind it.

Two ticks is not always two scopes. If both fit inside one scope's work, we quote one.

An estimate. The quote comes after we look. The binding number is issued via a formal quote once the NDA is signed and we have seen the product and verified access, and it can go down or up based on the scope and the effort. You approve it before any SOW, and nothing moves after that.

This travels with your enquiry.

Buying for an Amazon, Shopify or Microsoft requirement

These are not separate products and they have no separate price list. You buy the plans above, scoped to what the programme asks for.

Tell us the programme and the date it has to be done by. That is what decides the scope count, and the scope count is what decides the price.

SOC 2, ISO 27001 and DPDP readiness

Scoped per engagement, with no price list. Each one has its own page setting out what the work covers.

These are scoped per engagement and carry no price list. CERT-In readiness for Indian operations is handled inside the DPDP work. Compliance work pairs naturally with pentest evidence: findings from a Compliance Plan engagement map straight onto the controls.

Questions buyers ask before signing

What is the difference between the Essentials and Compliance plans?

The Essentials Plan covers 1 scope in 6 business days with a technical + executive report, 6 hours of founder-led consulting, and 1 free retest. The Compliance Plan covers 2 scopes in 12 business days and adds systematic OWASP WSTG v4.2 test-case coverage, SOC 2 + ISO 27001 compliance mapping, real-world attack simulation beyond OWASP Top 10, and 12 hours of consulting. Both plans include 1 free retest within one month. Choose the Compliance Plan if you have a compliance deadline or an enterprise deal in the pipeline.

How long does the full engagement take, including retests?

Engagement duration (testing + v1.0 report) depends on plan and scope count: 6 business days on the Essentials Plan (1 scope), 12 business days on the Compliance Plan (2 scopes). A scope is 6 business days, 5 days of testing and 1 day writing the report, so the report is produced inside the window rather than after it. For larger estates we confirm the schedule when we scope the work with you. Business days are Monday to Friday; the weekend is our quality buffer and is not counted against the timeline. After v1.0 ships, the retest is scheduled when your team has finished the fixes. Earliest start: as soon as you are ready. Latest start: one month after v1.0 (this is the upper bound on when retest can begin, not a mandatory wait). Retest itself takes 1 to 3 business days, then v2.0 closes the engagement. Faster remediation on your side closes the engagement faster.

Can I add more scopes after the engagement starts?

Yes, you can add scopes during scoping or after the engagement starts. Neither plan caps the number of scopes. On the Essentials Plan each additional scope is INR 44,999; on the Compliance Plan each additional scope is INR 74,999. A scope is 6 business days, 5 days of testing and 1 day writing the report. For more than two scopes we confirm the schedule when we scope the work. Adding scopes during the engagement is possible but extends the timeline and requires a scope confirmation note in writing before testing begins on the new scope.

What counts as one scope?

One scope is one application surface tested as a complete unit. Examples: a web application is 1 scope, a REST API is 1 scope, an Android app is 1 scope, an iOS app is 1 scope. Web app + API = 2 scopes (separate surfaces, different attack vectors). iOS + Android = 2 scopes (separate platforms, separate code, separate runtime). A microservices backend with 3 distinct services may count as 1 scope or 3 scopes depending on whether they share authentication and architecture. We confirm scope count during scoping before final pricing. If you are unsure, send us your architecture and we will tell you what we would count as a single scope.

What do I pay on top of the price, and how do the USD and EUR figures work?

Indian buyers are charged GST on top of the INR price. Export of services is a zero-rated supply under Indian GST, and we supply under a Letter of Undertaking, so no Indian GST is added outside India. Any tax due in your own country remains yours to account for. The INR price is the one that binds. USD and EUR figures on this page are indicative, converted at roughly INR 95 to the dollar and INR 110 to the euro as at August 2026, and international engagements are invoiced at the rate on the date of your quote.

What is real-world attack simulation, and why is it on the Compliance Plan?

Real-world attack simulation tests beyond the OWASP Top 10 baseline by simulating how a determined attacker would actually compromise your application. This includes chained exploits (using one finding to amplify another), privilege escalation (moving from a regular user to admin), and lateral movement (accessing systems outside the initial entry point). We also test business logic flaws specific to your application such as payment race conditions, IDOR in financial flows, and authorization gaps in tenant-isolated data. The Compliance Plan includes this because a certificate puts an auditor on the other side of the report, and an audit expects evidence the application withstood a focused attacker rather than only that the OWASP categories were covered. The Essentials Plan covers OWASP Top 10:2025 + PTES, which is what an enterprise customer, an investor or an acquirer evaluating you is asking to see.

What does the SOC 2 + ISO 27001 compliance mapping include?

Each finding in the Compliance Plan report is mapped to specific control requirements in two frameworks. SOC 2 mapping covers the Trust Services Criteria 2017, typically CC6.1 (logical access security), CC6.3 (role-based access), CC6.6 (protection against external threats), CC7.2 (monitoring), and CC8.1 (change management) for a typical web or API engagement. Separately from the per-finding mapping, the engagement itself is evidence for CC4.1, which calls for ongoing and/or separate evaluations: an external test by a party with no role in building or running the systems is the separate half of that criterion. ISO 27001 mapping covers Annex A controls from the 2022 revision, typically A.5.15 and A.8.3 (access control), A.8.20 to A.8.23 (network and communications security), A.8.25 to A.8.29 (secure development and testing), and A.8.15 (logging). The compliance evidence package is delivered as a separate section of the report and can be handed to your auditor as direct evidence of penetration testing, findings, and remediation. Useful for SOC 2 Type 1, SOC 2 Type 2, and ISO 27001 internal or external audits.

How many consulting hours are included with each pentest?

Essentials Plan: 6 hours of founder-led security consulting. Compliance Plan: 12 hours of founder-led security consulting. Use these hours during the engagement (scope clarification, remediation pairing) or anytime in the 6-month or 12-month consulting window (architecture review, compliance prep, threat modeling, incident readiness). Both founders are available. Hours do not roll over but typically get fully used.

How much does penetration testing cost in India?

Cybersecify offers penetration testing starting at INR 74,999 for a single scope (AI, web app, API, Android, iOS, desktop, cloud, IoT, internal network, or external network) with delivery in 6 business days. The Essentials Plan includes 6 consulting hours and 1 free retest. The Compliance Plan at INR 1,79,999 includes 2 scopes, 12 business days, SOC 2 + ISO 27001 compliance evidence, real-world attack simulation, 12 consulting hours, and 1 free retest. All prices exclude taxes.

Which pentest vendors publish their pricing publicly?

Cybersecify publishes its prices in full rather than quoting only after a call. The Essentials Plan is INR 74,999 for one scope in 6 business days; the Compliance Plan is INR 1,79,999 for two scopes in 12 business days and adds SOC 2 and ISO 27001 evidence mapping. Both include one free retest. Prices exclude taxes, the scope picker on this page gives you a figure before you contact us, and a full sample report is public.

Can I see a sample report before buying?

Yes. We publish a full redacted sample showing the exact structure, finding format, compliance mapping, and methodology you receive. You can view it online or download it as a PDF. View sample report →

Why do you ask for 50% upfront?

Nothing is invoiced until the scope is agreed in writing, and the binding number comes last, not first. Before a proforma invoice exists you have had a response to your inquiry, a non-binding estimate, a mutual NDA signed by both parties, a walkthrough of your product, with test credentials and access verification to confirm what is actually there, a formal quote issued against that confirmed scope and approved by you, and a SOW signed by an authorised signatory on both sides setting out the exact scopes you picked, the timeline and the deliverables. The estimate can move in either direction once we have looked: two surfaces may fit inside one scope, or something may need a scope of its own. Once the SOW is signed, nothing moves. You are approving a document you have read, not a description on a web page. The advance confirms the testing slot, which is capped at six pentests a month because both founders work every engagement. The remaining 50% falls due after the v1.0 report is delivered, so the findings are in your hands before we are paid in full. Both sides are exposed for half, and neither is asked to extend trust the other has not already matched.

Do you carry professional indemnity insurance?

No, and that is a pricing decision rather than an oversight. Carrying it would raise the price of every engagement, including the many where nobody asks. What limits your exposure is written into the documents you sign: a mutual liability cap at the fees you have paid, with refund as the maximum remedy; written authorisation to test, scoped in the SOW, which is what makes the engagement lawful; a named out of scope list, so nothing is tested that you did not agree to; encrypted handling of evidence with written confirmation when it is deleted; a rework or refund commitment if delivery misses the SOW; and a clause protecting the integrity of findings, so nobody can lean on us to soften one. If your procurement mandates professional indemnity cover, tell us at scoping and we will quote it as a custom engagement rather than pretend the standard one includes it. Full terms are in the RFP template.

Still have questions?

Book a 30-min call with Ashok. We'll talk through your scope, your timeline, and which plan actually fits. No sales pressure.