Enterprise Center now offers a new navigation that organizes features and settings by enterprise product. ​SIA​ administrators can now access all configuration settings and reports from the Threat Protection area of the navigation menu. If your organization is also licensed for the Enterprise Application Access (EAA) or Multi-Factor Authentication (MFA) products, you can access EAA features from the Application Access area of the menu and MFA features from the Multi-Factor Authentication navigation area.

With multi-tenancy, a Managed Security Service Provider (MSSP) can give their customers separate access to ​SIA​ without purchasing separate product licenses. You can create a tenant for each customer and assign administrators to each tenant. A tenant administrator can create and manage ​SIA​ components within their tenant, such as policies, lists, locations, certificates, ​ETP Client​s, and more.

The mobile client is now in limited availability and supports bring your own device (BYOD). With BYOD, end users can activate ​ETP Client​ on their personal devices without using the enterprise-wide entitlement code.

A new version of the desktop client is now available. This update includes bug fixes and Walled Garden, which is a new feature in limited availability.

• 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.

• Deploy individual lists. If a list is ready for deployment, an administrator can now select the specific lists they are allowed to manage and would like to deploy. Before this update, a deploy operation would publish all lists that the administrator was permitted to manage.

• New filters and dimensions added to DNS Summary and Proxy Summary reports. New filter criteria and dimensions for access control are now available in the DNS Summary and Proxy Summary activity reports.

• Scheduled Reports Enhancements. You can now schedule reports for access control events, as well as threat events. Additionally, you can schedule a report for DNS Summary or Proxy Summary activity data. The DNS Summary and Proxy Summary scheduled reports show the top activity based on ​SIA​ reporting dimensions such as location, domain, geographical region, and more.

• Updated firewall hostname for DoT. The Security Connector DNS Forwarder and ​ETP Client​ now use the *.akaetp.net hostname for DNS-over-TLS (DoT) connections. Make sure you update your firewall, on-premise proxy, and allowlists to use this hostname with outbound TCP port 443 or 853. Note: For ​ETP Client​, the port you must allow depends on the port that’s configured in the policy. In a policy, you can select port 443 or 853 for DoT. For DNS Forwarder, the port you must allow depends on the port configured in Security Connector for a DNS Forwarder configuration.

A new version of the desktop client is now available.

As of June 1, 2021, these features are available:

A new version of the ​ETP Client​ is now available. This release provides a number of bug fixes, including:

Policy Deprecations. Based on updates to external threat feeds, ​SIA​ now alerts you to needed deprecations of policy actions that are defined for applications, categories, and operations. When you display the policy in the UI, a window indicates the needed deprecations. You can then confirm the deprecations and deploy the policy update.