Aug 23, 2021 — Client 3.5.0 launch
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.
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.
Jul 7, 2021 — ETP updates
-
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.
Jun 21, 2021 — Desktop client 3.4.0 launch
A new version of the desktop client is now available.
May 28, 2021 — ETP updates
As of June 1, 2021, these features are available:
Apr 30, 2021 — Client version 3.3.2 launch
A new version of the ETP Client is now available. This release provides a number of bug fixes, including:
Apr 8, 2021 — ETP updates
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.
Jan 21, 2021 — ETP updates
Bulks Actions in Enterprise Center. The Enterprise Center user interface for SIA now allows you to complete some operations in bulk. These operations include:
Nov 18, 2020 — Secure DNS Forwarder availability
Secure DNS Forwarder is now generally available with Security Connector 2.7.0
Nov 17, 2020 — Application visibility and control (AVC) beta release
If your organization is participating in the AVC beta, you can now control access to web applications. You can define default policy behavior, or you can create a policy that is based on risk level, acceptable use policy (AUP) categories, category operations, applications, or specific operations for an application. You assign actions to each area of the AVC policy. As you configure each component, the detailed settings you set take precedence over more general settings. For example, the policy action you apply to an application takes precedence over an action that’s applied to its corresponding category or category operation.