diff --git a/docs/cloud-native-security/cspm-faq.asciidoc b/docs/cloud-native-security/cspm-faq.asciidoc index 9beb616e77..5e6f4f0a68 100644 --- a/docs/cloud-native-security/cspm-faq.asciidoc +++ b/docs/cloud-native-security/cspm-faq.asciidoc @@ -78,7 +78,7 @@ You can access findings data using the following index patterns: Resources are fetched and evaluated against benchmark rules when a security posture management integration is deployed. After that, the CSPM integration evaluates every 24 hours, and the KSPM integration evaluates every four hours. *Can I configure an integration's fetch cycle?* -No, the four-hour fetch cycle is not configurable. +No, the fetch cycle's timing is not configurable. *Can I contribute to the CSP ruleset?* You can't directly edit benchmark rules. The rules are defined https://github.com/elastic/csp-security-policies[in this repository], where you can raise issues with certain rules. They are written in https://www.openpolicyagent.org/docs/latest/policy-language/[Rego]. diff --git a/docs/cloud-native-security/cspm.asciidoc b/docs/cloud-native-security/cspm.asciidoc index a87bded2d0..1a48a609de 100644 --- a/docs/cloud-native-security/cspm.asciidoc +++ b/docs/cloud-native-security/cspm.asciidoc @@ -17,5 +17,5 @@ This feature currently supports Amazon Web Services (AWS), Google Cloud Platform [[cspm-how-it-works]] == How CSPM works -Using the read-only credentials you will provide during the setup process, it will evaluate the configuration of resources in your environment every 4 hours. +Using the read-only credentials you will provide during the setup process, it will evaluate the configuration of resources in your environment every 24 hours. After each evaluation, the integration sends findings to Elastic. A high-level summary of the findings appears on the <>, and detailed findings appear on the <>.