The Dispatcher Security Checklist

Adobe strongly recommends that you complete the following checklist before going on production.

Use the Latest Version of Dispatcher

You should install the latest available version that is available for your platform. You should upgrade your Dispatcher instance to use the latest version to take advantage of product and security enhancements. See Installing Dispatcher.

Restrict Clients that Can Flush Your Cache

Adobe recommends that you limit the clients that can flush your cache.

Enable HTTPS for transport layer security

Adobe recommends to enable HTTPS transport layer on both author and publish instances.

Restrict Access

When configuring the Dispatcher you should restrict external access as much as possible. See Example /filter Section in the Dispatcher documentation.

Make Sure Access to Administrative URLs is Denied

Make sure you use filters to block external access to any administrative URLs, such as the Web Console.

See Testing Dispatcher Security for a list of URLs that need to be blocked.

Use Allowlists Instead Of Blocklists

Allowlists are a better way of providing access control since inherently, they assume that all access requests should be denied unless they are explicitly part of the allowlist. This model provides more restrictive control over new requests that might not have been reviewed yet or taken into consideration during a certain configuration stage.

Run Dispatcher with a Dedicated System User

When configuring the Dispatcher you should ensure that the web server is ran by a dedicated user with least privileges. It is recommended to only grant write access to the dispatcher cache folder.

Additionally, IIS users need to configure their website as follows:

1. In the physical path setting for your web site, select Connect as specific user.
2. Set the user.

Prevent Denial of Service (DoS) Attacks

A denial of service (DoS) attack is an attempt to make a computer resource unavailable to its intended users.

At the dispatcher level, there are two methods of configuring to prevent DoS attacks:

• Use the mod_rewrite module (for example, Apache 2.4) to perform URL validations (if the URL pattern rules are not too complex).

• Prevent the dispatcher from caching URLs with spurious extensions by using filters.
  For example, change the caching rules to limit caching to the expected mime types, such as:

  • .html
  • .jpg
  • .gif
  • .swf
  • .js
  • .doc
  • .pdf
  • .ppt

  An example configuration file can be seen for restricting external access, this includes restrictions for mime types.

To safely enable full functionality on the publish instances, configure filters to prevent access to the following nodes:

• /etc/
• /libs/

Then, configure filters to allow access to the following node paths:

• /etc/designs/*

• /etc/clientlibs/*

• /etc/segmentation.segment.js

• /libs/cq/personalization/components/clickstreamcloud/content/config.json

• /libs/wcm/stats/tracker.js

• /libs/cq/personalization/* (JS, CSS and JSON)

• /libs/cq/security/userinfo.json (CQ user information)

• /libs/granite/security/currentuser.json (data must not be cached)

• /libs/cq/i18n/* (Internalization)

Configure Dispatcher to prevent CSRF Attacks

AEM provides a framework aimed at preventing Cross-Site Request Forgery attacks. In order to properly make use of this framework, you need to allowlist CSRF token support in the dispatcher. You can do this by:

1. Creating a filter to allow the /libs/granite/csrf/token.json path;
2. Add the CSRF-Token header to the clientheaders section of the Dispatcher configuration.

Prevent Clickjacking

To prevent clickjacking we recommend that you configure your webserver to provide the X-FRAME-OPTIONS HTTP header set to SAMEORIGIN.

For more information on clickjacking please see the OWASP site.

Perform a Penetration Test

Adobe strongly recommends to perform a penetration test of your AEM infrastructure before going on production.