Detecting Cryptomining In Cloud

Detecting Cryptomining In Cloud

Overview

Cybersecurity skill for detecting cryptomining in cloud. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "detecting cryptomining in cloud"

• "This skill teaches security teams how to detect and respond to unauthorized cryp"

• When cloud billing alerts indicate unexpected compute cost spikes

• When GuardDuty generates CryptoCurrency or Impact finding types

• When investigating compromised IAM credentials that may be used to launch mining instances

• When monitoring container workloads for unauthorized process execution

• When establishing proactive detection controls against resource hijacking attacks

Do not use for legitimate cryptocurrency mining operations, for non-cloud mining detection on physical hardware, or for general malware analysis unrelated to mining activity.

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

• Amazon GuardDuty enabled with Runtime Monitoring for EC2, ECS, and EKS
• CloudWatch or Azure Monitor configured for compute utilization alerting
• VPC Flow Logs enabled for network traffic analysis to mining pool IPs
• AWS Cost Anomaly Detection or Azure Cost Management alerts configured

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()}

1. Define Detection Scope — Identify the specific cryptomining in cloud techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.
2. Collect Baseline Data — Gather historical logs and establish normal behavior patterns for cryptomining in cloud.
3. Build Detection Queries — Write detection rules, Sigma rules, or SIEM queries targeting cryptomining in cloud indicators.
4. Execute Hunts — Run queries against the collected data, starting with broad filters and narrowing down.
5. Triage Results — Investigate alerts, filter false positives, and validate findings against known-good behavior.
6. 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

1. Reconnaissance — Gather target information, identify attack surface, enumerate services
2. Analysis/Exploitation — Execute the technique, analyze results, document findings
3. Reporting — Document IOCs, write findings, provide remediation recommendations

Verification

• All cryptomining in cloud procedures executed completely and documented
• Findings validated against multiple data sources
• False positives identified and filtered
• Results documented with evidence and timestamps
• Recommendations provided with risk-based prioritization

Anti-Rationalization Table