Stages removal of security content (elastic#574) (elastic#580)

Author: lcawl

docs/en/stack/redirects.asciidoc

@@ -288,4 +288,108 @@ See {ref}/how-monitoring-works.html[How monitoring works].
 === Troubleshooting monitoring
 
 This page has moved.
-See {ref}/monitoring-troubleshooting.html[Troubleshooting monitoring].
+See {ref}/monitoring-troubleshooting.html[Troubleshooting monitoring].
+
+[role="exclude",id="auditing"]
+=== Auditing security events
+
+This page has moved. 
+//See {ref}/auditing.html[Auditing security events].
+
+[role="exclude",id="audit-event-types"]
+=== Audit event types
+
+This page has moved.
+//See {ref}/audit-event-types.html[Audit event types].
+
+[role="exclude",id="audit-log-output"]
+=== Logfile audit output
+
+[[audit-log-ignore-policy]]
+This page has moved.
+//See {ref}/audit-log-output.html[Logfile audit output].
+
+[role="exclude",id="auditing-search-queries"]
+=== Auditing search queries
+
+This page has moved.
+//See {ref}/auditing-search-queries.html[Auditing search queries].
+
+[role="exclude",id="encrypting-communications"]
+=== Encrypting communications
+
+This page has moved.
+//See {ref}/encrypting-communications.html[Encrypting communications].
+
+[role="exclude",id="ssl-tls"]
+=== Setting up TLS on a cluster
+
+This page has moved.
+//See {ref}/ssl-tls.html[Setting up TLS on a cluster].
+
+[role="exclude",id="ciphers"]
+=== Enabling cipher suites for stronger encryption
+
+This page has moved.
+See {ref}/ciphers.html[Enabling cipher suites for stronger encryption].
+
+[role="exclude",id="ip-filtering"]
+=== Restricting connections with IP filtering
+
+This page has moved.
+//See {ref}/ip-filtering.html[Restricting connections with IP filtering].
+
+[role="exclude",id="ccs-clients-integrations"]
+=== Cross cluster search, clients, and integrations
+
+This page has moved.
+//See {ref}/ccs-clients-integrations.html[Cross cluster search, clients, and integrations]. 
+
+[role="exclude",id="cross-cluster-configuring"]
+=== Cross cluster search and security
+
+This page has moved.
+//See {ref}/cross-cluster-configuring.html[Cross cluster search and security].
+
+[role="exclude",id="java-clients"]
+=== Java Client and security
+
+[[transport-client]]
+This page has moved.
+//See {ref}/java-clients.html[Java Client and security].
+
+[role="exclude",id="http-clients"]
+=== HTTP/REST clients and security
+
+This page has moved.
+//See {ref}/http-clients.html[].
+
+[role="exclude",id="hadoop"]
+=== ES-Hadoop and Security
+
+This page has moved.
+//See {ref}/hadoop.html[].
+
+[role="exclude",id="beats"]
+=== Beats and Security
+
+See:
+
+* {auditbeat-ref}/securing-beats.html[{auditbeat}]
+* {filebeat-ref}/securing-beats.html[{filebeat}]
+* {heartbeat-ref}/securing-beats.html[{heartbeat}]
+* {metricbeat-ref}/securing-beats.html[{metricbeat}]
+* {packetbeat-ref}/securing-beats.html[{packetbeat}]
+* {winlogbeat-ref}/securing-beats.html[{winlogbeat}]
+
+[role="exclude",id="secure-monitoring"]
+=== Monitoring and security
+
+This page has moved.
+//See {ref}/secure-monitoring.html[].
+
+[role="exclude",id="separating-node-client-traffic"]
+=== Separating node-to-node and client traffic
+
+This page has moved.
+See {ref}/separating-node-client-traffic.html[Separating node-to-node and client traffic].

docs/en/stack/security/get-started-security.asciidoc

@@ -352,7 +352,7 @@ Logstash and {es}.
 * <<beats,Configuring security in the Beats>>. Configure authentication 
 credentials and encrypt connections to {es}. 
 
-* <<java-clients,Configuring the Java transport client to use encrypted communications>>.
+* Configuring the Java transport client to use encrypted communications.
 
 * {hadoop-ref}/security.html[Configuring {es} for Apache Hadoop to use secured transport]. 
 

docs/en/stack/security/index.asciidoc

@@ -53,9 +53,9 @@ A critical part of security is keeping confidential data confidential.
 Elasticsearch has built-in protections against accidental data loss and
 corruption. However, there's nothing to stop deliberate tampering or data
 interception. The {stack-security-features} preserve the integrity of your
-data by <<ssl-tls, encrypting communications>> to and from nodes. For even
-greater protection, you can increase the <<ciphers, encryption strength>> and
-<<separating-node-client-traffic, separate client traffic from node-to-node communications>>.
+data by <<ssl-tls, encrypting communications>> to and from nodes.
+//For even greater protection, you can increase the <<ciphers, encryption strength>> and
+//<<separating-node-client-traffic, separate client traffic from node-to-node communications>>.
 
 
 [float]
@@ -96,13 +96,13 @@ include::authentication/index.asciidoc[]
 
 include::authorization/index.asciidoc[]
 
-include::{xes-repo-dir}/security/auditing/index.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/auditing/index.asciidoc[]
 
-include::{xes-repo-dir}/security/securing-communications.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/securing-communications.asciidoc[]
 
-include::{xes-repo-dir}/security/using-ip-filtering.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/using-ip-filtering.asciidoc[]
 
-include::{xes-repo-dir}/security/ccs-clients-integrations.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/ccs-clients-integrations.asciidoc[]
 
 include::get-started-security.asciidoc[]