Playbook Development
Build a tailored, go-to guide for handling an incident
TrustedSec helps organizations document steps that analysts and investigators will perform during the hands-on Incident Response process.
Organizations often respond to the same types of incidents over and over again. From malware to phishing to ransomware, oftentimes the attack scenarios are the same. Because of this, analysts and responders tend to perform the same tasks when responding to these events. However, most organizations find that these tasks are based on ad hoc knowledge, not performed consistently, and not documented. The solution to best protect against these types of issues is to create Incident Response Playbooks.
The creation and utilization of Incident Response Playbooks allows analysts to respond to an incident consistently, ensures that correct procedures are followed, and provides an organization with a roadmap to determine where processes can be automated and enhanced to improve critical response time.
A proven process to excel at a critical moment
With their years of experience, TrustedSec’s Incident Response team is able to provide a unique insight into attacks and assist in creating Incident Response Playbooks. This process includes:
- Determining what common incidents an organization is seeing and reviewing industry research;
- Interviewing appropriate personnel to find the tools used in current procedures or processes; and
- Documenting the methods critical for success prescribed with the organization’s input.
Get real security guidance from real security experts.
Experts across security domains are ready to tackle your security challenges.
Read our blog
Explore the latest cybersecurity topics on the TrustedSec Security Blog
Building a Detection Foundation: Part 5 - Correlation in Practice
From Data Sources to DetectionWe've covered a lot of ground in this series: Windows Security events for logon tracking and process execution; PowerShell…
Building a Detection Foundation: Part 4 - Sysmon
Filling the Gaps Native Logging Can'tAt this point in our series, we have Windows Security events capturing logon sessions and process creation, and…
Building a Detection Foundation: Part 3 - PowerShell and Script Logging
The Second Most Important Data Source You're Probably Not CapturingIn Part 2, we enabled process creation logging with command lines. That's a big…
Building a Detection Foundation: Part 2 - Windows Security Events
The Audit Policies Nobody ConfiguresIn Part 1, we looked at why relying on a single telemetry source is a recipe for blind spots. Now let's get practical.…
Building a Detection Foundation: Part 1 - The Single-Source Problem
The Uncomfortable Truth About Your Telemetry Let me start with an observation that might hit close to home. In my years working Incident Response cases and…
Adventures in Primary Group Behavior, Reporting, and Exploitation
If you’ve administered Active Directory (AD) for any significant time, chances are you’ve come across the primaryGroupID attribute. Originally developed as a…
Updating the Sysmon Community Guide: Lessons Learned from the Front Lines
Over the past few weeks I’ve been spending a significant amount of time updating the Sysmon Community Guide. This wasn’t driven by theory, trends, or what…
Hiding in the Shadows: Covert Tunnels via QEMU Virtualization
Attackers are getting increasingly creative—not just with their payloads, but with how they deliver and operate them. In a recent Incident Response engagement,…
Gobbling Up Forensic Analysis Data Using Velociraptor
Lately I have been working with Velociraptor for its endpoint and digital forensic capabilities and specifically spent time in many cases in the past two years…
Observations From Business Email Compromise (BEC) Attacks
Since joining TrustedSec, I have gotten to work numerous cases, and each of them is like unraveling a mystery to get at the truth—especially the situations…