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
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
Guides - Privacy & Security Tips
Windows processes which are significantly important
Message
<blockquote data-quote="Andy Ful" data-source="post: 689256" data-attributes="member: 32260"><p>This additional LSA protection can break LSA plug-ins and drivers. I read somewhere, that even after checking this feature in Audit mode, some drivers could (rarely) crash the system.</p><p>.</p><p>From technet.microsoft.com paper - Recommended practices.</p><p>.</p><p><em>Use the following list to thoroughly test that LSA protection is enabled before you broadly deploy the feature:</em></p><ul> <li data-xf-list-type="ul"><em>Identify all of the LSA plug-ins and drivers that are in use within your organization. This includes non-Microsoft drivers or plug-ins such as smart card drivers and cryptographic plug-ins, and any internally developed software that is used to enforce password filters or password change notifications.</em></li> <li data-xf-list-type="ul"><em>Ensure that all of the LSA plug-ins are digitally signed with a Microsoft certificate so that the plug-in will not fail to load.</em></li> <li data-xf-list-type="ul"><em>Ensure that all of the correctly signed plug-ins can successfully load into LSA and that they perform as expected.</em></li> <li data-xf-list-type="ul"><em>Use the audit logs to identify LSA plug-ins and drivers that fail to run as a protected process.</em></li> </ul><p><a href="https://technet.microsoft.com/en-us/library/dn408187(v=ws.11).aspx" target="_blank">Configuring Additional LSA Protection</a></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 689256, member: 32260"] This additional LSA protection can break LSA plug-ins and drivers. I read somewhere, that even after checking this feature in Audit mode, some drivers could (rarely) crash the system. . From technet.microsoft.com paper - Recommended practices. . [I]Use the following list to thoroughly test that LSA protection is enabled before you broadly deploy the feature:[/I] [LIST] [*][I]Identify all of the LSA plug-ins and drivers that are in use within your organization. This includes non-Microsoft drivers or plug-ins such as smart card drivers and cryptographic plug-ins, and any internally developed software that is used to enforce password filters or password change notifications.[/I] [*][I]Ensure that all of the LSA plug-ins are digitally signed with a Microsoft certificate so that the plug-in will not fail to load.[/I] [*][I]Ensure that all of the correctly signed plug-ins can successfully load into LSA and that they perform as expected.[/I] [*][I]Use the audit logs to identify LSA plug-ins and drivers that fail to run as a protected process.[/I] [/LIST] [URL="https://technet.microsoft.com/en-us/library/dn408187(v=ws.11).aspx"]Configuring Additional LSA Protection[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top