Deactivate Code42 Agent
- 10 Nov 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Deactivate Code42 Agent
- Updated on 10 Nov 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Deactivate Code42 Agent deactivates a set of agents for:
- Assets returned by the selected query or assets selected on the relevant asset page.
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.
- Use stored credentials from Datadog adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
- When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
Note:
To use this option, you must successfully configure an Datadog adapter connection.
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.
- Code42 Domain - The hostname or IP address of the Code42 server.
- Authentication Method - Select the authentication method to use.
- User Credentials - Fill in the Username and Password.
- Client Credentials - Fill the Client ID and Client Secret.
- Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
- HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
- Gateway Name - Select the Gateway through which to connect to perform the action.
Required Permissions
The stored credentials, or those provided in Connection and Credentials, must have permission to perform this Enforcement Action.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?