GreyNoise (Beta)

Enrich incoming events with GreyNoise threat intelligence data

Overview

GreyNoise enrichment is in open beta starting with Panther version 1.117, and is available to all customers. Please share any bug reports and feature requests with your Panther support team.

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.

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.

  • The value of the ip key in a GreyNoise table entry in Panther.

See the complete GreyNoise.API.V3 schema below.

Setting up GreyNoise enrichment

Step 1: Create an API key in GreyNoise

Step 2: Create the GreyNoise enrichment in Panther

To configure GreyNoise enrichment in Panther:

  1. In the left-hand navigation bar of your Panther Console, click Configure > Enrichments.

  2. In the upper-right corner, click Create New.

  3. Click GreyNoise.

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

  5. Click Setup.

    • Your new GreyNoise configuration will be visible in the Configure > Enrichments page.

After adding a GreyNoise enrichment, there may be a delay of up to 45 minutes before incoming log data begins to be enriched. This allows time for the initial data synchronization to complete.

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:

  1. In the left-hand navigation bar in your Panther Console, click Configure > Enrichments.

  2. In the list of Enrichments, locate the GreyNoise source you'd like to modify, and click its name.

  3. Click on the Enriched Log Types tab.

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

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

Business Service Intelligence

Business Service Intelligence helps identify whether an IP address belongs to a known business service (like CDNs, cloud providers, or other commercial services). This information can be crucial for filtering false positives and understanding the context of network traffic.

  • found: whether the IP was found in GreyNoise's business service database

  • category: the type of business service (e.g., CDN, hosting, cloud provider)

  • name: the name of the business service (e.g., Cloudflare, AWS, Google)

  • description: a description of the business service

  • explanation: additional context about why this IP is associated with the service

  • last_updated: timestamp of when this business service information was last updated

  • reference: a URL reference for more information about the service

  • trust_level: a numeric trust level indicating the reliability of the service (higher values indicate more trustworthy services)

Internet Scanner Intelligence

Internet Scanner Intelligence provides detailed information about IPs observed conducting internet-wide scanning or attack activity. This is the core threat intelligence data from GreyNoise.

  • found: whether internet scanner intelligence data was found for the IP

  • first_seen: the first date this IP was observed by GreyNoise

  • last_seen: the last date this IP was observed by GreyNoise

  • last_seen_timestamp: a detailed timestamp of the last observation

  • actor: the threat actor or entity associated with the scanning activity

  • spoofable: whether the observed traffic is easily spoofable

  • classification: the classification of the IP (benign, malicious, or unknown)

  • cves: an array of CVE identifiers associated with scanning activity from this IP

  • bot: whether the IP is identified as a bot

  • vpn: whether the IP is associated with a VPN service

  • vpn_service: the name of the VPN service, if identified

  • tor: whether the IP is a known Tor exit node

  • tags: an array of behavioral tags describing the scanning activity (see Using GreyNoise tags in detections)

  • metadata: detailed metadata about the IP including ASN, geolocation, organization, and scanning patterns

Metadata

The metadata object within Internet Scanner Intelligence provides detailed context about the scanning IP:

  • asn: the Autonomous System Number

  • carrier: the mobile carrier, if applicable

  • category: the IP category (e.g., hosting, business, isp)

  • datacenter: the datacenter provider, if applicable

  • destination_asns: an array of ASNs targeted by scanning from this IP

  • destination_cities: an array of cities targeted by scanning from this IP

  • destination_countries: an array of countries targeted by scanning from this IP

  • destination_country_codes: an array of country codes targeted by scanning from this IP

  • domain: the domain associated with the IP

  • latitude / longitude: geographic coordinates

  • mobile: whether the IP is associated with mobile networks

  • organization: the organization that owns the IP

  • os: the detected operating system

  • rdns: reverse DNS lookup result

  • rdns_parent: the parent domain from reverse DNS

  • rdns_validated: whether the reverse DNS has been validated

  • region: the geographic region

  • sensor_count: the number of GreyNoise sensors that observed this IP

  • sensor_hits: the total number of times this IP was observed across all sensors

  • single_destination: whether the IP targets only a single destination

  • source_city / source_country / source_country_code: the source location information

Tags

Tags within Internet Scanner Intelligence represent specific behavioral patterns identified by GreyNoise:

  • id: a unique identifier for the tag

  • name: the display name of the tag

  • slug: a URL-friendly identifier

  • category: the tag category (e.g., activity, tool, worm)

  • description: a detailed explanation of what this tag represents

  • intention: the intent classification (benign, malicious, or unknown)

  • recommend_block: whether GreyNoise recommends blocking traffic from IPs with this tag

  • created: the date this tag was created

  • updated_at: timestamp of the last update to this tag

  • cves: an array of CVE identifiers associated with this tag

  • references: external references or citations related to this tag

GreyNoise.API.V3 schema

The 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?