Guardicore Platform Agent​ 7.3.0-v53.0 is now in limited availability. If you are eligible for this upgrade, you can go to ​Akamai​ Control Center > Enterprise Center > Client & Connectors > ​Manage and Download Clients to deploy version 7.3.0. Otherwise, contact your ​Akamai​ account representative to try this update.

To learn more about the​ ​Guardicore Platform Agent​ rollout process, refer to the rollout documentation.

New features and improvements

• Guardicore Segmentation. Guardicore Platform Agent 7.3.0 supports Guardicore Segmentation v53.0.
• SIA Threat Protection. Guardicore Platform Agent now supports the following SIA features and enhancements:
  • WireShark is no longer required to capture packets in Guardicore Platform Agent.
  • The Threat Protection executables and dependencies are now moved to the Guardicore Platform Agent installation directory.
  • If you don’t want Threat Protection to use the localhost, contact your ​Akamai​ representative to use a different IP address. By default, Threat Protection uses the localhost when it acts as a DNS proxy.
• Enterprise Application Access. Guardicore Platform Agent now supports the following EAA features and enhancements:
  • Access now supports http proxies.
  • The Access executables and dependencies are now moved to the Guardicore Platform Agent installation directory.
  • (Beta) Edge Transport is now supported on Ubuntu. Contact ​Akamai​ support to enable this feature.
• General agent changes. In addition to the above changes, note the following:
  • Access and Threat Protection statuses reported in the client inventory in Enterprise Center are now updated to more clearly and accurately communicate each component's state.
  • You can now selectively install Access, Threat Protection, and Segmentation using command line install parameters. When you specify at least one component selection parameter, the installer doesn't install components that aren't specified. If you don’t specify any components, the agent is enabled with Access (Cloud Zone and Edge Transport) and Threat Protection.
    • Component selection is available only for new installations.
    • When upgrading the agent, only existing components are updated.
  • Active Directory username formats are now supported:
    • User principal name (UPN): username@example.com
    • Down-level logon name: DOMAIN\username

Known issues

• You may encounter issues when running SentinelOne together with Guardicore Platform Agent on macOS.

• On macOS, after disconnecting or stopping the FortiClient VPN, Edge Transport in Guardicore Platform Agent doesn’t reconnect automatically. The workaround is to turn Access off and on again in the agent.

• When upgrading Guardicore Platform Agent on macOS, the recommended approach is to deploy and run the installer package, which automatically performs the upgrade from an existing 7.x installation. As a secondary option (not recommended for general use), some MDM workflows may choose to run the provided uninstall.sh script prior to installation in specific scenarios. If your MDM uses the uninstall.sh script, it must be executed with elevated privileges:

  Shell

  sudo /Library/Application\ Support/Guardicore\ Platform\ Agent/macos/scripts/uninstall.sh
  

  Otherwise, the uninstall may fail because it’s not run with sufficient permissions.
  After the uninstall completes, deploy and install a new Guardicore Platform Agent version using your MDM solution.

Limitations

• Threat Protection and Guardicore Segmentation aren’t supported on Ubuntu.

• When upgrading the agent from version 7.2.x to 7.3.0 on Ubuntu, the Edge Transport component isn’t installed. To enable Edge Transport on Ubuntu, you need to uninstall the agent first and then install version 7.3.0.

• After upgrading to Chrome 142 or later, when attempting to authenticate or establish device posture, users may see a one-time permission prompt in Chrome asking whether to allow the IdP page to "Look for and connect to any device on your local network". Users must click Allow to allow Access to continue. Otherwise, Access may fail to authenticate or establish device posture. Note that if a user clicks Block, they will have to navigate to site permissions in Chrome and allow Local network access for the IdP URL to unblock Access.

  • To suppress the prompt on end user devices and grant Local Network Access (LNA) permissions for your IdP URL, you can pre-configure managed devices:

    • Google Workspace administrators may set a LocalNetworkAccessAllowedForUrls Chrome policy for the IdP URL using the Custom Configurations page in Google Workspace.

    • For Windows devices, MDM administrators may create a configuration profile with an OMA-URI property for the./Device/Vendor/MSFT/Registry/HKLM/SOFTWARE/Policies/Google/Chrome/LocalNetworkAccessAllowedForUrls URI and add the IdP URL to the allowlist. To learn more about setting up Chrome policies on Windows, refer to Chrome Enterprise documentation.

    • For macOS devices, MDM administrators may use Profile Manager to create and deploy a configuration profile with a payload that gives your IdP URL LNA permissions. Add these keys and values to your com.google.Chrome.plist file and convert it to a configuration profile using your preferred conversion tool:

      XML

      <key>LocalNetworkAccessAllowedForUrls</key>
      <array>
          <string>youridp.com</string>
      </array>
      <key>LocalNetworkAccessRestrictionsEnabled</key>
      <true/>
      

      To learn more about setting up Chrome policies on macOS, refer to Chrome Enterprise documentation.

Fixed issues

• Guardicore Platform Agent
  • Resolved issues with the Guardicore Platform Agent service restarting when a remote user was logged in to the workstation.
  • Fixed an issue that triggered OTA update notifications despite no OTA update being available for download.
  • Fixed an issue preventing the browser from launching for IDP authentication following agent or system restarts.
  • Improved agent’s responsiveness and performance.
• Threat Protection in explicit mode
  • Fixed an issue where adding or removing a network interface (for example, a VPN connection) temporarily disabled protection. Threat Protection now remains enabled during network interface changes.

Supported macOS versions

Guardicore Platform Agent 7.3.0 supports the following macOS versions:

• macOS 14 (Sonoma)
• macOS 15 (Sequoia)
• macOS 26 (Tahoe)

Required free disk space: ~200MB
Supported CPUs:

• Intel: x86_64
• Apple: M1, M2, M3, M4

Supported Windows versions

​Guardicore Platform Agent 7.3.0 supports the following Windows versions:

• Windows 10 Home/Enterprise/Pro 64-bit
  • 1803 or later
• Windows 11 Home/Enterprise/Pro
  • 21H2
  • 22H2
  • 23H2
  • 24H2
  • 25H2

Required free disk space: ~200MB
Supported CPUs:

• x86_64
• ARM64

Supported Linux versions

​Guardicore Platform Agent 7.3.0 supports the following Ubuntu versions running GNOME desktop environment:

• 22.04
• 24.04

Required free disk space: ~200MB
Supported CPUs:

• x86_64