Exec and Tech
Red-team report structure — executive pulse and technical findings from $LAB_RT engagement, RoE scope front and center.
Visual · t21_exec_and_tech
Exec = risk themes; tech = repro + ATT&CK. $LAB_RT only. Original Cyberlium.
Executives need the so-what; engineers need replayable steps — both stay inside the engagement you were authorized to run.
Red-team reports open with scope and RoE ($LAB_RT hosts, dates, objectives), executive summary with risk themes and detection gaps — not trophy counts from stranger networks — and technical sections with numbered emulation steps, ATT&CK mapping, purple outcomes, and remediation handoff. Avoid live creds, real PII, or weaponized cookbooks in appendices. Cyberlium teaches dual-audience writing from YOUR lab exercise — not copy-paste breach reports, not sensational 'domain owned' without detection context, not anti-forensics sections. Clarity helps defenders prioritize — ego hurts trust.
1. Executive pulse
Objective, top gaps, detection coverage delta, recommended investments — one page max.
Plain language — no jargon wall without business impact tie-in.
Command guide
Try these commands — Executive pulse
═══ LINUX / macOS (Terminal Practice) ═══
Check system state and user context
Command — copy this
id whoami uname -a
Inspect network sockets listening for connections
Command — copy this
ss -tuln 2>/dev/null || netstat -tuln
Audit active processes
Command — copy this
ps aux | grep -v "\[" | head -15
═══ WINDOWS (POWERSHELL) ═══ Query user identity and system information
Command — copy this
whoami /all Get-ComputerInfo | Select-Object CsName, OsName, OsVersion
Primary tools to practice this lesson: grep, curl. Reference sites: Executive summary (https://attack.mitre.org/resources/adversary-emulation-plans/); CISA debrief (https://www.cisa.gov/resources-tools/resources/red-team-exercises). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Technical body
Methodology, RoE adherence, timeline UTC, TTP sections with proof redacted, purple map summary.
Separate demonstrated vs planned-emulation if brief was literacy-only.
3. Integrity
State $LAB_RT only; refuse stranger evidence; no cover-tracks appendix.
Data touched: synthetic markers only — transparency for legal and blue.
4. What you ship: exec + tech outline
Report outline with exec pulse headers + tech section list + RoE scope block.
5. What you record before the next lesson
Exec and tech outline path.
6. Wrong vs right: stranger phishing vs authorized RT lab
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
- Wrong: Exec summary claims breach of competitor because lab felt easy.
- Right: Exec + tech outline for $LAB_RT engagement. Next: ATT&CK Mapping in Reports.
Mission: report outline
1) Draft exec pulse headers. 2) List tech sections. 3) Write RoE scope block. 4) Add integrity/no-PII line.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “Exec pulse — detection gap vs business risk?”
APPLY: Exec summary emphasizes:
APPLY: True or False: Stranger breach paste belongs in report.
APPLY: Technical section includes: