Work in this lesson turns Threat Intelligence Foundations, Requirements, Sources, Collection, and Handling into a repeatable, reviewable practice. The activity uses a security operations team investigating coordinated phishing, credential abuse, malware, and cloud persistence and contributes to the wider objective to perform structured cyber threat analysis, intelligence production, hunting, prioritization, and operational communication.
The instructor traces a case involving a security operations team investigating coordinated phishing, credential abuse, malware, and cloud persistence. The demonstration links decisions to objective evidence, records the result in threat intelligence requirements plan, and tests the condition where collection priorities do not reflect business-critical assets.
Complete a controlled exercise covering Threat Intelligence Foundations, Requirements, Sources, Collection, and Handling. Confirm scope and responsibilities, examine the stated exception, reach a supported conclusion, and preserve the outcome in threat intelligence requirements plan.
Start where expected practice and observed evidence first diverge. Separate a missing record from an ineffective process, distinguish unclear ownership from a control failure, and treat “collection priorities do not reflect business-critical assets” as a hypothesis until tested against the applicable criteria and intended outcome.
Learners can apply Threat Intelligence Foundations, Requirements, Sources, Collection, and Handling, explain the reasoning used, and defend the result through threat intelligence requirements plan.