-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
New fileset for googlecloud firewall logs #14553
Conversation
864113e
to
6b3ef3c
Compare
Pinging @elastic/siem (Team:SIEM) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the addition of log.name
and the keep_original_message
. Either here or in a separate PR, can you please add those to vpcflow to keep them consistent?
9a8ac3b
to
9c724fc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ALLOWED: "allow", | ||
DENIED: "deny" | ||
}, | ||
default: "unknown" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please note that event.outcome
is still reserved.
The current thinking is that expected values in this field (when present) should be: "success" or "failure". Finer grained information such as "allow" or "deny" should be in another place, perhaps in event.action
or a custom field.
As usual, populating a reserved field signs you up to having to do a breaking change later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"destination.domain": "local-adrian-test", | ||
"destination.ip": "10.128.0.16", | ||
"destination.port": 80, | ||
"event.category": "firewall-rule", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
event.category
is still reserved, and at this time, there is no plan to have a category named "firewall-rule".
Leaving this here signs you up to have to do a breaking change, once the expected values are published for event.category
. The name of the category that will encapsulate firewall rule events is still very much in flux.
"related.ip": [ | ||
"10.128.0.16", | ||
"8.8.8.8" | ||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OMG thanks for filling that ❤️ 🙂
Other than me harping on the reserved fields, I'm really excited about this! Good work, as usual :-) |
Thanks @webmat Regarding |
This PR adds a new fileset, firewall, to the googlecloud module in Filebeat. It helps parsing firewall logs generated by rules under VPC Network -> Firewall Rules. Note that GCP only logs firewall events under the following conditions: - Logging needs to be enabled for each individual rule in order to log. - Only TCP and UDP rules can be logged. (cherry picked from commit 4a66f0b)
This PR adds a new fileset, firewall, to the googlecloud module in Filebeat. It helps parsing firewall logs generated by rules under VPC Network -> Firewall Rules. Note that GCP only logs firewall events under the following conditions: - Logging needs to be enabled for each individual rule in order to log. - Only TCP and UDP rules can be logged. (cherry picked from commit 4a66f0b)
…15621) * New fileset for googlecloud firewall logs (#14553) This PR adds a new fileset, firewall, to the googlecloud module in Filebeat. It helps parsing firewall logs generated by rules under VPC Network -> Firewall Rules. Note that GCP only logs firewall events under the following conditions: - Logging needs to be enabled for each individual rule in order to log. - Only TCP and UDP rules can be logged. (cherry picked from commit 4a66f0b) * googlecloud/vpcflow fileset: Populate additional log fields (#14608) To keep the vpcflow fileset of the googlecloud module aligned with the new firewall fileset, a `var.keep_original_message` option is added. Also the log.logger ECS field is now filled.
…l logs (elastic#15621) * New fileset for googlecloud firewall logs (elastic#14553) This PR adds a new fileset, firewall, to the googlecloud module in Filebeat. It helps parsing firewall logs generated by rules under VPC Network -> Firewall Rules. Note that GCP only logs firewall events under the following conditions: - Logging needs to be enabled for each individual rule in order to log. - Only TCP and UDP rules can be logged. (cherry picked from commit 4a66f0b) * googlecloud/vpcflow fileset: Populate additional log fields (elastic#14608) To keep the vpcflow fileset of the googlecloud module aligned with the new firewall fileset, a `var.keep_original_message` option is added. Also the log.logger ECS field is now filled. (cherry picked from commit 22fb66d)
…15621) (#15625) * New fileset for googlecloud firewall logs (#14553) This PR adds a new fileset, firewall, to the googlecloud module in Filebeat. It helps parsing firewall logs generated by rules under VPC Network -> Firewall Rules. Note that GCP only logs firewall events under the following conditions: - Logging needs to be enabled for each individual rule in order to log. - Only TCP and UDP rules can be logged. (cherry picked from commit 4a66f0b) * googlecloud/vpcflow fileset: Populate additional log fields (#14608) To keep the vpcflow fileset of the googlecloud module aligned with the new firewall fileset, a `var.keep_original_message` option is added. Also the log.logger ECS field is now filled. (cherry picked from commit 22fb66d)
This PR adds a new fileset,
firewall
, to thegooglecloud
module in Filebeat. It helps parsing firewall logs generated by rules under VPC Network -> Firewall Rules.Note that GCP only logs firewall events under the following conditions:
See https://cloud.google.com/vpc/docs/using-firewall-rules-logging.