|
| 1 | +# [CASE] SSH Scan Activity – Authorized Red Team Exercise |
| 2 | + |
| 3 | +### Case ID (slug-friendly) |
| 4 | + |
| 5 | +soc147-sshscan-2025-10-21 |
| 6 | + |
| 7 | +### Case Title |
| 8 | + |
| 9 | +Authorized Network Scan from Internal Red Team Host |
| 10 | + |
| 11 | +### Executive Summary |
| 12 | + |
| 13 | +An alert was triggered by the SOC147 rule — SSH Scan Activity. |
| 14 | +Investigation determined that the scanning originated from an internal penetration testing machine (PentestMachine, 172.16.20.5). |
| 15 | +The activity was verified as part of an authorized Red Team exercise. No compromise or malicious intent detected |
| 16 | + |
| 17 | +### Timeline (Key Timestamps) |
| 18 | + |
| 19 | +2021-06-13 16:23 — Nmap scan initiated from 172.16.20.5 |
| 20 | + |
| 21 | +2021-06-13 16:23 — Outbound SSH scan traffic to 172.16.20.1 – 172.16.20.6 |
| 22 | + |
| 23 | +2023-07-28 12:00 — Email received from redteam@letsdefend.io |
| 24 | + notifying scheduled scanning |
| 25 | + |
| 26 | +2025-10-21 — Case reviewed and confirmed as authorized Red Team activity |
| 27 | + |
| 28 | +### Artifacts / Indicators of Compromise (IOCs) |
| 29 | + |
| 30 | +IP Address: 172.16.20.5 — Source (PentestMachine) |
| 31 | + |
| 32 | +IP Range: 172.16.20.1 – 172.16.20.6 — Scanned hosts |
| 33 | + |
| 34 | +MD5 Hash: 3361bf0051cc657ba90b46be53fe5b36 — Legitimate Nmap binary |
| 35 | + |
| 36 | +E-mail Sender: redteam@letsdefend.io |
| 37 | + — Red Team communication |
| 38 | + |
| 39 | +E-mail Domain: letsdefend.io — Official internal domain |
| 40 | + |
| 41 | +### Technical Analysis |
| 42 | + |
| 43 | +The PentestMachine executed the command: |
| 44 | + |
| 45 | +nmap -sV -sP 172.16.20.0/24 |
| 46 | + |
| 47 | + |
| 48 | +Multiple outbound SSH connection attempts were observed in network logs. |
| 49 | + |
| 50 | +File hash verification confirmed the binary as a legitimate version of Nmap. |
| 51 | + |
| 52 | +No signs of malware infection, persistence, or data exfiltration. |
| 53 | + |
| 54 | +Email review confirmed that Red Team activity was pre-approved and authorized. |
| 55 | + |
| 56 | +### Mitigation / Response Actions |
| 57 | + |
| 58 | +Verified Red Team authorization via email correspondence. |
| 59 | + |
| 60 | +Ensured containment of PentestMachine during verification process. |
| 61 | + |
| 62 | +Updated SOC documentation to whitelist 172.16.20.5 during future Red Team exercises. |
| 63 | + |
| 64 | +No further response required. |
| 65 | + |
| 66 | +### Recommendations / Next Steps |
| 67 | + |
| 68 | +Maintain a central calendar for Red Team activity scheduling to avoid future false positives. |
| 69 | + |
| 70 | +Implement tagging in SIEM for known internal testing hosts. |
| 71 | + |
| 72 | +Conduct periodic review of SOC alert correlation rules to minimize noise. |
| 73 | + |
| 74 | +### AI Prompt & Response (AI Support Summary) |
| 75 | + |
| 76 | +Prompt: |
| 77 | +“Analyze SSH Scan Activity alert (SOC147) and determine if it represents a real threat or Red Team activity.” |
| 78 | + |
| 79 | +AI Response: |
| 80 | +The scan originated from 172.16.20.5 (PentestMachine). |
| 81 | +Command nmap -sV -sP 172.16.20.0/24 indicates authorized reconnaissance. |
| 82 | +Emails from redteam@letsdefend.io |
| 83 | + confirm scheduled testing. |
| 84 | +No malware, C2 communication, or compromise indicators found. |
| 85 | +Classified as False Positive (Authorized Red Team exercise). |
| 86 | + |
| 87 | +### Case Owner |
| 88 | + |
| 89 | +Ievgen Bondarenko |
0 commit comments