Skip to content

Commit b683416

Browse files
Sec reqs
1 parent 8610c74 commit b683416

File tree

3 files changed

+30
-74
lines changed

3 files changed

+30
-74
lines changed

raw-migrated-files/docs-content/serverless/security-requirements-overview.md

Lines changed: 0 additions & 50 deletions
This file was deleted.

raw-migrated-files/toc.yml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -238,7 +238,6 @@ toc:
238238
- file: docs-content/serverless/security-prebuilt-rules-management.md
239239
- file: docs-content/serverless/security-query-alert-indices.md
240240
- file: docs-content/serverless/security-reduce-notifications-alerts.md
241-
- file: docs-content/serverless/security-requirements-overview.md
242241
- file: docs-content/serverless/security-response-actions-config.md
243242
- file: docs-content/serverless/security-response-actions-history.md
244243
- file: docs-content/serverless/security-response-actions.md

solutions/security/get-started/elastic-security-requirements.md

Lines changed: 30 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -4,59 +4,62 @@ mapped_urls:
44
- https://www.elastic.co/guide/en/serverless/current/security-requirements-overview.html
55
---
66

7-
# Elastic Security requirements
7+
# Elastic Security requirements [security-requirements-overview]
88

9-
% What needs to be done: Align serverless/stateful
9+
% Need to revisit these paras
10+
% {{elastic-sec}} is an inbuilt part of {{kib}}. To use {{elastic-sec}}, you only need an {{stack}} deployment (an {{es}} cluster and {{kib}}).
1011

11-
% Use migrated content from existing pages that map to this page:
12+
% {{ecloud}} offers all of the features of {{es}}, {{kib}}, and {{elastic-sec}} as a hosted service available on AWS, GCP, and Azure. To get started, sign up for a [free {{ecloud}} trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
1213

13-
% - [x] ./raw-migrated-files/security-docs/security/sec-requirements.md
14-
% - [ ] ./raw-migrated-files/docs-content/serverless/security-requirements-overview.md
14+
% For information about installing and managing the {{stack}} yourself, see [Installing the {{stack}}](/get-started/the-stack.md).
1515

16-
{{elastic-sec}} is an inbuilt part of {{kib}}. To use {{elastic-sec}}, you only need an {{stack}} deployment (an {{es}} cluster and {{kib}}).
17-
18-
{{ecloud}} offers all of the features of {{es}}, {{kib}}, and {{elastic-sec}} as a hosted service available on AWS, GCP, and Azure. To get started, sign up for a [free {{ecloud}} trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
19-
20-
For information about installing and managing the {{stack}} yourself, see [Installing the {{stack}}](/get-started/the-stack.md).
21-
22-
The [Support Matrix](https://www.elastic.co/support/matrix) page lists officially supported operating systems, platforms, and browsers on which {{es}}, {{kib}}, {{beats}}, and Elastic Endpoint have been tested.
16+
The [Support Matrix](https://www.elastic.co/support/matrix) page lists officially supported operating systems, platforms, and browsers on which components such as {{beats}}, {{agent}}, {{elastic-defend}}, and {{elastic-endpoint}} have been tested.
2317

2418

2519
## Node role requirements [node-role-requirements]
2620

27-
To use Elastic Security, at least one node in your Elasticsearch cluster must have the [`transform` role](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/transforms-settings.md). Nodes are automatically given this role when they’re created, so changes are not required if default role settings remain the same. This applies to on-premise and cloud deployments.
21+
```yaml {applies_to}
22+
stack:
23+
```
24+
25+
To use {{elastic-sec}}, at least one node in your Elasticsearch cluster must have the [`transform` role](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/transforms-settings.md). Nodes are automatically given this role when they’re created, so changes are not required if default role settings remain the same. This applies to on-premise and cloud deployments.
2826

2927
Changes might be required if your nodes have customized roles. When updating node roles, nodes are only assigned the roles you specify, and default roles are removed. If you need to reassign the `transform` role to a node, [create a dedicated transform node](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/node-settings.md#transform-node).
3028

3129

3230
## Space and index privileges [_space_and_index_privileges]
3331

32+
3433
To use {{elastic-sec}}, your role must have at least:
3534

3635
* `Read` privilege for the `Security` feature in the [space](/deploy-manage/manage-spaces.md). This grants you `Read` access to all features in {{elastic-sec}} except cases. You need additional [minimum privileges](/solutions/security/investigate/cases-requirements.md) to use cases.
3736
* `Read` and `view_index_metadata` privileges for all {{elastic-sec}} indices, such as `filebeat-*`, `packetbeat-*`, `logs-*`, and `endgame-*` indices.
3837

3938
::::{note}
40-
[*Configure advanced settings*](/solutions/security/get-started/configure-advanced-settings.md) describes how to modify {{elastic-sec}} indices.
39+
[Configure advanced settings](/solutions/security/get-started/configure-advanced-settings.md) describes how to modify {{elastic-sec}} indices.
4140
::::
4241

4342

4443
For more information about index privileges, refer to [{{es}} security privileges](/deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md).
4544

4645

47-
## Feature-specific requirements [_feature_specific_requirements]
46+
## Feature-specific requirements [security-requirements-overview-feature-specific-requirements]
4847

4948
There are some additional requirements for specific features:
5049

51-
* [*Detections requirements*](/solutions/security/detect-and-alert/detections-requirements.md)
50+
* [Detections requirements](/solutions/security/detect-and-alert/detections-requirements.md)
5251
* [Cases requirements](/solutions/security/investigate/cases-requirements.md)
5352
* [Entity risk scoring requirements](/solutions/security/advanced-entity-analytics/entity-risk-scoring-requirements.md)
5453
* [Machine learning job and rule requirements](/solutions/security/advanced-entity-analytics/machine-learning-job-rule-requirements.md)
55-
* [*{{elastic-defend}} requirements*](/solutions/security/configure-elastic-defend/elastic-defend-requirements.md)
54+
* [{{elastic-defend}} requirements](/solutions/security/configure-elastic-defend/elastic-defend-requirements.md)
5655
* [Configure network map data](/solutions/security/explore/configure-network-map-data.md)
5756

5857

59-
## License requirements [_license_requirements]
58+
## License requirements [security-license-requirements]
59+
60+
```yaml {applies_to}
61+
stack:
62+
```
6063

6164
All features are available as part of the free Basic plan **except**:
6265

@@ -67,22 +70,26 @@ All features are available as part of the free Basic plan **except**:
6770
[Elastic Stack subscriptions](https://www.elastic.co/subscriptions) lists the required subscription plans for all features.
6871

6972

70-
## Advanced configuration and UI options [_advanced_configuration_and_ui_options]
73+
## Advanced configuration and UI options [security-requirements-overview-advanced-configuration-and-ui-options]
7174

72-
[*Configure advanced settings*](/solutions/security/get-started/configure-advanced-settings.md) describes how to modify advanced settings, such as the {{elastic-sec}} indices, default time intervals used in filters, and IP reputation links.
75+
[Configure advanced settings](/solutions/security/get-started/configure-advanced-settings.md) describes how to modify advanced settings, such as the {{elastic-sec}} indices, default time intervals used in filters, and IP reputation links.
7376

7477

75-
## Third-party collectors mapped to ECS [_third_party_collectors_mapped_to_ecs]
78+
## Third-party collectors mapped to ECS [security-requirements-overview-third-party-collectors-mapped-to-ecs]
7679

7780
The [Elastic Common Schema (ECS)](https://www.elastic.co/guide/en/ecs/current) defines a common set of fields to be used for storing event data in Elasticsearch. ECS helps users normalize their event data to better analyze, visualize, and correlate the data represented in their events. {{elastic-sec}} can ingest and normalize events from any ECS-compliant data source.
7881

7982
::::{important}
80-
{{elastic-sec}} requires [ECS-compliant data](https://www.elastic.co/guide/en/ecs/current). If you use third-party data collectors to ship data to {{es}}, the data must be mapped to ECS. [*Elastic Security ECS field reference*](asciidocalypse://docs/docs-content/docs/reference/security/fields-and-object-schemas/siem-field-reference.md) lists ECS fields used in {{elastic-sec}}.
83+
{{elastic-sec}} requires [ECS-compliant data](https://www.elastic.co/guide/en/ecs/current). If you use third-party data collectors to ship data to {{es}}, the data must be mapped to ECS. [{{elastic-sec}} ECS field reference](asciidocalypse://docs/docs-content/docs/reference/security/fields-and-object-schemas/siem-field-reference.md) lists ECS fields used in {{elastic-sec}}.
8184
::::
8285

8386

8487

85-
## Cross-cluster searches [_cross_cluster_searches]
88+
## Cross-cluster searches [security-cross-cluster-searches]
89+
90+
```yaml {applies_to}
91+
stack:
92+
```
8693

8794
For information on how to perform cross-cluster searches on {{elastic-sec}} indices, see:
8895

0 commit comments

Comments
 (0)