GreyNoise - Enrich Asset Data
- 28 Jan 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
GreyNoise - Enrich Asset Data
- Updated on 28 Jan 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
GreyNoise - Enrich Asset Data (Enrich Device Data with GreyNoise IO) enriches each of the query result devices based on IP address. When there is a match, Axonius data is enriched with the data from GreyNoise IO.
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.
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.
- Use stored credentials from the GreyNoise IO adapter (optional) - Select this option to use the first connected GreyNoise IO adapter credentials.
Requried Fields
These fields must be configured to run the Enforcement Set.
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.
- 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.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?