Security and Compliance

The platform adheres to guidelines established by international regulatory bodies for data security and privacy protection. The software is designed to comply with current data protection laws such as GDPR and HIPAA. To prevent breaches in data privacy, users should follow guidance and best practices regarding the storage of PHI as indicated below.

Overview of Security and Compliance Practices

  • ISO 27001, ISO 27701, & ISO 13485

  • Compliant with GDPR, HIPAA, PIPEDA, and DSPTK requirements

  • Transport Layer Security (TLS 1.2) for web-based API communication security

  • Data encrypted at rest using Advanced Encryption Standard (AES)-256

  • Service Organization Controls 1/SSAE, 16/SSAE 3402

  • Federal Information Security Management Act (FISMA) Moderate

  • Payment Card Industry Data Security Standard Level 1

  • Federal Information Processing Standard Publication 140-2

  • Regularly scheduled penetration testing by a third-party security firm

  • Periodic network scanning

  • Granular role-based access allows tight regulation over who can access and interact with data within the platform

  • Public Key Infrastructure (PKI) to provide digital signatures to track actions within the security architecture

  • Audit logging actions on the objects within the platform are recorded

  • Data policies mitigating risk from attachments that could contain malware

  • System hosts (virtual instances) deployed as known fixed images

  • Automated secure code scanning adhering to Open Web Application Security Project (OWASP) guidance

  • Two-factor authentication available for Enterprise license users

Health Insurance Portability and Accountability Act (HIPAA)

File content is the only place where users may safely store Protected Health Information (PHI). Personal data should not be stored in metadata or path names. Note that, to operate in a HIPAA compliant manner, you will also need a BAA with Illumina. Contact your account manager or Illumina Technical Support for more information. If you need to request an audit trail, contact Illumina Technical Support with the information you need.

General Data Protection Regulation (GDPR)

Data file content is the only place where users may safely store Personal Data is in file content. Personal data should not be stored in metadata or path names.

General Guidance

Data can be brought to the platform through several mechanisms. Care should be taken when specifying data to be uploaded or connected to avoid unintentional privacy breach when dealing with sensitive data.

  • Ensure AWS S3 key prefixes are properly specified when creating a storage configuration and that all S3 objects under the prefix shall be made available.

  • Take care when deleting data from the platform sourced from AWS S3 connected storage configurations as the delete operation will delete the object from the source AWS S3 bucket.

  • Ensure the path to the source data is correct and does not include unintended files when performing uploads through the service connector or command-line interface.

Last updated