Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
General Security Discussions
Inside Microsoft's plan to kill PPLFault
Message
<blockquote data-quote="danb" data-source="post: 1059312" data-attributes="member: 62850"><p>I only care about facts as well. Here are five.</p><p></p><p>First, most of the third party cybersecurity companies existed long before Microsoft decided to get serious about malware. Many of these third party companies developed tech that Microsoft utilizes in their own cybersecurity products today. Do you want all third party cybersecurity companies to step aside, and simply shut down their business because Microsoft “has everything under control”?</p><p></p><p>Second, there are hundreds or thousands of cybersecurity features and tech that third party products offer, that no one else can. These features increase efficacy bigtime.</p><p></p><p>Third, have you ever heard the phrase “security through obscurity”? Microsoft is by far the biggest target for malware authors, and this will only worsen over time.</p><p></p><p>Forth, WDAC and SAC are not nearly as great or effective as you suggest. In short, WDAC is inflexible and SAC is not zero-trust. A kernel mode driver, written mainly by Microsoft, and supplied by a third party has tons of advantages over WDAC and SAC, not just is efficacy, but in usability as well. There is absolutely no comparison.</p><p></p><p>Fifth, your product is third party as well. Just because it is a script, and not a pre-compiled binary, does not exclude it from third party status. If Microsoft did not write it, then it is third party.</p></blockquote><p></p>
[QUOTE="danb, post: 1059312, member: 62850"] I only care about facts as well. Here are five. First, most of the third party cybersecurity companies existed long before Microsoft decided to get serious about malware. Many of these third party companies developed tech that Microsoft utilizes in their own cybersecurity products today. Do you want all third party cybersecurity companies to step aside, and simply shut down their business because Microsoft “has everything under control”? Second, there are hundreds or thousands of cybersecurity features and tech that third party products offer, that no one else can. These features increase efficacy bigtime. Third, have you ever heard the phrase “security through obscurity”? Microsoft is by far the biggest target for malware authors, and this will only worsen over time. Forth, WDAC and SAC are not nearly as great or effective as you suggest. In short, WDAC is inflexible and SAC is not zero-trust. A kernel mode driver, written mainly by Microsoft, and supplied by a third party has tons of advantages over WDAC and SAC, not just is efficacy, but in usability as well. There is absolutely no comparison. Fifth, your product is third party as well. Just because it is a script, and not a pre-compiled binary, does not exclude it from third party status. If Microsoft did not write it, then it is third party. [/QUOTE]
Insert quotes…
Verification
Post reply
Top