Where to Do Audit Certificate for Software, Website, Application & API
Need a security audit certificate for your software, website, mobile app or API? Learn where to get it, the CERT-In empanelled auditor list, process, documents and validity.
Before a payment app, banking platform, government portal or enterprise software goes live, regulators, banks and partners usually ask one question: "Where is your Security Audit Certificate?" In India, the accepted answer is an audit done by a CERT-In empanelled auditor. This guide explains what the certificate is, who needs it, and where to get it for your software, website, mobile application or API.
What is a Security Audit Certificate?
A Security Audit Certificate (often called a VAPT certificate or "Safe-to-Host" certificate) confirms that your system was tested by a qualified auditor for vulnerabilities such as those in the OWASP Top 10, and that the issues found were fixed and re-verified. It is issued after the final round of testing shows no open critical or high-risk findings.
Who issues it? CERT-In empanelled auditors
CERT-In (Indian Computer Emergency Response Team, under MeitY) maintains an official list of empanelled information security auditing organisations. Banks, NPCI, UIDAI, payment aggregators, government departments and most enterprise clients accept certificates only from these empanelled auditors.
👉 Official list of CERT-In empanelled auditors: https://www.cert-in.org.in/PDF/Empanel_org.pdf
CERT-In website: https://www.cert-in.org.in
The list is updated from time to time, so always check the latest PDF before signing with an auditor.
Audit types: software, website, application and API
- Website / Web application audit – Tests login, sessions, forms, payment pages and admin panels for issues like SQL injection, XSS, broken access control and misconfiguration. Required for "Safe-to-Host" on government servers (NIC/SDC) and by most banks.
- Mobile application audit (Android / iOS) – Checks APK/IPA for insecure storage, hard-coded keys, weak SSL pinning, root/jailbreak bypass and insecure API calls.
- API security audit – Tests REST/SOAP APIs for authentication flaws, broken object-level authorization, rate limiting, data exposure and injection. Essential for fintech APIs (UPI, BBPS, AEPS, payouts).
- Software / Source code review – Static and manual code review to find security bugs before release.
- Network & server (infrastructure) audit – VAPT of servers, firewalls, cloud setup and databases.
- Compliance audits – Such as RBI cyber security / IT audits, PA-PG guideline audits and ISO 27001 readiness, depending on your business.
Who needs a security audit certificate?
- Fintech companies, payment aggregators and API providers connecting with banks or NPCI
- AEPS / Aadhaar-based service providers (AUA/KUA, ASA)
- Websites and applications hosted on government servers
- BBPS, recharge and bill payment platforms
- SaaS, ERP and enterprise software vendors whose clients ask for it
- Any business handling customer personal or financial data
Step-by-step process
- Pick an auditor from the CERT-In empanelled list (link above). Compare 2–3 quotes.
- Define the scope – URLs, app builds, API endpoints and documentation, number of user roles, servers/IPs.
- Share access – Staging/UAT environment, test credentials for each role, API docs (Postman/Swagger), APK/IPA.
- First round of testing – The auditor shares a vulnerability report with severity ratings.
- Fix the issues – Your development team patches all findings.
- Re-test (revalidation) – The auditor confirms fixes.
- Certificate issued – Once no critical/high issues remain, you receive the signed audit certificate and final report.
Documents usually required
- Application URL(s), API endpoint list and API documentation
- Test user IDs for every role (admin, retailer, distributor, customer, etc.)
- Mobile app build (APK/IPA) and version number
- Server/IP details for infrastructure testing
- Company details and authorisation letter for testing
Time, cost and validity
- Time: Usually 1–4 weeks depending on scope and how fast issues are fixed.
- Cost: Depends on the number of pages, roles, APIs and apps — ask each auditor for a written quote.
- Validity: Most banks and partners ask for a fresh audit every year, and again after any major release or change.
Tips to pass the audit faster
- Use HTTPS everywhere with strong TLS settings
- Add security headers (CSP, HSTS, X-Frame-Options)
- Enforce strong passwords, OTP/2FA and session timeouts
- Validate every input on the server side
- Protect APIs with tokens, IP whitelisting, request signing and rate limits
- Never store keys or passwords in app code or logs
- Keep PHP, frameworks and server packages updated
Conclusion
For software, websites, applications and APIs in India, the security audit certificate should come from a CERT-In empanelled auditor. Check the latest official list here: CERT-In Empanelled Auditors (PDF), choose an auditor, fix the reported issues and get your certificate before going live.
Build your fintech or ERP with Pay2All
Recharge, Bill Payment, AEPS, DMT, PAN and travel APIs — plus billing & ERP software.