Trust Center & Governance

Data Protection Policy

Technical, administrative, and physical safeguards governing data encryption, database access control, and regulatory compliance.

1. Purpose & Scope

This Data Protection Policy establishes operational standards for safeguarding electronic Protected Health Information (ePHI), personally identifiable information (PII), and financial transaction telemetry across Exxari's application infrastructure.

This policy applies to all systems, database services, API microservices, and personnel handling platform data under applicable healthcare and financial regulatory frameworks.

Regulatory Scope Notice:

Exxari's data protection architecture enforces compliance controls aligned with HIPAA Security Rule, NIST SP 800-53, PCI-DSS v4.0, and applicable national health data regulations.

2. Application & File System Security

2.1 Isolation & Principle of Least Privilege

The web application operates within isolated application directories owned strictly by unprivileged system service accounts. The application daemon operates without root access, interactive login shell execution, or system administration privileges.

2.2 File System Permissions & Auditing

  • World-Writable Restrictions: World-writable files are explicitly banned across application binaries and configuration paths, restricted exclusively to isolated system temporary directories (`/tmp`).
  • SUID Root Control: SUID root binaries are restricted strictly to default operating system utilities (`sudo`, `passwd`) and monitored continuously against unauthorized privilege escalation.
  • Encryption & Storage: Application assets, diagnostic outputs, and report parsing caches reside on AES-256 encrypted storage volumes.

3. Cryptographic Controls & Key Management

All data transmitted or stored within Exxari services is protected using modern, audited cryptographic protocols:

  • Data in Transit: API communications and web sessions enforce mandatory TLS 1.2+ encryption with strong cipher suites. Plaintext HTTP traffic is automatically upgraded to HTTPS.
  • Data at Rest: Database records, diagnostic files, and backups are encrypted using AES-256 bit encryption.
  • SSL/TLS Key Security: Private keys are stored in isolated system directories (`/etc/ssl/private`), owned by root, and locked down with strict `600` file permissions to prevent unauthorized process access.

4. Database Security & Role Isolation

Database access enforces role separation and strict network isolation:

  • Unprivileged System User: The database engine operates under dedicated, unprivileged system accounts with restricted access strictly to its data directories.
  • Runtime Application Account: Web applications connect using restricted database users limited strictly to necessary DML operations (`SELECT`, `INSERT`, `UPDATE`, `DELETE`). Administrative privileges (`DROP`, `ALTER`, `TRUNCATE`) are disabled for application runtime connections.
  • Administrative Superuser: DBA and schema modification access requires Multi-Factor Authentication (MFA), encrypted Bastion connection, and audit logging. Direct external internet access to database ports is explicitly blocked.

5. Network Architecture & Firewall Rules

Host and cloud network perimeters are governed by host-based and network firewalls:

  • Host Firewall (UFW): Default-deny inbound traffic policy permitting only public web ports (80/443) and authenticated administrative access.
  • Remote Administration: SSH access (TCP/22) requires public key verification. Direct password logins are disabled across production systems.
  • VLAN & VPC Isolation: Production application hosts and database nodes operate within isolated Virtual Private Cloud (VPC) network segments.

Data Protection Office

For inquiries regarding technical security controls, data protection audits, or vulnerability reporting, contact our Security Office:

Office AddressData Protection Office, Exxari Inc.