Threat Hunting

Needle in the haystack. Found

Quickly identify anomalous behavior and catch targeted threats

Overview

Effective threat hunting isn't just about finding more data, it’s about finding the right data. GreyNoise empowers your hunt team to adopt the PEAK Framework by correlating your internal traffic against our real-time map of internet-wide mass scanning.

By using GreyNoise to filter out opportunistic probes, benign scanners, and botnet noise, you reveal the statistically significant anomalies that represent targeted attacks. Stop chasing false positives and focus on the signals that actually threaten your perimeter.

How GreyNoise
Helps You Hunt Smarter

Focus effort on highest risks

Eliminate time-consuming research of benign and opportunistic scanning, allowing hunters to focus on infrastructure actually used by threat actors.

Supports threat research and hypothesis development

Hunters can use GreyNoise to conduct threat research, validate assumptions, and explore attack vectors in order to develop hypotheses.

Correlate isolated incidents

GreyNoise helps threat hunters link isolated incidents to larger campaigns by mapping attacker infrastructure and patterns, connecting logged IPs to those exploiting relevant vulnerabilities.

How GreyNoise Maps to the PEAK Hunting Framework

Explore Available Fields

Filter by category & search available IP fields and their uses with GreyNoise.
Categories
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
NAME
Description & Use
HTTP Method
HTTP methods used (e.g., GET, POST). Provides context on attacker request.
Protocol Data
HTTP Path
Web paths targeted during scanning (e.g., /robots.txt, /admin). Reveals reconnaissance goals.
Protocol Data
HTTP Request Authorization
Authorization headers observed in HTTP requests. May reveal brute-force attempts.
Protocol Data
HTTP Request Cookies
Cookies included in HTTP requests. Adds context on reconnaissance or exploit attempts.
Protocol Data
HTTP Request Headers
Headers used in HTTP requests. Useful for tool fingerprinting.
Protocol Data
HTTP Request Origin
Origin IPs or addresses set in HTTP headers. May indicate spoofing.
Protocol Data
HTTP Useragent
User-Agent strings observed. Useful for identifying attacker tools or crawlers.
Protocol Data
Hassh Fingerprint
Fingerprint hash of SSH client behavior. Helps identify SSH attack tools.
Protocol Data
Hassh Port
Port associated with observed SSH behavior. Adds protocol context.
Protocol Data
ID
Unique tag identifier.
Tag Information
ID
Unique identifier for the record. Used to track and reference the vulnerability consistently across systems and reports.
Identification & Details
IP
The observed IP address itself. Primary entity to investigate or correlate across alerts.
Identity & Ownership
Intention
Tag’s intent classification: benign, malicious, suspicious, or unknown. Adds risk context.
Tag Information
JA3 Fingerprint
JA3 TLS fingerprint of client behavior. Useful for identifying attack tools, actors, botnets, and campaigns.
Protocol Data
JA3 Port
Port associated with observed JA3 TLS activity.
Protocol Data
Last Seen
Last date the IP was observed by GreyNoise sensors. Indicates recency of activity.
Activity Timeline
Last Seen Timestamp
Exact date and time the IP was last observed. Enables timeline reconstruction in investigations.
Activity Timeline
Mobile
Indicates if the IP belongs to a mobile/cellular network.
IP Address Metadata
Name
Display name of the tag. Analyst-facing label for quick recognition.
Tag Information
Organization
Organization responsible for the IP. Adds enrichment for attribution.
IP Address Metadata
Organization Count
Count of IPs linked to each organization. Useful for assessing exposure by provider.
Stats & Aggregates
Port
Port observed in scanning activity. Useful for identifying targeted services.
Observed Request Data
Protocol
Protocol (e.g., TCP/UDP) used in scanning activity. Adds layer-4 context.
Observed Request Data
RDNS
Reverse DNS value for the IP. May reveal hostnames tied to services or campaigns.
IP Address Metadata
RDNS Parent
Parent domain of the reverse DNS. Useful for clustering infrastructure.
IP Address Metadata
Recommended Block
Indicates whether IPs with this tag should be blocked. Supports automated policy decisions.
Tag Information
References
References (e.g., CVE pages, docs) supporting the tag. Provides analyst enrichment sources.
Tag Information
Region
State/province where the IP is registered. Adds sub-country geolocation context.
IP Address Metadata
SSH Key
SSH keys observed from traffic. Can reveal attacker tooling or campaigns.
Protocol Data
Sensor Count
Number of distinct sensors that saw the IP. Higher values indicates wider scanning footprint.
Sensor Metadata
Sensor Hits
Total number of events GreyNoise sensors recorded from this IP. Indicates activity volume.
Sensor Metadata
Single Destination
True if the IP only scanned one country. Suggests targeted reconnaissance.
IP Address Metadata

Find your needle.