Security at Orquesta
Last updated on February 16, 2023
Security and reliability is a top priority at Orquesta, underpinning all of our work and our daily activities.
In order to guarantee optimal security we work with data-protection specialists on our comprehensive security program. We've established procedures to regularly evaluate security risks, threats and vulnerabilities for our users. This system also enforces a management process to constantly manage risk and meet security needs. To ensure neutrality around these processes and standards, certifications and repetitive screenings are performed by external auditors.
Our Senior Management team is accountable for security and ensures that security capabilities and competence exist in all levels of our business. As a whole, we follow a holistic and collaborative approach to guarantee the confidentiality, availability, and integrity of your data. On this page, you can read about the various policies and security measures taken by Orquesta to secure customer data hosted on our platform from unauthorized access.
How we protect your data
Our infrastructure runs on the Google Cloud Platform, delivering infrastructure as a service with prime security capabilities.
ISO 27001 / SOC2 compliant data centres
The data centres used for storing your data and allowing the delivery of your data to your users are also certified for compliance with the ISO 27001 / SOC2 standards.
Data storage and encryption at rest
Your data is encrypted at rest in GCP cloud SQL instances. AES256 encryption is used by default using the services encryption services. This ensures the data is preserved and safe from prying eyes and manipulation.
Encryption in transit
All communication of your data between you, your services, and Orquestsa traverses the Internet via encrypted HTTPS traffic using TLS v1.2. Data is also encrypted during transit between Orquesta and our Content Delivery Networks (CDNs). This encryption during communication ensures information cannot be read or manipulated by unauthorized third parties.
All our data, including storage buckets and database daily backups, is replicated and geo-redundant thanks to the use of GCP. Backup data is encrypted at rest using AES-256 encryption.
We use Google Secrets Manager to manage encryption keys for maximum security in line with industry best practices.
Access to data
Access to your data is extremely restricted. We have hand-picked and trained support engineers and appropriate staff who after your explicit permission, can help fix your problem by accessing the affected data that you authorize. These actions are recorded, audited, and monitored. Orquesta’s feature set covers role-based access control which allows the org admin to set granular permissions.
We are a cloud-native service. We do not have data centres. Physical security to our servers and to your data is managed by GCP security certifications. We operate fully remote, so there are no physical offices where any of your data can be present.
Data retention policy
Your user data lives in our servers for as long as you need. Our Data Retention Policy and Data Classification Policy govern the way we manage data that needs deletion and retirement. Any data classified as PII is never stored and wiped immediately after our business rules engine evaluation completes. Versions, evaluation logs and audit logs are automatically deleted after the retention policy of your plan.
How we keep our service reliable
Auto-scalable serverless and containerized services
All our software components run serverless or in containers orchestrated by Kubernetes. The clusters are automatically resized when the load on the system exceeds a pre-defined threshold. We have a sleeping node of our application in most GCP locations globally. Our platform has been designed from scratch to support high volumes of web traffic and this technology stack, alongside a microservice architecture, is the fundamental piece that caters to our high availability needs.
Since we run serverless and containerised services, we manage no physical infrastructure, hardware, servers and networking components.
Disaster recovery and business continuity
Orquesta utilizes database replication architectures to ensure redundancy and uptime. Encrypted backups are made frequently and stored both onsite at the data center and copied to a remote storage location.
How we keep our code secure
All vulnerabilities are managed internally in our internal vulnerability management tool. We use Snyk, GCP Vulnerability Scanner and Github’s Dependabot to continuously scan our codebase and third-party libraris for vulnerabilities. Once a vulnerability is detected, it is assigned a score, using a scoring system, and an owner. Often, an automatic pull request is also created with the fix. We have an internal SLA that stipulates deadlines for fixing vulnerabilities, while progress is tracked by tools and, if necessary, a post-mortem is arranged as a learning exercise for our engineers to improve code security.
Code peer review
Our development process is based on GitHub’s pull request mechanism. Once a commit is made to a branch in a specific repository, the code is reviewed by members of the same team or from other engineering teams. Only once the pull request is approved by all tagged engineers is the code moved along in the development life cycle.
Quality Assurance (QA)
Once the code is ready to be tested, it is deployed to our staging environment. This environment runs a downscaled version of the production infrastructure and does not contain any production data. Quality assurance is performed in a different GCP cluster, entirely separate from production.
Secure Software Development Lifecycle
Security is part of our product organization and influences the product roadmap and specific features. We implement a philosophy of “security by design” where security features are embedded in the product and architecture design to ensure existing and new functionalities are free of vulnerabilities. We believe that engineers should be responsible for the code they create and have an established culture of accountability, which leads to a high level of code quality and security being maintained.
How we secure our business
Security monitoring and Incident Management
Our security compliance and technology landscape is continuously monitored by Vanta Platform and assessed according the SOC2 controls. Any control requiring attention triggers notifications to Senior Management.
Orquesta continually looks out for any indicators that could potentially lead to security incidents. To supplement this, any event-alerting tools we use also escalate into rotations for Orquesta’s 24x7 incident response team.
Security awareness program
All Orquesta employees and contracted third parties are required to comply with Orquesta policies relevant to their scope of work, including security and data privacy policies. Our standard work contract includes confidentiality clauses and we have an annual security awareness program that kicks off from initial onboarding.
Vendor security management
Every technology, SaaS or tool is assessed to ensure a good understanding of the risks involved. Each vendor with medium and high security impact requires a SOC2 certification in Vanta Platform . Confidentiality and non-disclosure agreements are required when sharing any sort of confidential information that could be sensitive, proprietary, and/or personal in nature, between Orquesta and an external third party. Any third-party service providers whose services involve access to any confidential information must agree contractually to data privacy and security commitments based on their level of access and handling of information.
The use of multi-factor authentication (MFA) is enforced throughout the main services Orquesta relies on. MFA is also encouraged by Orquesta to both its employees and customers. The use of MFA provides an additional measure for verifying a user’s claimed identity over the use of just a password. Currently, the minimum requirement for our MFA implementation is the use of a password combined with an access token (for instance, a code provided by Google Authenticator). MFA is also mandatorily enforced for GCP and GitHub access.
How you can protect your data
Roles and permissions
Orquesta strongly encourages the use of roles and permissions in order to provide different users with different levels of access rights to content, features, and functionality. This is in line with “least privilege” and “need to know” security principles, which add another safeguarding layer to prevent unauthorized access and limit damage in the event of a user’s credentials being compromised.
While all activities relevant to content and data traversing the Internet are conducted with HTTPS enforced on Orquesta’s side, we absolutely recommend that customers and users also enforce HTTPS so that content and data integrity is maintained and free from manipulation as it is served from our service to your users’ machines. The use of HTTPS websites also safeguards your important data and credentials away from the view of unauthorised third-parties
In case of a security incident
Incidents can happen to anyone — we are ready for such an event when it happens. We manage security incidents via a documented process, which includes notification of and cooperation with customers, data protection authorities, and law enforcement. Orquesta will notify affected customers without undue delay following incident detection, where we share a preliminary assessment of the incident and are open to cooperation. We follow article 33 of the GDPR when personal data is involved, and alert the supervisory authority regarding breach of personal data.
How to report vulnerabilities or contact Orquesta’s privacy and security officers
Our security team can be reached by mailing email@example.com.