Set sensitive values as secret in services integrations - #9238
Conversation
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
detection |
1776.2 | 1132.5 | -643.7 (-36.24%) | 💔 |
Package imperva_cloud_waf 👍(0) 💚(0) 💔(1)
Expand to view
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
event |
1564.95 | 1106.19 | -458.76 (-29.31%) | 💔 |
Package ti_crowdstrike 👍(0) 💚(0) 💔(2)
Expand to view
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
intel |
1876.17 | 1404.49 | -471.68 (-25.14%) | 💔 |
ioc |
4132.23 | 2762.43 | -1369.8 (-33.15%) | 💔 |
To see the full report comment with /test benchmark fullreport
|
💚 Build Succeeded
History
|
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
Package crowdstrike - 1.32.0 containing this change is available at https://epr.elastic.co/search?package=crowdstrike |
|
Package eset_protect - 0.2.0 containing this change is available at https://epr.elastic.co/search?package=eset_protect |
|
Package forcepoint_web - 1.8.0 containing this change is available at https://epr.elastic.co/search?package=forcepoint_web |
|
Package imperva_cloud_waf - 0.3.0 containing this change is available at https://epr.elastic.co/search?package=imperva_cloud_waf |
|
Package ti_crowdstrike - 0.5.0 containing this change is available at https://epr.elastic.co/search?package=ti_crowdstrike |
|
Package ti_eclecticiq - 0.3.0 containing this change is available at https://epr.elastic.co/search?package=ti_eclecticiq |
|
Package ti_threatconnect - 0.2.0 containing this change is available at https://epr.elastic.co/search?package=ti_threatconnect |
- Set sensitive values in several services integrations as secret - Marked non-sensitive values as not a secret - Upgraded pkg-spec to 3.0.3 where possible, gaining secrets validation from 3.0.2
- Set sensitive values in several services integrations as secret - Marked non-sensitive values as not a secret - Upgraded pkg-spec to 3.0.3 where possible, gaining secrets validation from 3.0.2
- Set sensitive values in several services integrations as secret - Marked non-sensitive values as not a secret - Upgraded pkg-spec to 3.0.3 where possible, gaining secrets validation from 3.0.2


0.0% Duplication on New Code
Proposed commit message
Checklist
changelog.ymlfile.Related issues