--- name: containing-active-breach-0ba9f670cfdb description: 'Executes containment strategies to stop active adversary operations and prevent lateral movement during a confirmed security breach. Implements short-term and long-term containment using network segmentation, endpoint isolation, credential revocation, and access control modifications. Activates for requests involving breach containment, lateral movement prevention, network isolation, active threat containment, or live incident response. ' domain: cybersecurity subdomain: incident-response tags: - breach-containment - lateral-movement - network-isolation - credential-revocation - live-response mitre_attack: - T1021 - T1570 - T1210 - T1072 version: 1.0.0 author: Krishna Kumar (xalgord) license: Apache-2.0 nist_csf: - RS.MA-01 - RS.MA-02 - RS.AN-03 - RC.RP-01 --- # Containing Active Breaches ## When to Use - A confirmed intrusion is in progress with an active adversary on the network - Malware is spreading laterally across endpoints or servers - A compromised account is being used for unauthorized access to systems - Ransomware encryption has been detected and is actively propagating - An attacker has established command-and-control communications from internal hosts **Do not use** for post-incident cleanup when the adversary is no longer active; use eradication procedures instead. ## Common Misconfigurations & Verification - **Partial containment tips off the adversary:** isolating one host or blocking one C2 IP while the actor holds Domain Admin and three other beacons lets them detect the response and detonate (ransomware) or burrow deeper. Scope the *full* compromise first, then contain compromised hosts, accounts, and all C2 channels in one coordinated action. - **Power-off destroys evidence:** pulling the plug or shutting down wipes RAM (fileless payloads, injected code, encryption keys) and breaks chain of custody. Prefer EDR network-isolation that keeps the host powered and the agent reachable; reserve power-off for active mass-destruction you cannot otherwise stop. - **Credential containment that misses Kerberos:** disabling accounts and resetting passwords does NOT invalidate existing Kerberos tickets or golden tickets. If Tier-0/DA is compromised you must double-reset KRBTGT (twice, ~12h apart) or the attacker re-authenticates at will. Disable accounts, don't delete (preserve the audit trail). - **Persistence beyond the known account:** check for additional service accounts, scheduled tasks, and implants on non-EDR/legacy hosts before declaring contained. **Verify containment actually held:** confirm C2 beacons have ceased from *every* host (not just isolated ones), confirm disabled creds now produce 4625 failures with no new successes, confirm isolated hosts are unreachable from adjacent subnets, watch honeypot/canary accounts for adversary attempts to break out, and confirm the KRBTGT second reset completes — re-validate rather than assuming the first round worked. ## Prerequisites - Confirmed incident classification with P1 or P2 severity from triage - EDR console access with host isolation capabilities (CrowdStrike Falcon, Microsoft Defender for Endpoint, SentinelOne) - Network firewall and switch management access for segmentation - Active Directory or identity provider administrative access for credential actions - Pre-approved containment authority documented in the incident response plan - Evidence preservation plan to avoid destroying forensic artifacts during containment ## Workflow ### Step 1: Assess Containment Scope Before taking containment actions, map the full scope of compromise to avoid partial containment that alerts the adversary: - Identify all confirmed compromised hosts via EDR telemetry and SIEM correlation - Map lateral movement paths using authentication logs (Windows Event ID 4624 Type 3 and Type 10) - Identify all compromised credentials (check for pass-the-hash, Kerberoasting, DCSync activity) - Determine C2 channels (beacon intervals, domains, IPs, protocols) - Assess whether the adversary has domain admin or equivalent privileges ``` Containment Scope Assessment: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Compromised Hosts: 5 (WKSTN-042, WKSTN-087, SRV-FILE01, SRV-DC02, WKSTN-103) Compromised Accounts: 3 (jsmith, svc-backup, admin-tier0) C2 Channels: HTTPS beacon to 185.220.x.x every 60s ± 15% jitter Lateral Movement: PsExec via svc-backup, RDP via admin-tier0 Adversary Privilege: Domain Admin (admin-tier0 compromised) Data at Risk: Finance share (\\SRV-FILE01\finance$) accessed ``` ### Step 2: Execute Short-Term Containment Implement immediate actions to stop adversary operations without destroying evidence: **Network Containment:** - Isolate confirmed compromised endpoints via EDR network containment (maintains agent communication) - Block C2 IP addresses and domains at perimeter firewall and internal DNS - Implement microsegmentation rules to prevent communication between compromised hosts - Sinkhole C2 domains at internal DNS to capture connection attempts from undiscovered implants **Identity Containment:** - Disable compromised user accounts in Active Directory (do not delete; preserve audit trail) - Reset passwords for all compromised accounts - Revoke active sessions and tokens (Azure AD: `Revoke-AzureADUserAllRefreshToken`) - Disable the compromised service account and rotate its credentials - If Domain Admin is compromised: double-reset the KRBTGT password (reset twice, 12 hours apart) **Endpoint Containment:** - Use EDR to terminate malicious processes on contained hosts - Block known malicious hashes in EDR prevention policy - Quarantine identified malware samples - Disable remote services (WinRM, RDP, SMB) on critical servers not yet compromised ### Step 3: Execute Long-Term Containment Implement sustainable containment while the investigation continues: - Create network ACLs isolating the compromised VLAN/subnet while allowing business-critical traffic - Deploy temporary jump hosts for administrators to access contained systems for investigation - Implement enhanced monitoring (full packet capture) on network segments adjacent to compromised hosts - Enable advanced audit policies on all domain controllers (4768, 4769, 4771 for Kerberos attacks) - Deploy canary tokens and honeypot accounts to detect adversary attempts to expand from containment ### Step 4: Validate Containment Effectiveness Confirm that containment measures have stopped adversary operations: - Monitor for new C2 callbacks from any internal host to known adversary infrastructure - Check for new lateral movement attempts (failed authentication from disabled accounts) - Verify that contained hosts cannot reach the internet except through the EDR agent - Confirm that compromised credentials produce authentication failures - Review SIEM for any new alerts matching the adversary's known TTPs ``` Containment Validation Checklist: [x] C2 beacon traffic ceased from all known compromised hosts [x] Disabled accounts producing expected 4625 failure events (no new successes) [x] Contained hosts unreachable via network scan from adjacent subnets [x] No new hosts exhibiting IOCs from the initial compromise [x] Honeypot account has not been accessed (adversary may be dormant) [ ] Full packet capture running on finance VLAN (pending switch config) ``` ### Step 5: Preserve Evidence During Containment Containment must not destroy forensic evidence: - Capture memory dumps from compromised hosts before any remediation (use WinPmem or Magnet RAM Capture) - Collect volatile data: running processes, network connections, logged-on users, scheduled tasks - Export relevant event logs before they rotate (Security, System, PowerShell, Sysmon) - Capture network traffic between compromised hosts and C2 infrastructure - Document all containment actions with timestamps for the incident timeline ### Step 6: Communicate Containment Status Provide structured status updates to incident commander and stakeholders: - Current containment effectiveness (percentage of adversary activity stopped) - Remaining risks (undiscovered implants, persistence mechanisms not yet identified) - Business impact of containment actions (which systems are offline, user impact) - Estimated timeline for eradication phase - Escalation needs (law enforcement notification, external IR retainer activation) ## Key Concepts | Term | Definition | |------|------------| | **Short-Term Containment** | Immediate actions to stop active adversary operations; typically network isolation and credential disablement | | **Long-Term Containment** | Sustainable measures allowing continued investigation while preventing adversary re-access | | **KRBTGT Double Reset** | Resetting the KRBTGT password twice to invalidate all existing Kerberos tickets including golden tickets | | **Network Containment** | EDR feature that isolates an endpoint from all network communication except the EDR management channel | | **Lateral Movement** | Adversary technique of moving from one compromised system to another within a network using stolen credentials or exploits | | **C2 Sinkholing** | Redirecting DNS queries for C2 domains to an internal server to prevent adversary communication and detect additional victims | | **Microsegmentation** | Granular network access controls between workloads that limit lateral communication paths | ## Tools & Systems - **CrowdStrike Falcon**: Endpoint containment with one-click network isolation preserving agent connectivity - **Microsoft Defender for Endpoint**: Live response console for remote containment actions and evidence collection - **Palo Alto Networks NGFW**: Application-aware firewall rules for C2 traffic blocking and microsegmentation - **Velociraptor**: Open-source endpoint monitoring and response tool for artifact collection during containment - **BloodHound**: Active Directory attack path mapping to identify potential lateral movement routes the adversary may exploit ## Common Scenarios ### Scenario: Ransomware Lateral Propagation via SMB **Context**: EDR alerts on three file servers showing rapid file encryption. The ransomware is spreading via SMB using a compromised domain service account. **Approach**: 1. Immediately isolate all three file servers via EDR network containment 2. Disable the compromised service account in Active Directory 3. Block SMB (TCP 445) between all server VLANs at the network switch layer 4. Deploy an emergency GPO disabling the SMB server service on non-critical endpoints 5. Capture memory from one encrypted server before it reboots 6. Search for the ransomware binary hash across all endpoints using EDR threat hunting **Pitfalls**: - Shutting down servers immediately, destroying volatile memory evidence - Only disabling the known compromised account without checking for other persistence mechanisms - Restoring from backup before confirming the adversary's access has been fully revoked ## Output Format ``` CONTAINMENT STATUS REPORT ========================= Incident: INC-2025-1547 Status: CONTAINED (Short-Term) Timestamp: 2025-11-15T15:47:00Z Containment Lead: [Name] ACTIONS TAKEN Network: - [x] 5 hosts isolated via CrowdStrike containment - [x] C2 IP 185.220.x.x blocked at perimeter FW (rule #4521) - [x] C2 domain evil.example[.]com sinkholed to 10.0.0.99 Identity: - [x] jsmith account disabled - [x] svc-backup account disabled, password rotated - [x] admin-tier0 account disabled - [x] KRBTGT first reset completed at 15:30 UTC Endpoint: - [x] Malicious hash blocked in EDR prevention policy - [x] Malware processes terminated on all contained hosts EVIDENCE PRESERVED - Memory dumps: 3 of 5 hosts completed - Event logs exported: all 5 hosts - Network capture: running on finance VLAN REMAINING RISKS - Possible undiscovered implants on non-EDR endpoints (15 legacy hosts) - KRBTGT second reset pending (scheduled 03:30 UTC +1 day) - Adversary may have exfiltrated data before containment BUSINESS IMPACT - Finance file share offline (affects 42 users) - 3 user workstations isolated (users reassigned to loaners) - Estimated restoration: pending eradication completion ``` --- Source attribution: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/incident-response/containing-active-breach/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 xalgord Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/incident-response/containing-active-breach/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Security Engineer Specialties: Specialty not specified Tools: Sentinelone, Microsoft Defender For Endpoint, Crowdstrike Falcon Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 4e678c8e646a2a31acc7754296a5e2db67fd90d5662725b1c644458a86a23bff