Active Directory - Enrich Devices with Local Users
- 04 Feb 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Active Directory - Enrich Devices with Local Users
- Updated on 04 Feb 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Active Directory - Enrich Devices with Local Users fetches local users data from devices returned by the selected query or selected on the relevant asset page and enriches them.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
Note:
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
Required Fields
These fields must be configured to run the Enforcement Set.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
- Hostname - A hostname that has WinRM service enabled.
- User Name and Password - The credentials for a user account that has the Required Permissions to perform this Enforcement Action.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
- Gateway Name - Select the Gateway through which to connect to perform the action.
APIs
Axonius uses the Microsoft PowerShell Management API.
Required Ports
Axonius must be able to communicate via the following ports:
- Port 5986 (requiring the WinRM service to be enabled in the Hostname)
Required Permissions
The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:
- Permission to run the
Get-WmiObject
PowerShell command.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?