Contents x
    Cisco Support - Enrich Cisco Devices OS with EOL/EOS
    • 21 Nov 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Cisco Support - Enrich Cisco Devices OS with EOL/EOS

    • Updated on 21 Nov 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Cisco Support - Enrich Cisco Devices OS with EOL/EOS enriches each of the assets that are the result of the query with End of Life/End of Service data from Cisco Support.

    See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

    Note:

    General Settings

    • 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.

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • 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.

    Additional Settings

    • 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.

    APIs

    Axonius uses the Cisco Support API.

    Required Ports

    Axonius must be able to communicate via the following ports:

    • 443

    Required Permissions

    The user must retrieve the Client ID and Client Secret from the Cisco Support.

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

    Was this article helpful?
    What's Next