Objective. Students will independently analyze a multi-stage attack scenario, produce a complete threat analysis report mapped to the ATT&CK framework, and deliver a five-minute defensive briefing to the class.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
This capstone lesson asks you to do what real security analysts do every day: receive raw evidence from an incident, reconstruct what happened, and explain it clearly to others so that defenses improve. You will work independently through a fictional but realistic incident package and produce both a written report and an oral briefing.
A professional threat analysis report answers five questions.
1. Who attacked? Identify the threat actor category — nation-state, cybercriminal group, hacktivist, insider, or script kiddie. Use observable behaviors and tooling to support your classification; you rarely know the actor's true identity.
2. How did they attack? Map every technique you can identify to the MITRE ATT&CK framework. Each technique has a unique ID in the format T####, and sub-techniques are written T####.###. Record the tactic category (e.g., Initial Access, Execution, Lateral Movement) alongside the ID.
3. What evidence do they leave? List indicators of compromise (IOCs): suspicious IP addresses, domain names, file hashes, registry keys, user-agent strings, and unusual process names found in the logs or captures.
4. What was affected? Identify every asset — workstation, server, user account, data store — that was touched, accessed, or modified.
5. What should change? Provide specific, prioritized countermeasures. Tie each recommendation to the vulnerability or technique it addresses.
MITRE ATT&CK is a publicly available knowledge base of adversary tactics, techniques, and procedures (TTPs). The Enterprise matrix organizes 14 tactics from Reconnaissance through Impact. When you analyze logs, ask which tactic phase fits each observed behavior, then look up the matching technique.
ATT&CK Navigator is a free browser tool that lets you highlight techniques on the matrix, color-code them by confidence level, and export the annotated matrix. Include your Navigator export or a screenshot in your report so the reader can see your mapping at a glance.
Common mistakes to avoid: do not list only tactic names without technique IDs; do not map a behavior to a technique unless the evidence actually supports it; and do not skip sub-techniques when they apply, because specificity improves remediation choices.
The Common Vulnerability Scoring System (CVSS) gives each vulnerability a numeric score from 0.0 to 10.0. The Base Score captures properties that do not change over time — attack vector, attack complexity, privileges required, user interaction, scope, and impact on confidentiality, integrity, and availability. The free CVSS calculator at first.org lets you select each metric and generates the score automatically.
In your report, note the CVSS Base Score for each exploited vulnerability, explain which metrics drove the score, and use that score to justify your remediation priority. A Critical score (9.0–10.0) should generally be remediated before a High (7.0–8.9), which comes before Medium (4.0–6.9).
Your five slides map directly to the five content areas your audience needs.
Speak to your audience, not to your slides. Prepare for questions by anticipating what a skeptical manager or peer analyst might ask: Why that threat actor category? What other techniques could explain the same evidence? What would you do first if you had only 48 hours?
When a peer or instructor asks a question you cannot fully answer, say what you do know and acknowledge the limit: "Based on the evidence in the package, I assessed X because of Y. I did not find enough data to confirm Z, so that would be my next investigative step." This approach demonstrates analytical integrity, which employers value more than false confidence.
Everything in your report must be traceable to evidence in the incident package or to a named, verifiable source such as the ATT&CK knowledge base or the CVSS specification. Do not invent IOCs or inflate severity to make the report look more dramatic. In real incidents, an inaccurate report can direct response teams to the wrong systems, waste resources, and leave the actual threat active. Professional accuracy is an ethical obligation in this field.
Your completed report and slides become a portfolio artifact. CompTIA Security+ and CySA+ employers expect candidates to demonstrate threat analysis skills. Keeping polished work samples — with any real-world or sensitive data removed — gives you concrete evidence to discuss in interviews.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.