Governance pillars motif representing public-sector assurance
Industry

Government & Public Sector

Overview

Securing the government sector

Government departments and public-sector undertakings must clear CERT-In empanelled security audits before portals and citizen services go live, and stay compliant with the CERT-In Directions 2022 on logging and incident reporting, and NCIIPC obligations apply on top of that for protected systems. Around 20% of our engagements are PSU and government work.

We deliver safe-to-host certification support, e-governance application testing and incident readiness, with engagements for public bodies such as the Gujarat Department of Science & Technology (DST) and the Institute of Seismological Research (ISR), Gujarat.

  • CERT-In empanelled audit & safe-to-host
  • CERT-In Directions 2022 logging & incident reporting
  • NCIIPC protected-system obligations
  • DPDP Act 2023 for citizen data
Talk to a public-sector specialist →

Key challenges we solve

CERT-In empanelled audits & safe-to-host

Protection of citizen data & e-governance

Critical national infrastructure resilience

Incident readiness & response

Sector FAQ

Government security questions

After Operation Sindoor in May 2025, a CERT-In scientist reported a surge in attempts on central government portals, and said attackers were shifting their attention to state systems. The incident categories CERT-In asks organisations to report include website defacement, unauthorised access, data leaks, phishing and malicious code inserted into sites. For a department, the realistic risks are defacement, denial of service, credential phishing against staff and compromised third-party components on public portals.

CERT-In issued its Comprehensive Cyber Security Audit Policy Guidelines in July 2025, which call for cyber security audits at least once a year, and CERT-In maintains a panel of empanelled security auditing organisations to carry them out. The Government's own account of NIC's practice includes an annual comprehensive audit of critical web applications and databases and of ICT infrastructure across central ministries, states and national data centres. For a department the practical point is that audit evidence should be current and tied to specific applications.

The Government has formulated a Cyber Crisis Management Plan for all government bodies to counter cyber attacks and enable coordinated recovery, and 213 sensitisation workshops on it have been held. In operational terms, a department needs a plan that names who decides, who talks to CERT-In and NIC, how services shift to fallback modes, and how recovery is verified. CERT-In also runs regular drills, including tabletop exercises, and these are the quickest way to find where a plan fails.

Citizen-facing portals, the APIs that connect departments, payment and benefit-transfer links, state data centres, and applications built years ago by different vendors on mixed technology. The Government's own list of NIC measures points at the same areas: removing obsolete and legacy systems, endpoint detection and response, continuous vulnerability assessment and zero trust. We typically test the public portal and its back-end APIs together, since a weakness in an internal service is often reachable through the public one.

Ask for proof, not assurances. CERT-In's technical guidelines on software and related bills of materials apply mainly to government, the public sector and essential services, and compliance can cascade to contractors and third-party providers. Government buyers are also expected to include AI bills of materials in AI-related procurements. Practically, contracts should require component lists, patching timelines, audit access and the right to security-test delivered code before acceptance.

CERT-In's 2022 directions name government organisations among those that must report listed incidents within six hours of noticing them, keep ICT logs for 180 days within India, and appoint a point of contact. Listed incidents include website defacement, unauthorised access, data breaches and malicious code injection. Many departments find the logging requirement harder than the reporting, because older applications and shared hosting do not always retain the logs that CERT-In may ask for, so check this early.

Talk to a public-sector security specialist