diff --git a/docs/en/security/tribe-clients-integrations.asciidoc b/docs/en/security/tribe-clients-integrations.asciidoc
index bee0fbb4bdf..f076ed2a4db 100644
--- a/docs/en/security/tribe-clients-integrations.asciidoc
+++ b/docs/en/security/tribe-clients-integrations.asciidoc
@@ -15,15 +15,16 @@ secured cluster:
 * <<http-clients, HTTP Clients>>
 
 
-{security} enables you to secure you Elasticsearch cluster. But Elasticsearch
-itself is only one product within the Elastic Stack. It is often the case that
-other products in the stack are connected to the cluster and therefore need to
-be secured as well, or at least communicate with the cluster in a secured way:
+{security} enables you to secure your {es} cluster. But {es} itself is only one
+product within the Elastic Stack. It is often the case that other products in
+the stack are connected to the cluster and therefore need to be secured as well,
+or at least communicate with the cluster in a secured way:
 
 * <<hadoop, Apache Hadoop>>
 * <<logstash, Logstash>>
 * <<kibana, Kibana>>
 * <<secure-monitoring, Monitoring>>
+* {kibana-ref}/secure-reporting.html[Reporting]
 
 include::tribe-clients-integrations/cross-cluster.asciidoc[]
 
@@ -42,5 +43,3 @@ include::tribe-clients-integrations/beats.asciidoc[]
 include::tribe-clients-integrations/kibana.asciidoc[]
 
 include::tribe-clients-integrations/monitoring.asciidoc[]
-
-include::tribe-clients-integrations/reporting.asciidoc[]
diff --git a/docs/en/security/tribe-clients-integrations/reporting.asciidoc b/docs/en/security/tribe-clients-integrations/reporting.asciidoc
deleted file mode 100644
index 31b1108ed2f..00000000000
--- a/docs/en/security/tribe-clients-integrations/reporting.asciidoc
+++ /dev/null
@@ -1,45 +0,0 @@
-[[secure-reporting]]
-=== Reporting and Security
-
-Reporting operates by creating and updating documents in Elasticsearch in
-response to user actions in Kibana.
-
-To use Reporting with {security} enabled, you need to <<kibana, set up Kibana
-to work with {security}>>. If you are automatically generating reports with
-<<xpack-alerting, {watcher}>>, you also need to configure {watcher} to trust the
-Kibana server's certificate.
-//TO-DO: Add link:
-//For more information, see {kibana-ref}/securing-reporting.html[Securing Reporting].
-
-[[reporting-app-users]]
-To enable users to generate reports, assign them the built in `reporting_user`
-and `kibana_user` roles:
-
-* If you're using the `native` realm, you can assign roles through
-**Management / Users** UI in Kibana or with the `user` API. For example,
-the following request creates a `reporter` user that has the
-`reporting_user` and `kibana_user` roles:
-+
-[source, sh]
----------------------------------------------------------------
-POST /_xpack/security/user/reporter
-{
-  "password" : "x-pack-test-password",
-  "roles" : ["kibana_user", "reporting_user"],
-  "full_name" : "Reporting User"
-}
----------------------------------------------------------------
-
-* If you are using an LDAP or Active Directory realm, you can either assign
-roles on a per user basis, or assign roles to groups of users. By default, role
-mappings are configured in <<mapping-roles, `config/shield/role_mapping.yml`>>.
-For example, the following snippet assigns the user named Bill Murray the
-`kibana_user` and `reporting_user` roles:
-+
-[source,yaml]
---------------------------------------------------------------------------------
-kibana_user:
-  - "cn=Bill Murray,dc=example,dc=com"
-reporting_user:
-  - "cn=Bill Murray,dc=example,dc=com"
---------------------------------------------------------------------------------