Contents x
    GreyNoise - Enrich Asset Data
    • 20 Mar 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    GreyNoise - Enrich Asset Data

    • Updated on 20 Mar 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    GreyNoise - Enrich Asset Data (Enrich Device Data with GreyNoise IO) enriches assets returned by the selected query, or selected on the relevant asset page, with data from GreyNoise IO. The enrichment is based on the IP addresses of the assets.

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

    Note:

    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 the GreyNoise IO 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 a GreyNoise 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.

    Connection and Credentials

    When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

    • Host Name or IP Address (default: api.greynoise.io) - Enter the host name or IP address for GreyNoise.
    • Key - The GreyNoise IO API key.
    • 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.

    Required Permissions

    The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

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

    Was this article helpful?
    What's Next