What is VAPT?
VAPT stands for vulnerability assessment and penetration testing. The vulnerability assessment finds and lists known weaknesses in your application, servers and dependencies. The penetration test goes further: a tester tries to exploit those weaknesses to show what an attacker could actually reach, and how badly. You need both to know your real risk.
The two get mixed up often, and some reports sold as a "VAPT" are only an automated scan. A scan is useful and cheap, but it can't tell you that a logged-in customer can read another customer's invoices by changing a number in the URL. Finding that takes a person who understands how your app is meant to work.
| Vulnerability assessment | Penetration test | |
|---|---|---|
| Question it answers | What known weaknesses do we have? | What could an attacker actually do with them? |
| How it's done | Mostly automated scanning, checked by hand | Manual testing of your app's logic, guided by scan results |
| Finds | Outdated libraries, misconfigurations, missing headers | Broken access control, auth bypasses, data leaks between users |
| Output | A list of issues with severity | Proven issues, impact, and how to reproduce them |
Who needs a security review?
- Startups selling to larger companies, whose buyers send a security questionnaire or ask for a recent pentest report before signing.
- Apps that handle payments, health or personal data, where a leak means lost trust and legal exposure.
- Teams about to launch or raise, who want to find the problems before users or investors do.
- Products built fast by several developers over time, where nobody has looked at security as a whole.
What we test
Web application and API testing
We test against the OWASP Top 10, the widely used list of the most critical web application risks. In practice that means checking access control between users and roles, login, sessions and password reset, injection such as SQL injection and cross-site scripting, insecure handling of files and uploads, and APIs that return more data than the screen shows. Business logic gets attention too: discount codes that stack, orders that can be edited after payment, limits that can be skipped.
Code review for secrets and vulnerable dependencies
We review the repository for API keys and passwords committed to code, known-vulnerable packages, and risky patterns, using tools such as SonarQube and Trivy alongside a manual read of the sensitive parts: authentication, payments and anything that touches personal data.
Cloud configuration review
Storage buckets open to the internet, over-broad access keys, databases reachable from anywhere and missing backups cause many real breaches. We review the setup on AWS and GCP and list what to lock down.
Container checks
If you ship in Docker, we scan your images for known vulnerabilities in the base image and installed packages, and recommend smaller, patched images.
What you get at the end
- A clear report. Every finding with its severity, where it is, how to reproduce it and what an attacker could do with it.
- A step-by-step fix plan written for your developers, in the order that removes the most risk first.
- Help fixing. If your team is stretched, we can fix the issues ourselves, since we build software as well as test it.
- A retest once fixes are in, and a retest report you can share with customers and investors.
We use standard tools such as Burp Suite for web and API testing. Testing runs on a staging copy where possible, and only within the scope, dates and accounts we agree with you in writing.
Are you CERT-In empanelled?
No. CERT-In, India's national computer emergency response team, maintains a list of empanelled security auditors. Some regulated businesses in India, and many government, banking and financial-sector clients, require an audit from a CERT-In empanelled organisation. If that applies to you, use an empanelled auditor for the certified audit. We are happy to help you get ready before it and to fix the findings after it.
For most startups, the need is different: find and fix real problems, and show a customer that a proper test was done. That is what our reviews are for.
Security work we have done
Our Docker Security Audit project assessed container images for known vulnerabilities and turned the scan results into a clear, prioritised report. The reports are private, so there is no public repository. FakeBuster is an open-source threat intelligence pipeline that follows trending news and checks claims through a three-layer chain of evidence. Both are listed on our work page. Because we also build web apps, APIs and mobile apps, we read your code the way the people who wrote it would.
What does a security review cost?
Penetration testing is scoped and quoted separately, because the work depends on how many apps, APIs, user roles and environments are in scope. You get a fixed written quote before testing starts, and the price does not move unless the scope does. If we are building your product, our "Build & grow" package (from ₹95,000 / $2,900) already includes a basic security check before launch.
For a sense of the market, Indian security firms publish ranges from tens of thousands of rupees to several lakh for a single web application, depending on scope and depth. Compare quotes on what is tested by hand, whether a retest is included, and whether the report explains how to fix each issue.
Application security questions
How long does a web app penetration test take?
Most single web apps and APIs take one to four weeks from kickoff to retest, depending on size, the number of user roles and how quickly fixes go in. The written plan states the testing days before you commit.
Will testing break our live app?
We test on a staging copy wherever possible. If production must be tested, we agree the time window, the accounts and anything that is off limits in writing, and avoid destructive tests.
Do you test mobile apps too?
Yes, the APIs behind them in particular, since that is where most mobile app data leaks happen. We also check how the app stores tokens and data on the device.
Can you fix what you find?
Yes. We build software as well as test it, so we can fix the issues or work with your developers, then retest.
Is a vulnerability scan enough?
A scan is a good first step and catches outdated packages and misconfigurations. It rarely finds access-control and business-logic flaws, which are often the most serious. Those need manual testing.