Detecting Email Forwarding Rules Attack
Overview
Cybersecurity skill for detecting email forwarding rules attack. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"detecting email forwarding rules attack"
"When proactively hunting for indicators of detecting email forwarding rules atta"
"After threat intelligence indicates active campaigns using these techniques"
"During incident response to scope compromise related to these techniques"
When proactively hunting for indicators of detecting email forwarding rules attack in the environment
After threat intelligence indicates active campaigns using these techniques
During incident response to scope compromise related to these techniques
When EDR or SIEM alerts trigger on related indicators
During periodic security assessments and purple team exercises
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)
- SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)
- Sysmon deployed with comprehensive configuration
- Windows Security Event Log forwarding enabled
- Threat intelligence feeds for IOC correlation
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Define Detection Scope — Identify the specific email forwarding rules attack techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.
- Collect Baseline Data — Gather historical logs and establish normal behavior patterns for email forwarding rules attack.
- Build Detection Queries — Write detection rules, Sigma rules, or SIEM queries targeting email forwarding rules attack indicators.
- Execute Hunts — Run queries against the collected data, starting with broad filters and narrowing down.
- Triage Results — Investigate alerts, filter false positives, and validate findings against known-good behavior.
- Document Findings — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.
Tools
- SIEM Platform — Central log aggregation and query execution
- Sigma Rules — Vendor-agnostic detection rule format
- MITRE ATT&CK Navigator — Technique mapping and coverage analysis
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: detecting-email-forwarding-rules-attack3description: Use when detect malicious email forwarding rules created by adversaries4 to maintain persistent access to email communications for intelligence collection5 and BEC attacks. Use when detecting malicious email forwarding rules created by6 adversaries to maintain.7domain: cybersecurity8tags:9- threat-hunting10- mitre-attack11- email-forwarding12- persistence13- bec14- t111415- proactive-detection16subdomain: threat-hunting17version: '1.0'18author: oyi7719license: Apache-2.020d3fend_techniques:21- Restore Object22- Restore Configuration23- Application Configuration Hardening24- Application Hardening25- Disable Remote Access26nist_csf:27- DE.CM-0128- DE.AE-0229- DE.AE-0730- ID.RA-0531category: cybersecurity32metadata:33 source: https://skillmd.com/skills/oyi77/detecting-email-forwarding-rules-attack34---3536# Detecting Email Forwarding Rules Attack3738## Overview3940Cybersecurity skill for detecting email forwarding rules attack. Follows industry best practices and security standards.4142## When to Use4344**Trigger phrases:**45- "detecting email forwarding rules attack"46- "When proactively hunting for indicators of detecting email forwarding rules atta"47- "After threat intelligence indicates active campaigns using these techniques"48- "During incident response to scope compromise related to these techniques"495051- When proactively hunting for indicators of detecting email forwarding rules attack in the environment52- After threat intelligence indicates active campaigns using these techniques53- During incident response to scope compromise related to these techniques54- When EDR or SIEM alerts trigger on related indicators55- During periodic security assessments and purple team exercises565758## When NOT to Use5960- When you lack proper authorization for testing61- For production systems without change management62- When the task requires legal or compliance expertise beyond technical scope636465## Prerequisites6667- EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)68- SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)69- Sysmon deployed with comprehensive configuration70- Windows Security Event Log forwarding enabled71- Threat intelligence feeds for IOC correlation7273## Workflow7475```python76# Example: IOC detection77import re7879IOC_PATTERNS = {80 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",81 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",82 "hash_md5": r"\b[a-f0-9]{32}\b",83 "hash_sha256": r"\b[a-f0-9]{64}\b",84}8586def extract_iocs(text: str) -> dict:87 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}88```89901. **Define Detection Scope** — Identify the specific email forwarding rules attack techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.912. **Collect Baseline Data** — Gather historical logs and establish normal behavior patterns for email forwarding rules attack.923. **Build Detection Queries** — Write detection rules, Sigma rules, or SIEM queries targeting email forwarding rules attack indicators.934. **Execute Hunts** — Run queries against the collected data, starting with broad filters and narrowing down.945. **Triage Results** — Investigate alerts, filter false positives, and validate findings against known-good behavior.956. **Document Findings** — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.9697## Tools9899- **SIEM Platform** — Central log aggregation and query execution100- **Sigma Rules** — Vendor-agnostic detection rule format101- **MITRE ATT&CK Navigator** — Technique mapping and coverage analysis102103104## Process1051061. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1071. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1081. **Reporting** — Document IOCs, write findings, provide remediation recommendations109110## Verification111112- [ ] All email forwarding rules attack procedures executed completely and documented113- [ ] Findings validated against multiple data sources114- [ ] False positives identified and filtered115- [ ] Results documented with evidence and timestamps116- [ ] Recommendations provided with risk-based prioritization117118## Anti-Rationalization Table119120| Rationalization | Reality |121|---|---|122| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |123| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |124| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |