To ensure a seamless rollout of Symantec Endpoint Protection across your ARM64 fleet, follow these deployment guidelines:
The Windows agent requires a 64-bit environment. is fully supported. Broadcom has dropped support for all 32-bit legacy operating systems, meaning older Windows 10 ARM installations must be upgraded before deployment. 3. Native Security Requirements
Leverages global threat data to identify new risks. Best Practices for Deploying SEP on ARM64 symantec endpoint protection arm64 hot
Memory mitigation techniques differ significantly between x86 and ARM64. Architecture Restrictions and Management Requirements
Review the precise integration steps for deploying Symantec packages via third-party unified endpoint management platforms like . To ensure a seamless rollout of Symantec Endpoint
Emulated agents often fail to monitor native ARM64 processes accurately, allowing sophisticated malware to bypass kernel-level detection.
: Schedule full system scans to run when devices are plugged into AC power, keeping the processor in a low-frequency state when running on battery. Threat Defense for AD
The unsupported features list (Custom Application Behavior, Threat Defense for AD, Web and Cloud Access Protection, Exploit Protection, etc.) may impact security postures that rely on these capabilities.
As ARM64-based Windows devices (e.g., Microsoft Surface Pro X, Lenovo ThinkPad X13s, newer Snapdragon X Elite laptops) enter enterprise environments, legacy x86 security agents face performance and compatibility challenges. Symantec Endpoint Protection (SEP) originally ran under emulation (CHPE or x64 emulation) on these devices, causing high CPU usage, scan delays, and potential instability.
By following these best practices and leveraging Symantec Endpoint Protection on ARM64, organizations can enhance their endpoint security and protect their devices from various types of threats.
Symantec Endpoint Protection for ARM64 offers several key features and benefits, including: