DocumentationAEMDispatcher Guide

The Dispatcher Security Checklist the-dispatcher-security-checklist

Last update: Fri Apr 26 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin

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

CAUTION
Complete the Security Checklist of your version of AEM before going live. See the corresponding Adobe Experience Manager documentation.

Use the Latest Version of Dispatcher use-the-latest-version-of-dispatcher

Install the latest version that is available for your platform. Be sure you upgrade your Dispatcher instance so that you use the latest version to take advantage of product and security enhancements. See Installing Dispatcher.

NOTE
Check the current version of your Dispatcher installation by looking at the Dispatcher log file.
[Thu Apr 30 17:30:49 2015] [I] [23171(140735307338496)] Dispatcher initialized (build 4.1.9)
To find the log file, inspect the Dispatcher configuration in your httpd.conf.

Restrict Clients that Can Flush Your Cache 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 enable-https-for-transport-layer-security

Adobe recommends enabling HTTPS transport layer on both the author and publish instance.

Restrict Access restrict-access

When configuring the Dispatcher, 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-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 must be blocked.

Use Allowlists Instead Of Blocklists 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 considered during a certain configuration stage.

Run Dispatcher with a Dedicated System User 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.

Also, IIS users must 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 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 configure-dispatcher-to-prevent-csrf-attacks

AEM provides a framework aimed at preventing Cross-Site Request Forgery attacks. To properly use this framework, you must allowlist CSRF token support in the Dispatcher.

You can accomplish this by doing the following:

  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 prevent-clickjacking

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

For more information on clickjacking, see the OWASP site.

Perform a Penetration Test perform-a-penetration-test

Adobe recommends performing a penetration test of your AEM infrastructure before going on production.

recommendation-more-help
ce382601-480f-4a99-8be7-73178d4b6ef5