[Network Threat Protection] ──> [Proactive Threat Scan] ──> [Informed Insight Engine] (Firewall & IPS Layer) (Behavioral & Zero-Day) (Reputation & Submissions)
SEP incorporates behavioral analysis to detect and block suspicious activities that may indicate a new or unknown threat.
(Article ID: 280167) - Exceptions defined with the [Program_Files] prefix variable may not work correctly when files are located in Program Files (x86) directory. Workaround: Use absolute paths instead of the predefined prefix variable. Symantec Endpoint Protection 14.3.11213.9000 Te...
Historically, enabling the policy automatically forced Symantec’s proprietary browser extensions onto Google Chrome and Microsoft Edge. However, this deployment model frequently caused conflicts with third-party endpoint management platforms. What's new for Symantec Endpoint Protection 14.3 RU9?
Organizations running RU9 should ensure they have upgraded to at least to fully address these vulnerabilities. Organizations running RU9 should ensure they have upgraded
| Component | Issue Fixed | |-----------|--------------| | SEPM | Invalid URL error when adding a domain with an * as a Trusted Web Domain | | SEPM | Client Version sorting does not correctly sort 14.3.10148.8000 | | SEPM | HTTP 401 Unauthorized errors observed intermittently in Server Activity log | | SEPM | Log files not being periodically removed during DiskFileCleanup tasks | | Windows Client | Improper handling of lower-case characters in hash exception policy | | Windows Client | Bugcheck (DPC_WATCHDOG_VIOLATION) on Teefer.sys | | Windows Client | Network slowdown due to large amount of firewall blocks in short period |
For organizations using a hybrid management model—where an on‑premises SEP Manager synchronizes with the Symantec Endpoint Security cloud—large‑scale synchronizations could occasionally fail or under‑report client counts. RU9 introduced the ASSET_SYNC_RESET command, allowing administrators to resynchronize group hierarchies for up to 5,000 clients. After running the command, you can verify success via Monitor > Logs > System Log type > Server Activity content type . After running the command
The RU9 release introduces several significant enhancements across the management console and client agents:
After upgrading SEPM, older clients (pre-14.x) will still report but cannot receive new memory exploit policies. Upgrade clients within 90 days.