- 16 Mar 2023
- 2 Minutes to read
-
Print
-
DarkLight
-
PDF
Axonius - Run Windows WMI Scan
- Updated on 16 Mar 2023
- 2 Minutes to read
-
Print
-
DarkLight
-
PDF
Axonius - Run Windows WMI Scan runs a WMI (Windows Management Instrumentation) scan on each of the query results entities, which are windows devices.
As part of the WMI scan, Axonius reaches out to devices directly and execute commands on them in memory, without installing anything or leaving any traces. The WMI scan retrieves important information about the device, including (but not limited to):
- Hostname
- Network Interfaces - including MAC addresses, IP addresses and subnets
- Operating system, kernel version and distribution
- List of installed software
- Users and admin users
- Hard drives and file systems
- CPUs and RAM
- Hardware details, including serial numbers
If Run WMI Scan action was executed on specific device, Windows Management Instrumentation (WMI) adapter is also listed as one of the device different adapters listed under the Adapter Connections tab, on the Device Profile page. Most of the WMI scan information is also displayed under the various Aggregated tables.
For more details, see Device Profile page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonious. You can change the name according to your needs.
- Add description (optional) - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs and Adapter Fetch History Modules
- Action name - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
- Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition statement syntax.
Connection Settings
- Use stored credentials from the Active Directory adapter (required, default: False) - Select this option to use the first connected Microsoft Active Directory (AD) adapter credentials.
- User and Password (optional, default: empty) - Provide credentials to connect and to execute the command on the windows device: user name and password.
- DNS Servers (optional, default: empty) - Specify a comma-separated list of DNS servers to be used to resolve the hostnames in the saved query supplied as a trigger (or devices that have been selected in the asset table).
- If supplied, Axonius will use the specified DNS server to resolve the devices' hostnames. For each asset, the first response will be the one to be used.
- If not supplied or if no response has been received from any of the specified DNS servers, the default DNS server will be used.
- Registry keys to check for existence (optional, default: empty) - Specify the registry keys that you want to check whether they exist.
- Tunnel Name - For Axonius-hosted (SaaS) deployments. Select the tunnel through which to connect to perform the action.
For more details about other Enforcement Actions available, see Action Library.