Healthcare Cybersecurity in India: Protecting Patient Data Under DPDP

  • Home
  • Healthcare Cybersecurity in India: Protecting Patient Data Under DPDP
Healthcare Cybersecurity in India: Protecting Patient Data Under DPDP
Healthcare Cybersecurity in India: Protecting Patient Data Under DPDP
Healthcare Cybersecurity in India: Protecting Patient Data Under DPDP
Healthcare Cybersecurity in India: Protecting Patient Data Under DPDP

Indian healthcare is undergoing a rapid digital transformation. Hospital management systems (HMS), electronic medical records (EMR), telemedicine platforms, and connected medical devices are generating and processing more patient data than ever before. This digital acceleration brings a parallel challenge: ensuring that sensitive personal data — medical records, diagnostic images, lab results, insurance information — is protected in compliance with the Digital Personal Data Protection (DPDP) Act 2023.

This guide covers the specific cybersecurity measures that Indian hospitals and healthcare providers need to implement for DPDP compliance, with practical architectures that work within the constraints of existing medical infrastructure.

What the DPDP Act Requires From Healthcare Providers

As data fiduciaries under the DPDP Act, hospitals and healthcare providers must:

  • Obtain explicit consent from patients for collection and processing of their personal data, with clear purposes stated
  • Implement reasonable security safeguards to prevent data breaches — this is the key requirement for IT/security teams
  • Notify the Data Protection Board within 72 hours of a personal data breach
  • Ensure data accuracy and completeness — especially critical for medical records that inform clinical decisions
  • Facilitate data subject rights — patients can request access to, correction of, and erasure of their data
  • Retain data only as long as necessary — healthcare data typically has longer retention periods (5-10 years depending on the type), but the principle still applies

Notably, the DPDP Act designates health data as “sensitive personal data,” which triggers higher standards for consent, security, and breach notification. The penalty for non-compliance can extend to ₹250 crore.

The Healthcare Cybersecurity Challenge

Healthcare networks face unique security challenges that make standard enterprise security approaches insufficient:

  • Legacy medical devices: CT scanners, MRI machines, ventilators, and infusion pumps often run outdated operating systems (Windows XP Embedded, Windows 7 Embedded) that can’t be patched. They have operational lifespans of 7-15 years.
  • Unencrypted medical protocols: DICOM (imaging) and HL7 (laboratory/clinical data) transmit in cleartext by default. These protocols were designed in the 1990s for interoperability, not security.
  • Converged IT/OT networks: Clinical devices, building management systems (HVAC, access control), and administrative IT share the same infrastructure in many hospitals.
  • 24/7 availability requirements: Patient-critical systems cannot be taken offline for patching, maintenance, or security updates without potentially affecting patient care.
  • Supply chain complexity: Medical device manufacturers, EMR vendors, PACS vendors, lab system vendors — each with their own security practices and update cycles.

A Phased Approach to Healthcare Cybersecurity for DPDP Compliance

Phase 1: Asset Discovery and Network Segmentation (1-2 months)

Goal: Know what’s on your network and isolate it appropriately.

Passive discovery: Use passive network monitoring (SPAN ports, NetFlow, or FortiGate’s traffic logging) to identify every device on the hospital network without active scanning. Medical devices can crash under active scanning. Document each device: IP, MAC, vendor, operating system, function, and connected services.

Network segmentation: Create isolation zones based on function and risk level:

  • Clinical VLAN 1 — Imaging (DICOM): CT, MRI, X-ray, ultrasound, PACS server, DICOM viewers. Rule: only DICOM traffic on port 11112. No outbound internet access.
  • Clinical VLAN 2 — Labs (HL7): Lab analysers, LIS server, HL7 interface engine. Rule: only HL7 traffic. No outbound internet access.
  • Clinical VLAN 3 — Patient Management: HMS, EMR servers, registration, billing. Limited to authorised clinical/admin staff via AD authentication.
  • IoT/Building VLAN: HVAC, CCTV, access control, environmental sensors. Fully isolated from clinical networks.
  • Guest VLAN: Patient and visitor Wi-Fi. Internet only, isolated from all clinical networks.
  • Administration VLAN: Staff desktops, peripherals. Access to clinical VLANs via application-specific proxies only — no general routing.

Fortinet approach: FortiGate firewall with inter-VLAN rules and FortiNAC for 802.1X device authentication on managed switches. FortiGate’s application control identifies DICOM and HL7 traffic and can enforce policies even on unauthenticated devices.

DPDP compliance outcome: Reasonable security safeguards demonstrated through network segmentation and least-privilege access controls.

Phase 2: Access Control and Authentication (1-2 months)

Goal: Know who and what is accessing patient data.

802.1X deployment: Implement 802.1X on all managed switches. Every device authenticates before getting network access. Medical devices that can’t do 802.1X get MAC authentication bypass (MAB) with registered MAC addresses only — unregistered MACs are dropped into a quarantine VLAN with minimal access.

Role-based access: Integrate FortiAuthenticator with the hospital’s Active Directory. Doctors get access to the EMR and PACS. Lab technicians get access to the LIS only. Administrative staff get access to HMS only. No admin gets access to systems they don’t need for their role.

Multi-factor authentication (MFA): Deploy MFA for all remote access, all administrator accounts, and any access to systems containing sensitive personal data. FortiAuthenticator supports TOTP, SMS, and push notification MFA.

Session logging: Log every access event — who accessed what system, from which device, at what time, and what data they viewed or modified. FortiGate logging plus FortiAnalyzer provides a searchable, compliant audit trail.

DPDP compliance outcome: Access controls and audit trails demonstrate that patient data is accessed only by authorised personnel, with full accountability for every access.

Phase 3: Monitoring and Threat Detection (1-2 months)

Goal: Detect and respond to security incidents affecting patient data.

Baseline behaviour: Medical devices have predictable traffic patterns. A CT scanner sends images to the PACS server after each scan. An infusion pump sends status updates every 30 seconds. A lab analyser sends HL7 messages when results are ready. Establish baselines for normal behaviour — the SIEM detects deviations.

Anomaly detection: Configure alerts for: medical devices communicating with unfamiliar IPs, sending data at unusual times, attempting internet access, or showing sudden traffic volume changes. These are indicators of compromise that traditional security tools miss.

Log retention: Maintain 180 days of logs from all critical systems (FortiGate, FortiAnalyzer, Windows Event Logs from domain controllers, EMR/PACS audit logs). This satisfies both CERT-In requirements and DPDP data protection obligations.

Incident response: A documented IR plan tailored for healthcare — with specific procedures for preserving clinical continuity during an incident, isolating affected systems without disrupting patient care, and reporting breaches to the Data Protection Board within 72 hours.

DPDP compliance outcome: 72-hour breach notification capability, evidence of monitoring, and documented incident response procedures.

Phase 4: Vendor and Supply Chain Security (Ongoing)

Goal: Ensure that third-party vendors don’t become a backdoor into patient data.

Vendor access controls: Medical device vendors often need remote access for maintenance. Use ZTNA (see Day 6) for time-bound, application-specific vendor access. No permanent VPN accounts. No vendor access to any system beyond the specific device they’re maintaining.

Vendor security assessments: Request security documentation from all medical device and EMR vendors. Understand their vulnerability management practices, patching cycles, and breach notification procedures. Include security requirements in procurement contracts.

Patching agreements: Work with medical device manufacturers to establish patching windows and validation procedures. Document when patches can’t be applied and the compensating controls in place.

DPDP compliance outcome: Supply chain risk management demonstrating that third-party access is controlled and monitored.

Measuring Compliance: A Healthcare DPDP Checklist

  • ✅ Asset inventory of all devices accessing patient data completed
  • ✅ Network segmentation implemented with least-privilege inter-VLAN rules
  • ✅ 802.1X or MAB deployed on all managed switches
  • ✅ Role-based access controls with AD integration for all clinical systems
  • ✅ MFA enabled for all admin and remote access
  • ✅ Centralised logging with 180-day retention (CERT-In compliant)
  • ✅ SIEM/SOAR monitoring for anomalous medical device behaviour
  • ✅ Documented incident response plan with healthcare-specific procedures
  • ✅ 72-hour breach notification procedure established
  • ✅ Vendor access controls with ZTNA or time-limited access
  • ✅ Data subject rights procedure (patient data access, correction, erasure)
  • ✅ Employee security awareness training conducted
  • ✅ Privacy policy and consent management for patient data processing
  • ✅ Data Protection Officer (DPO) appointed (for hospitals above specified thresholds)

How P J Networks Can Help

We’ve helped Indian hospitals from 50 beds to 1000+ beds implement DPDP-compliant cybersecurity architectures. Our approach is phased, practical, and designed to work within the constraints of existing medical infrastructure — including the unpatchable devices that every hospital has.

Contact our healthcare cybersecurity team for a compliance gap assessment. We’ll audit your current network architecture, identify DPDP compliance gaps, and deliver a phased remediation plan with budget estimates.


P J Networks has been securing Indian healthcare institutions since 2001. We specialise in medical device network security, DPDP compliance, and Fortinet-based hospital security architecture.

Leave a Reply

Your email address will not be published. Required fields are marked *