Enterprise Technical Security Architecture

MedOpera Security Whitepaper

Technical, architectural, and cryptographic controls implemented by DigiOpera Private Limited to protect hospital operations and patient medical records.

Engineered by DigiOpera Private Limited
•
Zero-Trust Hospital Cloud Architecture
•MeitY Sovereign Cloud Tier IV

01.Enterprise Security Overview & Principles

In a modern 24/7 hospital operating environment, software downtime or security compromise directly imperils patient safety, critical care delivery, and institutional trust. DigiOpera Private Limited architects MedOpera upon a non-negotiable Zero-Trust Security Framework.

Every request—whether originating from an internal nursing station, an ICU vital monitor, a mobile physician pad, or an external laboratory auto-analyzer—is authenticated, verified for explicit least-privilege role authorization, encrypted in flight, and logged to an immutable forensic audit journal.

Zero-Trust Boundaries

No implicit trust for internal hospital local area networks.

Defense in Depth

Multi-layered network, database, application, and physical guards.

Cryptographic Isolation

Hardware-accelerated AES-256 encryption across all data tiers.

02.Cryptographic Specifications

StateCryptographic AlgorithmKey Management / Standard
Data in TransitTLS 1.3 / ECDHE-RSA-AES256-GCM-SHA384Automated rotating SSL/TLS certificates via DigiCert/Let's Encrypt; HSTS preloaded
Data at RestAES-256-GCM Authenticated EncryptionDedicated Cloud KMS / HSM; annual automated envelope key rotation
User PasswordsArgon2id (m=64MB, t=3, p=4)FIPS-compliant per-user cryptographically random 128-bit salt
Token AuthenticationHMAC-SHA256 (JWT Claims with short TTL)15-minute access token window with secure server-side refresh revocation table

03.Multi-Tenant Database Isolation & Data Protection

MedOpera supports shared enterprise database infrastructure while providing ironclad, mathematically provable tenant data segregation:

  • PostgreSQL Row-Level Security (RLS): Every clinical entity (prescriptions, inpatient admissions, patient files, invoices) contains an indexed tenant_id UUID foreign key. At the database engine level, PostgreSQL RLS policies restrict execution so that query plans cannot return rows belonging to a different tenant ID.
  • Connection & SaveChanges Interceptors: In the .NET 9 application layer, EF Core interceptors strictly validate incoming tenant contexts. Any cross-tenant data mutation attempt immediately throws an unhandled security exception and terminates the transaction.
  • Dedicated Database Option: For tertiary university hospitals and corporate networks with over 300 beds, DigiOpera Private Limited provides single-tenant physical database provisioning upon dedicated virtual private cloud (VPC) clusters.

04.Identity, Role-Based Access Control (RBAC) & Session Hygiene

Hospital data leaks typically occur due to internal privilege creep or compromised shared terminals. MedOpera mitigates this via forensic identity controls:

Least-Privilege Roles

Strict segregation across 7 standard hospital operational roles (Admin, Receptionist, Doctor, Nurse, Pharmacist, Lab Tech, Accountant).

Dual Witness Narcotic Gate

Dispensing CDSCO Schedule X or narcotic pharmaceuticals requires secondary staff credential verification and timestamped witness sign-off.

Discharge Clearance Gates

Doctor, Nursing, Pharmacy, and Billing clearances are verified individually on the backend and cannot be bypassed via UI manipulation.

Session Auto-Lock

Workstations automatically lock after 15 minutes of inactivity to protect unattended nursing bay monitors.

05.Network Perimeter Defense & DDoS Mitigation

Our production ingress architecture utilizes multi-stage cloud perimeter filtering:

• Volumetric DDoS Shielding: Web Application Firewalls (WAF) inspect incoming requests, neutralizing Layer 3/4 volumetric floods and Layer 7 HTTP application attacks before traffic reaches application pods.

• Strict Ingress Filtering: Reverse proxies enforce strict Content Security Policy (CSP), X-Frame-Options: DENY, and strict Referrer-Policy headers to eliminate Clickjacking, Cross-Site Scripting (XSS), and MIME sniffing vectors.

06.Disaster Recovery, Automated Backups & High Availability

• Automated Write-Ahead-Log (WAL) Archiving: PostgreSQL continuous WAL archiving enables point-in-time recovery (PITR) down to the exact second.

• Dual-Region Snapshot Mirroring: Production database backups are encrypted with independent KMS keys and mirrored daily to a secondary geographic cloud zone within India.

• Quarterly Live Restoration Drills: DigiOpera systems engineering conducts quarterly unannounced restoration drills validating that complete hospital instances can be reconstructed within 120 minutes.

07.Immutable Forensic Audit Trails

Every critical medical, financial, and access event recorded in MedOpera writes an audit entry capturing:

  • Exact UTC and Asia/Kolkata timestamp
  • Authenticated User ID, Full Name, and Operational Role
  • Originating IP Address, User-Agent, and Terminal Identifier
  • Action Code (e.g. PRESCRIPTION_PRESCRIBED, MEDICATION_DISPENSED, INVOICE_CANCELLED, PATIENT_DISCHARGED)
  • Cryptographic JSON diff of Before and After entity states

Audit tables are append-only. No application role, including Hospital Admin, has permission to execute SQL UPDATE or DELETE operations against audit partitions.

08.Continuous VAPT & Security Audits

DigiOpera Private Limited subjects MedOpera to systematic Vulnerability Assessment and Penetration Testing (VAPT) performed by CERT-In empaneled independent third-party cybersecurity auditors.

Request SOC2 / VAPT Executive Summaries:
Chief Information Security Officer (CISO), DigiOpera Private Limited