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

Update to ECS v1.1.0 #13320

Closed
6 tasks done
andrewkroh opened this issue Aug 22, 2019 · 0 comments
Closed
6 tasks done

Update to ECS v1.1.0 #13320

andrewkroh opened this issue Aug 22, 2019 · 0 comments
Labels

Comments

@andrewkroh
Copy link
Member

andrewkroh commented Aug 22, 2019

@andrewkroh andrewkroh added the ecs label Aug 22, 2019
andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 23, 2019
This updates the fields.ecs.yml file and the vendored Go code to be based on ECS v1.1.0.

Relates elastic#13320
andrewkroh added a commit that referenced this issue Aug 24, 2019
This updates the fields.ecs.yml file and the vendored Go code to be based on ECS v1.1.0.

Relates #13320
andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 26, 2019
This updates the Suricata module to populate the ECS DNS fields. It does not remove existing `suricata.eve.dns.*` fields to preserve backward compatibility.

This also enhances the pipeline to handle the Suricata detailed DNS format (aka version 2). It requires that when using EVE DNS `version: 2` that `formats: [detailed]` is used (`grouped` can be enabled too but it is ignored).

`log.original` is now populated with the original JSON log data.

`source.address` and `destination.address` are now populated.

`event.end` is populated with the `flow.end` value now and hence some events that did not contain `flow.end` no longer have an `event.end`.

Relates elastic#13320
andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 26, 2019
This updates the panw.panos fileset to populate the ECS NAT fields. The original non-ECS fields are still being populated to not break backwards compatibility.

Relates elastic#13320
andrewkroh added a commit that referenced this issue Aug 26, 2019
This updates the panw.panos fileset to populate the ECS NAT fields. The original non-ECS fields are still being populated to not break backwards compatibility.

Relates #13320
andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 27, 2019
 Add DNS fields for ECS. This adds three fields:

- dns.question.registered_domain
- dns.header_flags
- dns.resolved_ip

Relates elastic#13320
andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 27, 2019
This adds ECS DNS fields to the Zeek DNS fileset (but does not change or remove any existing ones).

Relates elastic#13320
andrewkroh added a commit that referenced this issue Aug 27, 2019
This updates the Suricata module to populate the ECS DNS fields. It does not remove existing `suricata.eve.dns.*` fields to preserve backward compatibility.

This also enhances the pipeline to handle the Suricata detailed DNS format (aka version 2). It requires that when using EVE DNS `version: 2` that `formats: [detailed]` is used (`grouped` can be enabled too but it is ignored).

`event.original` is now populated with the original JSON log data.

`source.address` and `destination.address` are now populated.

`event.end` is populated with the `flow.end` value now and hence some events that did not contain `flow.end` no longer have an `event.end`.

Relates #13320
andrewkroh added a commit that referenced this issue Aug 27, 2019
Add DNS fields for ECS. This adds three fields:

- dns.question.registered_domain
- dns.header_flags
- dns.resolved_ip

Relates #13320
andrewkroh added a commit that referenced this issue Aug 27, 2019
This adds ECS DNS fields to the Zeek DNS fileset (but does not change or remove any existing ones).

Use event.original
Add registered_domain
Add dns.resolved_ip

Relates #13320
andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 29, 2019
Set `dns.type` to `answer` when a response packet is present and to `query` when there's only a request packet.

Relates elastic#13320
andrewkroh added a commit that referenced this issue Aug 30, 2019
Set `dns.type` to `answer` when a response packet is present and to `query` when there's only a request packet.

Relates #13320
andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 30, 2019
Set `dns.type` to `answer` when a response packet is present and to `query` when there's only a request packet.

Relates elastic#13320

(cherry picked from commit f2c6556)
andrewkroh added a commit that referenced this issue Aug 30, 2019
Set `dns.type` to `answer` when a response packet is present and to `query` when there's only a request packet.

Relates #13320

(cherry picked from commit f2c6556)
andrewkroh added a commit to andrewkroh/beats that referenced this issue Sep 5, 2019
This sets the ECS DNS fields. It does not remove the coredns.* fields to avoid introducing
a breaking change.

Relates elastic#13320
andrewkroh added a commit that referenced this issue Sep 11, 2019
This sets the ECS DNS fields. It does not remove the coredns.* fields to avoid introducing
a breaking change.

* Convert coredns ingest pipeline to YAML
* Update pipelines for ECS DNS
* Right trim trailing dots in dns.question.name

Relates #13320
leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
Set `dns.type` to `answer` when a response packet is present and to `query` when there's only a request packet.

Relates elastic#13320

(cherry picked from commit ba71859)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant