✔️ If your organization utilizes standalone, unmanaged (self-managed) endpoints, the native ARM64 installer package functions perfectly. 📋 System Requirements for ARM64 Compliance
For standalone workstations or isolated test setups that cannot connect to the cloud, use the unmanaged workflow.
ARM64 support for Linux agents (e.g., Amazon Linux 2023) is planned for the SEP 16 release cycle in 2026 . Feature Limitations on ARM64
: 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:
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. symantec endpoint protection arm64 work
Are you looking to deploy this to devices or as part of a larger enterprise fleet?
Before diving into Symantec’s specific support, we must understand why "Does it work?" is a complex question.
Network Threat Protection (Firewall and Intrusion Prevention) Unsupported Features on ARM64 and Custom Application Behavior Threat Defense for Active Directory (TDAD) Web and Cloud Access Protection Exploit Protection
For organizations using Symantec Data Loss Prevention (DLP), there is good news: introduced native support for ARM64 processors on Windows 11 endpoints. The DLP Agent can now be installed on Windows 11 systems running on ARM64 architecture, complementing the SEP client’s capabilities. Feature Limitations on ARM64 : Granular control over
If your ARM64 environment is Linux-based (common in data centers running AWS Graviton or Oracle Ampere A1 instances), the news is excellent.
SEP’s kernel-mode drivers (e.g., sysfer.sys , eeCtrl64.sys ) are x64 binaries and fail to load on ARM64 systems unless explicitly signed for ARM64. Broadcom does not provide ARM64 driver signatures for most versions.
Move the generated executable file directly onto the local ARM64 machine. Right-click the installer and select .
For a road warrior with a Surface Pro X, SEP is usable but sluggish. For a virtual desktop (VDI) on Azure ARM64, you should stress-test heavily. Before diving into Symantec’s specific support, we must
Let’s address the elephant in the room. "Working" and "Working well" are different. Here is what real-world testing reveals about SEP on ARM64:
Enterprise environments are rapidly transitioning toward energy-efficient hardware like Qualcomm Snapdragon processors, making ARM64 compatibility a critical requirement for corporate IT infrastructure. Broadcom has structured its endpoint security portfolio to address this shift, though deployment paths differ significantly from traditional x86/x64 systems. Core Compatibility Matrix Component / Platform Supported Architecture Management Method Required Windows 11 ARM64 (Snapdragon) Cloud-managed (ICDm / SES) Symantec Endpoint Protection 14.3 (RU7+) Windows 11 ARM64 Cloud-managed or Unmanaged only On-Premises SEPM Server x64 Only (No ARM endpoint management) Cannot manage ARM64 clients Symantec DLP Endpoint Agent Apple Silicon (M1/M2/M3) No support for Windows ARM64 How Deployment Works on ARM64
Use the sysinfo command on your ARM64 device and cross-reference the build number with Broadcom’s official "SEP Client Compatibility Matrix" (updated quarterly). Do not assume later builds automatically support ARM64—always check the release notes for the phrase "Windows 11 ARM64."
Does Symantec Endpoint Protection ARM64 Work? Compatibility, Deployment, and Exclusions