Skip to content

Lost money to a cyber fraud? Call 1930 now and file at cybercrime.gov.in. The first hour matters.

What to do, step by step →
Cyber Crime Help Desk An initiative from Kramate for Society
Business security 6 min read

Cyber Security for Hospitals, Schools and NBFCs: 3 Playbooks

Cyber security for hospitals, schools and NBFCs in India: the attacks each sector actually faces, the rules that apply to it, and a short playbook for each.

By Editorial team, Research and writing · Published
Colleagues around a meeting table reviewing documents and laptops together

In short

  • Hospitals should assume ransomware will reach the hospital information system and plan for care to continue on paper for 72 hours.
  • Schools lose money through fee payment fraud aimed at parents and lose trust through exposed student data; both are fixable with process, not technology.
  • NBFCs are regulated by RBI's IT governance direction and are targeted as sources of mule accounts; onboarding controls are security controls.
  • All three handle personal data under the DPDP Act 2023 and must report listed incidents to CERT-In within six hours.
  • Start each playbook with the one control that stops the sector's most common loss, then build outward.

Who this is for: Administrators, trustees, principals, CEOs and IT heads of Indian hospitals, clinics, schools, colleges, NBFCs and fintech lenders who need a sector-specific starting point rather than a generic checklist.

A generic cyber security checklist tells a hospital, a school and an NBFC to patch their servers and train their staff. All true, all insufficient. Each sector loses money and trust in a different way, and the first control each needs is different. This guide gives a short playbook for each, starting with cyber security for hospitals, then schools, then NBFCs, and ends with what all three share under Indian law.

Cyber security for hospitals: plan for the day the HIS goes dark

Hospitals are attacked because downtime is intolerable. A clinic that cannot open its billing system for a day loses revenue; a hospital that cannot see lab results or imaging has to slow admissions and move to paper, and attackers price ransom demands on that pressure. The hospital information system, the imaging archive and the lab system are the targets, and in many Indian hospitals they sit on one flat network alongside ward computers, visitor Wi-Fi and devices the vendor installed years ago and never updated.

The second exposure is patient data. Reports, prescriptions, ID copies and insurance forms leak through misconfigured servers, shared WhatsApp groups and exported spreadsheets. Patients then receive calls from "the insurance company" quoting details only the hospital should know. Under the DPDP Act 2023, health data is personal data, and a leak is a breach with notification duties.

Hospital playbook

First moves for a hospital or diagnostic chain

  • Write and rehearse a 72-hour paper fallback: how registration, prescriptions, lab requests and discharge work when the HIS is unavailable. Print the forms now.
  • Back up the HIS, imaging and lab databases to a location the hospital network cannot write to, and restore from it once a quarter to prove it works.
  • Separate the networks: clinical systems, medical devices, administration and guest Wi-Fi should not be able to reach each other freely.
  • Inventory connected medical devices and vendor remote-access links; close the ones nobody can account for.
  • Stop the WhatsApp report habit: patient reports go through the portal or app, never through staff personal phones.
  • Name the person who files the CERT-In report within six hours and the person who drafts the patient notice under the DPDP Act.

The full sequence for the day ransomware lands is in our ransomware playbook, and the regulatory clocks are in the data breach response plan template. Accreditation bodies increasingly ask for evidence of these controls, so the work supports NABH and insurer reviews as well.

Schools and colleges: fee fraud and student data

A school is not a high-value technical target. It is a high-value social target. Parents trust messages that appear to come from the school, and fraudsters know the fee calendar.

Fee payment fraud works like this: a few days before fees are due, parents receive a WhatsApp or SMS from a number with the school's name and logo, with a payment link or a UPI ID. Some pay. The school discovers it when parents ask why receipts have not arrived. No system was hacked; a class group's member list, or a leaked parent directory, was enough.

Student data is the second problem. Admission forms carry photographs, Aadhaar copies, addresses and medical notes. They end up on shared drives, in ERP endpoints without authentication, and in the inboxes of staff who left. Children's data has heightened protection under the DPDP Act: verifiable parental consent, and a ban on tracking and targeted advertising. The third problem lands on the principal's desk from outside: a student being bullied or sextorted online, with staff unsure of the reporting route.

School playbook

  1. Publish exactly one way to pay fees (the school portal or a named bank account) and tell parents in writing that the school never sends payment links in messages. Repeat it before every fee cycle.
  2. Keep the parent directory off WhatsApp. Use the ERP's messaging, and limit who can export contact lists.
  3. Audit where admission documents live. Move them to access-controlled storage; delete copies on personal devices and old email accounts.
  4. Revoke ERP, email and drive access on the day a staff member leaves.
  5. Give every teacher a one-page reporting route for a child in distress online: Childline 1098, the NCPCR portal, and the cybercrime.gov.in child-abuse reporting channel. Our guide to reporting online child abuse material covers the mandatory reporting duty, and the parents' guide to child online safety is material you can share with families.
  6. Run a short session for office staff on the fake-link patterns; the awareness training guide describes a format that works for small teams.

NBFCs and fintech lenders: regulated, fast and targeted

An NBFC is attacked at the speed of its own APIs. Fast onboarding is the business model, and fast onboarding with weak checks produces mule accounts: identities, real or synthetic, that pass KYC and become the receiving accounts for digital-arrest and investment scams. When 1930 complaints trace money to those accounts, the NBFC becomes part of the investigation and a subject of regulatory interest.

Technical weaknesses are the second exposure: mobile apps that trust the client, OTP flows that can be replayed, APIs that return another borrower's records when an ID is changed. Regulatory findings are the third: RBI inspections now routinely test cyber controls, and the Master Direction on IT governance (November 2023) sets expectations for governance, controls, audits and incident reporting. The RBI's role in cyber fraud, and its Sachet and Ombudsman channels, are explained in our RBI explainer.

NBFC playbook

  • Treat onboarding as a security control: velocity checks, device fingerprinting, video KYC where permitted, and monitoring of new accounts that immediately receive and forward funds.
  • Test the mobile app and APIs with authenticated, role-aware penetration testing; unauthenticated scans miss the flaws that matter in lending.
  • Map the RBI direction's requirements to named owners and dates; the board is accountable for IT governance under it.
  • Build the 1930 and law-enforcement request process: who receives a freeze request, how fast it is actioned, how records are produced.
  • Prepare the digital lending disclosures and grievance process; harassment complaints about recovery practices are reported to RBI Sachet and attract scrutiny.

Shared duty: all three sectors must report listed cyber incidents to CERT-In within six hours and keep logs for 180 days, under the directions of 28 April 2022. (Source: CERT-In directions under section 70B(6), cert-in.org.in)

What all three sectors share

The DPDP Act 2023 applies to each as a data fiduciary: consent, purpose limitation, reasonable security safeguards, breach notification, and penalties that can reach ₹250 crore. The DPDP compliance checklist is the common starting point, and DPDP compliance work is usually where a sector programme begins.

Each also faces the same human attacks as any office: a fake invoice to the accounts team, a "director" asking for gift cards, a screen-sharing request to "fix KYC". And each has a board, trust or management committee that is accountable but rarely briefed. A single hour with leadership, walking through the sector's worst realistic day, is where budget and ownership usually come from.

CERT-In's advisories are worth subscribing to in every sector; they regularly cover the hospital, education and financial systems that Indian organisations actually run.

SectorMost common lossFirst control
HospitalRansomware halts the HISOffline backups plus a rehearsed paper fallback
SchoolFee payment fraud on parentsOne published payment channel; no links in messages
NBFCMule accounts and API flawsOnboarding velocity checks; authenticated app and API testing

Next step: pick the one control in the table for your sector and give it an owner and a date this week. For hospitals, that means scheduling a backup restore test. For schools, a notice to parents about the single payment channel. For NBFCs, a review of accounts opened in the last 30 days that have already forwarded funds. If you want the full playbook tailored and presented to your board, the board cyber risk briefing is built for that conversation.

Frequently asked questions

Why are hospitals targeted by ransomware more than other businesses?

Because the pressure to pay is highest. A hospital that cannot see lab results, imaging or admission records has to slow or stop care, and attackers price their demands on that urgency. Hospital networks also carry old equipment that cannot be patched, which makes initial access easier.

What is fee payment fraud in schools?

Parents receive a message, often on WhatsApp from a number that looks like the school's, with a payment link or UPI ID for term fees, usually a few days before the genuine reminder. The money goes to a fraudster. The school learns of it when parents ask for receipts. The fix is a single published payment channel and a rule that fees are never collected by link in a message.

Which RBI rules apply to an NBFC's cyber security?

The Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices (November 2023) applies to most NBFCs and sets expectations for IT governance, controls, audits and incident reporting. Separate directions cover outsourcing of IT services and digital lending. Check the RBI site for the tier your NBFC falls in.

Do schools really need DPDP compliance?

Yes. Schools process children's personal data, which the DPDP Act treats with extra care: verifiable parental consent is required, and tracking or targeted advertising directed at children is prohibited. Admission forms with Aadhaar copies and photographs on shared drives are the most common exposure we see.

Is a VAPT enough for any of these sectors?

No. A VAPT finds technical weaknesses in systems at a point in time. The losses described here mostly come from process gaps: unverified payment links, unrevoked staff access, fast onboarding without checks. Pair a test with the sector playbook, not instead of it.

If you want help with this

  • Vulnerability assessment and penetration testing (VAPT) · Manual testing of your web apps, mobile apps, APIs, networks and cloud by people who think like the attacker, with findings ranked by what would actually be exploited first and a report your engineers can act on.
  • DPDP Act 2023 compliance · A practical path to compliance with the Digital Personal Data Protection Act 2023 and its rules, from gap assessment and consent design to breach notification planning and a DPO you can call.
  • Leadership and board cyber-risk briefing with ransomware tabletop · training · A three-hour briefing for founders, directors and CXOs that explains cyber risk in business terms and then runs a ransomware tabletop in which the leadership team makes the real decisions.
Talk to us
E

Written by

Editorial team

Research and writing