GreyNoise Expands Real-Time Edge Intelligence in Elastic Security GreyNoise expanded its integration with Elastic Security, adding purpose-built Kibana dashboards for edge observability, detection rules correlating perimeter and network activity with GreyNoise intelligence, and real-time enrichment that adds GreyNoise classifications to IPs in Elastic Security events. The new dashboards visualize allowed inbound traffic from malicious IPs, allowed outbound connections to malicious infrastructure, and alert volume with and without GreyNoise enrichment, while the detection rules cover allowed inbound and outbound connections involving malicious IPs, successful VPN logins from malicious IPs, and reconnaissance and brute-force activity from IPs GreyNoise has not observed. GreyNoise said security teams face pressure as AI shortens the time between vulnerability discovery and development of a working exploit, and that many internet-facing systems at the network edge cannot support endpoint agents. Today we’re announcing an expanded integration between GreyNoise and Elastic, with new content for Elastic Security. The integration includes purpose-built Kibana dashboards for edge observability, detection rules that correlate perimeter and network activity with GreyNoise intelligence, and real-time enrichment that adds GreyNoise classifications to the IPs in your Elastic Security events. Add the GreyNoise integration in Elastic https://www.elastic.co/docs/reference/integrations/ti greynoise to get started. How GreyNoise and Elastic Work Together in the SOC Security teams are under pressure as AI shortens the time between vulnerability discovery and the development of a working exploit. At the network edge, many internet-facing systems cannot support endpoint agents, leaving SOC analysts to investigate attacks through firewall, VPN, and network logs. GreyNoise continuously observes internet-wide scanning and exploitation through a global sensor network. We classify the associated IPs, tag the exploitation behavior, and record post-exploitation artifacts and command-and-control infrastructure. That intelligence gives analysts context for the network activity and alerts they investigate in Elastic Security. Elastic Security is an agentic security operations platform that offers SIEM, endpoint security, and native automation. It brings security data into a common schema so analysts can search across sources, build detections, and investigate activity in one place. Together, GreyNoise and Elastic put that context where analysts work: dashboards for real-time edge observability and detection rules to detect attacks at the network edge. What's Included in the Integration The expanded integration includes two categories of new content: 1. New dashboards visualize allowed inbound traffic from malicious IPs, allowed outbound connections to malicious infrastructure, and alert volume with and without GreyNoise enrichment. 2. New detection rules cover allowed inbound and outbound connections involving malicious IPs, successful VPN logins from malicious IPs, and reconnaissance and brute-force activity from IPs GreyNoise has not observed – this may be an indication of a targeted attack. Elastic Security Dashboard: Malicious Firewall Traffic The Malicious Firewall Traffic dashboard in Elastic Security helps SOC analysts identify allowed inbound connections from malicious IPs and internal hosts reaching malicious infrastructure. Built in Elastic’s Kibana dashboard capabilities, it shows: - Connection activity: Allowed inbound and outbound connections and successful VPN logins involving IPs GreyNoise classifies as malicious. - GreyNoise context: Classifications and tags that show what each IP has been observed doing across the internet. SOC analysts can prioritize VPN logins from malicious IPs and internal hosts reaching malicious infrastructure, then use GreyNoise real-time intelligence to add valuable context for investigating the activity without manually piecing together firewall and VPN logs. GreyNoise Detection Rules in Elastic Security The integration includes the following detection rules to bring these use cases into your SOC’s existing alert triage workflow. Allowed Inbound from Malicious Infrastructure Allowed inbound connections from malicious or suspicious IPs can expose gaps in perimeter security. By matching firewall logs against GreyNoise intelligence, this rule alerts SOC analysts to potentially targeted threat activity their firewall has permitted. Each alert includes context about the external IP, giving analysts a starting point to investigate the activity. The analyst can then review the firewall policy that allowed the connections and determine whether a misconfiguration, outdated access rule, or overly permissive policy needs attention. Allowed Outbound to Malicious Infrastructure Outbound connections to malicious infrastructure can indicate a compromised internal host. These detections help SOC analysts identify the hosts involved and investigate potential command-and-control activity, data exfiltration, or botnet participation. - Outbound Connection to Malicious Infrastructure: Flags internal hosts connecting to IPs GreyNoise classifies as malicious or suspicious. - Egress to Tor Exit Nodes: Flags allowed outbound connections to destinations identified by GreyNoise’s Tor attribute, helping analysts determine whether anonymized traffic is expected. This gives SOC analysts a focused set of internal hosts and destinations to investigate, with context to decide whether to isolate a host or block further connections. Flag Authentication Attempts from Compromised Hosts A successful VPN login from known malicious infrastructure warrants investigation. This rule flags successful logins from IPs GreyNoise classifies as malicious, helping SOC analysts identify potentially compromised credentials or unauthorized access. Analysts can investigate the account, IP, and session activity to determine whether access was authorized and what response is needed. Reduce Alert Volume and Surface Targeted Threats Known internet-wide scanning can bury activity that deserves closer investigation. Two rules filter out known mass-scanning IPs and focus on unseen IPs instead. - Combine “Recon from Unseen Sources” into a single alert to identify potentially targeted reconnaissance activity - “Brute Force from Unseen Sources” opens a high-severity case in Elastic Security when an unseen IP makes repeated credential attempts. This gives SOC analysts fewer alerts to review and helps them prioritize potentially targeted activity. Get Started The GreyNoise dashboards and detection rules are available now for Elastic Security. Follow the installation guide https://docs.greynoise.io/docs/elastic-installation-guide to add the GreyNoise integration in Elastic. Read the full report