GreyNoise - Enrich Asset Data
- 16 Mar 2023
- 2 Minutes to read
-
Print
-
DarkLight
-
PDF
GreyNoise - Enrich Asset Data
- Updated on 16 Mar 2023
- 2 Minutes to read
-
Print
-
DarkLight
-
PDF
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.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonious. You can change the name according to your needs.
- Add description (optional) - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs and Adapter Fetch History Modules
- Action name - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
- Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition statement syntax.
Connection Settings
Click to view Connection Settings
- Use stored credentials from the GreyNoise IO adapter (optional) - Select this option to use the first connected GreyNoise IO adapter credentials.
- Key (required) - The GreyNoise IO API key.
- Verify SSL (optional) - Verify the SSL certificate offered by the value supplied in Use stored credentials from the GreyNoise IO adapter. For more details, see SSL Trust & CA Settings.
- If enabled, the SSL certificate offered by the value supplied in Use stored credentials from the GreyNoise IO adapter will be verified against the CA database inside of Axonius. If the SSL certificate can not be validated against the CA database inside of Axonius, the connection will fail with an error.
- If disabled, the SSL certificate offered by the value supplied in Use stored credentials from the GreyNoise IO adapter will not be verified against the CA database inside of Axonius.
- HTTPS proxy (optional) - A proxy to use when connecting to the value supplied in Use stored credentials from the GreyNoise IO adapter.
- If supplied, Axonius will utilize the proxy when connecting to the value supplied in Use stored credentials from the GreyNoise IO adapter.
- If not supplied, Axonius will connect directly to the value supplied in Use stored credentials from the Greynoise IO adapter.
- HTTPS proxy password (optional) - The password to use when connecting to the value supplied in Use stored credentials from the GreyNoise IO adapter via the value supplied in HTTPS proxy.
- If supplied, Axonius will authenticate with this value when connecting to the value supplied in HTTPS proxy.
- If not supplied, Axonius will not perform authentication when connecting to the value supplied in HTTPS proxy.
For more details about other Enforcement Actions available, see Action Library.