Qualify for the tender.
Survive the audit.
Pentesting and security advisory for Indian GovTech, PSU and citizen-services platforms. CERT-In empanelled audit support (sub-contract delivery), MeitY / STQC certification alignment, NCIIPC for notified CII, GIGW 3.0 for government websites, GeM and CPPP tender language, the DPDP Act 2023 §17 carve-out reality, and the six-hour incident-reporting playbook that actually meets the timeline.
AxVeil delivers via empanelled partners for regulator-facing GovTech work
AxVeil LLP is not currently CERT-In empanelled. For Government of India, state-government, PSU and CII engagements where the buyer or regulator legally requires a CERT-In empanelled auditor on the signed audit report, AxVeil delivers the operator-led technical work as a sub-contractor to an empanelled partner firm. The empanelled firm holds the buyer contract and signs the regulator-facing submission. Buyers retain a direct contract with the empanelled firm; AxVeil provides the depth behind it.
For pre-tender readiness, GIGW conformance, advisory work, internal security programme build-out and DPDP-readiness work where empanelment is not a legal qualifier, AxVeil contracts directly. See the full empanelment disclosure on the BFSI page →
Pain points GovTech founders bring to scoping
Tender disqualification on the security clause
GeM / CPPP / state-IT-department RFPs increasingly reference CERT-In empanelled audit, STQC certification, NCIIPC controls or GIGW 3.0 as mandatory qualifiers. Missing any one disqualifies the bid before commercial evaluation.
Six-hour incident-reporting window
CERT-In's April 2022 directions impose a six-hour notification window for a long list of incident classes. Most GovTech operators do not yet have the 24x7 monitoring, classification matrix and pre-approved templates to meet it.
Citizen-data scale at PSU pricing
Crore-scale citizen-record platforms run on procurement budgets that assume mid-market SaaS volumes. The threat model is wrong for the price point; the engagement has to be sized for the right model.
Cross-department API integration sprawl
DigiLocker, e-Sign, e-Pramaan, Aadhaar authentication, GSTN, NPCI rails, UIDAI gateways, e-Hospital, e-District integrations across central, state and municipal boundaries. BOLA / BFLA across departmental trust boundaries is the dominant API-layer risk.
Legacy J2EE / WebLogic / Oracle stack
Many central-government and PSU applications still run on a J2EE / WebLogic / Oracle DB stack from the 2010s, deployed inside government data centres (NDC / SDC) with their own patch-cycle and change-control rules. Modern pentest methodology has to adapt to that constraint, not the reverse.
Whistleblower and RTI exposure of poor security posture
Findings that leak via RTI, parliamentary question or activist whistleblower become front-page news. Engagement reports are designed to be defensible in that environment — accurate, proportionate, remediated.
Compliance frameworks the engagement maps to
CERT-In — Information Security Auditor empanelment + April 2022 Directions
link ↗CERT-In Information Security Auditor empanelment is the procurement-floor credential for almost every GoI / state / PSU digital security audit. The April 2022 directions (No. 20(3)/2022-CERT-In) impose a six-hour incident-reporting window for a defined list of incident classes, KYC retention obligations on intermediaries, and log-retention requirements for service providers operating in India.
MeitY — Ministry of Electronics and Information Technology
link ↗Policy and procurement framework for central-government digital services. National Cyber Security Policy 2013 (with the 2024 draft consultation under way), e-Governance Standards under the MeitY mission, DigiLocker / e-Sign / e-Pramaan integrator approvals, the National Cloud (MeghRaj) provider empanelment and the public-sector cloud-empanelment refresh.
STQC — Standardisation Testing and Quality Certification
link ↗MeitY-attached body operating the formal product-level evaluations — Common Criteria, ITSAR for telecom equipment under the Trusted Telecom Product framework, e-Pramaan integrator certifications, GIGW (Guidelines for Indian Government Websites) v3.0 conformance assessment.
NCIIPC — National Critical Information Infrastructure Protection Centre
link ↗Nodal agency under NTRO for Critical Information Infrastructure protection across Power, BFS, Telecom, Transport, Government and Strategic & Public Enterprises. Issues sector-specific Guidelines for Protection of Critical Information Infrastructure; coordinates Protected System notifications under §70 of the IT Act 2000.
DPDP Act 2023 + DPDP Rules 2025
link ↗Digital Personal Data Protection Act 2023. §17 specified-instrumentality exemptions for sovereign functions, but most citizen-services platforms operate as full Data Fiduciaries with consent, purpose-limitation, retention and breach-notification obligations to the Data Protection Board. Penalties up to INR 250 crore per breach.
GIGW 3.0 + GeM / CPPP tender language
link ↗Guidelines for Indian Government Websites v3.0 cover accessibility (WCAG 2.1 AA), information architecture, security and privacy. GeM (Government e-Marketplace) onboarding and CPPP (Central Public Procurement Portal) tenders progressively reference CERT-In audit, STQC certification and GIGW conformance as qualifying criteria.
Sample attack scenarios exercised
Three scenarios commonly run in a GovTech engagement. Each maps to public-record incident archetypes against Indian government and PSU systems.
Case study
State-government citizen-services portal, multi-department integration footprint. Eight-week engagement delivered as sub-contractor to a CERT-In empanelled partner. Scope: citizen-facing portal, departmental admin consoles, four integration APIs (e-Sign, DigiLocker, payment gateway, state-treasury), and the six-hour incident-reporting readiness assessment.
Outcome: 11 Critical and 23 High findings closed before regulator submission, including three cross-district BOLA paths in the application API. Six-hour reporting playbook implemented with named on-call owners and a quarterly tabletop. CERT-In audit certificate issued by the partner firm on retest pass. Tender qualification preserved for the subsequent procurement cycle.
Full redacted report and reference call available under mutual NDA. Request via the scoping form →
Related work
Frequently asked questions
Does my GovTech product need a CERT-In audit before government procurement?+
Almost always, yes. The CERT-In April 2022 directions plus the subsequent MeitY procurement guidance make a CERT-In empanelled audit a baseline qualification for almost every Government of India and PSU tender for a digital product or service that handles citizen data or government information. GeM (Government e-Marketplace) onboarding for ICT product categories, CPPP (Central Public Procurement Portal) tender responses for software services, MeitY-funded programmes and most state-government IT-department RFPs all reference CERT-In empanelment as either a mandatory qualifier or a strong scoring criterion. AxVeil itself is not currently CERT-In empanelled (see the BFSI disclosure), so for GovTech engagements we deliver the technical work as a sub-contractor to an empanelled partner who signs the regulator-facing report — the buyer signs paperwork directly with the empanelled firm.
What is the six-hour CERT-In incident-reporting timeline and how do I meet it?+
CERT-In's April 2022 directions (No. 20(3)/2022-CERT-In) require any service provider, intermediary, data centre, body corporate and government organisation to report a defined list of cyber incidents to CERT-In within six hours of noticing them. The reportable list covers compromise of critical systems, unauthorised access to ICT systems, identity theft, website defacements, malicious-code attacks, attacks on servers / endpoints / IoT / SCADA, DDoS, attacks on email infrastructure, and unauthorised access to social-media accounts. Meeting the six-hour window requires: a 24x7 monitoring or callout function, a pre-approved incident-classification matrix, a templated CERT-In notification form ready to populate, named on-call owners with delegated authority, and tabletop-exercised escalation chains. The engagement deliverable includes the playbook, the templates and a tabletop exercise that validates the timeline.
How does STQC and MeitY product certification fit alongside the audit?+
STQC (Standardisation Testing and Quality Certification, Ministry of Electronics and Information Technology) operates the formal product-level certifications: Common Criteria evaluations, ITSAR (Indian Telecom Security Assurance Requirements) for telecom equipment under the Trusted Telecom Product framework, the e-Pramaan / DigiLocker integrator certifications, and the GIGW (Guidelines for Indian Government Websites) 3.0 compliance assessment for government websites and applications. STQC is a separate body of work from the CERT-In empanelled audit — STQC certifies the product against a defined evaluation profile; the CERT-In audit certifies the security posture of the deployed system and its operator. Many GovTech RFPs ask for both. The AxVeil engagement covers the technical work for both tracks; STQC certificate issuance is handled by the appropriate STQC-authorised laboratory.
We are a CII / Protected System under NCIIPC. What changes?+
Section 70 of the IT Act 2000 empowers the Government to declare any computer resource that directly or indirectly affects Critical Information Infrastructure as a Protected System. NCIIPC (National Critical Information Infrastructure Protection Centre) operates as the nodal agency under the National Technical Research Organisation (NTRO) for the sectors notified as CII — Power, Banking & Financial Services, Telecom, Transport, Government and Strategic & Public Enterprises. Notification as a Protected System adds penalties under §70 (up to ten years imprisonment for unauthorised access), specific NCIIPC reporting obligations, mandatory adoption of NCIIPC's Guidelines for Protection of Critical Information Infrastructure, and an annual CISO-led security audit by a CERT-In empanelled auditor. Engagement scope expands to include NCIIPC controls mapping, supply-chain risk on critical components, and the §70 procedural compliance posture.
DPDP Act 2023 plus DPDP Rules 2025 — what does a GovTech operator owe?+
DPDP Act §17 provides specified exemptions for processing of personal data by the State and its instrumentalities for sovereign functions (national security, prevention of offences, judicial functions, research, statistical analysis) — but the exemption is bounded, requires notified instrument, and does not extend to most citizen-services GovTech use cases. Citizen-services platforms (DigiLocker integrations, PMJAY claim systems, scholarship portals, GST and tax-filing, e-District, transport / driving-licence systems, state-level health-and-education portals) operate as Data Fiduciaries under the full DPDP regime: lawful processing, consent capture (with §6 grounds for legitimate State use limited), purpose limitation, retention, breach notification to the Data Protection Board, children-data §9 obligations, and Significant Data Fiduciary obligations where notified by volume / sensitivity. The DPDP Rules 2025 detail the operational mechanics. The engagement includes a §17-applicability mapping and a Data Fiduciary posture review against the operating Act and Rules.
Scope a GovTech engagement
Send the buyer (central / state / PSU / municipal), the tender or procurement reference, the qualifier(s) the RFP demands (CERT-In, STQC, NCIIPC, GIGW), and the next submission deadline. We respond with a fixed-fee proposal and name the empanelled partner who will sign the regulator-facing report.
Request a scoping call →