HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Security and privacy are built into the Azure platform, and any feature that Optimizely develops must meet the highest quality standards. This is ensured by various coding guidelines that have to be met before the code is considered for inclusion in the platform.

Guidelines include performance considerations, security concerns, and globalization and localization aspects. Optimizely bases much of its platform-related security efforts on the [Open Web Application Security Project (OWASP)](🔗).

The Optimizely platform is tested against:

  • Injection

  • Cross-site scripting (XSS)

  • Broken authentication and session management

  • Insecure direct object references

  • Cross-site request forgery (CSRF)

  • Security misconfiguration

  • Insecure cryptographic storage

  • Failure to restrict URL access

  • Insufficient transport layer protection

  • Unvalidated redirects and forwards

See [Security in the Optimizely Content Management System (CMS) Developer Guide](🔗).

The following information describes specific security aspects related to DXP.

## DDoS protection

_DDoS (Distributed Denial of Service)_ attacks are common and complex, and traditional on-premises solutions cannot handle these. Optimizely DXP offers advanced protection at the network edge through its CDN provider including UDP and ICMP protocols, DNS amplification, Layer 7 and 3/4, SYN/ACK, and SMURF (see information on the Internet for this terminology).

Microsoft Azure also protects against attacks generated from outside and inside the platform.

## Web Application Firewall

_Web Application Firewall (WAF)_ sits in front of web applications to filter out malicious traffic at the application layer (Layer 7 of the Open Systems Interconnection (OSI) Model, including HTTPS and HTTP traffic). A WAF stops attacks at the network edge, protecting your website from common web threats and specialized attacks before they reach your servers.

WAF is included as part of the Optimizely DXP, see [Web Application Firewall](🔗) for details.

## SSL (Secure Sockets Layer)

SSL is commonly used for encrypted integration and communication with other services through REST and web service APIs. All domains in DXP are protected by SSL by default. SSL termination is at the CDN for the editorial/administrative views and the public website. Optimizely Customized Commerce packages also include SSL termination at the CDN for _Commerce Manager_.

## VPN (Virtual Private Network)

VPN can allow a secure connection to an internal corporate resource. Note that communication is _one-way_ to the on-premises system.

## Application environment

Azure Web Apps do not use the traditional version of Microsoft Windows, but rather a purpose-built version with a smaller attack surface and reduced vulnerability. Each customer solution uses isolated resources, with independent databases and Web Apps.

## Anti-malware

Optimizely DXP relies on [Microsoft's standard approach for Azure anti-malware](🔗) to provide real-time protection and content scanning.

## Service window and patching

DXP uses Azure Web Apps to run Optimizely applications and thus aligns with the Microsoft patch release cycle. Microsoft is responsible for patch management. Optimizely works closely with Microsoft for any edge cases involving patching.

## Product updates and upgrades

Optimizely has a [continuous release cycle](🔗) with new [releases on a weekly basis](🔗). Releases include both new features and fixes, and you can upgrade your solution at a cadence that makes sense for your business.


You are responsible for installing appropriate software updates to the Optimizely platform in your solution.

## Compliance

Optimizely DXP leverages the Microsoft Azure platform, therefore the underling infrastructure follows [Microsoft Azure compliance standards](🔗), certifications, and supporting processes.

## Penetration testing

[Microsoft and their Red Team](🔗) regularly provide a penetration test to the underlying infrastructure of DXP. The Optimizely platform is also subject to regular penetration tests conducted by customers and partners.

However, any implementation on top of the Optimizely platform could unexpectedly introduce a security hole. Therefore, you need to ensure that your solution is thoroughly tested before going live.

You can either conduct your own tests using tools or security services of your choice, or you can order this service through [Optimizely Expert Services](🔗).

If you plan to perform your own penetration tests, you need to notify Optimizely at least **10 business days** before the planned testing.

To notify Optimizely about your test, [submit a ticket to Optimizely](🔗) with your test plan including:

  • Test type and approach

  • Contact information for emergency issues

  • Expected start and end times

  • Listing of IP addresses and DNS names from where the tests will originate

## Outbound IP addresses

While the outbound IP addresses of a DXP environment can stay static for extended periods of time, there is no guarantee that they will. They can change at any time, and Optimizely has no way of monitoring this or proactively informing customers of a potential change.

Therefore, Optimizely strongly discourages using the outbound IP addresses for security purposes since important site functionality may break at any time when the outbound IP addresses change.

Instead, you should use other methods of securing the traffic, like certificate/key-based authentication or a VPN.

## Related topics

  • [Web Application Firewall](🔗)

  • [Optimizely Trust Center](🔗)