Skip to content

Latest commit

 

History

History
59 lines (36 loc) · 3.13 KB

data_integrity_policy.md

File metadata and controls

59 lines (36 loc) · 3.13 KB
Raw

Data Integrity Policy

BloomAPI takes data integrity very seriously. As stewards and partners of BloomAPI 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 BloomAPI mission of data protection.

Applicable Standards from the HITRUST Common Security Framework

  • 10.b - Input Data Validation

Applicable Standards from the HIPAA Security Rule

  • 164.308(a)(8) - Evaluation

Data integrity Policy

Production Systems that create, receive, store, or transmit customer data (hereafter "Production Systems") must follow the following guidelines.

Disabling non-essential services

  • All Production Systems must disable services that are not required to achieve the business purpose or function of the system.

Monitoring Log-in Attempts

  • All access to Production Systems must be logged. This is done following the BloomAPI Auditing Policy.

Prevention of malware on Production Systems

  • All Production Systems are to only be used for BloomAPI business needs.

Patch Management

  • 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 BloomAPI managed software on Production Systems.

Intrusion Detection and Vulnerability Scanning

  • Production Systems are monitored using IDS systems. Suspicious activity is logged and alerts are generated.
  • Vulnerability scanning of Production Systems must occur on a predetermined, regular basis. Results are reviewed by Security Officer, with defined steps for risk mitigation, and retained for future reference.

Production System Security

  • System, network, and server security is managed and maintained by the CTO 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.

Production Data Security

  • 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 BloomAPI customer Production Data is segmented and only accessible to customers authorized to access data.
  • All Production Data at rest is stored on encrypted volumes.

Transmission Security

  • All data transmission is encrypted end to end. Encryption is not terminated at the network end point, and is carried through to the application.
  • Encryption keys and machines that generate keys are protected from unauthorized access.
  • Encryption keys are limited to use for one year and then must be regenerated.
  • In the case of BloomAPI 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. These logs must be available for audit.