-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[csp] Telemetry for csp configuration #43223
Conversation
We collect the boolean configurations which can be derived by any end-user of Kibana by making any HTTP request. Since the rules configuration involves strings that can leak identifiable information, we only collect whether the rules have been changed from their defaults.
Pinging @elastic/kibana-security |
💚 Build Succeeded |
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.
code LGTM
x-pack/legacy/plugins/oss_telemetry/server/lib/collectors/csp/csp_collector.ts
Show resolved
Hide resolved
x-pack/legacy/plugins/oss_telemetry/server/lib/collectors/csp/csp_collector.ts
Show resolved
Hide resolved
x-pack/legacy/plugins/oss_telemetry/server/lib/collectors/csp/csp_collector.test.ts
Outdated
Show resolved
Hide resolved
x-pack/legacy/plugins/oss_telemetry/server/lib/collectors/csp/csp_collector.test.ts
Outdated
Show resolved
Hide resolved
I relaxed the reliance on the constant defaults and switched the rule check over to a snapshot. |
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 - apologies for all the nits
💚 Build Succeeded |
We collect the boolean configurations which can be derived by any end-user of Kibana by making any HTTP request. Since the rules configuration involves strings that can leak identifiable information, we only collect whether the rules have been changed from their defaults.
…p-metrics-selectall * 'master' of github.com:elastic/kibana: (50 commits) [Uptime] update monitor list configs for mobile view (elastic#43218) [APM] Local UI filters (elastic#41588) [Code] Upgrade ctags langserver (elastic#43252) [Code] show multiple definition results in panel (elastic#43249) Adds Metric Type to full screen launch tracking (elastic#42692) [Canvas] Convert Autocomplete to Typescript (elastic#42502) [telemetry] add spacesEnabled config back to xpack_main (elastic#43312) [ML] Adds DF Transform Analytics list to Kibana management (elastic#43151) Add TLS client authentication support. (elastic#43090) [csp] Telemetry for csp configuration (elastic#43223) [SIEM] Run Cypress Tests Against Elastic Cloud & Cypress Command Line / Reporting (elastic#42804) docs: add tip on agent config in a dt (elastic#43301) [ML] Adding bucket span estimator to new wizards (elastic#43288) disable flaky tests (elastic#43017) Fix percy target branch for PRs (elastic#43160) [ML] Adding post create job options (elastic#43205) Restore discover histogram selection triggering fetch (elastic#43097) Per panel time range (elastic#43153) [Infra UI] Add APM to Metadata Endpoint (elastic#42197) Sentence case copy changes (elastic#43215) ...
Summary
We collect the boolean configurations which can be derived by any
end-user of Kibana by making any HTTP request. Since the rules
configuration involves strings that can leak identifiable information,
we only collect whether the rules have been changed from their defaults.
The following shape is added to the telemetry payload: