Cisco Support - Enrich Cisco Devices OS with EOL/EOS

Cisco Support - Enrich Cisco Devices OS with EOL/EOS enriches assets with End of Life/End of Service data from Cisco Support 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 types 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.

Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Host Name or IP Address - The hostname or IP address of the Cisco Support server.
Client ID (required) - The credentials for a user account that has the Required Permissions to perform this action.
Client Secret (required) - A Client Secret Key associated with a user account that has the Required Permissions to perform this action.

These fields are optional.

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.
HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

Axonius uses the Cisco Support API.

Axonius must be able to communicate via the following ports:

For more details about other Enforcement Actions available, see Action Library.