Fingerprint encrypted connections
Fingerprint SSL or SSH connections via the JA3/HASSH packages so analysts can identify and track attacker movements across encrypted channels
Assessing the scope of a malware attack
Pivot off a malware hash in Zeek's / Bro’s files.log to immediately see all other hosts in an environment that have downloaded the malicious file and then prioritize additional incident response work such as agent deployment. Learn more.
Locating PCAP files needed for an investigation
Pivot from the logs of a Zeek-parsed connection directly into connection packets in Moloch using the shared Community ID appended to the Zeek / Bro conn.log. Learn more.
Verifying containment and remediation
Use Zeek's / Bro’s network logs for conducting post-breach monitoring to look for the recurrence of malware beaconing.
Use Zeek's / Bro's continuous logging across protocols to establish the "ground truth" of what happened historically, minimizing both legal expenses and the scope of disclosure
Detecting SSH client bruteforce attacks
Discover when a client attempts to authenticate beyond a pre-configured threshold and then successfully authenticates. Learn more.
Detecting hidden C2 server communications
Uncover live C2 communications via Zeek’s / Bro’s dpd.log when an attacker attempts to disguise their C2 traffic in a purported SSL connection. Watch video.
Lateral movement detection
Detect lateral movement in MITRE ATT&CK related to SMB and DCE-RPC traffic, such as indicators targeting Windows Admin Shares and Remote File Copy or stream Zeek / Bro logs to the Real Intelligence Threat Analytics (RITA) tool to create a daily report of potential beaconing activity. Watch Video.
Detecting off-port protocol usage
Use Zeek’s / Bro’s deep protocol parsing capabilities to identify network services, such as HTTP or DNS, running on non-standard ports. Watch video.
Fingerprinting connections for fraud detection
Create custom Zeek / Bro logs to fingerprint connections and identify issues like API fraud and account takeovers.
Enhance traffic monitoring with local context
Use the Zeek / Bro Input Framework to append internal server names and IT contact information fields to the conn.log to accelerate investigations and remediation workflows. Learn more.
Enhancing DNS visibility
Use Zeek’s / Bro's dns.log—which contains both queries and responses—to access forensic information server logs can’t provide, due to a lack of detail. Learn more.
Identifying vulnerable software
Use Zeek’s / Bro's software.log to identify outdated or vulnerable software, such as Java or Flash, running in an environment. Watch video.
Flagging Cyrillic keyboard usage
Monitor Zeek’s / Bro's rdp.log to identify the use of Russian character set keyboards in an environment, which could signal unusual behavior.
Verifying that sensitive connections use strong encryption
Verify via Zeek’s / Bro’s ssl.log that all TLS sessions for sensitive connections use appropriately strong ciphers, and prompt security ops staff to take remedial action if less secure ciphers are detected. Watch video.
Creating inventories of connected devices
Inventory network-connected devices and their services without needing to install host agents, and use Zeek’s / Bro’s software.log to monitor BYO software used by employees. Watch video.
Monitoring risky SSL certificates
Monitor self-signed and expired, or soon-to-expire, certificates via Zeek’s / Bro’s ssl.log. Watch video.
Troubleshooting a load balancer issue
Diagnose a load balancer performance problem that is difficult or impossible to replicate in a lab environment via evidence gathered from Zeek’s / Bro’s network logs and end finger pointing between security and network operations teams.