+++ 
title = "OPSEC" 
chapter = false 
weight = 10 
pre = "3. " 
+++

# OPSEC Guide for Angerona

This guide covers operational security considerations when using Angerona agent, including detection risks, best practices, and the built-in OPSEC checking system.

## 📋 Table of Contents

- [Overview](#overview)
- [OPSEC Checking System](#opsec-checking-system)
- [Command Risk Assessment](#command-risk-assessment)
- [Detection Avoidance](#detection-avoidance)
- [Best Practices](#best-practices)
- [OPSEC by Command](#opsec-by-command)

---

## Overview

Operational Security (OPSEC) is critical when conducting red team operations. Angerona includes built-in OPSEC checking to help operators make informed decisions and avoid accidental security violations.

### Key Principles

1. **Minimize Detection**: Avoid commands and behaviors that trigger security alerts
2. **Use Built-in Commands**: Prefer Angerona's native commands over `shell` when possible
3. **Monitor Artifacts**: Review artifacts created by commands
4. **Review OPSEC Warnings**: Always read and understand OPSEC popup messages
5. **Operational Timing**: Adjust sleep intervals and jitter based on operational needs

---

## OPSEC Checking System

Angerona implements a two-stage OPSEC checking system:

### OPSEC Pre-Check (`opsec_pre`)

Runs **before** task creation and can block execution:

- **Blocking**: Can set `OpsecPreBlocked=True` to prevent task execution
- **Warning**: Can provide detailed warnings without blocking
- **Bypass Roles**: Defines who can approve blocked tasks:
  - `operator`: Any operator can bypass
  - `other_operator`: Requires approval from a different operator
  - `lead`: Only operation lead can approve

### OPSEC Post-Check (`opsec_post`)

Runs **after** task creation but **before** agent execution:

- **Artifact Review**: Warns about artifacts that will be created
- **Final Warning**: Last chance to cancel before agent picks up task
- **Context-Aware**: Reviews artifacts generated by `create_tasking`

---

## Command Risk Assessment

### 🔴 CRITICAL OPSEC RISK

These commands are **extremely detectable** and should be used with extreme caution:

| Command | Risk Level | Detection Likelihood | Alternatives |
|---------|-----------|---------------------|--------------|
| `keylog_start` | CRITICAL | Minutes to hours | Credential theft, browser credential extraction, clipboard monitoring |
| `steal_token` (LSASS) | CRITICAL | High-priority alerts | `make_token` for domain credentials |
| `kill` (critical PIDs) | CRITICAL | System instability | Blocked for PIDs 0, 4, 8 |

### 🟠 HIGH OPSEC RISK

These commands are **highly detectable** and require careful consideration:

| Command | Risk Level | Detection Likelihood | Alternatives |
|---------|-----------|---------------------|--------------|
| `shell` | HIGH | High (cmd.exe spawn) | Use built-in Angerona commands when possible |
| `steal_token` | HIGH | High (EDR/XDR monitoring) | `make_token` when credentials available |
| `rm` (system files) | HIGH | Blocked for safety | Never delete system files |
| `screenshot` | HIGH | Screen capture detection | Use sparingly, consider timing |
| `samdump` (registry) | CRITICAL | Very High (direct SAM access) | Requires SYSTEM privileges, heavily monitored, detection within minutes |
| `samdump` (files) | MEDIUM-HIGH | Medium-High (file access) | Lower detection profile, useful for offline analysis |
| `samdump` (remote) | HIGH | High (network traffic + registry) | Network traffic detectable, service manipulation logged |
| `browser_dump` | HIGH | High (browser credential access) | Browser credential access is heavily monitored |

### 🟡 MEDIUM OPSEC RISK

These commands have **moderate detection risk**:

| Command | Risk Level | Detection Likelihood | Notes |
|---------|-----------|---------------------|-------|
| `inline_execute` | MEDIUM | Memory allocation, API calls | In-process execution reduces some detection vectors |
| `inline_execute_assembly` | MEDIUM | CLR loading, memory allocation | In-process execution (no process injection) |
| `download` | MEDIUM | File access logging | Large files may trigger DLP |
| `upload` | MEDIUM | File write detection | Suspicious extensions monitored |
| `socks` | MEDIUM | Network traffic analysis | High bandwidth usage |
| `rpfwd` | MEDIUM | Network connection monitoring | Persistent connections |
| `make_token` | MEDIUM | Authentication logging | Less detectable than `steal_token` |

### 🟢 LOW OPSEC RISK

These commands have **low detection risk**:

| Command | Risk Level | Detection Likelihood | Notes |
|---------|-----------|---------------------|-------|
| `ls`, `cd`, `pwd` | LOW | Minimal | Read-only operations |
| `cat` | LOW | File read logging | May detect credential extraction |
| `ps` | LOW | Process enumeration | May be logged but low priority |
| `whoami` | LOW | Minimal | No system modifications |
| `list_tokens` | LOW | Token enumeration | Lower risk than token theft |

---

## Detection Avoidance

### EDR/XDR Detection

**Endpoint Detection and Response (EDR)** and **Extended Detection and Response (XDR)** solutions monitor:

- **Process Creation**: `shell` command spawns `cmd.exe` (highly monitored)
- **Memory Allocation**: `inline_execute` and `inline_execute_assembly` allocate executable memory (may be scanned)
- **CLR Loading**: Loading .NET assemblies into memory may trigger EDR detections
- **Token Manipulation**: `steal_token` and `make_token` generate authentication events
- **Memory Access**: Accessing LSASS memory triggers high-priority alerts
- **API Hooking**: Keyloggers and screen capture use monitored APIs
- **File Operations**: File writes to sensitive locations trigger alerts

**Mitigation Strategies:**
- Use built-in Angerona commands instead of `shell` when possible
- Use `inline_execute_assembly` for .NET assembly execution (in-process, no process injection)
- Use `inline_execute` for BOFs when possible (no process creation)
- Prefer `make_token` over `steal_token` when credentials are available
- Avoid accessing LSASS or other critical system processes
- Use keylogging only when absolutely necessary
- Limit file operations to user directories when possible

### Network Monitoring

**Network Intrusion Detection Systems (NIDS)** and firewalls monitor:

- **SOCKS Proxies**: Continuous network traffic patterns
- **Reverse Port Forwarding**: Persistent connections and port listeners
- **Large File Transfers**: High bandwidth usage
- **Suspicious Ports**: Non-standard ports may be flagged

**Mitigation Strategies:**
- Use non-standard ports for SOCKS and RPFWD
- Limit bandwidth usage during file transfers
- Use appropriate sleep intervals to reduce network activity
- Consider operational timing (e.g., during business hours)

### Behavioral Analysis

**Behavioral analysis engines** monitor:

- **Timing Patterns**: Predictable beacon intervals
- **Command Sequences**: Common attack patterns
- **Anomalous Activity**: Unusual system behavior

**Mitigation Strategies:**
- Use jitter (10-30%) to randomize sleep intervals
- Vary command execution patterns
- Avoid executing commands in rapid succession
- Use appropriate sleep intervals (30-60 seconds for stealth)

### Data Loss Prevention (DLP)

**DLP systems** monitor:

- **File Access**: Reading sensitive files (SAM, configs, etc.)
- **File Transfers**: Large downloads/uploads
- **Screen Capture**: Screenshot detection
- **Credential Extraction**: Detecting credential theft patterns

**Mitigation Strategies:**
- Limit access to sensitive files
- Use chunked transfers for large files
- Use screenshots sparingly
- Consider operational timing for sensitive operations

---

## Best Practices

### 1. Use Built-in Commands

**❌ Avoid:**
```
shell whoami
shell tasklist
shell dir
```

**✅ Prefer:**
```
whoami
ps
ls
```

Built-in Angerona commands:
- Don't spawn `cmd.exe` (highly monitored)
- Have better OPSEC characteristics
- Provide structured output
- Integrate with Mythic UI features

### 2. Adjust Sleep Intervals

**Initial Deployment:**
- Use 30-60 seconds with 10-30% jitter
- Provides good balance between responsiveness and stealth

**Interactive Operations:**
- Reduce to 5-10 seconds with 10-20% jitter
- Only when needed for responsive interaction

**Stealth Mode:**
- Increase to 60-120 seconds with 20-40% jitter
- Minimizes network activity and detection risk

### 3. Review OPSEC Warnings

**Always:**
- Read OPSEC popup messages carefully
- Understand the risks before approving
- Consider alternatives when suggested
- Consult with team lead for critical operations

**Never:**
- Ignore OPSEC warnings
- Bypass warnings without understanding risks
- Execute critical commands without approval

### 4. Monitor Artifacts

**Regularly:**
- Review artifacts created by commands
- Check the Artifacts page in Mythic UI
- Identify patterns that might trigger alerts
- Clean up artifacts when possible

### 5. Limit High-Risk Operations

**Critical Operations:**
- `keylog_start`: Use only when absolutely necessary
- `steal_token` (LSASS): Prefer `make_token` when possible
- `shell`: Use only when no alternative exists
- `screenshot`: Use sparingly and consider timing

**Timing Considerations:**
- Execute high-risk operations during low-activity periods
- Avoid simultaneous high-risk operations
- Space out operations to reduce detection correlation

### 6. Use Token Operations Wisely

**Best Practices:**
- Prefer `make_token` over `steal_token` when credentials are available
- Use `rev2self` after completing privileged operations
- Limit token impersonation duration
- Verify token context with `whoami` before operations

### 7. File Operations

**Best Practices:**
- Use user directories for staging files
- Avoid writing to System32, Windows, Program Files
- Use relative paths when possible
- Clean up temporary files after operations

---

## OPSEC by Command

### File System Commands

#### `ls`, `cd`, `pwd`
- **Risk**: LOW
- **Detection**: Minimal, read-only operations
- **Best Practice**: Use freely for navigation

#### `cat`
- **Risk**: LOW (operation), MEDIUM (credential detection)
- **Detection**: File read logging, credential extraction detection
- **Best Practice**: Use for reading files, be aware of credential detection

#### `download`
- **Risk**: MEDIUM
- **Detection**: File access logging, DLP for large files
- **Best Practice**: Use chunked transfers, limit file sizes, avoid sensitive files

#### `upload`
- **Risk**: MEDIUM
- **Detection**: File write detection, suspicious extensions monitored
- **Best Practice**: Avoid sensitive locations, use non-suspicious extensions when possible

#### `cp`, `mkdir`, `rm`
- **Risk**: LOW (user directories), HIGH (system files)
- **Detection**: File write/delete logging, blocked for system files
- **Best Practice**: Use in user directories, never delete system files

### Process Management Commands

#### `ps`
- **Risk**: LOW
- **Detection**: Process enumeration may be logged
- **Best Practice**: Use freely for reconnaissance

#### `kill`
- **Risk**: HIGH (critical PIDs), MEDIUM (user processes)
- **Detection**: Process termination logging, blocked for critical PIDs
- **Best Practice**: Never kill critical system processes

### Token Operations

#### `list_tokens`
- **Risk**: LOW
- **Detection**: Token enumeration may be logged
- **Best Practice**: Use for reconnaissance before token theft

#### `steal_token`
- **Risk**: CRITICAL (LSASS), HIGH (other processes)
- **Detection**: High-priority alerts, especially for LSASS
- **Best Practice**: Always requires approval, prefer `make_token` when possible

#### `make_token`
- **Risk**: MEDIUM
- **Detection**: Authentication event logging
- **Best Practice**: Less detectable than `steal_token`, use when credentials available

### Code Execution Commands

#### `inline_execute`
- **Risk**: MEDIUM
- **Detection**: Memory allocation (executable pages), API calls (LoadLibraryA, GetProcAddress), symbol resolution
- **Best Practice**: In-process execution reduces detection vectors compared to process spawning. Use for lightweight operations.

#### `inline_execute_assembly`
- **Risk**: MEDIUM
- **Detection**: CLR loading, memory allocation, AMSI/ETW bypass attempts may trigger behavioral detections
- **Best Practice**: In-process execution (no process injection). Use `--amsi` and `--etw` flags when needed, but be aware they may be detected.

#### `rev2self`
- **Risk**: LOW
- **Detection**: Minimal
- **Best Practice**: Use after completing privileged operations

### Network Tunneling

#### `socks`
- **Risk**: MEDIUM
- **Detection**: Continuous network traffic, flow analysis
- **Best Practice**: Use non-standard ports, limit bandwidth, be aware of high traffic

#### `rpfwd`
- **Risk**: MEDIUM
- **Detection**: Persistent connections, port listeners
- **Best Practice**: Avoid privileged ports, consider operational timing

### System Operations

#### `shell`
- **Risk**: HIGH
- **Detection**: cmd.exe spawn is highly monitored
- **Best Practice**: Use only when no alternative exists, always requires approval

#### `browser_info`
- **Risk**: LOW
- **Detection**: Registry reads may be logged if auditing enabled
- **Best Practice**: Read-only operation, safe for information gathering

#### `browser_dump`
- **Risk**: HIGH
- **Detection**: Browser credential access is heavily monitored by EDR/XDR
- **Best Practice**: Use only when necessary, always requires approval, consider timing

#### `samdump`

The `samdump` command supports three methods with different OPSEC profiles:

**Registry Method (Default):**
- **Risk**: CRITICAL
- **Detection**: Direct SAM/SYSTEM registry access is heavily monitored by EDR/XDR solutions
- **Detection Timeframe**: Likely within minutes
- **Best Practice**: Requires SYSTEM privileges (use `steal_token` on SYSTEM process first), always requires approval, consider timing, highest detection risk
- **Alternatives**: Use files method for lower detection profile, or Mimikatz via `inline_execute_assembly` for different detection signatures

**Files Method:**
- **Risk**: MEDIUM-HIGH
- **Detection**: File access and RegLoadKey operations are monitored but less aggressively than direct registry access
- **Detection Timeframe**: Medium-High (hours to days)
- **Best Practice**: Lower detection profile than registry method, still requires SYSTEM or backup/restore privileges, useful for offline analysis of backup files
- **Use Case**: When you have access to SAM/SYSTEM files from backups or offline systems

**Remote Method:**
- **Risk**: HIGH
- **Detection**: Network traffic (RPC calls), service manipulation (Remote Registry), and remote registry access are monitored
- **Detection Timeframe**: High (minutes to hours)
- **Best Practice**: Network traffic is detectable, authentication attempts are logged, use only when local access is not possible, higher visibility due to network activity
- **Use Case**: When you need to dump SAM from a remote system over the network

#### `screenshot`
- **Risk**: HIGH
- **Detection**: Screen capture detection, behavioral analysis
- **Best Practice**: Use sparingly, consider timing, large screenshots may trigger alerts

#### `keylog_start`
- **Risk**: CRITICAL
- **Detection**: Extremely detectable, likely within minutes or hours
- **Best Practice**: Use only when absolutely necessary, always requires lead approval

### Control Commands

#### `sleep`
- **Risk**: LOW
- **Detection**: Timing analysis for predictable patterns
- **Best Practice**: Use jitter (10-30%) to randomize intervals

#### `exit`
- **Risk**: LOW
- **Detection**: Minimal
- **Best Practice**: Use when agent removal is required

---

## OPSEC Warning Examples

### Blocking Message (shell whoami)

```
🚨 OPSEC BLOCKED - Command Has Safer Alternative

This command contains operations that have safer built-in alternatives in Angerona:

  🚨 whoami: Use Angerona's 'whoami' command instead (no cmd.exe spawn)

⚠️ cmd.exe spawn: This command would spawn cmd.exe (highly detectable)

💡 SAFER ALTERNATIVES:
  → Use: 'whoami' (Angerona built-in, no cmd.exe)

⚠️ TO PROCEED: You need approval from another operator.
```

### Blocking Message (steal_token)

```
🚨 HIGH OPSEC RISK - Token Theft Operation

Token theft operations are EXTREMELY monitored by:
  • EDR/XDR solutions (high-priority alerts)
  • Security Information and Event Management (SIEM)
  • Behavioral analysis engines
  • Process monitoring tools

⚠️ WARNING: Stealing tokens from critical processes (LSASS, System) will trigger
   immediate high-priority security alerts.

💡 ALTERNATIVES:
  → Use 'make_token' if you have domain credentials (less detectable)
  → Use 'list_tokens' first to identify high-value tokens
  → Consider alternative privilege escalation methods

⚠️ TO PROCEED: You need approval from another operator.
```

### Blocking Message (keylog_start)

```
🚨 CRITICAL OPSEC RISK - Keylogger Operation

Keyloggers are EXTREMELY detectable by:
  • EDR/XDR solutions
  • Anti-malware engines
  • Behavioral analysis
  • API hooking detection

⚠️ WARNING: Detection is likely within MINUTES or HOURS.

💡 ALTERNATIVES:
  → Credential theft (LSASS dumping, token theft)
  → Browser credential extraction
  → Clipboard monitoring
  → Network credential interception

⚠️ TO PROCEED: You need approval from a lead operator.
```

---

## Related Documentation

- [Commands Reference](commands.md) - Detailed command documentation with OPSEC notes
- [Features Overview](features.md#opsec-checking) - OPSEC checking system details
- [Getting Started](getting-started.md#security-considerations) - Security best practices
- [Usage Examples](examples.md) - OPSEC-aware examples

---

**Remember**: OPSEC is a shared responsibility. Always review warnings, understand risks, and consult with your team before executing high-risk operations.

**Last Updated:** 2024

