If you are using the traditional Symantec Endpoint Protection Manager (SEPM) rather than the cloud console, you can still deploy clients to Arm devices. You would do this through the Client Deployment Wizard. The SEPM console is where you can also check the compatibility of features like Host Integrity.
If you are currently managing a mixed environment (ARM and x86), I can provide:
Native ARM64 agents ensure that the protection agent does not crash, a common issue with non-native security tools on Windows on ARM. 5. Potential Challenges symantec endpoint protection arm64 work
Broadcom provides ARM64/aarch64 installers for specific Linux distributions, managed through the (SEP Linux Packager) tool.
For standalone workstations or isolated test setups that cannot connect to the cloud, use the unmanaged workflow. If you are using the traditional Symantec Endpoint
While the journey has involved gradual feature rollouts across different SEP versions (14.3 RU2 for M1, RU5 for M2, and RU8 for M3, for example), the current state of support is mature and enterprise-ready. The key to success lies in using the right version of the SEP client for your specific operating system, leveraging tools like the SES cloud console for Windows deployments and the seplpkg tool for Linux.
Symantec Endpoint Protection (SEP) provides native support for ARM64 architectures across Windows, macOS, and Linux, primarily starting with version . However, management and feature availability vary significantly by platform. Windows on ARM Support If you are currently managing a mixed environment
Symantec Endpoint Protection (SEP) provides native support for ARM64 architecture on both Windows and macOS, though there are specific management and feature limitations to note as of early 2026. Windows on ARM64 Support
Based on the latest updates from Broadcom's support center , the 2026-era SEP agents are optimized for high-efficiency cores, mitigating previous issues with resource consumption.