You're reading from Threat Hunting with Elastic Stack Solve complex security challenges with integrated prevention, detection, and response

Product type Paperback

Published in Jul 2021

Publisher Packt

ISBN-13 9781801073783

Length 392 pages

Edition 1st Edition

Tools

Kibana

Concepts

Cybersecurity

Author (1):

Andrew Pease

View More author details

Table of Contents (18) Chapters

Preface

1. Section 1: Introduction to Threat Hunting, Analytical Models, and Hunting Methodologies

2. Chapter 1: Introduction to Cyber Threat Intelligence, Analytical Models, and Frameworks FREE CHAPTER

3. Chapter 2: Hunting Concepts, Methodologies, and Techniques

4. Section 2: Leveraging the Elastic Stack for Collection and Analysis

5. Chapter 3: Introduction to the Elastic Stack

6. Chapter 4: Building Your Hunting Lab – Part 1

7. Chapter 5: Building Your Hunting Lab – Part 2

8. Chapter 6: Data Collection with Beats and Elastic Agent

9. Chapter 7: Using Kibana to Explore and Visualize Data

10. Chapter 8: The Elastic Security App

11. Section 3: Operationalizing Threat Hunting

12. Chapter 9: Using Kibana to Pivot Through Data to Find Adversaries

13. Chapter 10: Leveraging Hunting to Inform Operations

14. Chapter 11: Enriching Data to Make Intelligence

15. Chapter 12: Sharing Information and Analysis

16. Assessments

17. Other Books You May Enjoy

The Elastic Common Schema

In the previous chapters, most notably in Chapter 7, Using Kibana to Explore and Visualize Data, we discussed that the Elastic Common Schema (ECS) is a data model, developed by Elastic and their community, to describe common fields that are used when storing data in Elasticsearch. ECS defines specific field names, organizations, and data types for each field that is stored in Elasticsearch. While ECS is an open source model and is frequently contributed to by the Elastic community, it is maintained by Elastic.

Later, we'll see why ECS is strongly encouraged but not mandatory for storing data in Elasticsearch. When data cannot be stored in ECS, data providers can use general ECS guidelines (Elastic, https://www.elastic.co/guide/en/ecs/current/ecs-guidelines.html) to name and structure custom fields. This helps uniformly structure fields that are not in ECS.

While ECS is a data model, it is also an ideology that data should be stored uniformly so that...