![]() ![]() “We are currently restructuring our testing process to improve compatibility testing and will not be releasing new SONAR signatures until this new process is in place. It is this part of our process that we will be improving to avoid future issues,” Cox added. “The compatibility testing part of the quality assurance process for SONAR signatures missed catching this compatibility issue. We also offer add-ons for endpoint protection, business management (PSA) and backup & disaster recovery software and integration with leading AV. Compare price, features, and reviews of the software side-by-side to make the best choice for your business. Some of their clients complained that the update wasn’t tested enough before being released so Symantec detailed the quality assurance process for SONAR – a behavior-based technology integrated into SEP’s Proactive Threat Protection – and explained the cause of the problem. Symantec Endpoint Protection using this comparison chart. “The SONAR signature update caused new file operations that create the conflict and led to the system crash.”įortunately, immediately after customers started reporting the problem, the company rushed to address the issue and instructed affected users on how to install the updated signatures. Symantec Endpoint Protection and Norton customers are fully protected from WannacCry by multiple layers of advanced protection. “The root cause of the issue was an incompatibility due to a three way interaction between some third party software that implements a file system driver using kernel stack based file objects – typical of encryption drivers, the SONAR signature and the Windows XP Cache manager,” Orla Cox of Symantec Security Response explained. Another ingredient that led to the incident was represented by certain third-party software. Some time has passed since we’ve heard of a situation that involves the infamous blue screen of death (BSOD).Īccording to Symantec, the problem existed in the SONAR definitions and only affected Windows XP users who performed the update via LiveUpdate. ![]() After analyzing the incident, the security firm determined that it was caused by a compatibility issue. A number of Symantec customers who applied the updates for Symantec Endpoint Protection (SEP) on July 12 complained that they started experiencing blue screens.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |