Aug 18, 2021 — ETP updates

• New Risky Threat Categories. ​Akamai​ has added risky categories to the threat settings of a policy. These risky categories include Adware, Coin Mining, Newly Seen Domains, Newly Registered Domains, Potentially Harmful Domains, and DNS Tunneling services. Before this update, risky domains were tracked in a policy setting where administrators could select an action that would send all risky domains to the proxy for scanning. With these new risky categories, you can select an action for each category.

• Option to remove a risk level from a policy. When configuring application visibility and control (AVC) and an acceptable use policy (AUP), an administrator can now remove a risk level from the policy configuration.

• File hash exception lists. File hash lists are now called file hash exception lists.

• Bug fixes and UI enhancements. This release includes updates to the user interface and bug fixes.

Important: The ​SIA​ legacy user interface will reach its end of life in December 2021. Please use the new Enterprise Center user interface to complete all your ​SIA​ operations.

These features are in beta:

• Sub-locations. You can now configure sub-locations for ​SIA​ locations. A sub-location can represent different virtual local area networks (VLANs) that are routed to the Internet with the same IP address as the parent location. This feature allows you to apply different policies to your sub-locations and in turn, define more granular access.

• Local breakout for bypass domains. The Local Breakout for Bypass Domains setting is enabled by default in a policy to ensure that domains configured in ​SIA​ for bypass are directed to the origin from the branch or enterprise network. Disable this option if your network does not have a direct route Internet and cannot access these origins.

• Changes to ​SIA​ policy logic include:

  • Prioritization of custom exception and block lists. If the domain, IP address, or URL found in a custom block or exception list is also found in Akamai Security lists, the Microsoft 365 list, or in an AUP and AVC configuration, the policy action associated with the custom exception or block list takes priority.

  • Updated handling of policy conflicts. In addition to prioritizing the policy action of a custom exception or block list, these also applies:

    • If the same domain with different suffix lengths is specified in multiple custom lists (for example, in multiple block or exception lists) or in multiple ​SIA​ lists (for example, in multiple acceptable use policies), ​SIA​ enforces the policy action assigned to the longest address.

    • If the same domain, IP address, or URL is configured in multiple custom lists or in multiple ​SIA​ lists with conflicting policy actions, ​SIA​ selects the action based on this priority:

      1. Bypass
      2. Block
      3. Monitor
      4. Classify
      5. Allow

  To try any of these beta features, contact your Akamai representative.