rencore.com (opens in a new tab) Start a trial (opens in a new tab)

Infrastructure

Last updated Security & Privacy

AI summary

Rencore Governance secures connections using TLS 1.3 and operates on a separate Azure subscription protected by firewalls with restricted access. Customer data is processed in isolated Azure Container Instances that are deleted after each analysis. Rencore GmbH holds ISO 27001:2022 and ISO 27017 certifications, and a SOC 2 Type 2 report is available on request.

Customers connect to Rencore Governance over TLS 1.3, and its Azure infrastructure runs in a separate subscription behind firewalls.

How do customers connect securely to Rencore Governance?

The web portal interface is always enforced over TLS 1.3 (https). Any communication with data storage happens from the web portal’s backend.

How does Rencore secure the infrastructure and the services in Azure?

Rencore Governance is hosted in a separate Azure subscription. Nobody has access to this subscription except for the Product Operations team, which has access to the cloud infrastructure. No access to customer data or encryption keys is allowed to anyone at Rencore unless granted in accordance with the System Access Control Policy.

All resources in the Rencore Governance infrastructure are deployed into a specific Virtual Network, where firewalls are enabled by default across all services. Requests are automatically denied unless the requests come from a service within the virtual network. Our CI/CD platform is allowed to deploy updates to the infrastructure as part of normal operations, which requires access to the administrative interface of Microsoft Azure; this access is granted just in time for the update procedure to be completed and it is automatically removed right after it. Other than this process, no external requests are allowed, even if they were authenticated. Only our Web Application Firewall allows external requests from the direction of the internet.

Processing data from a customer tenant (connecting to, downloading, and analyzing data), happens from inside Azure Container Instances. Every ACI is deployed to our Virtual Network and is uniquely deployed for each customer and each job. We delete each container when the analysis has finished, and therefore, we can never reuse containers.

Does Rencore’s infrastructure adhere to any particular compliance standards?

Rencore Governance has a SOC 2 Type 2 report, which is available on request: request access on trust.rencore.com. The same applies for materials pertaining to Rencore’s ISO 27001:2022 and ISO 27017 certification. See Certifications and compliance for details.

Rencore adheres to its catalogue of security and other internal policies: a broad overview of this can be obtained from the Rencore security report.

Frequently asked questions

How is my connection to Rencore Governance secured?

All connections use TLS 1.3, and the web portal interface is always enforced over HTTPS. Communication with data storage happens from the web portal backend.

How does Rencore prevent unauthorized access to customer data?

Rencore Governance runs in a separate Azure subscription accessible only to the Product Operations team. All infrastructure resources are behind firewalls in a Virtual Network that denies external requests by default. The System Access Control Policy restricts access to customer data and encryption keys.

Is Rencore Governance compliant with security standards?

Yes. Rencore Governance has a SOC 2 Type 2 report. Rencore holds ISO 27001:2022 and ISO 27017 certifications. Materials for both are available on request through trust.rencore.com.

How does Rencore process customer data?

Customer data processing happens in Azure Container Instances within the Virtual Network. Each container is uniquely deployed for each customer and job, then deleted after analysis completes, preventing container reuse.

Who at Rencore has access to customer data?

Only the Product Operations team has access to the Rencore Governance Azure subscription. However, the System Access Control Policy governs all access to customer data and encryption keys, restricting it unless specifically authorized.