A library of toolchains to adopt, follow, and spark inspiration.
Each one completes a real job, start to finish, and describes the tools it uses and its configuration of steps. Toolchains also tell you when their tools are swappable for other tools you may have in your stack or are thinking about adopting.
A stack is the tools you use. A toolchain is how they work together to get a job done.
No toolchain matches.Clear the search or a filter.
Protect · NIST CSF
This toolchain helps you remediate a known-exploited flaw on an internet-facing server.
A server with a known-exploited vulnerability faces the internet: the flaw is on CISA's Known Exploited Vulnerabilities (KEV) list, so attackers are already using it. The team blocks the risk first, patches it, and moves the server so it's reachable only through the approved private access path.
Estimated price
Not estimated yet
Time to deploy
Not estimated yet
People to deploy
Not estimated yet
The chain11 steps · 4 mapped
Mapped
Not mapped yet
A person does it
Steps20 tools named
Your attack surface scanner finds a server on the internet running a version with a known flaw.
Tools that fit this step
runZeroCensysnaabu
→ Hands to Vulnerability scanner
The flaw is on CISA's KEV list, so attackers are already using it. That puts it at the top of the queue.
→ Hands to Vulnerability scanner
A vulnerability scanner looks at the server up close and confirms the flaw, the version and the port an attacker would use.
Tools that fit this step
Tenable NessusQualys VMDRRapid7 InsightVMnuclei
What a tool must do
core Scans hosts for published CVEs
core Reports the affected version and port
core Scans one host on demand
core Hands findings to other tools
→ Hands to CMDB
The CMDB says who owns the server and what it's for. It's still needed, but only by people inside the company.
Tools that fit this step
ServiceNow CMDBNetBox
→ Hands to Firewall, Ticketing
As a stopgap, a firewall rule blocks the port the flaw is reached through. The server stays up; the way in doesn't.
Tools that fit this step
Palo Alto NetworksFortiGatepfSense
→ Hands to Ticketing
The owner gets a ticket with the finding, the business context and the firewall rule, so nobody removes the block by accident.
Tools that fit this step
JiraServiceNow
What a tool must do
core Opens a ticket from another tool
core Assigns an owner
core Closes a ticket from another tool
extra Attaches evidence
→ Hands to Network change
Your network team moves the server off the internet into a private subnet. It's still needed, just not by the whole world.
→ Hands to VPN, Patch management
Staff reach the server over the VPN, the approved private access path, so it no longer has to face the internet.
Tools that fit this step
OpenVPNtailscaleWireGuard
The patch goes on. That fixes the flaw itself instead of hiding it.
Tools that fit this step
Microsoft IntuneAutomoxQualys Patch Management
→ Hands to Vulnerability scanner
The scanner checks the server again and no longer detects the flaw.
This toolchain helps you patch a critical flaw tonight, not next week.
A scan finds a critical flaw. The patch tool checks whether the fix is out and whether policy applies it on its own. Because it's critical, the patch moves up from its weekly window to tonight, right after business hours. If policy installs it automatically, automation reschedules it; if not, IT schedules a manual patch for the same window. IT and Security both know it's coming, and a second scan closes the loop.
Estimated price
Not estimated yet
Time to deploy
Not estimated yet
People to deploy
Not estimated yet
The chain8 steps · 0 mapped
Mapped
Not mapped yet
A person does it
Steps12 tools named
A scan finds a critical vulnerability on a group of servers.
The patch tool checks whether a patch is out, and whether policy installs it automatically or someone has to do it by hand. The chain takes one path or the other.
Tools that fit this step
Microsoft IntuneAutomoxIvanti Neurons for Patch ManagementManageEngine Patch Manager Plus
→ Hands to IT team, Automation
Manual path: if policy says it's a manual patch, IT schedules it for tonight's window.
→ Hands to Patch management
Automated path: policy installs it, so the scanner's severity overrides the weekly schedule. The patch is set for tonight, as soon as business hours end.
Tools that fit this step
TinesTorqShuffle
→ Hands to Ticketing, Patch management
A ticket flags it as an escalated patch, so IT and Security watch for anything that breaks after it goes on.
Tools that fit this step
JiraServiceNow
What a tool must do
core Opens a ticket from another tool
core Assigns an owner
core Closes a ticket from another tool
extra Attaches evidence
The patch goes on after hours.
Tools that fit this step
Microsoft IntuneAutomoxIvanti Neurons for Patch ManagementManageEngine Patch Manager Plus
→ Hands to Vulnerability scanner
The scanner checks the same servers again for the vulnerability.
This toolchain helps you turn an alert into a contained incident.
An alert looks like a real threat. The analyst confirms it, proves the machine was compromised, then blocks the attacker, finds out how they got in, patches that hole on every other machine, and verifies the fix with a rescan.
Estimated price
Not estimated yet
Time to deploy
Not estimated yet
People to deploy
Not estimated yet
The chain11 steps · 0 mapped
Mapped
Not mapped yet
A person does it
Steps23 tools named
The SIEM raises an alert. The analyst pulls the related logs and sees a real threat, so the alert becomes an investigation.
Tools that fit this step
Splunk Enterprise SecurityMicrosoft SentinelWazuh
→ Hands to Case management
The investigation gets a case, so every finding from here on lands in one place.
Tools that fit this step
TheHivePalo Alto Cortex XSOAR
→ Hands to EDR
Logs can't say whether the machine was compromised. EDR data can: what ran, what it touched and who it talked to. It was compromised, so the investigation becomes an incident.
Tools that fit this step
CrowdStrikeSentinelOneVelociraptor
→ Hands to SOAR
The incident response playbook starts.
Tools that fit this step
TinesPalo Alto Cortex XSOARShuffle
→ Hands to Firewall, Malware sandbox, Threat hunting
SOAR blocks the attacker's addresses at the firewall.
Tools that fit this step
Palo Alto NetworksFortiGatepfSense
The malware runs in a sandbox, which shows what it does and how it got in: a vulnerability on the machine.
Tools that fit this step
Joe Security (Joe Sandbox)CAPEv2
→ Hands to Vulnerability scanner
A threat hunt looks for the same activity on other machines.
Tools that fit this step
VelociraptorCrowdStrikeSentinelOne
→ Hands to Vulnerability scanner
A scan finds every other machine on the network with the same vulnerability.
Tools that fit this step
Tenable NessusQualys VMDRRapid7 InsightVM
What a tool must do
core Scans hosts for published CVEs
core Reports the affected version and port
core Scans one host on demand
core Hands findings to other tools
→ Hands to Ticketing
IT gets a ticket to patch those machines before the attacker, or anyone else, tries the same way in.
Tools that fit this step
JiraServiceNow
What a tool must do
core Opens a ticket from another tool
core Assigns an owner
core Closes a ticket from another tool
extra Attaches evidence
→ Hands to Patch management
IT patches every machine on the list and rebuilds the compromised one from a clean image.
Tools that fit this step
Microsoft IntuneAutomoxIvanti Neurons for Patch Management
→ Hands to Vulnerability scanner
A rescan no longer detects the vulnerability, and the hunt finds no new activity. Then the case closes.
The flaw is on [CISA's KEV list](https://www.cisa.gov/known-exploited-vulnerabilities-catalog), so attackers are already using it. That puts it at the top of the queue.
Takes in
Nothing comes in; this is where the chain starts.
Hands out
Vulnerability scanner (Tenable Nessus)
Example data not written yet.
What this step does
A vulnerability scanner looks at the server up close and confirms the flaw, the version and the port an attacker would use.
Scans hosts for published CVEs
Reports the affected version and port
Scans one host on demand
Hands findings to other tools
How we check
Scans hosts for published CVEs. A scan of a host with a known CVE reports that CVE id.
Reports the affected version and port. The finding for that CVE names the product version and the listening port.
Scans one host on demand. A scan can target one host by address without scanning the network.
Hands findings to other tools. Findings can be read or pushed as structured data through a documented API or integration.
Takes in
An exposed host the attack surface scanner found from Attack surface mgmt, runZero
JiraPicked for this chainIn your toolchainNot on our roster????
?Opens a ticket from another toolWe haven’t looked yet
?Assigns an ownerWe haven’t looked yet
?Attaches evidenceWe haven’t looked yet
?Closes a ticket from another toolWe haven’t looked yet
Price: We haven’t looked yetLicence: We haven’t looked yet
0 of 2 tools in this role have a decision on every requirement.
What this step does
A scan finds a critical vulnerability on a group of servers.
Scans hosts for published CVEs
Reports the affected version and port
Scans one host on demand
Hands findings to other tools
How we check
Scans hosts for published CVEs. A scan of a host with a known CVE reports that CVE id.
Reports the affected version and port. The finding for that CVE names the product version and the listening port.
Scans one host on demand. A scan can target one host by address without scanning the network.
Hands findings to other tools. Findings can be read or pushed as structured data through a documented API or integration.
Takes in
Nothing comes in; this is where the chain starts.
Hands out
Patch management (Microsoft Intune)
Example data not written yet.
Hand-offs here not checked yet
Tenable Vulnerability ManagementPicked for this chainIn your toolchainNot on our roster????
?Scans hosts for published CVEsWe haven’t looked yet
?Reports the affected version and portWe haven’t looked yet
?Scans one host on demandWe haven’t looked yet
?Hands findings to other toolsWe haven’t looked yet
Price: We haven’t looked yetLicence: We haven’t looked yet
What this step does
The patch tool checks whether a patch is out, and whether policy installs it automatically or someone has to do it by hand. The chain takes one path or the other.
Requirements not mapped yet. We have written requirements for Vulnerability scanner, Ticketing so far.
Manual path: if policy says it's a manual patch, IT schedules it for tonight's window.
Takes in
Patch management (Microsoft Intune)
Example data not written yet.
Hands out
Patch management (Microsoft Intune)
Example data not written yet.
What this step does
Automated path: policy installs it, so the scanner's severity overrides the weekly schedule. The patch is set for tonight, as soon as business hours end.
Requirements not mapped yet. We have written requirements for Vulnerability scanner, Ticketing so far.
Palo Alto Cortex XSOARIn your toolchainNot on our roster
What this step does
Logs can't say whether the machine was compromised. EDR data can: what ran, what it touched and who it talked to. It was compromised, so the investigation becomes an incident.
Requirements not mapped yet. We have written requirements for Vulnerability scanner, Ticketing so far.