- Home
- Correlation Rule Library
- Crackmapexec detection
Detecting CrackMapExec
Rule added on 30th April, 2024In this page
Rule type:
Correlation
Rule description:
CrackMapExec (CME) is an open-source post exploitation tool that is used for penetration testing to assess the Active Directory (AD) security. However, it may be used by attackers who exploit its features for malicious reasons, such as collecting AD information to laterally move within the targeted network.
Impact:
It can be used by adversaries in the following ways:
- Password spraying
- Credential enumeration
- SMB enumeration
- Brute force
Data source:
Windows:
Required configuration: The rules is based on the process creation and termination. Prerequisites required are installing and configuring Sysmon, enabling audit process creation audit policy, and the command line auditing.
Relevant MITRE ATT&CK techniques and tactics:
Criteria:
(Process name contains "crackmapexec" )
'CrackMapExec'- Use of 'crackmapexec' in command line may suggest that attackers are attempting to perform reconnaissance on the target's network,
gather information about users, domains, and services.When to enable this rule:
Enabling this rule will help you meet the security standards' requirements listed below:
Security standards (NIST CSF 2.0):
DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
When this rule is triggered, you're notified when CrackMapExec is being used within the network. This enables you to stop the runtime activity and prevent attacker goals.
PR.PS-05: Installation and execution of unauthorized software are prevented
When this rule is triggered, you're notified when CrackMapExec is being used within the network. This enables you to detect the use of unauthorized softwares within the network and prevent credential theft and other attacker goals.
Known false positives: The blue teams might use the tool to test the effectiveness of their defensive measures and incident response protocols.
Next steps:
When this alert is triggered, the following measures can be implemented:
- Identification: Identify the alert as a new incident or within an ongoing incident.
- Analysis: Analyze the impact and extent of the compromise to comprehend the severity of the attack.
- Response: Respond promptly by initiating an automated workflow to cease the malicious process.
- Network Traffic Analysis: Monitor and analyze the network traffic for identifying the signatures and patterns associated with CrackMapExec such as unusual SMB connections.