[Google Workspace] Fixed a bug where a panel in the Login Dashboard did not filter correctly. #12628
+21,147
−8,769
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…astic#12571) Updates the following integrations to ECS 8.17.0: - fortinet_fortiedr - fortinet_fortigate - fortinet_fortimail - fortinet_fortimanager - fortinet_fortiproxy - goflow2 - hashicorp_vault - imperva - iptables
…astic#12569) Update the following integrations to ECS 8.17.0: - arista_ngfw - cef - checkpoint - cisco_aironet - cisco_asa - cisco_ftd - cisco_ios - cisco_ise - cisco_nexus - cisco_secure_email_gateway - citrix_waf
…astic#12572) Updated the following integrations to ECS 8.17.0: - juniper_srx - modsecurity - netflow - osquery - panw - pfsense - proxysg
…astic#12574) Updated the following integrations to ECS 8.17.0: - qnap_nas - snort - sonicwall_firewall - sophos - squid - stormshield - suricata - tcp - udp - watchguard_firebox - zeek
- The time format used "week-based-year" (Y) instead of "year-of-era" (y). The former gives very different results when calculating the month and date, since it is week-based. - Regenerated test files with updated dates.
elastic#12612) * Fix dashboard query in [Metrics System] Host overview * update pr link
* Add 9.0.0 constraint to sec-windows-platform packages * Fix typo * add scanner options to allow small test files * Update packages/microsoft_exchange_server/data_stream/httpproxy/agent/stream/filestream.yml.hbs * Update packages/microsoft_exchange_server/data_stream/httpproxy/agent/stream/filestream.yml.hbs * Update packages/microsoft_exchange_server/data_stream/httpproxy/agent/stream/filestream.yml.hbs * Update packages/microsoft_exchange_server/data_stream/httpproxy/agent/stream/filestream.yml.hbs * Update packages/microsoft_exchange_server/data_stream/httpproxy/agent/stream/filestream.yml.hbs
* Docker Enablement for v9.0.0 Signed-off-by: Andreas Gkizas <[email protected]>
…ingress, istio and containerd integrations (elastic#12535) * Enabling 9.0.0 kibana support for kubernetes, kubernetes_otel, nginx_ingress, istio and containerd integrations Signed-off-by: Andreas Gkizas <[email protected]>
Fixed a bug where a panel in the Login Dashboard did not filter correctly. The 'Successful Logins by Compromised Users [Logs Google Workspace]' panel showed all logins. The panel was renamed to accurately describe the data being shown after a filter for google_workspace.login.is_suspicious: true was added. Updated ingest to store google_workspace.login data that are boolValue to capture is_suspicious flag on logins. Changed name of panel 'Successful Logins by Compromised Users [Logs Google Workspace]' to 'Successful Logins that are Suspicious [Logs Google Workspace]'. Added filter for google_workspace.login.is_suspicious: true to renamed panel.
StacieClark-Elastic
added
bug
added correct PR number
💔 Build Failed
Failed CI StepsHistory |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed a bug where a panel in the Login Dashboard did not filter correctly. The 'Successful Logins by Compromised Users [Logs Google Workspace]' panel showed all logins. The panel was renamed to accurately describe the data being shown after a filter for google_workspace.login.is_suspicious: true was added. Updated ingest to store google_workspace.login data that are boolValue to capture is_suspicious flag on logins. Changed name of panel 'Successful Logins by Compromised Users [Logs Google Workspace]' to 'Successful Logins that are Suspicious [Logs Google Workspace]'. Added filter for google_workspace.login.is_suspicious: true to renamed panel.
Checklist
changelog.ymlfile.How to test this PR locally
Load the test data into the local elastic stack:
In the google_workspace package directory
Related issues
Successful Logins by Compromised Userspanel #8745