GreyNoise (Beta)
Enrich incoming events with GreyNoise threat intelligence data
Overview
GreyNoise provides real-time intelligence about internet-wide scan and attack activity. GreyNoise helps security teams filter out background noise by identifying and labeling IPs conducting mass scanning, enabling faster, more accurate threat detection.
Learn how to view stored enrichment data here, and how to view log events with enrichment data here.
GreyNoise enrichment in Panther requires a GreyNoise API key.
How GreyNoise enrichment works in Panther
By default, GreyNoise is configured to run against every log source in your Panther environment (yet is possible to disable for a log type, if desired). Panther will attempt to match each incoming log event, across all log types, against the GreyNoise Panther-managed enrichment before it passes through the detection engine.
If Panther identifies a match between an incoming event and GreyNoise entry, GreyNoise data is appended to the matching log event under a top-level p_enrichment key. It can then be referenced in detection logic and searches.
For more information on detection writing using an enrichment source, see Writing a detection using custom enrichment data.
How a match between a log event and GreyNoise is made
A log event is enriched with GreyNoise Panther-managed enrichment data (under p_enrichment) if a match is found between:
Any of the values of the Selector field(s) configured for each associated log type.
For each log type, the default Selectors are the Indicator Fields (represented by
p_any_*) associated with the enrichment table's primary key's indicator field designations (though the Selectors are configurable). Learn more about this auto-mapping here.
The value of the
ipkey in a GreyNoise table entry in Panther.ipis the primary key of the GreyNoise table and is preset by Panther.See an example of
ipin the Example GreyNoise enrichment table entry below.
See the complete GreyNoise.API.V3 schema below.
Setting up GreyNoise enrichment
Step 1: Create an API key in GreyNoise
Follow the GreyNoise documentation to generate an API key for use in Panther.
Step 2: Create the GreyNoise enrichment in Panther
To configure GreyNoise enrichment in Panther:
In the left-hand navigation bar of your Panther Console, click Configure > Enrichments.
In the upper-right corner, click Create New.
Click GreyNoise.
In the Enrichment Settings form, provide values for the following fields:
Name: enter a descriptive name for your integration.
API Key: enter the API key you generated in Step 1.
Refresh period (minutes): configure how often Panther will refresh GreyNoise data. The default refresh period is 360 minutes and the minimum refresh period is 60 minutes.
Click Setup.
Your new GreyNoise configuration will be visible in the Configure > Enrichments page.
Enabling, disabling, or modifying GreyNoise enrichment for a log type
GreyNoise enrichment is enabled by default for each log type in your Panther instance.
If you'd like to disable (or later enable) GreyNoise enrichment for a certain log type, or alter a log type's selectors:
In the left-hand navigation bar in your Panther Console, click Configure > Enrichments.
In the list of Enrichments, locate the GreyNoise source you'd like to modify, and click its name.
Click on the Enriched Log Types tab.
On the right-hand side, click Edit Log Types.
If you'd like to enable this enrichment for a new log type, click Add Log Type.
In the new row that populates, select a Log Type and, in the Selectors field, at least one event field.
If you'd like to disable this enrichment for a log type, locate that log type's row, and click the trash icon.
If you don't see a log type listed, click on the drop-down arrow next to Auto-mapped Log Types. Locate the log type's row and click the edit icon.
If you'd like to alter the selectors for a log type, click into the Selectors field and add or remove selections for event fields.
In the upper-right corner, click Save.
Understanding GreyNoise classifications
GreyNoise classifies IP addresses into the following categories:
Benign: IPs exhibiting common internet behavior that is not malicious
Malicious: IPs with known malicious intent
Unknown: IPs observed by GreyNoise but not yet classified
Example of using GreyNoise tags in detections
GreyNoise provides detailed tags about scanning behavior. The recommend_block field within tags indicates whether GreyNoise recommends blocking traffic from the IP address. This can be particularly useful in detection logic:
Example GreyNoise enrichment table entry
The below is an example of a GreyNoise API response normalized by Panther, showing an IP address identified as part of a known CDN service with benign scanning behavior:
GreyNoise data structure
GreyNoise.API.V3 schema
GreyNoise.API.V3 schemaThe following is the Panther-managed GreyNoise.API.V3 schema, representing how GreyNoise intelligence data is stored in Panther. See an event that has been parsed with this schema above.
Last updated
Was this helpful?

