Showing posts with label Corelight. Show all posts
Showing posts with label Corelight. Show all posts

Threat Hunting: Unveiling the Ghosts in the Machine with Corelight and Microsoft Sentinel

The digital realm is a battlefield. Not just for the attackers who claw at the gates, but for the defenders who patrol its darkened corridors. In this war, intel is everything. But have you ever wondered if you have what it takes to be the one hunting the predators, rather than just being the prey? Today, we're not just discussing the theory; we're diving deep into the practicalities, dissecting a simulated attack. We'll weave together the threads of network evidence and endpoint telemetry, using the potent combination of Corelight and Microsoft Defender 365, orchestrated through Microsoft Sentinel. Forget the passive watch tower; this is about proactive engagement, about understanding the enemy's playbook so you can dismantle it before it causes irreparable damage.

This isn't about finding the obvious malware signature; it's about spotting the subtle anomaly, the whisper in the server logs, the digital footprint of an intruder who believes they're invisible. It's about piecing together fragments of data to reconstruct a narrative of compromise, and then neutralizing the threat before it escalates. Welcome to the heart of Sectemple – where we transform curiosity into capability, and passive observation into aggressive defense.

The landscape of cybersecurity is a relentless tide of evolving threats. Attackers, fueled by desperation or pure malice, are constantly devising new ways to breach defenses. They are the shadows, the ghosts in the machine, operating in the blind spots that every organization inevitably possesses. But what if you could turn the tables? What if you could leverage sophisticated tools and methodologies to hunt these adversaries down, to understand their motives, their tactics, and their ultimate goals? That's the essence of threat hunting – transforming your security posture from a reactive fire brigade into a pre-emptive strike force.

The Unseen Enemy: Why Traditional Defenses Aren't Enough

For years, we've relied on perimeter security, firewalls, intrusion detection systems – the metaphorical castle walls. These are essential, don't get me wrong. They're the first line of defense, designed to keep out the known threats. But the modern attacker isn't lumbering through the main gate anymore. They're finding the unlocked window, the back alley entrance, the cleverly disguised social engineering ploy. They dwell within your network, moving laterally, exfiltrating data, and often remaining undetected for months.

This is where the limitation of traditional security solutions becomes apparent. They are designed to detect known bad, not to uncover the unknown good. They excel at flagging blatant violations, but they often miss the subtle, insidious actions of a determined adversary who understands your systems better than you do.

Consider the sheer volume of data generated by a corporate network. Logs from firewalls, servers, endpoints, applications – it's an ocean of information. Sifting through this manually is an impossible task. Automated tools can help, but they are often tuned to look for specific signatures, leaving a vast expanse of potentially malicious activity unchecked.

"The greatest security is not having a firewall, but knowing where the fire is and how to put it out before it spreads." - Unknown Architect of Digital Fortresses

This is the crucial gap that threat hunting aims to fill. It’s not about replacing your existing security stack; it’s about augmenting it. It’s about empowering your security team with the mindset and the tools to proactively search for threats that have bypassed or are evading your automated defenses.

The Hunter's Arsenal: Corelight, Microsoft Defender 365, and Sentinel

To effectively hunt, you need the right tools. Today’s digital detective relies on a sophisticated arsenal, and the synergy between network and endpoint data is paramount. This is where the combination of Corelight, Microsoft Defender 365, and Microsoft Sentinel shines.

Corelight: The Network's Nervous System

Corelight, built on the open-source Zeek (formerly Bro) framework, provides unparalleled visibility into network traffic. It doesn't just log packets; it interprets them, creating rich, structured data logs that detail connections, protocols, file transfers, and even suspicious command-line arguments. Think of it as the network's nervous system, providing detailed insights into every interaction happening across your infrastructure. This data is invaluable:

  • Connection Details: Source and destination IPs, ports, duration, and volume of data transfer.
  • Protocol Analysis: Deep inspection of application-layer protocols like HTTP, DNS, SMB, and more.
  • File Extraction: Captures and analyzes files transmitted over the network.
  • Behavioral Insights: Identifies unusual connection patterns or protocol anomalies.

Microsoft Defender for Endpoint (MDE): The Eyes on the Ground

While Corelight watches the network highways, Microsoft Defender for Endpoint (MDE) is your eyes and ears on the individual machines – the endpoints. MDE provides robust endpoint detection and response (EDR) capabilities. It monitors processes, file activity, registry changes, and network connections originating from endpoints. This telemetry is critical for understanding what's happening *on* a machine during a suspected intrusion.

  • Advanced Threat Detection: Machine learning and behavioral analytics to spot novel threats.
  • Endpoint Investigations: Rich post-breach forensic data, including process trees and network connections.
  • Vulnerability Management: Identifies weaknesses on endpoints that attackers could exploit.
  • Attack Surface Reduction: Tools to block malware and malicious activities before they execute.

Microsoft Sentinel: The Intelligence Hub

Bringing these two powerful data sources together is Microsoft Sentinel, a cloud-native Security Information and Event Management (SIEM) and Security Orchestration, Automation, and Response (SOAR) solution. Sentinel ingests logs from a vast array of sources, including Corelight and MDE, and uses its analytics engine to correlate events, detect threats, and automate responses.

  • Unified Data Ingestion: Connects to both cloud and on-premises data sources.
  • Intelligent Analytics: Leverages AI and machine learning for threat detection.
  • Automated Playbooks: Orchestrates responses to detected threats.
  • Threat Hunting Interface: Provides a powerful query interface for proactive investigation.

When you combine the granular network insights from Corelight with the deep endpoint telemetry from MDE, and feed it all into Sentinel, you create a comprehensive view of an incident. You can trace an attack from its initial network ingress, through its lateral movement across endpoints, to its final objective.

Anatomy of a Simulated Attack: A Threat Hunter's Perspective

Let's walk through a hypothetical (but realistic) scenario. Imagine an attacker gains initial access through a phishing email containing a malicious attachment on a user's workstation. This is where the hunt begins.

Phase 1: Initial Access and Reconnaissance

The user clicks the attachment, which executes a payload. This payload might be a simple dropper, or it could be more sophisticated, establishing a reverse shell or downloading a more advanced implant. From the MDE perspective, we'd see an unusual process spawning from a legitimate application (e.g., Word or Outlook). We'd monitor its network connections and any outbound communication.

Corelight, meanwhile, would log the connection initiated by the workstation. We'd see the destination IP, the port used, and the protocol. If the attacker is scanning the internal network for further targets, Corelight would log this reconnaissance activity – perhaps using SMB or RDP to probe other machines. Sentinel would correlate these events: the suspicious process on the endpoint from MDE, and the unusual network connections logged by Corelight, flagging this as a potential high-fidelity alert.

Phase 2: Lateral Movement

The attacker now aims to move deeper into the network. They might use stolen credentials, exploit a vulnerability, or leverage administrative tools to access other machines. MDE would detect the abnormal login attempt or the exploit execution on a new endpoint. Simultaneously, Corelight would log the connection between the compromised machine and the new target, detailing the protocol (e.g., SMB for file sharing or RDP for remote desktop).

Sentinel's role here is crucial. By correlating the MDE alert on the target machine with the Corelight logs showing the connection *from* the initially compromised host, the threat hunter can confidently identify the lateral movement. This is far more powerful than just seeing an alert on one machine in isolation. You're seeing the attacker's path.

Phase 3: Objective Execution (Data Exfiltration)

The attacker's goal might be data theft. They'll locate sensitive files, consolidate them, and then attempt to exfiltrate them. MDE would observe the unusual file access and potential staging of data. More importantly, it would see any attempts to compress or encrypt large volumes of data, or to establish outbound connections to suspicious external IPs.

Corelight would provide visibility into the outbound data transfer. We could analyze the volume, the destination, and potentially even extract the files being transferred if they are unencrypted. Sentinel enables the threat hunter to query logs for patterns indicative of exfiltration: large outbound transfers to unusual destinations, use of non-standard ports for data egress, or connections to known command-and-control (C2) infrastructure.

The Threat Hunter's Mindset: Beyond the Alerts

Being a threat hunter isn't just about mastering tools. It's about adopting a specific mindset. It requires:

  • Curiosity: Always asking "what if?" and "why is this happening?"
  • Skepticism: Not taking logs at face value, but questioning anomalies.
  • Methodology: Having a structured approach to investigations, from hypothesis to remediation.
  • Technical Depth: Understanding operating systems, networks, and common attack techniques.
  • Data Fluency: Being able to query, analyze, and interpret large datasets effectively.

Threat hunting is about looking for the 'unknown unknowns' – the threats that no one anticipated. It's a continuous process of hypothesis generation, data collection, analysis, and refinement. You hypothesize that an attacker might be using a specific C2 channel, then you query Corelight logs for connections to suspicious IPs on unusual ports. You hypothesize that an insider is exfiltrating data, then you examine MDE logs for large data movements and Corelight logs for unusual outbound transfers.

Veredicto del Ingeniero: ¿Estás Listo para Cazar?

The tools we've discussed – Corelight, MDE, and Sentinel – represent the cutting edge of threat detection and response. They provide the visibility and intelligence needed to hunt effectively. However, owning the best tools doesn't automatically make you a great hunter. It requires dedication, continuous learning, and a willingness to think like the adversary.

The question isn't just "Could you be a threat hunter?" It's "Are you willing to commit to the relentless pursuit of truth in the digital shadows?" The attackers aren't resting. Neither can the defenders. Investing in these technologies is a significant step, but the true power lies in the human element – the analyst who knows how to wield them, who possesses the analytical prowess to see patterns where others see noise.

Arsenal del Operador/Analista

  • Corelight: For deep network visibility and Zeek logs.
  • Microsoft Defender for Endpoint: For comprehensive endpoint telemetry and response.
  • Microsoft Sentinel: For SIEM/SOAR, data correlation, and proactive threat hunting queries.
  • KQL (Kusto Query Language): The language of Sentinel – essential for crafting effective hunt queries.
  • Python: For scripting custom analysis or automating tasks with log data.
  • Books: "The Microsoft Sentinel Playbook: Security Operations and Automation" for mastering the platform.
  • Certifications: Microsoft Certified: Security Operations Analyst Associate (SC-200) for validated skills.

Taller Práctico: Primeros Pasos en la Detección con Sentinel

Let's start with a simple hunt query in Microsoft Sentinel to search for unusual outbound SMB connections, a common lateral movement technique. This requires that you have Corelight data (or equivalent Zeek logs) and MDE data ingested into Sentinel.

  1. Hypothesize: Attackers often use SMB (port 445) to move laterally between Windows machines. Large or unusual SMB connections could indicate reconnaissance or data staging.

  2. Formulate Query: Navigate to the Logs section in Microsoft Sentinel and use KQL.

    
    SecurityConnection
    | where RemotePort == 445
    | where Direction == "Outbound"
    | summarize count() by SourceIp, RemoteIp, bin(TimeGenerated, 1h)
    | where count_ > 5  // Adjust threshold based on your network baseline
    | order by count_ desc
            
  3. Analyze Results: Examine the output. High counts from a single SourceIp to multiple RemoteIps within an hour could indicate scanning. High counts from one SourceIp to one RemoteIp could indicate large file transfers. Investigate any suspicious IPs or connections further using MDE and other Corelight logs.

  4. Refine: Add conditions to filter by specific processes if available in your logs, or correlate with other suspicious activities seen on the SourceIp from MDE data.

Preguntas Frecuentes

¿Qué es la diferencia entre IDS y Threat Hunting?

An Intrusion Detection System (IDS) is primarily reactive, alerting on known malicious signatures or policy violations. Threat hunting is proactive, actively searching for undetected threats based on hypotheses and behavioral analysis, even when no alert has fired.

Do I need Corelight specifically?

While Corelight provides excellent, structured Zeek logs, the principle applies to any robust network data source. The key is having rich, interpretable network telemetry ingested into your SIEM like Sentinel.

How much data can Microsoft Sentinel handle?

Sentinel is a cloud-native solution designed for scalability. It can ingest and analyze vast quantities of data from diverse sources, limited primarily by your Azure subscription's capacity and cost considerations.

El Contrato: Tu Próxima Misión de Caza

Now that you've seen the gears and levers of proactive defense, your mission, should you choose to accept it, is to consider your own network's visibility. Do you have the data? Do you have the tools? More importantly, do you have the *mindset*?

Your challenge: Identify one potential threat hunting hypothesis that is relevant to your environment (e.g., "Detecting suspicious RDP connections to servers outside business hours," or "Identifying unusual DNS queries to known malicious domains"). Then, outline the data sources you would need (network logs, endpoint logs, etc.) and the type of queries you might construct in a SIEM like Sentinel to test that hypothesis. Document your thought process. The digital shadows are vast; start by illuminating your own corner.

Threat Hunting in the Modern SOC: A Comprehensive Splunk and Corelight Analysis

The Shadow Beneath the Surface

The flickering lights of the SOC are often a facade, hiding the relentless, unseen battle against adversaries who move like phantoms in the network. Threat hunting isn't just a buzzword; it's the proactive, deep-dive investigation into your own systems, seeking the anomalies that traditional defenses miss. It’s an art born from necessity, a meticulous dissection of digital entrails to find the whispers of compromise before they become screams. Today, we’re dissecting a potent combination for this grim work: Splunk and Corelight.

Threat Hunting vs. Incident Response: Two Sides of the Same Coin

Many confuse threat hunting with incident response (IR). Let's be clear: they are fundamentally different, yet complementary, disciplines. Incident response is reactive; it kicks in when an alarm sounds, a breach is confirmed. Your IR team scrambles to contain, eradicate, and recover. Threat hunting, on the other hand, is *proactive*. It’s the hunter stalking the prey, armed with hypotheses, not alerts. It’s about finding the intruder who hasn't triggered a single alarm yet, the one who knows how to lie low.
"The difference between attacking and defending is perception. The attacker sees a lock, the defender sees a potential weak point." - Anonymous
While IR deals with knowns and immediate threats, threat hunting dives into the unknown, using advanced analytics and deep network visibility to uncover hidden malicious behavior. It’s the difference between calling the fire department when your house is engulfed in flames and patrolling your neighborhood at midnight looking for suspicious activity.

The Next-Generation SOC Stack: Splunk, Corelight, and SOAR

The modern Security Operations Center (SOC) needs more than just a SIEM. It requires a layered, integrated approach that combines the power of data aggregation, deep network intelligence, and automated response. This is where the synergy between Splunk, Corelight, and Splunk Phantom SOAR comes into play.
  • **Splunk SIEM**: The central nervous system. It collects, indexes, and analyzes vast amounts of log data from across your entire IT infrastructure. It’s your primary tool for correlation, alerting, and historical analysis. Without comprehensive data ingestion, even the best hunting techniques falter.
  • **Corelight NDR**: The eyes and ears. Built on the industry-standard Zeek (formerly Bro) framework, Corelight provides unparalleled visibility into network traffic. It doesn’t just log connections; it generates rich, high-fidelity network metadata, offering insights into protocols, file transfers, TLS sessions, and even suspicious command-and-control (C2) communications that raw packet captures might miss or that traditional firewalls ignore. This deep packet inspection (DPI) and behavioral analysis are critical for threat hunting.
  • **Splunk Phantom SOAR**: The rapid response arm. When a threat is identified, either through proactive hunting or an alert, SOAR automates the repetitive, time-consuming tasks. It orchestrates playbooks, integrates with other security tools, and executes actions like isolating an endpoint, blocking an IP address, or fetching threat intelligence, thereby drastically reducing the mean time to respond (MTTR).
This trifecta forms a powerful weapon against modern threats, enabling teams to move from passive monitoring to active threat discovery and rapid remediation.

Why Corelight NDR Powered by Zeek is the Gold Standard

Zeek has been a staple in network security analysis for years, beloved by researchers and security professionals for its powerful scripting capabilities and deep protocol parsing. Corelight takes this open-source foundation and hardens it for enterprise deployment, adding critical features for high-performance networks and sophisticated threat detection. Corelight’s value proposition for threat hunting lies in its ability to generate actionable, high-fidelity network metadata. Unlike raw packet captures (PCAP) that are often voluminous and require deep forensic expertise to parse, or basic NetFlow data that lacks context, Corelight’s logs are structured and informative. They provide:
  • **Comprehensive Protocol Analysis**: Deep understanding of HTTP, DNS, SMB, SMTP, and many other protocols, including conversation details.
  • **File Extraction**: Capability to extract files traversing the network for malware analysis.
  • **TLS/SSL Decryption Insights**: Metadata on certificates, cipher suites, and JA3/JA3S hashes for identifying malicious encryption usage.
  • **Behavioralytics**: Detection of anomalies and suspicious patterns in network behavior.
This rich stream of data, when fed into Splunk, provides the granular context hunters need to distinguish between benign network chatter and stealthy adversarial activity. It's the difference between finding a needle in a haystack and having a finely tuned magnet to pull that needle out.

The Corelight and Splunk Joint Solution Advantage

When Corelight’s deep network intelligence meets Splunk's powerful analytics engine, the result is a potent force multiplier for any SOC. The joint solution offers several key advantages:
  • **Rapid, Precise Answers**: Corelight provides the high-quality, contextualized data, and Splunk’s search processing language (SPL) allows analysts to rapidly query, pivot, and visualize this data. This means faster answers to critical security questions. Instead of wading through raw packets, a hunter can ask Splunk: “Show me all DNS requests for known malicious domains originating from *this* internal IP range in the last 24 hours.”
  • **Enhanced Threat Detection**: The combination allows for the creation of highly specific detection rules. For example, hunting for living-off-the-land techniques can be significantly enhanced by analyzing PowerShell execution logs (from Splunk) correlated with unusual network connections observed by Corelight.
  • **Streamlined Investigation**: When an alert fires or a hypothesis is being tested, the tight integration means analysts can jump from a Splunk dashboard to the relevant Corelight logs, and vice-versa, with minimal friction. This reduces the time spent on context switching and increases the time spent on actual analysis.
  • **Automation Potential**: By feeding Corelight data into Splunk, and then orchestrating response through Splunk Phantom, the entire lifecycle from detection to remediation can be significantly accelerated. Imagine identifying a suspicious SMB session via Corelight, creating an alert in Splunk, and then having Phantom automatically isolate the source machine.
This integrated approach moves beyond siloed tools, creating a cohesive ecosystem where each component amplifies the capabilities of the others.

Network Security Use Cases: Where the Hunt Truly Begins

The real power of this integrated solution shines when applied to specific threat hunting scenarios. Here are a few common use cases:
  • **Malware C2 Communication Detection**: Hunting for command-and-control (C2) beaconing. Corelight can identify suspicious DNS requests, unusual HTTP User-Agents, or connections to known bad IPs. Splunk can then be used to pivot from these indicators to analyze the source machine's other network activities, logged processes, or user activity.
  • **Lateral Movement Identification**: Adversaries frequently move laterally within a network after initial compromise. Corelight logs can reveal unusual SMB, RDP, or WinRM traffic patterns between internal machines that don’t typically communicate. Splunk can correlate this with endpoint logs to identify the specific processes or users involved.
  • **Data Exfiltration Detection**: Monitoring for large outbound file transfers, especially to unusual destinations or outside of business hours. Corelight's file analysis and connection logs are invaluable here. Splunk can then help identify the source of the data and the user responsible.
  • **Suspicious TLS/SSL Usage**: Identifying self-signed certificates, expired certificates used in C2, or connections to known malicious JA3/JA3S hashes. Corelight provides these metrics, allowing Splunk to flag potentially compromised internal systems or external threats.
The key is to leverage the *context* provided by Corelight's network metadata within Splunk's powerful analytical framework.

Practical Demo: Threat Hunting in Action

In a typical threat hunt using Corelight and Splunk, the process might look like this: 1. **Hypothesis Formulation**: You suspect a specific type of malware known for its distinctive network beaconing. 2. **Data Collection (Implicit)**: Corelight continuously streams network metadata to Splunk. 3. **Splunk Querying**: You craft a Splunk SPL query targeting specific patterns observed in Corelight logs. For example, looking for unusual HTTP POST requests with specific User-Agents, or repeated DNS queries to non-existent domains. ```spl index=main sourcetype=corelight:http OR sourcetype=corelight:dns | search uri="/malicious_path" OR user_agent="SuspiciousAgent/1.0" | stats count by src_ip, dest_ip, _time | sort -count ``` 4. **Analysis and Pivot**: If the query returns results, you examine the source IPs and suspicious patterns. You might then pivot to other Corelight log types (e.g., `corelight:files` to see if any files were transferred) or Splunk logs (e.g., endpoint security logs) for the identified `src_ip`. 5. **SOAR Integration**: If suspicious activity is confirmed, you trigger a Splunk Phantom playbook. This could automatically enrich the alert with threat intelligence, query other security tools, and potentially isolate the suspect endpoint. This iterative process, moving from hypothesis to data to action, is the core of effective threat hunting. The Corelight and Splunk integration makes each step faster and more insightful.

Engineer's Verdict: Is This the Future of SOC Defense?

The integration of deep network visibility (Corelight/Zeek) with a robust SIEM (Splunk) and an automated SOAR platform represents a significant leap forward for modern SOC operations. It addresses the increasing sophistication of threats that bypass traditional signature-based defenses. **Pros:**
  • **Unparalleled Network Visibility**: Corelight provides granular, actionable network metadata that is crucial for detecting stealthy threats.
  • **Powerful Analytics**: Splunk excels at processing, correlating, and visualizing massive datasets, making complex hunting investigations feasible.
  • **Automation**: Splunk Phantom dramatically reduces response times and analyst workload.
  • **Synergy**: The combined solution creates a defense-in-depth strategy that is far greater than the sum of its parts.
  • **Industry Standard**: Both Splunk and Zeek (as the foundation of Corelight) are widely adopted and respected in the security community.
**Cons:**
  • **Complexity and Cost**: Implementing and managing a full-stack solution like this requires significant investment in terms of licensing, hardware, and skilled personnel.
  • **Steep Learning Curve**: Mastering SPL for advanced Splunk queries and understanding the nuances of Zeek logs requires dedicated training and experience.
  • **Data Volume**: The sheer volume of data generated can be overwhelming if not properly managed, indexed, and stored.
Overall, this integrated approach is not just the future; it’s a present-day necessity for organizations serious about proactive defense. For those willing to invest the resources, it provides a formidable capability to hunt down and neutralize advanced threats.

Operator's Arsenal: Essential Tools for the Hunt

To excel in threat hunting, an analyst needs a well-equipped toolkit:
  • **Corelight & Splunk**: The foundational elements for network visibility and log analysis. A subscription to Corelight and proper Splunk licensing are essential.
  • **Splunk Phantom**: For automating response actions.
  • **Zeek (Standalone/Remote Probes)**: For analyzing specific network segments or for environments where a full Corelight deployment isn't feasible.
  • **Wireshark/tcpdump**: For deep packet inspection when metadata isn't enough or for initial data capture.
  • **Threat Intelligence Platforms (TIPs)**: To ingest and correlate threat feeds into Splunk.
  • **Endpoint Detection and Response (EDR)**: To correlate network findings with endpoint activity.
  • **Python with Libraries**: For custom scripting, automation, and data analysis (e.g., `pandas`, `requests`, `scapy`).
  • **Books & Certifications**:
  • "The Web Application Hacker's Handbook" (for web-centric threats affecting network traffic)
  • "Practical Threat Hunting: From Data to Actionable Intelligence"
  • Splunk Certifications (e.g., Enterprise Certified Admin, Certified Threat Hunter)
  • Corelight Training
  • Network Security Certifications (e.g., CCNA Security, Network+)
This isn't a cheap arsenal, but the cost of not having it is far higher.

Frequently Asked Questions

  • Q: What is the primary difference between threat hunting and incident response?
    A: Threat hunting is proactive, seeking unknown threats before they are detected. Incident response is reactive, dealing with confirmed security events.
  • Q: What kind of data does Corelight provide that is useful for threat hunting?
    A: Corelight generates rich network metadata, including detailed protocol analysis, file extraction, TLS insights, and behavioral analytics, which is far more contextual than raw logs or NetFlow.
  • Q: How does Splunk Phantom fit into the threat hunting workflow?
    A: Splunk Phantom automates response actions based on findings from threat hunting or alerts, significantly reducing the time from detection to remediation.
  • Q: Is it possible to do effective threat hunting with just a SIEM?
    A: While a SIEM is critical, effective threat hunting often requires deeper network visibility than a SIEM alone can provide. Combining SIEM with NDR (like Corelight) is optimal.
  • Q: Where can I learn more about Zeek for network analysis?
    A: The official Zeek website (zeek.org) and the Corelight documentation are excellent resources.

The Contract: Your Engagement Rules

The digital shadows are vast, and the adversaries are relentless. You've seen the architecture, the tools, and the methodology. Now, it's your turn to engage. **Your Challenge:** Imagine you've received a tip about a potential insider threat using covert channels to exfiltrate data via DNS tunneling. Using the principles discussed, outline a specific Splunk query (leveraging hypothetical Corelight logs for DNS and potentially TLS) you would use to hunt for this activity. Detail what you would look for in the results and which logs you might pivot to next for further investigation. This isn't about theoretical knowledge; it's about the cold, hard application of skill. Show us your hunting grounds. The network waits for no one.