PFRDA · Circular

Guidelines on Classification of Cybersecurity Incidents

PFRDA/2025/05/ICS/01

In short
PFRDA/2025/05/ICS/01, issued on 4 September 2025, adds incident classification to PFRDA’s 2024 cyber security guidelines, which had none. Intermediaries and regulated entities are advised to prioritise incidents by business impact and recovery effort rather than first come, first served, and may classify them as Critical, High, Medium or Low. One rule is mandatory: an incident that disrupts normal operations and affects service delivery must be classified High or Critical.

This page is the record of the instrument itself — reference, dates, scope and source. For what it means in practice, read Every Indian cyber instrument, and who each one binds.

The record

ReferencePFRDA/2025/05/ICS/01
Issued byPFRDA (PFRDA)
Instrument typeCircular
Date of issue4 September 2025
StatusIn force
BindsAll PFRDA intermediaries and regulated entities, alongside the 2024 Guidelines. Four categories — Critical, High, Medium and Low — and one firm rule: an incident that disrupts normal operations or service delivery must be classified High or Critical.
Dates it setsIn effect on issue. The instrument sets no further dates.
PFRDA Incident Classification Guidelines, 2025 as the register holds it, read from the issuing regulator's own notification.

What it says

  • Supplements section 4.1.5 of the 2024 Guidelines, which set out incident response but did not classify incidents.
  • Advises prioritising incidents by potential business impact and estimated recovery effort, not by order of arrival or ease of recovery.
  • Sets four categories with examples: ransomware and exfiltration of sensitive data are Critical, unauthorised access to servers is High, and targeted scans are Medium.
  • Requires an incident that disrupts, stops or varies normal operations and affects service delivery to be classified High or Critical.

Read the instrument

The link below goes to the issuing regulator’s own copy. Where a regulator serves its text through a PDF viewer or a query-string URL, it points at the document rather than at a landing page that may not render it.

Not a reading list. Each of these alters the obligation on this page — the amendment that moved a date, the sibling that binds the entity class this one excludes, or the separate track it is routinely merged with.

This record is one entry in the Indian cyber regulation register, which publishes the same fields for every instrument as an open dataset. Indicative, and not legal advice: whether an instrument reaches your organisation turns on your licences and registrations, and is a determination for your legal team.

Every instrument cited here was verified against the issuing regulator's own notification on .

Knowing the instrument is not knowing where you stand.

Every instrument on this page asks an organisation to know its own exposure. Your organisation already has a security rating, calculated from signals anyone outside it can see — including whoever supervises you. Request the complimentary Cyber Risk Rating Report and read what those signals say.

Get your free rating →Opens Bitsight’s request form; Bitsight handles what you submit there.Every Indian cyber instrument, and who each one binds