Data Integrity

17.0 Data Integrity Policy

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

Production systems that create, receive, store, or transmit Customer data (hereafter "Production Systems") must follow the guidelines described in this section.

17.1 Applicable Standards

17.1.1 Applicable Standards from the HITRUST Common Security Framework

  • 10.b - Input Data Validation

17.1.2 Applicable Standards from the HIPAA Security Rule

  • CFR ยง 164.308(a)(8) - Evaluation

17.2 Disabling Non-Essential Services

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

17.3 Monitoring Log-in Attempts

  1. All access to Production Systems must be logged. This is done following the iDialogs Auditing and Data Access Policies.

17.4 Prevention of Malware on Production Systems

  1. All Production Systems must have OSSEC, Linux Malware Detect, and ClamAV running, and set to scan system every 2 hours and at reboot to assure no malware is present. Detected malware is automatically quarantined, evaluated, and removed. Incidents of malware are logged and investigated.
  2. Virus scanning software is run on all Production Systems for anti-virus protection.
    1. Hosts are scanned daily for malicious binaries in critical system paths.
    2. The malware signature database is checked hourly and automatically updated if new signatures are available.
    3. Logs of virus scans are maintained according to the requirements outlined in 8.6.
  3. All Production Systems are to only be used for iDialogs business needs.

17.5 Patch Management

Software patches and updates will be applied to all systems in a timely manner. In the case of routine updates, they will be applied after thorough testing following the policies outlined in the iDialogs Configuration Management Policy. In the case of updates to correct known vulnerabilities, priority will be given to testing to speed the time to production. Critical security patches are applied within 30 days from testing and all security patches are applied within 90 days after testing.

  1. Administrators subscribe to mailing lists to assure up to date on current version of all iDialogs managed software on Production Systems.
  2. Automated emails from OSSEC are sent to relevant administrators with security notices and information logged by the system.

17.6 Intrusion Detection and Vulnerability Scanning

  1. Production systems are monitored using multi-tiered IDS systems. These systems include OSSEC for host-based monitoring and SNORT for network level monitoring. Suspicious activity is logged and alerts are generated.
  2. 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.

17.7 Production System Security

  1. System, network, and server security is managed and maintained by the CTO and the Security Officer.
  2. Up to date system lists and architecture diagrams are kept for all production environments.
  3. Access to Production Systems is controlled using centralized tools and two-factor authentication over VPNs.

17.8 Production Data Security

  1. Reduce the risk of compromise of Production Data.
  2. Implement and/or review controls designed to protect Production Data from improper alteration or destruction.
  3. Ensure that confidential data is stored in a manner that supports user access logs and automated monitoring for potential security incidents.
  4. Ensure iDialogs Customer Production Data is segmented and only accessible to Customer authorized to access data.
  5. All Production Data at rest is stored on encrypted volumes using encryption keys managed by iDialogs. Encryption at rest is ensured through the use of automated deployment scripts referenced in the Configuration Management Policy.
  6. 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.
  7. Encrypted volumes use AES encryption with a minimum of 128-bit keys, or keys and ciphers of equivalent or higher cryptographic strength.

17.9 Transmission Security

  1. All data transmission is encrypted end to end using encryption keys managed by iDialogs via the Amazon KMS service. Encryption is not terminated at the network end point, and is carried through to the application.
  2. 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.
  3. Transmission encryption keys use a minimum of 2048-bit RSA keys, or keys and ciphers of equivalent or higher cryptographic strength (e.g., 256-bit AES session keys in the case of IPsec encryption).
  4. Any keys not managed directly by the AWS KMS service will maintain a 4096-bit asymmetric cipher with an AES 256-bit encrypted key. This applies to keys used for access to systems by authorized personnel (i.e. SSH keys)
  5. Transmission encryption keys are limited to use for a maximum of two years and then must be regenerated.
  6. In the case of iDialogs provided APIs, provide mechanisms to assure person sending or receiving data is authorized to send and save data.
  7. System logs of all transmissions of Production Data access. These logs must be available for audit.