Use standard, automated methods and tools to move the generated files from each Windows endpoint to a location accessible from your OT sensors.ĭo not update filenames or separate the files from each other.
Are overwritten if you run the script again.Īfter having run the script as described earlier, import the generated data to your sensor to view the device details in the Device inventory.Remain on the local drive until you delete them.The filename indicates the system name, date, and time of the snapshot with the following syntax: CX-snaphot_SystemName_Month_Year_Time The following files appear:Īfter the script runs to probe the registry, a CX-snapshot file appears with the registry information. To acquire the script, contact customer support.ĭeploy the script once, or using ongoing automation, using standard automated deployment methods and tools.Ĭopy the script to a local drive and unzip it. Running the script doesn't affect the endpoint. The script you run to detect enriched Windows data is run as a utility and not as an installed program. This procedure describes how to obtain, deploy, and run the script on the Windows workstation and servers that you want to monitor in Defender for IoT. If an OT network sensor has already learned the device, running the script will retrieve its information and enrichment data. A Defender for IoT OT sensor already monitoring the network where the device is connected.Administrator permissions on any devices where you intend to run the script.The script described in this article is supported for the following Windows operating systems:īefore you start, make sure that you have: Running a local script is also useful for regulated networks that have waterfalls and one-way elements.įor more information, see Configure Windows Endpoint Monitoring. While you can use active scanning and scheduled WMI scans to obtain this data, working with local scripts bypasses the risks of running WMI polling on an endpoint. This article describes how to configure Defender for IoT to detect Windows workstations and servers with local surveying, performed by distributing and running a script on each device. The Device inventory pages on the sensor and on-premises management console show enriched data about Windows devices, including data about the Windows operating system and applications installed, patch-level data, open ports, and more.
Same as other detected devices, detected Windows workstations and servers are displayed in the Device inventory. In addition to detecting OT devices on your network, use Defender for IoT to discover Microsoft Windows workstations and servers.
0 kommentar(er)
