Book Image

Operationalizing Threat Intelligence

By : Kyle Wilhoit, Joseph Opacki
Book Image

Operationalizing Threat Intelligence

By: Kyle Wilhoit, Joseph Opacki

Overview of this book

We’re living in an era where cyber threat intelligence is becoming more important. Cyber threat intelligence routinely informs tactical and strategic decision-making throughout organizational operations. However, finding the right resources on the fundamentals of operationalizing a threat intelligence function can be challenging, and that’s where this book helps. In Operationalizing Threat Intelligence, you’ll explore cyber threat intelligence in five fundamental areas: defining threat intelligence, developing threat intelligence, collecting threat intelligence, enrichment and analysis, and finally production of threat intelligence. You’ll start by finding out what threat intelligence is and where it can be applied. Next, you’ll discover techniques for performing cyber threat intelligence collection and analysis using open source tools. The book also examines commonly used frameworks and policies as well as fundamental operational security concepts. Later, you’ll focus on enriching and analyzing threat intelligence through pivoting and threat hunting. Finally, you’ll examine detailed mechanisms for the production of intelligence. By the end of this book, you’ll be equipped with the right tools and understand what it takes to operationalize your own threat intelligence function, from collection to production.
Table of Contents (18 chapters)
1
Section 1: What Is Threat Intelligence?
6
Section 2: How to Collect Threat Intelligence
12
Section 3: What to Do with Threat Intelligence

Prioritized collection requirements

Closely related to the earlier-discussed Focused Collection Requirements (FCRs), in Chapter 3, Guidance and Policies, PCRs are collection requirements created by a collection management function that align to requirements that intelligence consumers need to be addressed. They are specifically aligned to an organization's prioritized and stated need for data defined in the intelligence requirements. FCRs and PCRs differ in the sense of the audience that consumes the collection data and the scope of that information. FCRs are typically meant to inform internal CTI key stakeholders, whereas PCRs are typically shared externally to the CTI function, such as with the information security or network engineering departments or even executives who may have specific requests for collection as a key stakeholder.

From a collection management perspective, PCRs help guide and drive CTI analysts and researchers toward collection goals to serve their customers...