Notification

Icon
Error

Discover devices vulnerable to Intel SA-00086

Posted: Tuesday, December 5, 2017 1:46:37 PM(UTC)
Bruce.B

Bruce.B

Member Administration Original PosterPosts: 562
7
Like
DISCLAIMER: The Intel discovery tool has been known to hang on Virtual Machines. As a result running the package on a VM may cause it to hang and end up on a 'Package Timeout' error.

Intel has identified several security vulnerabilities in its Management Engine (ME), Trusted Execution Engine (TXE) and Server Platform Services (SPS) that could place impacted PCs, servers and IoT platforms at risk. Attackers could gain unauthorized access to systems using the Management Engine feature.
This topic outlines how you can deploy the Intel-SA-00086 discovery tool using the Lansweeper deployment module and afterwards run a report that lists whether your computers are vulnerable or not.
To make use of this guide make sure the following are in order:

If the requirements are in order, you can mass check whether your computers are vulnerable or not by doing the following 3 things, setting up custom registry scanning for the registry value created by the Intel tool, deploying the Intel tool and reporting on the results:

1) Set up Custom Registry Scanning for the registry key the Intel tool will create:
  • Go to Scanning\File & Registry Scanning
  • Click Add Registry Scan
  • Enter the following in the Regpath field: HKEY_LOCAL_MACHINE\SOFTWARE\Intel\Setup and Configuration Software\INTEL-SA-00086 Discovery Tool\System Status
  • Enter the following in the Regvalue field: System Risk

UserPostedImage

2) Go to Deployment\Security Options and set up your package share and share user.

3) Follow the instructions found in the Installer Center to add the deployment to your Lansweeper installation.


UserPostedImage


4) Follow the instructions found in the Report Center to add the report to your Lansweeper installation.


UserPostedImage

5) Patch your systems via the vendor resources listed in the Intel article found here.
Bruce.B
#1Bruce.B Member Administration Original PosterPosts: 562  
posted: 12/5/2017 2:20:41 PM(UTC)
If you have any feedback or questions regarding this topic, please contact us via support@lansweeper.com.

Active Discussions

Lansweeper Acknowlege from Alerts
by  Hilbers   Go to last post Go to first unread
Last post: Today at 7:55:38 AM(UTC)
Lansweeper LsAgent for Windows command line options?
by  Brandon  
Go to last post Go to first unread
Last post: Yesterday at 4:49:17 PM(UTC)
Lansweeper EmailLog.txt file become big in size
by  Ary Ahmed   Go to last post Go to first unread
Last post: 4/18/2021 10:56:58 AM(UTC)
Lansweeper LsAgent.ini
by  Orion Poplawski  
Go to last post Go to first unread
Last post: 4/17/2021 4:49:12 PM(UTC)
Lansweeper LSagent force a scan
by  Orion Poplawski   Go to last post Go to first unread
Last post: 4/17/2021 4:46:49 PM(UTC)
Lansweeper MS Edge Chromium LanSweeper Extension development
by  steveb  
Go to last post Go to first unread
Last post: 4/16/2021 10:59:56 PM(UTC)
Lansweeper Office 365 v2 Scanning Error
by  DJX   Go to last post Go to first unread
Last post: 4/16/2021 7:37:57 PM(UTC)
Lansweeper Database size growing too large
by  JTempleton  
Go to last post Go to first unread
Last post: 4/16/2021 5:19:22 PM(UTC)