Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding library category to the schema #2154

Merged
merged 11 commits into from
Feb 8, 2023
1 change: 1 addition & 0 deletions CHANGELOG.next.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@ Thanks, you're awesome :-) -->
#### Added

* adding `name` field to `threat.indicator` #2121
* adding `library` option to `event.category` #2154

#### Improvements

Expand Down
2 changes: 1 addition & 1 deletion docs/fields/field-details.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -3389,7 +3389,7 @@ Note: this field should contain an array of values.

*Important*: The field value must be one of the following:

api, authentication, configuration, database, driver, email, file, host, iam, intrusion_detection, malware, network, package, process, registry, session, threat, vulnerability, web
api, authentication, configuration, database, driver, email, file, host, iam, intrusion_detection, library, malware, network, package, process, registry, session, threat, vulnerability, web

To learn more about when to use which value, visit the page
<<ecs-allowed-values-event-category,allowed values for event.category>>
Expand Down
13 changes: 13 additions & 0 deletions docs/fields/field-values.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -142,6 +142,7 @@ This field is an array. This will allow proper categorization of some events tha
* <<ecs-event-category-host,host>>
* <<ecs-event-category-iam,iam>>
* <<ecs-event-category-intrusion_detection,intrusion_detection>>
* <<ecs-event-category-library,library>>
* <<ecs-event-category-malware,malware>>
* <<ecs-event-category-network,network>>
* <<ecs-event-category-package,package>>
Expand Down Expand Up @@ -282,6 +283,18 @@ Relating to intrusion detections from IDS/IPS systems and functions, both networ
allowed, denied, info


[float]
[[ecs-event-category-library]]
==== library

Events in this category refer to the loading of a library, such as (dll / so / dynlib), into a process. Use this category to visualize and analyze library loading related activity on hosts. Keep in mind that driver related activity will be captured under the "driver" category above.


*Expected event types for category library:*

start


[float]
[[ecs-event-category-malware]]
==== malware
Expand Down
7 changes: 7 additions & 0 deletions experimental/generated/ecs/ecs_flat.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3064,6 +3064,13 @@ event.category:
- denied
- info
name: intrusion_detection
- description: Events in this category refer to the loading of a library, such as
(dll / so / dynlib), into a process. Use this category to visualize and analyze
library loading related activity on hosts. Keep in mind that driver related
activity will be captured under the "driver" category above.
expected_event_types:
- start
name: library
- description: Malware detection events and alerts. Use this category to visualize
and analyze malware detections from EDR/EPP systems such as Elastic Endpoint
Security, Symantec Endpoint Protection, Crowdstrike, and network IDS/IPS systems
Expand Down
7 changes: 7 additions & 0 deletions experimental/generated/ecs/ecs_nested.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4056,6 +4056,13 @@ event:
- denied
- info
name: intrusion_detection
- description: Events in this category refer to the loading of a library, such
as (dll / so / dynlib), into a process. Use this category to visualize and
analyze library loading related activity on hosts. Keep in mind that driver
related activity will be captured under the "driver" category above.
expected_event_types:
- start
name: library
- description: Malware detection events and alerts. Use this category to visualize
and analyze malware detections from EDR/EPP systems such as Elastic Endpoint
Security, Symantec Endpoint Protection, Crowdstrike, and network IDS/IPS
Expand Down
7 changes: 7 additions & 0 deletions generated/ecs/ecs_flat.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2995,6 +2995,13 @@ event.category:
- denied
- info
name: intrusion_detection
- description: Events in this category refer to the loading of a library, such as
(dll / so / dynlib), into a process. Use this category to visualize and analyze
library loading related activity on hosts. Keep in mind that driver related
activity will be captured under the "driver" category above.
expected_event_types:
- start
name: library
- description: Malware detection events and alerts. Use this category to visualize
and analyze malware detections from EDR/EPP systems such as Elastic Endpoint
Security, Symantec Endpoint Protection, Crowdstrike, and network IDS/IPS systems
Expand Down
7 changes: 7 additions & 0 deletions generated/ecs/ecs_nested.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3976,6 +3976,13 @@ event:
- denied
- info
name: intrusion_detection
- description: Events in this category refer to the loading of a library, such
as (dll / so / dynlib), into a process. Use this category to visualize and
analyze library loading related activity on hosts. Keep in mind that driver
related activity will be captured under the "driver" category above.
expected_event_types:
- start
name: library
- description: Malware detection events and alerts. Use this category to visualize
and analyze malware detections from EDR/EPP systems such as Elastic Endpoint
Security, Symantec Endpoint Protection, Crowdstrike, and network IDS/IPS
Expand Down
7 changes: 7 additions & 0 deletions schemas/event.yml
Original file line number Diff line number Diff line change
Expand Up @@ -283,6 +283,13 @@
- allowed
- denied
- info
- name: library
description: >
Events in this category refer to the loading of a library, such as (dll / so / dynlib), into a process.
Use this category to visualize and analyze library loading related activity on
hosts. Keep in mind that driver related activity will be captured under the "driver" category above.
expected_event_types:
- start
- name: malware
description: >
Malware detection events and alerts. Use this category to visualize and analyze
Expand Down