[6.7] Stages removal of security content

docs/en/stack/redirects.asciidoc

@@ -314,4 +314,199 @@ This page has moved. See:
 ** {heartbeat-ref}/monitoring.html[Heartbeat]
 ** {metricbeat-ref}/monitoring.html[Metricbeat]
 ** {packetbeat-ref}/monitoring.html[Packetbeat]
-** {winlogbeat-ref}/monitoring.html[Winlogbeat] 
+** {winlogbeat-ref}/monitoring.html[Winlogbeat] 
+
+[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[Monitoring and security].
+
+[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].
+
+[role="exclude",id="custom-realms"]
+=== Integrating with other authentication systems
+
+This page has moved.
+//See {ref}/custom-realms.html[Integrating with other authentication systems].
+
+[role="exclude",id="anonymous-access"]
+=== Enabling anonymous access
+
+This page has moved.
+//See {ref}/anonymous-access.html[Enabling anonymous access].
+
+[role="exclude",id="controlling-user-cache"]
+=== Controlling the user cache
+
+This page has moved.
+//See {ref}/controlling-user-cache.html[Controlling the user cache].
+
+[role="exclude",id="saml-guide"]
+=== Configuring SAML single-sign-on on the {stack}
+
+This page has moved.
+//See {ref}/saml-guide.html[Configuring SAML SSO on the {stack}].
+
+[role="exclude",id="saml-kibana"]
+=== Configuring Kibana
+
+[[saml-kibana-basic]]
+This page has moved.
+//See {ref}/saml-kibana.html[Configuring Kibana].
+
+[role="exclude",id="defining-roles"]
+=== Defining roles
+
+[[roles-application-priv]]
+This
+[[roles-management-file]]
+page has moved.
+
+[role="exclude",id="securing-aliases"]
+=== Granting privileges for indices and aliases
+
+This page has moved.
+
+[role="exclude",id="mapping-roles"]
+=== Mapping users and groups to roles
+
+[[mapping-roles-file]]
+This
+[[ldap-role-mapping]]
+page has moved.
+
+[role="exclude",id="field-and-document-access-control"]
+=== Setting up field and document level security
+
+This page has moved.
+
+[role="exclude",id="run-as-privilege"]
+=== Submitting requests on behalf of other users
+
+This page has moved.
+
+[role="exclude",id="custom-roles-authorization"]
+=== Customizing roles and authorization
+
+This page has moved.
+
+[role="exclude",id="saml-guide-authentication"]
+=== Configure {es} for SAML authentication
+
+[[saml-attribute-mapping]]
+This
+[[saml-create-realm]]
+page
+[[saml-enc-sign]]
+has
+[[saml-logout]]
+moved
+[[req-authn-context]]
+.
+
+[role="exclude",id="saml-guide-idp"]
+=== The identity provider
+
+This page has moved.
+
+[role="exclude",id="saml-role-mapping"]
+=== Configuring role mappings
+
+This page has moved.

docs/en/stack/security/authentication/active-directory-realm.asciidoc

@@ -66,7 +66,10 @@ properties are populated in the user's _metadata_:
 
 This metadata is returned in the 
 {ref}/security-api-authenticate.html[authenticate API] and can be used with
-<<templating-role-query, templated queries>> in roles.
+//TEMPORARILY OMIT:<<templating-role-query,
+templated queries
+//>>
+in roles.
 
 Additional metadata can be extracted from the Active Directory server by configuring
 the `metadata` setting on the Active Directory realm.

docs/en/stack/security/authentication/index.asciidoc

@@ -13,10 +13,10 @@ include::pki-realm.asciidoc[]
 include::saml-realm.asciidoc[]
 include::kerberos-realm.asciidoc[]
 
-include::{xes-repo-dir}/security/authentication/custom-realm.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authentication/custom-realm.asciidoc[]
 
-include::{xes-repo-dir}/security/authentication/anonymous-access.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authentication/anonymous-access.asciidoc[]
 
-include::{xes-repo-dir}/security/authentication/user-cache.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authentication/user-cache.asciidoc[]
 
-include::{xes-repo-dir}/security/authentication/saml-guide.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authentication/saml-guide.asciidoc[]

docs/en/stack/security/authentication/ldap-realm.asciidoc

@@ -73,12 +73,22 @@ populated in the user's _metadata_:
 
 This metadata is returned in the
 {ref}/security-api-authenticate.html[authenticate API], and can be used with
-<<templating-role-query, templated queries>> in roles.
+//TEMPORARILY OMIT:<<templating-role-query,
+templated queries
+//>>
+in roles.
 
 Additional fields can be included in the user's metadata by  configuring
 the `metadata` setting on the LDAP realm. This metadata is available for use
-with the <<mapping-roles-api, role mapping API>> or in
-<<templating-role-query, templated role queries>>.
+with the 
+//TEMPORARILY OMIT:<<mapping-roles-api,
+role mapping API
+//>>
+or in
+//TEMPORARILY OMIT:<<templating-role-query,
+templated role queries
+//>>
+.
 
 [[ldap-ssl]]
 ==== Setting up SSL Between Elasticsearch and LDAP

docs/en/stack/security/authorization/index.asciidoc

@@ -3,20 +3,20 @@ include::overview.asciidoc[]
 
 include::built-in-roles.asciidoc[]
 
-include::{xes-repo-dir}/security/authorization/managing-roles.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authorization/managing-roles.asciidoc[]
 
 include::privileges.asciidoc[]
 
 include::document-level-security.asciidoc[]
 
 include::field-level-security.asciidoc[]
 
-include::{xes-repo-dir}/security/authorization/alias-privileges.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authorization/alias-privileges.asciidoc[]
 
-include::{xes-repo-dir}/security/authorization/mapping-roles.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authorization/mapping-roles.asciidoc[]
 
-include::{xes-repo-dir}/security/authorization/field-and-document-access-control.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authorization/field-and-document-access-control.asciidoc[]
 
-include::{xes-repo-dir}/security/authorization/run-as-privilege.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authorization/run-as-privilege.asciidoc[]
 
-include::{xes-repo-dir}/security/authorization/custom-authorization.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/authorization/custom-authorization.asciidoc[]

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]
@@ -79,9 +79,11 @@ operational issues.
   provides more information about how Security supports user authentication,
   authorization, and encryption.
 
+////
 * <<ccs-tribe-clients-integrations>>
   shows you how to interact with an Elasticsearch cluster protected by the 
   {stack-security-features}.
+////
 
 [float]
 === Have Comments, Questions, or Feedback?
@@ -96,13 +98,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/tribe-clients-integrations.asciidoc[]
+//TEMPORARILY OMIT:include::{xes-repo-dir}/security/tribe-clients-integrations.asciidoc[]
 
 include::get-started-security.asciidoc[]