Threat actor profiling for adversary emulation — APT group research, sophistication tiers, MITRE ATT&CK mapping, initial access vectors, custom archetypes.
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./packages/decepticon/decepticon/skills/standard/soundwave/threat-profile/SKILL.mdThreat profiling defines who the red team is emulating. Without a clear profile, the engagement devolves into arbitrary tool usage instead of realistic adversary simulation.
Use the confirmed tier when available. If the requested profile needs a tier decision, use this table to explain the options:
| Tier | Actor Type | Sophistication | Best For |
|---|---|---|---|
| 1 | Opportunistic attacker | Low | Vulnerability assessment, external scan |
| 2 | Targeted cybercriminal | Medium | Penetration test, focused engagement |
| 3 | APT / nation-state | High | Full red team, advanced simulation |
| 4 | Insider threat | Varies | Internal assessment, assumed breach |
Gather or derive these fields from the operator's context and current evidence. For a named actor, optionally load the matching emulation playbook (emulation/<actor>/SKILL.md, indexed by emulation/SKILL.md) when that specialist detail is useful. Skillogy returns skill bodies, not sibling reference files:
The profile must be consistent with what the RoE allows. There's no point emulating spearphishing if social engineering isn't authorized.
| RoE Constraint | Profile Implication |
|---|---|
| External only, no social engineering | Focus on T1190, T1595, T1133 |
| Phishing authorized | Include T1566, T1598 |
| Internal assumed breach | Start from T1078 (Valid Accounts) |
| Full red team | Full kill chain TTPs |
When authoring a threat profile, these are the two compatible representations:
(a) Standalone plan/threat-profile.json — full ThreatProfile schema:
{
"engagement_name": "...",
"actor_name": "APT29-like (Cozy Bear)",
"actor_aliases": ["Cozy Bear", "The Dukes"],
"group_id": "G0050",
"tier": "tier-3",
"sophistication": "nation-state",
"motivation": "espionage",
"initial_access": ["T1195.002", "T1566.001", "T1078"],
"key_ttps": ["T1059.001", "T1053.005", "T1071.001", "T1048.003", "T1550.001"],
"tools": ["Cobalt Strike", "Mimikatz", "WMI Event Subscription"],
"infrastructure": ["Compromised SaaS", "Domain fronting via CDN"],
"recent_cti_delta": "Q1 2026 reports show shift toward OAuth abuse and CI/CD supply-chain",
"confidence": "probable"
}tier is the StrEnum value: "tier-1" (opportunistic), "tier-2" (targeted cybercrime), "tier-3" (APT / nation-state), "tier-4" (insider). Map to sophistication informally — tier-3 ↔ "nation-state", tier-2 ↔ "high", tier-1 ↔ "low/medium".
(b) Embedded summary — one-entry threat_actors list inside conops.json for backward-compat (the legacy ThreatActor shape: name + sophistication + motivation + initial_access + ttps). Skip tier/group_id/tools/infrastructure here — those live only in the standalone profile.
When specialist detail about a named actor is useful, load the emulation catalog and relevant playbook:
load_skill("/skills/standard/soundwave/threat-profile/emulation/SKILL.md") # routing table
load_skill("/skills/standard/soundwave/threat-profile/emulation/apt29/SKILL.md") # e.g. APT29Each playbook gives you (a) the ThreatProfile seed for plan/threat-profile.json, (b) the
ordered kill_chain to copy into conops.json (mapped to the 5 ObjectivePhase buckets),
and (c) the actor-specific RoE/safety gates to carry into abort.json + deconfliction.json.
Prune any technique the RoE forbids (Step 3) before writing. Available: apt29, sandworm,
scattered-spider, volt-typhoon, lazarus, fin7, lockbit.
plan/threat-profile.json must validate against ThreatProfile. Fields not listed here are not part of the model and are ignored by the validator.
| field | type | required | allowed values / nested keys |
|---|---|---|---|
engagement_name | str | yes | |
actor_name | str | yes | |
actor_aliases | list[str] | no | |
group_id | str | no | |
tier | ThreatTier | yes | one of tier-1, tier-2, tier-3, tier-4 |
sophistication | str | yes | |
motivation | str | yes | |
initial_access | list[str] | no | |
key_ttps | list[str] | no | |
tools | list[str] | no | |
infrastructure | list[str] | no | |
recent_cti_delta | str | no | |
confidence | FindingConfidence | no | one of verified, probable, unverified |
version | str | no | |
last_updated | str | no |
PurpleAILAB/Decepticon
98e51d3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.