## Summary
Added new configuration option for Elastic Defend integration's
Traditional Endpoint environment:
- Data Collection only configuration option
- uses the already available config policy (added here #144087)
- the default option is NGAV (as before)
Test:
- go to Management / Integrations
- select Elastic Defend
- press the 'Add Elastic Defend' button
<img width="1321" alt="image"
src="https://user-images.githubusercontent.com/39014407/214846703-9632f6e7-18a8-4312-a61d-8ee9255833e0.png">
### Checklist
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
This PR adds more information to the plugin's README.md file. As
suggested by @alisonelizabeth , I added the text from the handover
document here so that it can easily be found close to the code.
## Summary
This PR updates UI to use `findUserActions` API introduced in #148861
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
### How to test
Verify User action behaviour is same as before in Case View page
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Adds to the appropriate mappings to ensure elastic-agent can write logs
for the new "Defend for containers" service coming in 8.8
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
## Summary
Added endpoint to support _search in search passthrough API from enterprise search.
---------
Co-authored-by: saarikabhasi <nairsaarika.bhasi@elastic.co>
Co-authored-by: Saarika Bhasi <55930906+saarikabhasi@users.noreply.github.com>
## Summary
This pull request adds the users installed detection rules package to
the alert telemetry.
This enables Threat Researchers / Detection Engineers to develop these
rules for more fine-grained filtering and tuning.
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
### For maintainers
- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
## Summary
This adds a new highlighted field to alert details for Malware alerts
which come from Endpoints to show the `quarantined_path` of a file, if
there is one.
This change is meant to assist with users who use the new Get File
response action to retrieve files that the Endpoint has quarantined,
which is a common use case for analysts exploring a potential attack.
This field isn't mapped, so the actions are purposefully removed since
we can't search by it.
<img width="1728" alt="image"
src="https://user-images.githubusercontent.com/56395104/214412096-99e9915a-300a-415d-a0dc-d1368eb7897b.png">
### Checklist
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
We receive a number of SDHs each month around Rule Data Client
initialization failures causing rule failures later on. Often these are
due to `.partial` indices preventing the mapping update process during
initialization, but we've also seen transient failures due to ES being
overloaded during startup, as well as mapping issues from customers
adding additional component templates.
This PR stores any error encountered during initialization and throws
the same error message again each time `getWriter` is called instead of
throwing a generic error message. This should help triage the issues
faster, as we won't have to spend as much time asking for support to
track down the error message from the first attempt at initializing the
RDC.
### Before

### After

## Summary
Sets the Get File feature flag to true by default in preparation for the
release of the feature.
### Checklist
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Replaces duplicated string literal paths in the router for our
`ML_PAGES` constants.
E.g.
```ts
path: '/aiops/change_point_detection',
```
is now
```ts
path: createPath(ML_PAGES.AIOPS_CHANGE_POINT_DETECTION),
```
**Addresses:** https://github.com/elastic/kibana/issues/130966
**Based on:** https://github.com/elastic/kibana/issues/135127
## Summary
This PR deprecates the Sidecar SO of type `siem-detection-engine-rule-execution-info` in favour of storing Rule Execution Logging data within the rule itself, making use of the work previously done in the Alerting Framework:
- https://github.com/elastic/kibana/pull/140882
- https://github.com/elastic/kibana/pull/147278
Work done:
- **Pass execution statuses and metrics from rule executors to the Framework:** through the use of `RuleMonitoringService` and `RuleResultService` from within the rule execution log client for executor. `x-pack/plugins/security_solution/server/lib/detection_engine/rule_monitoring/logic/rule_execution_log/client_for_executors/client.ts`
- **Fetch execution statuses and metrics from rules themselves instead of the sidecar `siem-detection-engine-rule-execution-info` saved objects**: through the use of the new function `createRuleExecutionSummary` in `x-pack/plugins/security_solution/server/lib/detection_engine/rule_monitoring/logic/rule_execution_log/create_rule_execution_summary.ts`, which extracts last execution information from the rule itself.
- **Remove the siem-detection-engine-rule-execution-info saved objects type from the codebase. Mark it as deleted in Kibana Core:** added `siem-detection-engine-rule-execution-info` to `packages/core/saved-objects/core-saved-objects-migration-server-internal/src/core/unused_types.ts`; and got rid of the related Saved Object client.
- **Make sure to keep backward compatibility in the Detection API endpoints and rule execution events we write into the Event Log**: API compatibility is maintained. No breaking changes.
### Checklist
- [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
## Summary
Fixed a bug where the hourly task was incorrectly setting all uploaded
files to DELETED state.
This is because the file doc `_index` property was expected to be in the
form of e.g. `.fleet-file-data-agent`, but actually it contains a
backing index name e.g. `.fleet-files-agent-000001`
How I tested:
- Enroll an agent and request a few diagnostics (requires latest changes
from agent pr)
- Wait for files to be uploaded, the files should be visible here in
READY state: `GET .fleet-files-agent/_search`
- Wait some time (up to 1h) for the task to run
- Expect that the files are still in READY state after the task has run.
- Previously all diagnostics files were set to DELETED in 1 hour
<img width="1394" alt="image"
src="https://user-images.githubusercontent.com/90178898/215104906-94e0364c-1e54-4287-87f7-7c560bf0e41e.png">
Example hit from metadata index:
```
{
"_index": ".fleet-files-agent-000001",
"_id": "2023-01-27T10-25-16Z-00.0c99a40e-5eec-42a4-bbeb-8c92e61f9e42",
"_score": null,
"_source": {
"transithash": {
"sha256": "d8187866600a3783490f93ffb0920b35180095c1b5392c3c561da516b7b17c82"
},
"upload_id": "7695aeac-5837-44a3-8597-8d64aeed3aa2",
"file": {
"Status": "READY",
"ext": "zip",
"ChunkSize": 4194304,
"size": 445046,
"mime_type": "application/zip",
"name": "elastic-agent-diagnostics-2023-01-27T10-25-16Z-00.zip",
"hash": {
"sha256": "",
"md5": ""
}
},
"agent_id": "0c99a40e-5eec-42a4-bbeb-8c92e61f9e42",
"action_id": "2023-01-27T10-25-16Z-00",
"contents": null,
"src": "agent",
"upload_start": 1674815116965
},
"sort": [
1674815116965
]
},
```
### Checklist
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
The commit fixed the bits of code where we were using directly an index field name as an object key. This can cause errors if the field name is a reserved JS keyword.
The fix reconfigured that part of the code by replacing plain Objects with `Map` that doesn't suffer from this issue.
part of: https://github.com/elastic/kibana/issues/145666
## Summary
This PR contains changes in the `dataProvider` function for the
addToTimeline action:
- add support for empty values excluding the field, to make it
consistent with the legacy implementation.
- id changes removing the "draggable" word.
- extracted `getIdForField` function to reduce the main function
complexity (linter warning appeared)
This PR also introduces the `CellAction` type for action creation:
- `isCompatible` method parameters uses the new
`CellActionCompatibilityContext` type instead of
`CellActionExecutionContext`, it omits the `field.value` and the
references values, they are not needed to check the compatibility and,
in some situations, it is not possible to pass them.
- use CellAction type in all SecuritySolution action creators
- action creators now return plain objects instead of using
`createAction` (deprecated) function.
- all actions now check `fieldHasCellActions(field.name)` in the
`inCompatible` function, to keep the consistency with legacy code.
- `useLoadAction` hooks now integrate the error control, components
don't need to check the `error` anymore.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
The `useEffect` hooks that set up subscriptions related to the
`timefilter` were missing `[]` to be only called when the code is
mounted, without it they were called on every render. This PR adds the
missing `[]` and also combines the two hooks into one.
Closes#149537
## Summary
This PR will fix the padding issue in metrics explorer. I tried to
investigate what caused the issue and couldn't find any lead in the
`toolbar` component history (nothing changed there). I opened our
monitoring cluster and there the only difference I saw was the
`gutterSize` defined in the flex groups and then all flex items inside
have the correct margins.
<img width="1808" alt="image"
src="https://user-images.githubusercontent.com/14139027/214890355-d5d682b9-4716-4ead-858c-0cf3718122bb.png">
I tried to add `gutterSize` to both flex groups but unfortunately, it
didn't work - the flex items didn't get the margins. Probably the way
the `eu` component passes them is changed. I don't see this issue on any
of the other pages inside Infrastructure so it's maybe an edge case.
I got the "inspiration" for this fix from the [euiFlex
docs](https://elastic.github.io/eui/#/layout/flex#flex-grids-and-flex-groups-can-nest)
and by adding the existing 2 groups in another flex group with defined
`gutterSize` and `direction` to get the correct spacing between the
groups. I am also open to other ideas: I decided to still add this fix
and invest more time to investigate the cause of the bug only if this
fix is not a possible solution to the issue.