Domino’s physical infrastructure is hosted and managed within Amazon’s secure data centers and utilize the Amazon Web Service (AWS) technology. Amazon continually manages risk and undergoes recurring assessments to ensure compliance with industry standards. Amazon’s data center operations have been accredited under:
- ISO 27001
- SOC 1 and SOC 2/SSAE 16/ISAE 3402 (Previously SAS 70 Type II)
- PCI Level 1
- FISMA Moderate
- Sarbanes-Oxley (SOX)
Domino utilizes ISO 27001 and FISMA certified data centers managed by Amazon. Amazon has many years of experience in designing, constructing, and operating large-scale data centers. AWS data centers are housed in nondescript facilities, and critical facilities have extensive setback and military grade perimeter control berms as well as other natural boundary protection. Physical access is strictly controlled both at the perimeter and at building ingress points by professional security staff utilizing video surveillance, state of the art intrusion detection systems, and other electronic means. Authorized staff must pass two-factor authentication no fewer than three times to access data center floors. All visitors and contractors are required to present identification and are signed in and continually escorted by authorized staff.
Amazon only provides data center access and information to employees who have a legitimate business need for such privileges. When an employee no longer has a business need for these privileges, his or her access is immediately revoked, even if they continue to be an employee of Amazon or Amazon Web Services. All physical and electronic access to data centers by Amazon employees is logged and audited routinely.
For additional information see: https://aws.amazon.com/security.
Firewalls are utilized to restrict access to systems from external networks and between systems internally. By default all access is denied and only explicitly allowed ports and protocols are allowed based on business need. Each system is assigned to a firewall security group based on the system’s function. Security groups restrict access to only the ports and protocols required for a system’s specific function to mitigate risk.
The contents of your project files are stored in Amazon’s S3 data storage service. For additional information see: https://aws.amazon.com/security . Some meta data about project files is stored in a Git repository. The Domino platform verifies that any user asking for a file is authorized to access the requested file.
Each Run of a Project on the Domino platform runs within its own isolated environment and cannot interact with other Project Runs or areas of the system. This restrictive operating environment is designed to prevent security (of users’ code and data files) and stability issues. These self-contained environments isolate processes, memory, and the file system using LXC while host-based firewalls restrict applications from establishing local network connections.
We use a database to store information about users (such as username and email address) as well as meta data about Projects and Runs (e.g., timestamps and status messages). This data is stored in a database hosted by MongoLab. More information about MongoLab’s security can be found at: http://docs.mongolab.com/security/.
We do not store users’ passwords anywhere in our system.
Data at rest
Data is encrypted anytime it is “at rest” in the Domino platform, including in our “blob store”, and on disk on the “executor” machines that run user scripts.
Data in transit
Data is encrypted during transit between users’ machines and different parts of the Domino platform. We use industry-standard SSL for encrypted communication.
System configuration and consistency is maintained through standard, up-to-date images, configuration management software, and by replacing systems with updated deployments. Systems are deployed using up-to-date images that are updated with configuration changes and security updates before deployment. Once deployed, existing systems are decommissioned and replaced with up-to-date systems.
Operating system access is limited to Domino staff and requires username and key authentication. Operating systems do not allow password authentication to prevent password brute force attacks, theft, and sharing.
Software Engineering Methodology
Every line of code is reviewed before being deployed to our production environment. Among other things, code reviewers are trained to look for security vulnerabilities.
Access to Customer Data
Domino staff does not access or interact with customer data or applications as part of normal operations. There may be cases where Domino is requested to interact with customer data or applications at the request of the customer for support purposes or where required by law.
To report a security vulnerability, please email firstname.lastname@example.org. For non-emergency issues, we encourage customers to open a support ticket by emailing email@example.com.
Best Practices for Securing Your Projects
We recommend that you:
- Do not store passwords or other private keys/credentials inside your source code files. Instead, use the Secure Config feature to store secure values safely.
- Do not use third-party libraries or dependencies without verifying that they are safe and trustworthy.