About CookiePro Hosting Options, Locations, and Backup
Your CookiePro account can be hosted with cloud hosting provided by CookiePro.
CookiePro cloud hosting is provided by Microsoft Azure located in Europe. Microsoft's cloud infrastructure has the following certifications and attestations: ISO/IEC 27001:2013, ISO 27017/27018, SSAE 16/ISAE 3402 SOC 1 Type 1 and Type 2, AT Section 101 SOC 2 and 3 Type 1 and Type 2, and FedRAMP certification and accreditation.
The CookiePro service is provided by OneTrust. OneTrust LLC’s Information Security Management System (ISMS) is ISO/IEC 27001:2013 certified as reflected in the certificate found here.
OneTrust LLC’s Privacy Information Management System (PIMS) is ISO/IEC 27701:2019 certified as reflected in the certificate found here. The PIMS is comprised of components, network devices, and software that are operated by OneTrust employees within its defined system physically operating within the Microsoft Azure production accounts used to make OneTrust Privacy, Security, and Third-Party Risk software available to customers.
OneTrust has completed a Type 2 SOC for Service Organizations (SOC 2 Type 2) examination as of February 27, 2020.
|
Hosting Option |
Cloud |
|---|---|
|
Tenancy |
Multi-tenant cloud environment with dedicated tenant databases. |
|
Geolocation |
Located in Germany. |
|
Update Schedule |
Upgrades approximately every 3-5 weeks. |
|
License |
Included with all license types. |
|
Support |
No support plan required. |
|
Hosting Costs |
Hosting included in license. |
CookiePro Hosting Locations & IP Addresses
CookiePro cloud hosting is provided through Microsoft Azure in the following locations.
The following table details the data center hosting locations and Admin Portal IP addresses for the CookiePro application environment. These IP addresses can be used to safelist communication from OneTrust in your network.
The table includes IP addresses that use Classless Inter-Domain Routing (CIDR) notation, such as 20.54.106.120/29. In CIDR notation, IP addresses are written as a prefix (20.54.106.120), followed by a suffix that indicates how many bits are in the entire address (29).
For example, when 20.54.106.120/29 is mentioned, the IP addresses 20.54.106.120, 20.54.106.121, 20.54.106.122, 20.54.106.123, 20.54.106.124, 20.54.106.125, 20.54.106.126, and 20.54.106.127 should be safelisted. In another example, when 13.86.126.174/32 is mentioned, only the IP address 13.86.126.174 should be safelisted as 32 refers to a single IP address. You can use this subnet calculator to enter the CIDR IP address for additional details on the IP range.
The CookiePro application provides multiple options to deliver email notifications, as detailed here. Based on your selected email server configuration, email notifications will be delivered in one of the following ways:
-
For Custom SMTP Relay or Microsoft Exchange Online: Emails are sent from the CookiePro application to the customer's SMTP server or Microsoft Exchange server from the IPs listed in the table below. The customer's SMTP server or Microsoft Exchange server then delivers the email to the recipient (e.g. data subject, vendor, etc.).
-
For Default Configuration or Send on Behalf of my Domain: Emails are delivered directly to the email recipient (e.g. data subject, vendor, etc.) via the OneTrust cloud email platform.
The automated security of the OneTrust cloud email platform ensures that customers do not manage the DomainKeys Identified Mail (DKIM) and Sender Policy Framework (SPF). The IP addresses used for email delivery are not published for this purpose, which therefore eliminates the need to rotate DKIM keys or update SPF for IP changes. If you require IP safelisting for email delivery within your internal teams, OneTrust recommends using the Custom SMTP Relay or Microsoft Exchange Online configuration.
Traffic originating from OneTrust to the customer network, such as for an integration endpoint (if applicable), SMTP server endpoint (if applicable), etc., will use the following OneTrust egress IPs. If your network team safelists OneTrust egress IPs, you are encouraged to review and update your firewall.
|
CookiePro Application Environment |
Data Center Hosting Location |
Primary Hosting Location |
Disaster Recovery Hosting Location |
Admin Portal IP Addresses |
|---|---|---|---|---|
|
Germany |
Frankfurt |
Berlin |
|
CookiePro Web Scanner Locations & IP Addresses
The following table details the Web Scanner IP addresses for the CookiePro application environment. These IP addresses can be used to safelist communication from OneTrust in your network. The Web Scanner IP addresses for all OneTrust environments are also available as an IP text list here.
The table includes IP addresses that use CIDR notation, such as 20.54.106.120/29. You can use this subnet calculator to enter the CIDR IP address for additional details on the IP range.
Traffic originating from OneTrust to the customer website when a cookie scan is initiated will use the following OneTrust egress IPs. If your network team safelists OneTrust egress IPs, you are encouraged to review and update your firewall.
|
CookiePro Application Environment |
Data Center Hosting Location |
Primary Hosting Location |
Disaster Recovery Hosting Location |
Web Scanner IP Address |
|---|---|---|---|---|
|
North Europe |
Ireland |
Netherlands |
|
|
|
Central US |
Iowa |
Virginia |
|
CookiePro Backups of Hosted Accounts
Backups for cloud-hosted implementations are managed, performed, and tested by Microsoft Azure. Azure provides a 14-day backup to prevent against accidental data deletion and uses transactional log backup for Azure SQL, as detailed in Microsoft's Automated backups in Azure SQL Database article. The entire database is backed up, with the ability to create a database from backup at any point in time with up-to-the-second level of granularity within the last 14 days. For details on the frequency of backup, see Azure SQL Database Backup Frequency. Backups are stored encrypted with Azure Transparent Data Encryption AES-256. For Disaster Recovery requirements, all backups are replicated by Azure from the Primary Hosting Location to the respective paired Disaster Recovery Hosting Location.