<!-- Copyright (c) 2026 defconxt. All rights reserved. -->
<!-- Licensed under AGPL-3.0 — see LICENSE file for details. -->
<!-- NERF is a trademark of defconxt. -->
---
name: performing-social-engineering-metrics-tracking
description: >-
  Design and implement metrics frameworks to measure social engineering program effectiveness and organizational resilience.
domain: cybersecurity
subdomain: social-engineering
tags:
  - metrics
  - program-effectiveness
  - resilience-measurement
  - kpi-tracking
  - reporting
version: "1.0"
author: defconxt
license: AGPL-3.0
metadata:
  mitre-attack: ["T1598"]
  cwe: ["CWE-693"]
  tools: ["gophish-reporting", "phishing-dashboard", "security-metrics"]
---

# Performing Social Engineering Metrics Tracking

## Overview

Design and implement metrics frameworks to measure social engineering program effectiveness and organizational resilience.

## Prerequisites

| Tool / Requirement | Details |
|---|---|
| `gophish-reporting` | Security tooling |
| `phishing-dashboard` | Security tooling |
| `security-metrics` | Security tooling |
| Isolated lab environment for testing | Environment requirement |
| Authorization and signed Rules of Engagement (RoE) | Environment requirement |
| Relevant target samples or systems acquired through authorized channels | Environment requirement |

## Quick Reference

```bash
# Initialize working environment
mkdir -p /tmp/performing-social-engineering-metrics-tracking/{output,logs,artifacts}

# Execute primary analysis with gophish-reporting
echo "[*] Running Performing Social Engineering Metrics Tracking with gophish-reporting..."

# Validate results with phishing-dashboard
echo "[*] Cross-validating with phishing-dashboard..."

# Generate summary report
cat /tmp/performing-social-engineering-metrics-tracking/output/report.json
```

## Workflow

### Step 1: Preparation and Reconnaissance

```bash
# Identify target and gather initial intelligence
file ./target_sample
gophish-reporting --version 2>/dev/null || echo "Install gophish-reporting"

# Set up working directory
mkdir -p /tmp/performing-social-engineering-metrics-tracking/{output,logs,artifacts}
```

### Step 2: Primary Analysis

```bash
# Execute primary analysis with gophish-reporting
# Refer to Quick Reference above for detailed commands
echo "[*] Running Performing Social Engineering Metrics Tracking with gophish-reporting..."

# Log all operations
script -q /tmp/performing-social-engineering-metrics-tracking/logs/session.log
```

### Step 3: Deep Investigation

```bash
# Apply phishing-dashboard for secondary analysis
echo "[*] Deep investigation with phishing-dashboard..."

# Cross-reference findings
diff /tmp/performing-social-engineering-metrics-tracking/output/primary.json /tmp/performing-social-engineering-metrics-tracking/output/secondary.json
```

### Step 4: Documentation and Reporting

```bash
# Generate structured findings report
cat <<'EOF' > /tmp/performing-social-engineering-metrics-tracking/output/report.json
{
  "technique": "performing-social-engineering-metrics-tracking",
  "domain": "social-engineering",
  "tools_used": ["gophish-reporting", "phishing-dashboard"],
  "findings": [],
  "recommendations": []
}
EOF
```

## Verification

- [ ] Environment and tools verified and operational
- [ ] Target samples acquired through authorized channels
- [ ] Primary analysis completed with findings documented
- [ ] Secondary validation performed with independent tooling
- [ ] All artifacts preserved in structured output directory
- [ ] Detection opportunities documented for blue team

## References

- [MITRE ATT&CK T1598](https://attack.mitre.org/techniques/T1598) — Related technique
- [gophish-reporting Documentation](https://gophish-reporting.org/) — Primary tooling
- [phishing-dashboard Reference](https://phishing-dashboard.org/) — Secondary tooling
