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

aws using invalid field values according to ECS #3044

Closed
Tracked by #3016
jsoriano opened this issue Apr 11, 2022 · 2 comments · Fixed by #3342
Closed
Tracked by #3016

aws using invalid field values according to ECS #3044

jsoriano opened this issue Apr 11, 2022 · 2 comments · Fixed by #3342
Assignees
Labels
Integration:aws AWS Team:Cloud-Monitoring Label for the Cloud Monitoring team

Comments

@jsoriano
Copy link
Member

jsoriano commented Apr 11, 2022

[0] parsing field value failed: field "event.category"'s value "network_traffic" is not one of the allowed values (authentication, configuration, database, driver, file, host, iam, intrusion_detection, malware, network, package, process, registry, session, threat, web)
[1] parsing field value failed: field "event.outcome"'s value "allow" is not one of the allowed values (failure, success, unknown)
[2] parsing field value failed: field "event.outcome"'s value "deny" is not one of the allowed values (failure, success, unknown)
[3] parsing field value failed: field "event.type"'s value "flow" is not one of the allowed values (access, admin, allowed, change, connection, creation, deletion, denied, end, error, group, indicator, info, installation, protocol, start, user)

"network_traffic" => "network"
"allow" => "success"
"deny" => "failure"
"flow" => "connection"?

Part of #3016

@jsoriano jsoriano changed the title aws[0] parsing field value failed: field "event.category"'s value "network_traffic" is not one of the allowed values (authentication, configuration, database, driver, file, host, iam, intrusion_detection, malware, network, package, process, registry, session, threat, web)[1] parsing field value failed: field "event.outcome"'s value "allow" is not one of the allowed values (failure, success, unknown)[2] parsing field value failed: field "event.outcome"'s value "deny" is not one of the allowed values (failure, success, unknown)[3] parsing field value failed: field "event.type"'s value "flow" is not one of the allowed values (access, admin, allowed, change, connection, creation, deletion, denied, end, error, group, indicator, info, installation, protocol, start, user) "network_traffic" => "network""allow" => "success""deny" => "failure""flow" => "connection"? aws using invalid field values according to ECS Apr 11, 2022
@jsoriano jsoriano added Team:Cloud-Monitoring Label for the Cloud Monitoring team Integration:aws AWS labels Apr 11, 2022
@jsoriano
Copy link
Member Author

@elastic/obs-cloud-monitoring do you have a timeline for this issue? This is blocking elastic/elastic-package#771. Thanks!

@kaiyan-sheng kaiyan-sheng self-assigned this May 11, 2022
@kaiyan-sheng
Copy link
Contributor

@jsoriano Sorry about that!! Let me start a PR on this and we might need some help from the security team to review the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Integration:aws AWS Team:Cloud-Monitoring Label for the Cloud Monitoring team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants