<!-- Copyright (c) 2026 defconxt. All rights reserved. -->
<!-- Licensed under AGPL-3.0 — see LICENSE file for details. -->
<!-- NERF is a trademark of defconxt. -->
---
name: analyzing-supply-chain-social-engineering
description: >-
  Analyze social engineering attacks targeting supply chain relationships including vendor compromise and trust exploitation.
domain: cybersecurity
subdomain: social-engineering
tags:
  - supply-chain
  - vendor-compromise
  - trust-exploitation
  - third-party-risk
  - business-relationships
version: "1.0"
author: defconxt
license: AGPL-3.0
metadata:
  mitre-attack: ["T1199"]
  cwe: ["CWE-693"]
  tools: ["supply-chain-mapper", "vendor-risk-tool", "osint-framework"]
---

# Analyzing Supply Chain Social Engineering

## Overview

Analyze social engineering attacks targeting supply chain relationships including vendor compromise and trust exploitation.

## Prerequisites

| Tool / Requirement | Details |
|---|---|
| `supply-chain-mapper` | Security tooling |
| `vendor-risk-tool` | Security tooling |
| `osint-framework` | 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/analyzing-supply-chain-social-engineering/{output,logs,artifacts}

# Execute primary analysis with supply-chain-mapper
echo "[*] Running Analyzing Supply Chain Social Engineering with supply-chain-mapper..."

# Validate results with vendor-risk-tool
echo "[*] Cross-validating with vendor-risk-tool..."

# Generate summary report
cat /tmp/analyzing-supply-chain-social-engineering/output/report.json
```

## Workflow

### Step 1: Preparation and Reconnaissance

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

# Set up working directory
mkdir -p /tmp/analyzing-supply-chain-social-engineering/{output,logs,artifacts}
```

### Step 2: Primary Analysis

```bash
# Execute primary analysis with supply-chain-mapper
# Refer to Quick Reference above for detailed commands
echo "[*] Running Analyzing Supply Chain Social Engineering with supply-chain-mapper..."

# Log all operations
script -q /tmp/analyzing-supply-chain-social-engineering/logs/session.log
```

### Step 3: Deep Investigation

```bash
# Apply vendor-risk-tool for secondary analysis
echo "[*] Deep investigation with vendor-risk-tool..."

# Cross-reference findings
diff /tmp/analyzing-supply-chain-social-engineering/output/primary.json /tmp/analyzing-supply-chain-social-engineering/output/secondary.json
```

### Step 4: Documentation and Reporting

```bash
# Generate structured findings report
cat <<'EOF' > /tmp/analyzing-supply-chain-social-engineering/output/report.json
{
  "technique": "analyzing-supply-chain-social-engineering",
  "domain": "social-engineering",
  "tools_used": ["supply-chain-mapper", "vendor-risk-tool"],
  "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 T1199](https://attack.mitre.org/techniques/T1199) — Related technique
- [supply-chain-mapper Documentation](https://supply-chain-mapper.org/) — Primary tooling
- [vendor-risk-tool Reference](https://vendor-risk-tool.org/) — Secondary tooling
