diff --git a/docs/products-solutions.asciidoc b/docs/products-solutions.asciidoc
index 4b0a2cf4e..a8fca573c 100644
--- a/docs/products-solutions.asciidoc
+++ b/docs/products-solutions.asciidoc
@@ -5,11 +5,11 @@ The following Elastic products support ECS out of the box, as of version 7.0:
 
 * {beats-ref}/beats-reference.html[{beats}]
 * {apm-get-started-ref}/overview.html[APM]
-* {siem-guide}/siem-overview.html[Elastic SIEM app]
-** {siem-guide}/siem-field-reference.html[SIEM Field Reference Guide] - a list of ECS fields used in the SIEM app
+* {security-guide}/es-overview.html[Elastic Security]
+** {security-guide}/siem-field-reference.html[Elastic Security Field Reference] - a list of ECS fields used in the SIEM app
 * https://www.elastic.co/products/endpoint-security[Elastic Endpoint Security
 Server]
-* {logs-guide}/logs-app-overview.html[Logs app]
+* {logs-guide}/logs-app-overview.html[Logs Monitoring]
 * Log formatters that support ECS out of the box for various languages can be found
   https://github.com/elastic/ecs-logging/blob/master/README.md[here].
 
diff --git a/docs/using-getting-started.asciidoc b/docs/using-getting-started.asciidoc
index 8b71d1412..8e322d742 100644
--- a/docs/using-getting-started.asciidoc
+++ b/docs/using-getting-started.asciidoc
@@ -285,5 +285,5 @@ Here are some examples of additional fields processed by metadata or parser proc
 We've covered at a high level how to map your events to ECS. Now if you'd like your events to render well in the Elastic
 solutions, check out the reference guides below to learn more about each:
 
-* https://www.elastic.co/guide/en/logs/guide/current/logs-fields-reference.html[Logs UI fields reference]
-* https://www.elastic.co/guide/en/security/master/siem-field-reference.html[Elastic Security fields reference]
+* {logs-guide}/logs-fields-reference.html[Logs Monitoring Field Reference]
+* {security-guide}/siem-field-reference.html[Elastic Security Field Reference]