bytepatch://secure-shell — bash
$ ssh root@bytepatch.tech
↳ establishing encrypted tunnel… [ OK ]
↳ bypassing firewall layers… [ OK ]
↳ decrypting payload 0x8F3A… [ OK ]
↳ mounting secure assets… [ OK ]
[░░░░░░░░░░░░░░░░░░░░] 0%
ACCESS GRANTED
Home Services Work About Research Contact Cyber Range
Services/Cyber Security/Penetration Testing

Penetration Testing

Manual, exploit-driven VAPT services for web applications, mobile apps, APIs, cloud and networks — delivered from Delhi NCR to clients across India and worldwide. We break in the way a real attacker would, then hand your developers the exact fix.

PTES OWASP WSTG NIST SP 800-115 CVSS v3.1 OWASP MASVS
Overview

A scanner reports. We break in.

An automated scan tells you a parameter looks injectable. A penetration test shows you the 40,000 customer records it pulled out, the admin session it hijacked and the S3 bucket it reached from there. That gap — between a theoretical finding and a proven breach — is the entire point of hiring a human.

Roughly 70% of what we report on a typical engagement is invisible to scanners: broken object-level authorisation, business-logic abuse, race conditions in payment flows, tenant isolation failures and privilege escalation chains. Those are the findings that end up in breach post-mortems.

Every engagement is fixed-price, scoped in writing, and ends with a free retest so you can prove the holes are actually closed.

engagement BPT-PT-0184 — recon
$ nmap -sV -Pn --top-ports 1000 app.client.example
443/tcp open https nginx 1.24.0
8080/tcp open http Jenkins 2.401 — unauthenticated /script
$ ffuf -u https://api.client.example/v2/FUZZ -w endpoints.txt
/users/{id}/invoices   [Status: 200, Size: 14822]
$ curl -H "Authorization: Bearer $LOW_PRIV" .../users/1042/invoices
HTTP/2 200 — returned another tenant's invoices
→ BOLA confirmed · CVSS 8.1 High · 41,206 records reachable
$ _

// illustrative output — client identifiers redacted

Scope options

Nine kinds of penetration test.

Most clients start with one and expand. Each can be booked standalone or combined into a full-scope engagement.

Web application

Web app pen test

Full OWASP Top 10 and ASVS Level 2 coverage — injection, broken access control, SSRF, deserialisation, plus the business-logic abuse no scanner has a signature for.

Mobile application

iOS & Android pen test

Static and dynamic analysis against OWASP MASVS: insecure local storage, certificate pinning bypass, hardcoded secrets, root/jailbreak detection and the backend the app talks to.

API

REST & GraphQL pen test

Endpoint enumeration, BOLA and BFLA, mass assignment, rate-limit bypass, JWT flaws and GraphQL introspection abuse — mapped to the OWASP API Security Top 10.

Network

External & internal

Perimeter testing from the internet and assumed-breach testing from inside the LAN: exposed services, weak credentials, SMB and Active Directory attack paths, lateral movement.

Cloud

AWS / Azure / GCP

IAM privilege escalation paths, public storage, over-permissive roles, exposed metadata services, insecure defaults and misconfigured security groups.

Wireless

Wi-Fi & RF

Rogue access points, WPA2/WPA3 handshake attacks, guest-network segmentation failures and captive-portal bypass across your office footprint.

Social engineering

Phishing & vishing

Authorised phishing, smishing and pretext calling campaigns that measure your real human attack surface — then feed the results into targeted staff training.

Red team

Full adversary simulation

Goal-oriented, multi-vector, low-and-slow simulation of a real threat actor. Tests your detection and response, not just your patch level.

AI & LLM

Prompt & agent security

Prompt injection, tool-abuse and data-exfiltration testing for LLM features and autonomous agents — aligned to the OWASP Top 10 for LLM Applications.

Methodology

Seven phases, every time.

Aligned to PTES, the OWASP Web Security Testing Guide and NIST SP 800-115 — so your auditor recognises the process and your engineers can follow the trail.

01

Scoping & rules of engagement

0.5 day

NDA signed, targets agreed, testing windows fixed, escalation contacts named and an authorisation-to-test letter executed. Nothing is touched before this document exists.

02

Reconnaissance

0.5–1 day

Passive and active intelligence: subdomain and asset discovery, technology fingerprinting, exposed credential checks against breach corpora, and public exposure mapping across code repos and cloud storage.

03

Scanning & enumeration

1 day

Port, service and application scanning to inventory the full attack surface, followed by manual enumeration of parameters, endpoints, user roles and trust boundaries that automation walks straight past.

04

Threat modelling

0.5 day

We map the discovered surface against realistic attacker goals for your business — steal the customer database, move money, take over an account — so testing effort lands where a breach would actually hurt.

05

Exploitation

2–5 days

The manual core of the engagement. Creative, chained exploitation to prove real impact: injection, broken access control, authentication bypass, race conditions and business-logic abuse.

06

Post-exploitation

0.5–2 days

Where authorised, we demonstrate privilege escalation, lateral movement and how much data is actually reachable from the first foothold — the difference between “a bug” and “a breach.”

07

Reporting & retest

1.5 days + retest

Executive summary, CVSS v3.1 rated findings with proof of concept, developer-ready remediation, a live read-out call with your engineers, and a free retest to confirm the fixes hold.

Audit trail

A real trial audit, start to finish.

Before a full engagement we run a short, non-intrusive trial audit and hand back an audit trail: every issue logged, scored, tied to a business consequence and given a deadline. Below is that exact deliverable from a live assessment — client identity anonymised as Test Site.

Representative sample only

These items are a sample from a short, non-intrusive trial scan. They show the kind of risk present rather than the full list. A complete audit finds, confirms and prioritises every issue across every system and regulation.

01

Understanding the environment

From publicly available signals alone we mapped this snapshot of the client's digital footprint. No credentials, intrusive scanning or exploitation were used to gather it.

Primary asset
Test Site — single-page web application
Hosting / CDN
Shared hosting + provider CDN
Data collection
Public contact form · third-party web analytics
Mail infrastructure
Provider MX · SPF present · no DMARC / DKIM observed
Exposed subdomains
9 discovered, incl. control panel, CRM, invoicing and autodiscover

This footprint tells us the client collects and stores personal data of website visitors — which brings it squarely within scope of India's DPDP Act 2023 and, for EU visitors, GDPR.

02

Security findings — the audit trail

A partial log of issues identified during the trial, each mapped to its business impact and a recommended remediation window.

Sample penetration test audit trail: findings with severity, CVSS score, business impact and remediation deadline
ID Finding Severity CVSS Business impact Fix by
TA-01Missing HTTP security headersCRITICAL9.1Clickjacking, injection & SSL-strip exposure of visitor data24 hrs
TA-02Email domain can be spoofed (no DMARC/DKIM)CRITICAL9.3Business-email compromise & invoice fraud impersonating your brand24 hrs
TA-03Unprotected contact-form endpointHIGH8.6Spam floods & poisoned lead data; infrastructure abused on your behalf7 days
TA-04No HTTPS enforcement (SSL stripping)HIGH8.2Session interception & data capture on untrusted networks7 days

…and more. This is a partial trial log — additional findings across TLS configuration, consent handling, information disclosure and resource integrity are withheld from this preview and confirmed in the full engagement.

03

Potential penalties & business consequences

Left unaddressed, gaps like these expose a business to statutory penalties alongside direct commercial harm. Figures below are statutory maximums — indicative of exposure, not assessed fines.

Regulatory frameworks, triggering failures and maximum statutory penalty exposure
Framework What can trigger it Maximum exposure
DPDP Act 2023Failure to take reasonable security safeguards to prevent a data breachUp to ₹250 crore
DPDP Act 2023Failure to notify the Data Protection Board & affected users of a breachUp to ₹200 crore
GDPR (EU visitors)Processing personal data without a lawful basis or valid consent€20M or 4% of global turnover
IT Act 2000 §43ANegligence in handling sensitive personal data causing wrongful lossUncapped compensation

Beyond fines: mandatory breach disclosure, loss of client contracts and remediation under deadline — typically far costlier than fixing proactively.

04

Compliance observations

DPDP Act 2023
No visible privacy notice or consent mechanism. Personal data is collected via the contact form and analytics without a published notice, lawful basis or consent capture — a foundational obligation under India's data-protection law now in force.
GDPR / ePrivacy
Trackers load before consent. Analytics and third-party fonts are loaded for EU visitors with no cookie or consent banner — a common trigger for supervisory-authority action where the site is reachable from the EU.
ISO 27001
No evidence of a managed ISMS. Baseline organisational and technical controls appear informal or absent — relevant if the business intends to reassure enterprise clients or pursue certification.

…further observations under the IT Act & SPDI Rules and PCI-DSS relevance are reserved for the full assessment.

Why this matters now

These findings are practical, not hypothetical. Each one points to an attack that takes little effort to carry out, and to a legal obligation that already applies. The good news: most of what a trial audit surfaces is inexpensive to fix and removes a large share of the risk.

Request a free trial audit for your site →
Pricing, in the open

This is exactly what your quotation looks like.

No “contact us for pricing.” Below is a real, unedited BytePatch quotation format for a mid-sized SaaS web application and its API — line items, tester-days, day rate, taxes and terms. Your numbers change with scope; the structure does not.

BytePatch Technologies logo BytePatch Technologies
New Delhi, India · developer@bytepatch.tech
Security engagement quotation
Quotation
BPT/2026/PT-0184
Issued 15 Aug 2026 · valid 30 days
Delivery: 10 working days from kickoff
Client
Sample SaaS Pvt Ltd
Engagement
Web application & API penetration test
Approach
Grey box — credentialed, 3 user roles
In scope
1 web app (~60 screens), 42 API endpoints, 4 external hosts
Standards
PTES · OWASP WSTG · NIST SP 800-115
Testing window
Weekdays 20:00–06:00 IST, staging environment
Sample penetration testing quotation line items and pricing in Indian rupees
# Line item Scope unit Days Rate Amount
01Scoping, threat modelling & rules of engagement1 engagement0.5₹12,000₹6,000
02Web application penetration test — OWASP Top 10 + ASVS L21 app, ~60 screens4.0₹12,000₹48,000
03REST API penetration test — OWASP API Top 1042 endpoints2.0₹12,000₹24,000
04Authentication, session & access-control testing (IDOR / BOLA)3 user roles1.0₹12,000₹12,000
05Business-logic abuse testing6 critical flows1.0₹12,000₹12,000
06External infrastructure & TLS configuration review4 hosts0.5₹12,000₹6,000
07Reporting — exec summary, CVSS v3.1 findings, PoC, remediation1 report1.5₹12,000₹18,000
08Remediation read-out call + developer Q&A90 minutes0.25₹12,000₹3,000
09Retest of remediated findings (within 30 days)1 cycle1.0Included
10Retest letter & security attestation for your clients1 documentIncluded
Subtotal (9.75 tester-days)₹1,29,000
First-engagement discount −10%−₹12,900
Net professional fees₹1,16,100
GST @ 18% (SAC 998343)₹20,898
Total payable₹1,36,998
Rupees one lakh thirty-six thousand nine hundred ninety-eight only
Commercial terms
  • 50% on signature, 50% within 7 days of report delivery.
  • Fixed price. Scope changes are re-quoted in writing before work starts — never billed as a surprise.
  • Mutual NDA signed before any technical detail is exchanged.
  • One free retest of remediated findings within 30 days of report delivery.
  • All evidence and client data destroyed 30 days after sign-off, with written confirmation.
Out of scope & assumptions
  • Denial-of-service and load testing — excluded unless separately commissioned.
  • Physical intrusion and social engineering — quoted separately.
  • Client supplies test credentials for each user role before kickoff.
  • Client holds authority over all in-scope assets and signs the authorisation-to-test letter.
  • Third-party providers (payment gateway, CDN, host) notified by client where their terms require it.

Sample figures for illustration. Your quotation is issued after a free 30-minute scoping call — book one here or build a rough number yourself with the instant estimate tool.

Packages

Penetration testing cost in India.

Starting prices in INR, exclusive of GST, at standard delivery. Final quote is fixed after a free scoping call.

Essential VAPT
₹16,000
starting from · one application, fast
  • Automated + manual vulnerability assessment
  • OWASP Top 10 coverage, single web app
  • CVSS v3.1 rated findings report
  • Remediation recommendations
  • 45-minute read-out call
  • Turnaround: 3–5 working days
Scope this test →
Full Manual Pen TestMost popular
₹35,200
starting from · the one most clients pick
  • Everything in Essential, plus:
  • Full manual grey-box test (web or mobile)
  • API, authentication & access-control testing
  • Business-logic and IDOR/BOLA testing
  • Proof-of-concept evidence per finding
  • Free retest + attestation letter
Scope this test
Full-Scope & Red Team
₹64,000
starting from · everything, adversary-style
  • Everything in Full Manual, plus:
  • Web + mobile + API + cloud + network
  • Threat modelling & architecture review
  • Assumed-breach / lateral movement testing
  • Compliance mapping (DPDP / ISO 27001 / SOC 2)
  • Executive board report + IR readiness review
Scope this test →
Deliverable sample

What one finding looks like.

Every issue in your report is written like this: scored, evidenced, reproducible, and closed with a fix a developer can actually ship.

Finding PT-0184-03

Broken object-level authorisation in the invoice API

High · CVSS 8.1
CWE-639 · OWASP API1:2023
Impact

Any authenticated user can read any other tenant's invoices by incrementing a numeric ID. During testing this exposed 41,206 invoice records across 380 tenants, including GSTINs, billing addresses and order values — a reportable personal-data breach under the DPDP Act.

Reproduction
1. Log in as tenant-a@example.com (role: Viewer)
2. GET /api/v2/users/1042/invoices
3. Replace 1042 with any other user id
HTTP 200 with the other tenant's invoice objects
Remediation

Authorise on the object, not the route. Resolve the tenant from the session server-side and scope every query to it — never trust an identifier supplied by the client.

- const inv = await Invoice.find(req.params.id)
+ const inv = await Invoice.findOne({
+   id: req.params.id,
+   tenantId: req.session.tenantId  // from session
+ })

Then add a regression test asserting a 404 for cross-tenant IDs, and sweep the remaining 11 endpoints that take a resource ID in the path.

What you get

Five deliverables, not one PDF.

Executive summary

Two pages your board, your insurer and your biggest client can all read. Risk posture, business impact and the three things to fix first — no jargon.

Technical findings report

Every issue with a CVSS v3.1 vector, CWE reference, OWASP mapping, reproduction steps and screenshot or request/response proof of concept.

Remediation plan

Prioritised by real risk, not scanner severity. Written for the developer who has to close it, with code-level guidance for your actual stack.

Read-out call

A live session with your engineering team to walk the findings, answer questions and agree the fix order before anyone opens a ticket.

Retest & attestation

We retest the remediated findings free within 30 days and issue a retest letter you can hand to clients, auditors and procurement teams.

Evidence destruction

All collected evidence and client data is destroyed 30 days after sign-off, confirmed to you in writing. Your data does not live on our disks.

Toolkit

Tools we test with.

Industry-standard offensive tooling, plus the custom scripts we write for your specific stack. Tools find the surface; the tester finds the breach.

Burp Suite Pro Nmap Metasploit sqlmap Nuclei ffuf Nessus OWASP ZAP Wireshark MobSF Frida objection BloodHound Impacket ScoutSuite Prowler Semgrep Ghidra John the Ripper Hashcat Custom exploit scripts
Compliance

Findings your auditor accepts.

Every finding is mapped to the frameworks you actually get assessed against, so one test satisfies several obligations at once.

DPDP Act, 2023
Reasonable security safeguards under Section 8(5), plus breach-reporting readiness.
ISO 27001:2022
Annex A 8.8 technical vulnerability management and A 8.29 security testing evidence.
SOC 2
Common Criteria CC7.1 vulnerability detection and CC4.1 monitoring evidence for your auditor.
PCI-DSS v4.0
Requirement 11.4 penetration testing and 11.3 vulnerability scanning for card environments.
RBI & SEBI guidelines
Annual VAPT expectations for regulated financial and capital-market entities in India.
CERT-In directions
Reporting formats and 6-hour incident-notification readiness aligned to CERT-In guidance.
FAQ

Penetration testing, answered.

How much does a penetration test cost in India?

A focused assessment of one web app starts at ₹16,000. A full manual grey-box test typically runs ₹35,000–₹90,000 depending on roles, endpoints and logic flows in scope. Full-scope engagements start around ₹64,000. We quote a fixed price after a free scoping call — no hourly surprises.

VAPT vs penetration test — what's the difference?

VAPT bundles two things. The vulnerability assessment is broad and mostly automated. The penetration test is narrow and manual — a human exploits those weaknesses, chains them and proves business impact. Most compliance regimes want both.

How long does it take?

A single web app is 5–10 working days from kickoff: 3–6 days testing, 1–2 days reporting, then the read-out. Full-scope engagements run 3–6 weeks. The retest is scheduled separately and usually takes a day.

Do you need our source code?

No. Most engagements are grey box — you give us test credentials per role and we work from outside like an attacker with a valid account. White-box access finds more, faster, and we recommend it for high-risk systems, but it's optional.

Will testing take our production site down?

No. DoS and load testing are explicitly out of scope unless commissioned. We throttle automation, agree testing windows in writing, and run anything potentially intrusive only with your written approval. Where staging mirrors production, we prefer to test there.

Is penetration testing legal in India?

Yes — when authorised. Unauthorised access is an offence under Sections 43 and 66 of the IT Act, 2000. Every engagement starts with a signed authorisation-to-test letter and written rules of engagement. We never test an asset you can't demonstrate authority over.

How often should we test?

At minimum annually, and after any major release, architecture change, cloud migration or acquisition. SOC 2 and ISO 27001 programmes generally expect an annual test plus a retest. Fast-shipping product teams often move to quarterly.

Do you help us fix what you find?

Yes. Every finding ships with remediation written for the developer who has to close it. We run a read-out call, stay available during remediation, and retest the fixes free within 30 days.

Keep reading

Related services & guides.

Ready when you are

Find it before they do.

Free 30-minute scoping call, a fixed-price quotation within 24 hours, and an NDA signed before a single detail is shared.

Book a scoping call Get instant estimate