Provata Health takes data integrity very seriously. As stewards and partners of Provata Health Customers, we strive to assure data is protected from unauthorized access and that it is available when needed. The following policies drive many of our procedures and technical settings in support of the Provata Health mission of data protection.
- 10.b - Input Data Validation
- 164.308(a)(8) - Evaluation
Production Systems that create, receive, store, or transmit customer data (hereafter "Production Systems") must follow the following guidelines.
- All Production Systems must disable services that are not required to achieve the business purpose or function of the system.
- All access to Production Systems must be logged. This is done following the Provata Health Auditing Policy.
- All Production Systems must have OSSEC running at set to scan system every 2 hours and at reboot to assure no malware is present. Detected malware is evaluated and removed.
- All Production Systems are to only be used for Provata Health business needs.
- Patches, application, and system OS versions are kept up to date at all times. New versions are tested.
- Administrators subscribe to mailing lists to assure up to date on current version of all Provata Health managed software on Production Systems.
- Production Systems are monitors using IDS systems. Suspicious activity is logged and alerts are generated.
- Vulnerability scanning of Production Systems must occur on a predetermined, regular basis, no less than annually. Currently it is weekly. Scans are reviewed by Security Officer, with defined steps for risk mitigation, and retained for future reference.
- System, network, and server security is managed and maintained by the VP of Engineering and the Security Officer.
- Up to date system lists and architecture diagrams are kept for all Production environments.
- Access to Production Systems is controlled using centralized tools and two-factor authentication.
- Reduce the risk of compromise of Production Data.
- Implement and/or review controls designed to protect Production Data from improper alteration or destruction.
- Ensure that Confidential data is stored in a manner that supports user access logs and automated monitoring for potential security incidents.
- Ensure Provata Health customer Production Data is segmented and only accessible to customer authorized to access data.
- All Production Data at rest is stored on encrypted volumes. Encryption at rest is ensured through the use of automated deployment scripts referenced in the Provata Health Configuration Management Policy.
- Volume encryption keys and machines that generate volume encryption keys are protected from unauthorized access. Volume encryption key material is protected with access controls such that the key material is only accessible by privileged accounts.
- Encrypted volumes use AES encryption with a minimum of 256-bit keys, or keys and ciphers of equivalent or higher cryptographic strength.
- All data transmission is encrypted end to end. Encryption is not terminated at the network end point, and is carried through to the application.
- Transmission encryption keys and machines that generate keys are protected from unauthorized access. Transmission encryption key material is protected with access controls such that the key material is only accessible by privileged accounts.
- Transmission encryption keys use a minimum of 4096-bit RSA keys, or keys and ciphers of equivalent or higher cryptographic strength.
- Transmission encryption keys are limited to use for one year and then must be regenerated.
- In the case of Provata Health provided APIs, provide mechanisms to assure person sending or receiving data is authorized to send and save data.
- System logs of all transmissions of Production Data access.