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

[1.x] Add event category configuration (#963) #977

Merged
merged 1 commit into from
Sep 23, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.next.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ Thanks, you're awesome :-) -->

* Added Mime Type fields to HTTP request and response. #944
* Added `threat.technique.subtechnique` to capture MITRE ATT&CK® subtechniques. #951
* Added `configuration` as an allowed `event.category`. #963

#### Improvements

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

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

authentication, database, driver, file, host, iam, intrusion_detection, malware, network, package, process, web
authentication, configuration, database, driver, file, host, iam, intrusion_detection, malware, network, package, process, 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
15 changes: 15 additions & 0 deletions docs/field-values.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -133,6 +133,7 @@ that will require subsequent breaking changes.
*Allowed Values*

* <<ecs-event-category-authentication,authentication>>
* <<ecs-event-category-configuration,configuration>>
* <<ecs-event-category-database,database>>
* <<ecs-event-category-driver,driver>>
* <<ecs-event-category-file,file>>
Expand All @@ -157,6 +158,20 @@ Events in this category are related to the challenge and response process in whi
start, end, info


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

Events in the configuration category have to deal with creating, modifying, or deleting the settings or parameters of an application, process, or system.

Example sources include security policy change logs, configuration auditing logging, and system integrity monitoring.


*Expected event types for category configuration:*

access, change, creation, deletion, info


[float]
[[ecs-event-category-database]]
==== database
Expand Down
13 changes: 13 additions & 0 deletions generated/ecs/ecs_flat.yml
Original file line number Diff line number Diff line change
Expand Up @@ -1651,6 +1651,19 @@ event.category:
- end
- info
name: authentication
- description: 'Events in the configuration category have to deal with creating,
modifying, or deleting the settings or parameters of an application, process,
or system.

Example sources include security policy change logs, configuration auditing
logging, and system integrity monitoring.'
expected_event_types:
- access
- change
- creation
- deletion
- info
name: configuration
- description: The database category denotes events and metrics relating to a data
storage and retrieval system. Note that use of this category is not limited
to relational database systems. Examples include event logs from MS SQL, MySQL,
Expand Down
13 changes: 13 additions & 0 deletions generated/ecs/ecs_nested.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2044,6 +2044,19 @@ event:
- end
- info
name: authentication
- description: 'Events in the configuration category have to deal with creating,
modifying, or deleting the settings or parameters of an application, process,
or system.

Example sources include security policy change logs, configuration auditing
logging, and system integrity monitoring.'
expected_event_types:
- access
- change
- creation
- deletion
- info
name: configuration
- description: The database category denotes events and metrics relating to
a data storage and retrieval system. Note that use of this category is not
limited to relational database systems. Examples include event logs from
Expand Down
13 changes: 13 additions & 0 deletions schemas/event.yml
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,19 @@
- start
- end
- info
- name: configuration
description: >
Events in the configuration category have to deal with creating, modifying, or
deleting the settings or parameters of an application, process, or system.

Example sources include security policy change logs, configuration auditing logging,
and system integrity monitoring.
expected_event_types:
- access
- change
- creation
- deletion
- info
- name: database
description: >
The database category denotes events and metrics relating to a data storage
Expand Down