Symantec Endpoint Protection Arm64 Work Jun 2026

The core rule of Symantec ARM64 operation is that Enterprise administrators must manage ARM64 endpoints as unmanaged local installations or register them via Broadcom's Integrated Cyber Defense Manager (ICDm) cloud console.

Before designing your rollout, verify that your client environment fulfills these foundational software baselines specified by Broadcom TechDocs: Requirement Category Supported Specification

For standalone workstations or isolated test setups that cannot connect to the cloud, use the unmanaged workflow. symantec endpoint protection arm64 work

: Granular control over which apps can run is not yet supported for ARM64 clients. System Requirements for Success To get SEP running on an ARM64 device, ensure you have:

: Endpoint-level AD mitigation modules do not initialize. The core rule of Symantec ARM64 operation is

Native applications utilize the ARM CPU directly, leading to faster file scanning, lower CPU usage, and improved system responsiveness. Emulated security software can cause a 10%–20% performance drag.

Symantec supports native ARM64 protection on (including 21H2, 22H2, 23H2, and 24H2). The Management Divide System Requirements for Success To get SEP running

Securing ARM64 hardware involves aligning the underlying Operating System (OS) with the specific management console. Traditional x86/x64 deployment structures do not translate directly to ARM64 architecture. Windows 11 ARM64 Implementation

: Systems running 14.3 RU8 or higher must have Microsoft Trusted Signing (formerly Azure Code Signing) enabled, which is standard on modern Windows 11 ARM64 builds. Supported vs. Unsupported Features on ARM64

Symantec Endpoint Protection (SEP) and Symantec Endpoint Security (SES) have evolved to support the ARM64 architecture

: For Windows, ARM packages are available within the "Full_Installation" download of SEP. For cloud users, you must specifically select the Windows ARM architecture when downloading the agent package from the console.