|Applies to Product:||USM Appliance™||AlienVault OSSIM®|
Windows Management Instrumentation (WMI) plugins collect Microsoft Windows events and data remotely. These plugins collect the information without an agent, using the Windows Management Instrumentation Command Line (WMIC) .
Note: Currently, WMIC does not support samba4/NTLMv2. Nor does WMIC work on more recent Windows versions, like Windows Server 2012 or above, because these versions authenticate with NLTMv2 only by default.
To use a WMI plugin with a Windows host that uses NTLMv2, you must manually enable NTLMv1 authentication. For information about this, see the Microsoft Support web pages.
# Plugin wmi-application-logger id:1518 version: 0.0.2
# Last modification: 2015-05-13 16:11
# Plugin Selection Info:
# AlienVault:WMI Application Logger:-
# Accepted products:
# alienvault - plugin-wmi -
cmd=wmic -U OSS_WMI_USER%OSS_WMI_PASS //OSS_WMI_HOST "Select LogFile,RecordNumber from Win32_NTLogEvent Where Logfile = 'Application'" | head -n 3 | tail -n 1 | cut -f 2 -d \|
cmd = wmic -U OSS_WMI_USER%OSS_WMI_PASS //OSS_WMI_HOST "Select ComputerName,EventCode,Logfile,Message,RecordNumber,SourceName,TimeWritten,User from Win32_NTLogEvent Where Logfile = 'Application' and RecordNumber > OSS_COUNTER" | cat
The following sections of a WMI plugin are essential.
You use [start_cmd] and [cmd] to return the last WMI Application event, and start reading from that event.
Additional Configuration Required Before You Enable an WMI Plugin
You need to perform the following additional configuration before you can use the WMI plugins.
This configuration procedure is for users who must contact the WMI plugin remotely from a Windows host. The procedure is appropriate for production.
Note: This procedure is based on Microsoft Windows 7. Microsoft Windows 10 no longer shows the Run box in the Start menu. However, Windows 10 does allow you to personalize the Start menu to include it. For more information, refer to the Windows 10 documentation.
To enable remote WMI access on Windows
Create a new user in the Windows host (without any administrator privileges) who can connect remotely. In this example, we use “wmiuser” as the username and “wmi” as the password.
Important: This step is performed to make the connection more secure.
Enable remote access and activation permissions for the user account you just created.
- In the Windows Start menu, type Dcomcnfg in the empty field and press Enter.
- In the Component Services dialog box, right-click My Computer and select Properties.
Click the COM Security tab, then Edit Limits under Access Permissions.
Click ANONYMOUS LOGON, enable Allow Remote Access, and then click OK.
- Click Apply.
- On the COM Security tab, under Launch and Activation Permissions, select Edit Limits, then click Add.
- In the empty field of the popup that appears, type the username for the new user account and click OK.
- On the Launch and Activation Permissions dialog box, select Remote Launch, Local Activation, and Remote Activation. Click OK.
Click Apply, and then OK.
Follow this procedure to create a file with your Windows IP and credentials on USM Appliance. You will need command line access to USM Appliance to complete this task.
To configure USM Appliance to use a WMI plugin
Connect to the AlienVault Console through SSH and use your credentials to log in.
The AlienVault Setup menu displays.
On the AlienVault Setup main menu, select Jailbreak System to gain command line access.
Select Yes when prompted. You will be in the root directory.
Add IPs, users, and password with the following formats.
If you do not use a domain, enter the following instead.
- Save the file.
In order for the WMI plugin to work correctly, you must update the plugin with the path to the wmi_credentials.csv file you just created. You will need command line access to USM Appliance to complete this task.
To specify the path to the WMI credentials file
Depending on which plugin you've enabled, locate the WMI configuration file or files in your USM Appliance instance. Potential file locations might be any of the following.
Create the file <wmi-xxxx-plugin>.cfg.local based on your choice and enter the path to your wmi_credentials.csv file in the credentials_file field.
- Save the file.
You can now enable the WMI plugin. See Enable Plugins on Assets.