Skip to content

Commit 03a7812

Browse files
authored
Updates Security billing topic (elastic#959)
Resolves elastic#790.
1 parent ef950de commit 03a7812

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

deploy-manage/cloud-organization/billing/security-billing-dimensions.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,7 @@ Endpoint Protection is an *optional* add-on to Security Analytics that provides
2828
* **Endpoint Protection Essentials** — Includes robust protection against malware, ransomware, and other malicious behaviors.
2929
* **Endpoint Protection Complete** — Adds endpoint response actions and advanced policy management.
3030

31-
You pay based on the number of protected endpoints you configure with the {{elastic-defend}} integration. Note that logs, events, and alerts ingested into your Security project from endpoints running {{elastic-defend}} are billed using the **Ingest** and **Retention** pricing described above.
32-
31+
You pay based on the number of protected endpoints configured with the {{elastic-defend}} integration. Logs, events, and alerts from these endpoints are billed using the **Ingest** and **Retention** pricing. If you're using {{elastic-defend}} solely for data collection (without Endpoint Essentials or Complete add-ons), endpoints do not count towards billing. In this case, you're only billed for data ingestion and retention, and you can configure event collection and telemetry in the policy without enabling protections.
3332

3433
## Cloud Protection [security-billing-cloud-protection]
3534

0 commit comments

Comments
 (0)