Symantec Endpoint Protection Arm64 Work Jun 2026

When deploying SEP to an Apple Silicon device (M1/M2/M3), you are installing a .

Support for ARM64 is available starting with . However, there are specific management constraints: symantec endpoint protection arm64 work

| Component | ARM64 Native? | Emulation (x86) Required? | Status | |-----------|--------------|---------------------------|--------| | | No | Yes | Runs via Windows Prism/ARM64 emulation | | LiveUpdate | No | Yes | Works; slower signature download/unpack | | Real-time Scanning | No | Yes | Functional; high CPU overhead | | Firewall (NDIS Filter) | Partial | No | ARM64 NDIS driver available only in SEP 14.3 RU9+ | | Trojans/Spyware scanning | No | Yes | Works | | Insight (SONAR) | No | Yes | Behavioral analysis impacted by emulation latency | When deploying SEP to an Apple Silicon device

Symantec Endpoint Protection (SEP) and the newer Symantec Endpoint Security (SES) do work on ARM64 processors | Emulation (x86) Required

As of the latest release cycles (SEP 14.3 RU9 and later), the core antivirus and firewall components do not have a native Arm64 build. Broadcom continues to ship a 64-bit Intel (x64) package.

Historically, SEP relied heavily on . These are pieces of code that load directly into the operating system kernel. This gave SEP "God mode"—it could intercept any file operation, network packet, or process execution with zero latency.

, but with specific management limitations and feature gaps. Broadcom support portal ARM64 Support & Performance