SEC504: Hacker Tools, Techniques, and Incident Handling

Experience SANS training through course previews.
Learn MoreLet us help.
Contact usConnect, learn, and share with other cybersecurity professionals
Engage, challenge, and network with fellow CISOs in this exclusive community of security leaders
Become a member for instant access to our free resources.
Sign UpMission-focused cybersecurity training for government, defense, and education
Explore industry-specific programming and customized training solutions
Sponsor a SANS event or research paper
We're here to help.
Contact UsDatadog’s Zack Allen joined to share threat intelligence resources and discuss tools and methodologies for analysts.
On this month’s SANS Threat Analysis Rundown, I was joined by Zack Allen, Senior Director of Security Research and Detection at Datadog, and author of the excellent weekly newsletter Detection Engineering Weekly. We covered a range of topics, from detection engineering and threat intelligence to group naming and recent compromises. Here's a recap of the discussion.
Zack began by discussing his Detection Engineering Weekly newsletter, a resource he has maintained for over two years, in which he curates cybersecurity news, threat intelligence, and detection research. He explained that his sources include Reddit communities, RSS feeds, and security Slack groups, highlighting the importance of staying informed across multiple platforms. We discussed how we missed the height of “threat intel Twitter” (those were the days!), and I noted that Zack’s newsletter is one of the sources I use every month to prepare for STAR. We discussed how detection engineering and threat intelligence are complementary, with Zack emphasizing that good detection engineers must understand threats deeply to write effective detections.
Annual threat reports are also great resources for threat intelligence, and this is the time of the year when many of them are released. There’s a cool repository that contains many of these reports that I recommend checking out: Awesome Annual Security Reports. These reports are not just for passive reading—organizations should use them to inform their detection strategies by identifying common intrusion chains, prioritizing patching, and refining detections based on emerging threats. It’s worth looking at security reports from our own organizations, too: Datadog’s State of Cloud Security Report and Red Canary’s 2025 Threat Detection Report.
Zack shared several resources from his most recent Detection Engineering Weekly newsletter, including a TrustedSec blog outlining how red teams help improve blue team defenses by simulating real-world attacks. As Zack pointed out, red teamers make excellent detection engineers because they understand how attacks get caught and can design better detection rules. Zack and I agree that organizations don’t need perfect security—even one well-placed detection could block an entire intrusion chain. Regular adversary simulations combined with threat intelligence can dramatically improve an organization’s resilience.
In our chat, we highlighted several recent threat reports that are notable and worth knowing about. These include:
There are tools and methodology available to analysts and defenders, including GuardDog, an open-source tool that detects malware within Python, npm, and Ruby packages. Zack’s team at Datadog found that adversaries are now specifically targeting security researchers and red teamers by planting malware in offensive security tools, and this tool can help identify that.
We also discussed a contentious topic, the naming of threat actors, as outlined in this blog post from Ryan Dewhirst. We acknowledge that there are pros and cons of different naming conventions, and that while names can be marketing-driven, they also help analysts quickly identify adversary clusters.
A blog about Lazarus Group infrastructure analysis was another source Zack highlighted in his newsletter due to how it demonstrated infrastructure hunting techniques using pivoting methods to track threat actor IP addresses and domains. Zack highlighted how open-source intelligence (OSINT) tools allow defenders to uncover relationships between domains, VPS providers, and malicious infrastructure. I added to that, that better attribution tracking and sourcing could help the community avoid duplicating work.
We closed by highlighting a few events to check out:
Make sure to tune in for next month’s STAR Livestream and check out Zack’s Detection Engineering Weekly newsletter for more threat insights!
Katie is the Director of Intelligence at Red Canary. She has worked on cyber threat intelligence, network defense, and incident response for nearly a decade for the U.S. Department of Defense, MITRE, Raytheon, and ManTech.
Read more about Katie Nickels