老铁最后的遗产，Symantec Endpoint Protection 14.3 RU9出来了

驭龙

https://techdocs.broadcom.com/us ... ction-14-3-RU9.html

可惜的是Windows客户端的部分只是添加BIP，浏览器入侵保护插件支持edge浏览器，以及客户端更新的URL服务地址，还有一些其他改进，但其他安全功能好像并没有更新，比较遗憾啊。

我几年前就不更新SEP安装包了，有需要的饭友自己找下载地址吧。

PS：这是赛门铁克辉煌时期的遗产了吧，不知道还能存在多久，反正Norton那边已经没戏了，现在用Norton还不如SEP客户端了，毕竟还有保留赛门铁克的技术，虽然是在吃老本，但起码还是当年正统的赛门铁克继承人。

pal家族

朱祁钰退位
朱祁镇重新上位了！！！

驭龙

pal家族 发表于 2024-6-23 23:52
朱祁钰退位
朱祁镇重新上位了！！！

反正大明是迟早没的，改变不了啥

话说SEP 多少年没换UI了，真的是省美工啊

一个和尚挑水喝

RU8隔离区的文件无法恢复的bug解决了吗。。。

驭龙

一个和尚挑水喝 发表于 2024-6-24 00:21
RU8隔离区的文件无法恢复的bug解决了吗。。。

好像没有吧

1. Symantec Endpoint Protection (Windows)
   
2. Incident ID: CRE-12238
   
3. Incident Description: Intermittent ccSvcHst.exe process crash due to memory_corruption
   
4. 
   
5. Incident ID: CRE-13906
   
6. Incident Description: "Browser Intrusion Prevention is malfunctioning" error after installing SEF definitions
   
7. 
   
8. Incident ID: CRE-14480
   
9. Incident Description: Ping and Tracert commands timeout with certain firewall rules defined
   
10. 
    
11. Incident ID: CRE-14688
    
12. Incident Description: Risk log does not show the complete path when a .cab file is detected
    
13. 
    
14. Incident ID: CRE-14781
    
15. Incident Description: Discrepancy in firewall state between the SEP client User Interface and SEPM in some cases
    
16. 
    
17. Incident ID: CRE-14790
    
18. Incident Description: Intermittent ccSvcHst.exe process crash due to TSE.dll
    
19. 
    
20. Incident ID: CRE-15006
    
21. Incident Description: Windows may not successfully boot with Microsoft Smart App Control enabled
    
22. 
    
23. Incident ID: CRE-15009
    
24. Incident Description: Application Control policy does not work for 32-bit applications if SentinelOne agent is installed
    
25. 
    
26. Incident ID: CRE-15338
    
27. Incident Description: High non-paged pool observed for SymEvent.sys
    
28. 
    
29. Incident ID: CRE-15367
    
30. Incident Description: Events for quarantine restoration and quarantine are identical in the Integrated Cyber Defense Manager
    
31. 
    
32. Incident ID: CRE-15507
    
33. Incident Description: SEP client installation updates are incorrectly applied after using the "smc -image" command
    
34. 
    
35. Incident ID: CRE-15581
    
36. Incident Description: Notification is not displayed when "Notify users when external devices are Allowed" is enabled
    
37. 
    
38. Incident ID: CRE-15741
    
39. Incident Description: Traffic log events with a time of 0 are not correctly inserted into the SEPM database
    
40. 
    
41. Incident ID: CRE-15863
    
42. Incident Description: Bugcheck due to memory_corruption observed when using Terragrunt commnds
    
43. 
    
44. Incident ID: CRE-15912
    
45. Incident Description: Client upgrade does not honor the client server communication setting to not preserve communications during the upgrade
    
46. 
    
47. Incident ID: CRE-15918
    
48. Incident Description: SEP client unexpectedly clears the quarantine status when it originates from on-premise EDR
    
49. 
    
50. Incident ID: CRE-16006
    
51. Incident Description: SEP client EDR module may encounter enrollment errors intermittently due to network issues
    
52. 
    
53. Incident ID: CRE-16065
    
54. Incident Description: Extended system boot observed when Host Integrity is set to perform a high frequency of checks
    
55. 
    
56. Incident ID: CRE-16115
    
57. Incident Description: SEP client requires a reboot even when reboot is suppressed if EFAInst is not able to correctly upgrade SymEFA
    
58. 
    
59. Incident ID: CRE-16169
    
60. Incident Description: SEP client unexpectedly clears the quarantine status when it originates from on-premise EDR
    
61. 
    
62. Incident ID: CRE-16196
    
63. Incident Description: SEP client repeatedly logs that a device has been allowed, even if it has not transitioned to disabled first
    
64. 
    
65. Incident ID: CRE-16532
    
66. Incident Description: SEP client Application Discovery scan impacts performance on system startup
    
67. 
    
68. Incident ID: CRE-16556
    
69. Incident Description: Sepwscssvc hang observed during upgrade
    
70. 
    
71. Incident ID: CRE-16599
    
72. Incident Description: LiveUpdate error connection timeout observed intermittently (0x00002EE2)
    
73. 
    
74. Incident ID: CRE-16806
    
75. Incident Description: High CPU utilization observed on system start from DWHWzrd
    
76. 
    
77. Incident ID: CRE-16979
    
78. Incident Description: Smc.exe fails to launch with Unexpected Error (32)
    
79. 
    
80. Incident ID: CRE-17048
    
81. Incident Description: Exceptions using [PROGRAM_FILES] does not work for Program Files (x86) directory
    
82. 
    
83. Incident ID: CRE-17053
    
84. Incident Description: Target Policy Rule returning true even though it's false
    
85. 
    
86. Incident ID: CRE-17093
    
87. Incident Description: Incorrect operating system displayed as Server 2016 instead of Server 2022
    
88. 
    
89. Incident ID: CRE-17161
    
90. Incident Description: Bugcheck observed on IDSVia64.sys
    
91. 
    
92. Incident ID: CRE-17218
    
93. Incident Description: Target Policy Rule rapidly switches when using ICMP DNS host criteria
    
94. 
    
95. Incident ID: CRE-17400
    
96. Incident Description: IPS browser extension causes slow loading times with Chrome and Edge
    
97. 
    
98. Incident ID: CRE-17641
    
99. Incident Description: SEP client repeatedly logs a device has been disabled, even if it has not transitioned to enabled first
    
100. 
     
101. Incident ID: CRE-17676
     
102. Incident Description: IPS browser extension causes slow initial loading time in Edge
     
103. 
     
104. Incident ID: CRE-17722
     
105. Incident Description: Visual Studio is unable to open when SEP is installed and TDAD is enabled
     
106. 
     

复制代码

bbszy

唯一的问题就是允许了虚拟网卡的流量就会默认允许所有经过这里的软件联网，诺顿就没有这个问题

qoo71

SEP用了很多年了。。日常用用也足够了。

大胖

哪位兄弟放个安装包出来，谢谢！

驭龙

bbszy 发表于 2024-6-24 02:48
唯一的问题就是允许了虚拟网卡的流量就会默认允许所有经过这里的软件联网，诺顿就没有这个问题

他们的防火墙并不是同一个技术，我之前说过的

wudimeisuowei

驭龙 发表于 2024-6-24 13:23
他们的防火墙并不是同一个技术，我之前说过的

SEP会不会像eset那样读写SSD硬盘那么厉害？SSD最怕的就是读写，机械硬盘无所谓。