Apoorva Joshi
f24b42980d
* Updating host risk score docs
* Update docs/experimental-machine-learning/host-risk-score.md
Co-authored-by: Justin Ibarra <brokensound77@users.noreply.github.com>
* Making some changes
* Adding space to :all the things:
Co-authored-by: Justin Ibarra <brokensound77@users.noreply.github.com>
(cherry picked from commit 74fa8ebe48)
103 lines
5.0 KiB
Markdown
103 lines
5.0 KiB
Markdown
# Host Risk Score- What is it?
|
|
|
|
The Host Risk Score package (available as a GitHub release [here](https://github.com/elastic/detection-rules/releases)) consists of all the artifacts required to stand up the host risk scoring framework in your environment. This framework leverages transforms and visualizations in Kibana to identify the most suspicious hosts in your environment, based on alert activity on the hosts.
|
|
To deploy this framework in your environment, follow the steps outlined below.
|
|
|
|
# Detailed steps
|
|
|
|
#### 1. Unzip the release bundle
|
|
|
|
#### 2. Modify artifacts to reflect Kibana space
|
|
For security reasons, we require that you restrict the Host Risk Score application to a specific Kibana space. In order to do so, run the `generate_scripts.py` script with your Kibana space as the argument.
|
|
|
|
Eg:
|
|
|
|
```
|
|
python generate_scripts.py --space default
|
|
```
|
|
|
|
This will create a folder named `<your-space-name>`, consisting of all the required artifacts, modified for your Kibana space. **For the steps that follow, please use the scripts from this folder.**
|
|
|
|
#### 3. Navigate to the Dev Tools console in Kibana
|
|
|
|
You will now upload all the Host Risk Score artifacts to Kibana. Remember to suffix the names of all the scripts, ingest pipelines, transforms etc. with your Kibana space, while uploading them.
|
|
#### 4. Uploading required scripts
|
|
|
|
Upload the contents of `ml_hostriskscore_levels_script.json`, `ml_hostriskscore_map_script.json` and `ml_hostriskscore_reduce_script.json` as individual scripts, using the Script API.
|
|
|
|
Eg:
|
|
|
|
```
|
|
PUT _scripts/ml_hostriskscore_levels_script_<your-space-name>
|
|
{content of the ml_hostriskscore_levels_script.json file}
|
|
```
|
|
|
|
#### 5. Upload required ingest pipelines
|
|
|
|
Upload the ingest pipeline in `ml_hostriskscore_ingest_pipeline.json` using the following API call:
|
|
|
|
|
|
```
|
|
PUT _ingest/pipeline/ml_hostriskscore_ingest_pipeline_<your-space-name>
|
|
{content of the ml_hostriskscore_ingest_pipeline.json file}
|
|
```
|
|
|
|
#### 6. Upload and start the `pivot` transform
|
|
|
|
Upload the `pivot` transform in `ml_hostriskscore_pivot_transform.json` using the following API call. This transform calculates the risk level per hour for each host in the Kibana space specified in Step 2:
|
|
|
|
|
|
```
|
|
PUT _transform/ml_hostriskscore_pivot_transform_<your-space-name>
|
|
{content of the ml_hostriskscore_pivot_transform.json file}
|
|
```
|
|
|
|
* Navigate to `Transforms` under `Management` -> `Stack Management`. For the transform with the ID `ml_hostriskscore_pivot_transform_<your-space-name>`, under `Actions`, click `Start`.
|
|
* Verify that the Transform started as expected by ensuring that documents are appearing in the destination index of the Transform, eg: using the Search/Count APIs:
|
|
|
|
|
|
```
|
|
GET ml_host_risk_score_<your-space-name>/_search (or _count)
|
|
```
|
|
|
|
#### 7. Create the space-aware `ml_host_risk_score_latest_<your-space-name>` index with appropriate mappings
|
|
|
|
```
|
|
PUT ml_host_risk_score_latest_<your-space-name>
|
|
{
|
|
"mappings" : {
|
|
"properties" : {
|
|
"host.name" : { "type" : "keyword" }
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
#### 8. Upload the `latest` transform
|
|
|
|
Upload the `latest` transform in `ml_hostriskscore_latest_transform.json` using the following API call. This transform gets the most current risk levels for all the hosts in the Kibana space specified in Step 2:
|
|
|
|
|
|
```
|
|
PUT _transform/ml_hostriskscore_latest_transform_<your-space-name>
|
|
{content of the ml_hostriskscore_latest_transform.json file}
|
|
```
|
|
|
|
* Navigate to `Transforms` under `Management` -> `Stack Management`. For the transform with the ID `ml_hostriskscore_latest_transform_<your-space-name>`, under `Actions`, click `Start`.
|
|
* Verify that the Transform started as expected by ensuring that documents are appearing in the destination index of the Transform, eg: using the Search/Count APIs:
|
|
|
|
|
|
```
|
|
GET ml_host_risk_score_latest_<your-space-name>/_search (or _count)
|
|
```
|
|
|
|
#### 8. Import the dashboards
|
|
|
|
* Navigate to `Management` -> `Stack Management` -> `Kibana` -> `Saved Objects`
|
|
* Click on `Import` and import the `ml_hostriskscore_dashboards.ndjson` file
|
|
* Navigate to `Analytics` -> `Dashboard`. You should see two dashboards- `Current Risk Scores for Hosts`, which displays the current list (Top 20) of suspicious hosts in your environment, and `Drilldown of Host Risk Score`, which allows you to further drill down into details of the risk associated with a particular host of interest.
|
|
|
|
# About hostnames and host IDs
|
|
|
|
The Host Risk Score app currently uses host names (`host.name`), not the `host.id` field, for both searching and displaying hosts. There may be some edge cases where hosts use the same name. Physical Windows clients - desktops and laptops - in an Active Directory forest, are unlikely to have name collisions, as their computer accounts and distinguished names should be unique. Non-domain member servers, desktops and laptops, in a Windows workgroup, may occasionally have name collisions. Macs are often not managed by a directory service and may have name collisions. Virtual servers, that are created from templates or cloning processes may have hostname collisions.
|