From 6eeb82fafa68282280f315f6d184d69469bfd608 Mon Sep 17 00:00:00 2001
From: Joe Desimone <56411054+joe-desimone@users.noreply.github.com>
Date: Thu, 16 May 2024 08:09:59 -0400
Subject: [PATCH] Update configure-integration-policy.asciidoc (#5203)

(cherry picked from commit af7722262da111e06f1653596235345108bb7a63)
---
 docs/getting-started/configure-integration-policy.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/getting-started/configure-integration-policy.asciidoc b/docs/getting-started/configure-integration-policy.asciidoc
index 9bcdffa5b9..9ef4e7796e 100644
--- a/docs/getting-started/configure-integration-policy.asciidoc
+++ b/docs/getting-started/configure-integration-policy.asciidoc
@@ -171,7 +171,7 @@ Malicious behavior protection levels are:
 * **Prevent** (Default): Detects malicious behavior on the host, forces the process to stop,
 and generates an alert.
 
-Select whether you want to use **Reputation service** for additional protection. Elastic's reputation service leverages our extensive threat intelligence knowledge to make high confidence real-time prevention decisions. For example, reputation service can detect suspicious downloads of binaries with low or malicious reputation.
+Select whether you want to use **Reputation service** for additional protection. Elastic's reputation service leverages our extensive threat intelligence knowledge to make high confidence real-time prevention decisions. For example, reputation service can detect suspicious downloads of binaries with low or malicious reputation. Endpoints communicate with the reputation service directly at https://cloud.security.elastic.co. 
 
 NOTE: Reputation service requires an active https://www.elastic.co/pricing[Platinum or Enterprise subscription] and is available on cloud deployments only.