Govt. orders security audit of key transport portals after reports of data being...
Source: The Hindu, 25 October 2026
Summary
- The Ministry of Road Transport and Highways (MoRTH) has asked CERT-In to run a forensic security audit of four portals that hold vehicle-owner data: VAHAN, SARATHI, e-Challan and PUCC.
- The trigger was reports that vehicle information is being sold through apps, websites and a Telegram channel for as little as ₹5.
- MoRTH has written to major app-store operators, including Google, asking them to remove such apps. It has also asked MeitY to review the data-sharing policy.
Key facts for Prelims
- CERT-In is the national agency for cyber incident response under Section 70B of the IT Act, 2000. It works under MeitY and was set up in 2004.
- NCIIPC (Section 70A) is a separate body that protects Critical Information Infrastructure. CERT-In handles incident response.
- VAHAN is for vehicle registration, SARATHI is for driving licences, e-Challan is for traffic violations and fines, and PUCC is for pollution control certificates.
- eDAR is the Electronic Detailed Accident Report. FASTag is the electronic toll collection tag.
- The National Transport Repository (NTR) is the MoRTH central database that consolidates VAHAN, SARATHI, e-Challan, eDAR and FASTag data.
- The DPDP Act, 2023 has these roles: Data Principal (the individual), Data Fiduciary (decides purpose and means of processing), Data Processor, and the Data Protection Board of India (adjudicator).
- Government bodies may access all data fields in accordance with the DPDP Act, 2023. Private entities get only domain-relevant fields and a daily search cap.
- Security firm named in the report: Cyderes. Digital rights body that filed the RTI: Internet Freedom Foundation (IFF).
Data and details
- Price of the data on sale: as little as ₹5.
- A Telegram-based channel returned the following when given a vehicle registration number (per the Cyderes investigation):
- Personal details: owner's full name, father's name, present and permanent addresses, PIN code and mobile number.
- Documents and records: driving-licence details, challan history, FASTag information, a downloadable registration certificate, and a PDF of the driving licence.
- Other popular apps identified:
- Vehicle Information App: 10 million downloads.
- VehicleSetu — RC & Challan Info: 1 million downloads.
- RTI data obtained by IFF:
- 25,314 credentials issued to private entities to access VAHAN, SARATHI, e-Challan and PUCC data.
- 1.708 crore queries run over 33 months.
- Derived from these two figures: roughly 5.2 lakh queries a month, or about 675 queries per credential on average. These are rough averages, not reported figures.
- Notably absent from the report:
- It does not say how the data reached the apps. The route could be credentialed API access, sub-licensing, or credential misuse.
- It does not say whether the portals themselves were breached. The audit is meant to establish this.
- MoRTH has sought MeitY's intervention to review the data-sharing policy; the article gives no outcome or timeline for this review.
- The article gives no timeline for the audit and no penalty on any entity.
Static–dynamic linkage
The state now holds large citizen databases built for service delivery. These include vehicle registration, licences, challans, pollution certificates and FASTag records. Governance of such data rests on three ideas:
- Purpose limitation: data is shared only for the purpose it was collected for.
- Data minimisation: only the fields needed are shared.
- Security safeguards: the holder of the data (the "data fiduciary") must prevent leaks.
The Digital Personal Data Protection (DPDP) Act, 2023 puts these ideas into law. This case tests whether controlled data access for businesses ("ease of doing business") leaks into a grey market of personal data. It is a real-world test of the state's duty as a data fiduciary.
Syllabus mapping: GS2 – Governance: e-governance, transparency and accountability | GS3 – Internal Security: cyber security | GS3 – S&T: IT applications | GS2 – Polity: right to privacy and data protection law
Background primer
CERT-In (Indian Computer Emergency Response Team)
- What it is:
- The national agency for cyber security functions, under Section 70B of the Information Technology Act, 2000. It sits under the Ministry of Electronics and Information Technology (MeitY).
- Founded:
- Established in 2004 under the IT Act, 2000, which was later amended by the IT (Amendment) Act, 2008. It was created because of the rise in hacking, malware, phishing and data breaches.
- Members:
- It has technical, analytical and administrative divisions staffed by cyber security experts, network engineers and digital forensics professionals.
- Mandate:
- Collection, analysis and dissemination of information on cyber incidents; forecasts and alerts; emergency measures; coordination of incident response; and guidelines, advisories and vulnerability notes.
- Why it matters:
- A single national technical agency for incident response, so that cyber incidents are handled in a coordinated way across government and industry.
VAHAN, SARATHI and the National Transport Repository (NTR)
- What it is:
- VAHAN covers vehicle registration, SARATHI covers driving licences, eChallan is the traffic enforcement solution, and PUCC is the Pollution Under Control compliance system. They are part of the eTransport Mission Mode Project. This is an e-governance programme led by MoRTH. It is implemented across 35 States/UTs.
- Why it matters:
- One national database that supports enforcement, services and ease of doing business.
Digital Personal Data Protection (DPDP) Act, 2023
- What it is:
- Parliament enacted it on 11 August 2023. It is the framework for protecting digital personal data in India. It follows the SARAL approach (Simple, Accessible, Rational, Actionable).
Additional context
- MoRTH's own data-sharing policy (from the Parivahan policy document):
- Private entities get data subject to consent of the Data Principal through a consent mechanism.
- Private entities can access NTR datasets only with MoRTH approval.
- MoRTH fixes a daily data access limit specific to each type of data recipient.
- A Data Recipient is also treated as a Data Fiduciary and is liable for legal action in case of a breach or unauthorised disclosure.
- MoRTH reserves the right to suspend access if a data breach or security incident is reported.
- Policy tools for citizens and for anonymised data:
- Citizens can see complete information on their own DL or RC through the mParivahan and DigiLocker apps.
- In line with NDSAP 2012, anonymised datasets are to be published on data.gov.in.
- Earlier access regime (an older PIB reply, apparently from FY 2019-20, so not like-for-like with today's numbers):
- Access had been given to 32 government entities and 87 private entities.
- Revenue from VAHAN and SARATHI access was ₹65 crore till then.
- The PIB reply also said that the Ministry offered a "Bulk Data Sharing Policy & Procedure" for certain fields of vehicle registration data.
- CERT-In's 2022 directions:
- Mandatory reporting of specified cyber incidents within six hours of detection.
- Maintenance of ICT system logs for at least 180 days.
Mains dimensions
- State as data fiduciary: Citizen data was collected under a statutory mandate (Motor Vehicles Act). Under Section 8 of the DPDP Act, the fiduciary owes security safeguards and breach notification. The fact that the Ministry is auditing its own portals shows the accountability gap.
- Access architecture versus leakage: The scale of private access (25,314 credentials, 1.708 crore queries in 33 months) shows how wide the "controlled" channel is. Daily caps and field limits have not prevented retail resale at ₹5 a record, although the article does not establish how the data reached the apps. If credentialed access was the route, access design, auditing and monitoring of credential holders matter more than caps alone.
- Privacy and safety harms: Name, address, mobile number and licence details enable stalking, fraud, social engineering and harassment. Challan and FASTag data can reveal movement patterns. Linked records also give a rich identity profile.
- Ease of doing business versus privacy: Selling or sharing data brings revenue and enables services such as insurance, banking and verification. Section 7 "legitimate uses" and Section 17 exemptions need tight purpose limitation. Government access to "all fields" also needs proportionality, in the spirit of the privacy judgments.
- Institutional coordination: MoRTH (data owner), NIC (host and developer), CERT-In (auditor), MeitY (policy), app stores (takedown) and the Data Protection Board (adjudication) all have a stake. This is a case for a coherent cyber and data-governance architecture.
- Way forward:
- Audit the portals and every credential holder's logs.
- Cut field-level access using masking and API-based verification instead of raw data.
- Add two-factor authentication and Aadhaar-authenticated OTP for users.
- Fix liability for downstream resale and enforce it.
- Add automated anomaly detection.
- Use the app-store takedown route, and bring a Data Principal consent dashboard (consent managers) for vehicle owners.
Possible Mains question
**GS3 / GS2, 15 marks:** "Large government databases built for e-governance are now becoming sources of personal-data leakage. Taking the recent audit of vehicle-registration and licensing portals as an example, discuss the gaps in India's data-sharing and data-protection framework and suggest reforms."
Related topics
- Right to Privacy (Puttaswamy judgment) and the DPDP Act, 2023 / DPDP Rules, 2025
- IT Act, 2000: Sections 43A, 70A, 70B, and CERT-In directions
- National Cyber Security Policy, NCIIPC, NCCC, and the Indian Cybercrime Coordination Centre (I4C)
- e-Governance: mission mode projects, NIC, DigiLocker, and the National Data Sharing and Accessibility Policy (NDSAP)
- Motor Vehicles (Amendment) Act, 2019 and FASTag/NETC
Topics: GS2Sci & Tech
All current affairs of 25 October 2026 → · UPSC Current Affairs