- Elastic Cloud Serverless
- Elasticsearch
- Elastic Observability
- Get started
- Observability overview
- Elastic Observability Serverless billing dimensions
- Create an Observability project
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Get started with dashboards
- Applications and services
- Application performance monitoring (APM)
- Get started with traces and APM
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Reduce storage
- Managed intake service event API
- Troubleshooting
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure a Synthetics project
- Multifactor Authentication for browser monitors
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Scale and architect a deployment
- Synthetics Encryption and Security
- Troubleshooting
- Application performance monitoring (APM)
- Infrastructure and hosts
- Logs
- Inventory
- Incident management
- Data set quality
- Observability AI Assistant
- Machine learning
- Reference
- Get started
- Elastic Security
- Elastic Security overview
- Security billing dimensions
- Create a Security project
- Elastic Security requirements
- Elastic Security UI
- AI for Security
- Ingest data
- Configure endpoint protection with Elastic Defend
- Manage Elastic Defend
- Endpoints
- Policies
- Trusted applications
- Event filters
- Host isolation exceptions
- Blocklist
- Optimize Elastic Defend
- Event capture and Elastic Defend
- Endpoint protection rules
- Identify antivirus software on your hosts
- Allowlist Elastic Endpoint in third-party antivirus apps
- Elastic Endpoint self-protection features
- Elastic Endpoint command reference
- Endpoint response actions
- Cloud Security
- Explore your data
- Dashboards
- Detection engine overview
- Rules
- Alerts
- Advanced Entity Analytics
- Investigation tools
- Asset management
- Manage settings
- Troubleshooting
- Manage your project
- Changelog
Entity risk scoring requirements
editEntity risk scoring requirements
editTo use entity risk scoring and asset criticality, you need the appropriate user roles. These features require the Security Analytics Complete project feature.
This page covers the requirements for using the entity risk scoring and asset criticality features, as well as their known limitations.
Entity risk scoring
editUser roles
editTo turn on the risk scoring engine, you need either the appropriate predefined Security user role or a custom role with the right privileges:
Predefined roles
- Platform engineer
- Detections admin
- Admin
Custom role privileges
| Cluster | Index | Kibana |
|---|---|---|
|
|
Read for the Security feature |
Known limitations
edit- The risk scoring engine uses an internal user role to score all hosts and users. After you turn on the risk scoring engine, all alerts in the project will contribute to host and user risk scores.
- You cannot customize alert data views or risk weights associated with alerts and asset criticality levels.
Asset criticality
editUser roles
editTo use asset criticality, you need either the appropriate predefined Security user role or a custom role with the right privileges:
Predefined roles
| Action | Predefined role |
|---|---|
View asset criticality |
|
View, assign, change, or unassign asset criticality |
|
Custom role privileges
Custom roles need the following privileges for the .asset-criticality.asset-criticality-<space-id> index:
| Action | Index privilege |
|---|---|
View asset criticality |
|
View, assign, or change asset criticality |
|
Unassign asset criticality |
|