[DOCS] Cleans up links to security content (#47610) (#47704)

Author: lcawl

docs/reference/ccr/apis/auto-follow/delete-auto-follow-pattern.asciidoc

@@ -43,13 +43,13 @@ DELETE /_ccr/auto_follow/<auto_follow_pattern_name>
 
 * If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-delete-auto-follow-pattern-desc]]
 ==== {api-description-title}
 
 This API deletes a configured collection of
-{stack-ov}/ccr-auto-follow.html[auto-follow patterns].
+<<ccr-auto-follow,auto-follow patterns>>.
 
 [[ccr-delete-auto-follow-pattern-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ccr/apis/auto-follow/get-auto-follow-pattern.asciidoc

@@ -57,12 +57,12 @@ GET /_ccr/auto_follow/<auto_follow_pattern_name>
 
 * If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-get-auto-follow-pattern-desc]]
 ==== {api-description-title}
 
-This API gets configured {stack-ov}/ccr-auto-follow.html[auto-follow patterns].
+This API gets configured <<ccr-auto-follow,auto-follow patterns>>.
 This API will return the specified auto-follow pattern collection.
 
 [[ccr-get-auto-follow-pattern-path-parms]]

docs/reference/ccr/apis/auto-follow/put-auto-follow-pattern.asciidoc

@@ -47,14 +47,13 @@ DELETE /_ccr/auto_follow/auto_follow_pattern_name
 * If the {es} {security-features} are enabled, you must have `read` and `monitor`
 index privileges for the leader index patterns. You must also have `manage_ccr`
 cluster privileges on the cluster that contains the follower index. For more
-information, see
-{stack-ov}/security-privileges.html[Security privileges].
+information, see <<security-privileges>>.
 
 [[ccr-put-auto-follow-pattern-desc]]
 ==== {api-description-title}
 
 This API creates a new named collection of
-{stack-ov}/ccr-auto-follow.html[auto-follow patterns] against the remote cluster
+<<ccr-auto-follow,auto-follow patterns>> against the remote cluster
 specified in the request body. Newly created indices on the remote cluster
 matching any of the specified patterns will be automatically configured as follower
 indices.

docs/reference/ccr/apis/follow/get-follow-info.asciidoc

@@ -45,8 +45,7 @@ GET /<index>/_ccr/info
 ==== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `monitor` cluster
-privileges. For more information, see
-{stack-ov}/security-privileges.html[Security privileges].
+privileges. For more information, see <<security-privileges>>.
 
 [[ccr-get-follow-info-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/get-follow-stats.asciidoc

@@ -46,7 +46,7 @@ GET /<index>/_ccr/stats
 
 * If the {es} {security-features} are enabled, you must have `monitor` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-get-follow-stats-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/post-forget-follower.asciidoc

@@ -73,7 +73,7 @@ POST /<leader_index>/_ccr/forget_follower
 
 * If the {es} {security-features} are enabled, you must have `manage_leader_index`
 index privileges for the leader index. For more information, see
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ccr-post-forget-follower-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/post-pause-follow.asciidoc

@@ -39,7 +39,7 @@ POST /<follower_index>/_ccr/pause_follow
 
 * If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-post-pause-follow-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/post-resume-follow.asciidoc

@@ -54,7 +54,7 @@ POST /<follower_index>/_ccr/resume_follow
 index privileges for the follower index. You must have `read` and `monitor`
 index privileges for the leader index. You must also have `manage_ccr` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-post-resume-follow-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/post-unfollow.asciidoc

@@ -43,7 +43,7 @@ POST /<follower_index>/_ccr/unfollow
 
 * If the {es} {security-features} are enabled, you must have `manage_follow_index` 
 index privileges for the follower index. For more information, see
-{stack-ov}/security-privileges.html[Security privileges].  
+<<security-privileges>>.  
 
 [[ccr-post-unfollow-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/put-follow.asciidoc

@@ -43,8 +43,7 @@ PUT /<follower_index>/_ccr/follow?wait_for_active_shards=1
 and `manage_follow_index` index privileges for the follower index. You must have
 `read` and `monitor` index privileges for the leader index. You must also have
 `manage_ccr` cluster privileges on the cluster that contains the follower index.
-For more information, see
-{stack-ov}/security-privileges.html[Security privileges].
+For more information, see <<security-privileges>>.
 
 [[ccr-put-follow-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/get-ccr-stats.asciidoc

@@ -45,7 +45,7 @@ GET /_ccr/stats
 
 * If the {es} {security-features} are enabled, you must have `monitor` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-get-stats-desc]]
 ==== {api-description-title}

docs/reference/ccr/getting-started.asciidoc

@@ -34,7 +34,7 @@ to control which users have authority to manage {ccr}.
 By default, you can perform all of the steps in this tutorial by
 using the built-in `elastic` user. However, a password must be set for this user
 before the user can do anything. For information about how to set that password,
-see {stack-ov}/security-getting-started.html[Tutorial: Getting started with security].
+see <<security-getting-started>>.
 
 If you are performing these steps in a production environment, take extra care
 because the `elastic` user has the `superuser` role and you could inadvertently

docs/reference/commands/certutil.asciidoc

@@ -224,7 +224,7 @@ Alternatively, you can specify the `--ca-pass`, `--out`, and `--pass` parameters
 By default, this command generates a file called `elastic-certificates.p12`,
 which you can copy to the relevant configuration directory for each Elastic
 product that you want to configure. For more information, see
-{xpack-ref}/ssl-tls.html[Setting Up TLS on a Cluster].
+<<ssl-tls>>.
 
 [float]
 [[certutil-silent]]

docs/reference/commands/setup-passwords.asciidoc

@@ -4,7 +4,7 @@
 == elasticsearch-setup-passwords
 
 The `elasticsearch-setup-passwords` command sets the passwords for the
-{stack-ov}/built-in-users.html[built-in users].
+<<built-in-users,built-in users>>.
 
 [float]
 === Synopsis
@@ -21,7 +21,7 @@ bin/elasticsearch-setup-passwords auto|interactive
 
 This command is intended for use only during the initial configuration of the
 {es} {security-features}. It uses the
-{stack-ov}/built-in-users.html#bootstrap-elastic-passwords[`elastic` bootstrap password]
+<<bootstrap-elastic-passwords,`elastic` bootstrap password>>
 to run user management API requests. After you set a password for the `elastic`
 user, the bootstrap password is no longer active and you cannot use this command.
 Instead, you can change passwords by using the *Management > Users* UI in {kib}
@@ -36,7 +36,7 @@ location, ensure that the *ES_PATH_CONF* environment variable returns the
 correct path before you run the `elasticsearch-setup-passwords` command. You can
 override settings in your `elasticsearch.yml` file by using the `-E` command
 option. For more information about debugging connection failures, see
-{stack-ov}/trb-security-setup.html[`elasticsearch-setup-passwords` command fails due to connection failure].
+<<trb-security-setup>>.
 
 [float]
 === Parameters

docs/reference/commands/users-command.asciidoc

@@ -33,7 +33,7 @@ Leading or trailing whitespace is not allowed.
 
 Passwords must be at least 6 characters long.
 
-For more information, see {xpack-ref}/file-realm.html[File-based User Authentication].
+For more information, see <<file-realm>>.
 
 TIP: To ensure that {es} can read the user and role information at startup, run
 `elasticsearch-users useradd` as the same user you use to run {es}. Running the

docs/reference/glossary.asciidoc

@@ -31,7 +31,7 @@ current master node fails.
 
 The {ccr} feature enables you to replicate indices in remote clusters to your
 local cluster. For more information, see 
-{stack-ov}/xpack-ccr.html[{ccr-cap}].  
+{ref}/xpack-ccr.html[{ccr-cap}].  
 
 [[glossary-ccs]] {ccs} (CCS)::
 

docs/reference/high-availability/backup-and-restore-security-config.asciidoc

@@ -96,7 +96,7 @@ prevent non-administrators exfiltrating data.
 +
 --
 The following example creates a new user `snapshot_user` in the
-{stack-ov}/native-realm.html[native realm], but it is not important which
+<<native-realm,native realm>>, but it is not important which
 realm the user is a member of:
 
 [source,js]
@@ -207,7 +207,7 @@ Then log into one of the node hosts, navigate to {es} installation directory,
 and follow these steps:
 
 . Add a new user with the `superuser` built-in role to the
-{stack-ov}/file-realm.html[file realm].
+<<file-realm,file realm>>.
 +
 --
 For example, create a user named `restore_user`:

docs/reference/high-availability/backup-cluster-data.asciidoc

@@ -22,6 +22,6 @@ It does *not* grant privileges to create repositories, restore snapshots, or
 search within indices. Hence, the user can view and snapshot all indices, but cannot
 access or modify any data.
 
-For more information, see {stack-ov}/security-privileges.html[Security privileges]
-and {stack-ov}/built-in-roles.html[Built-in roles].
+For more information, see <<security-privileges>>
+and <<built-in-roles>>.
 ====

docs/reference/ilm/apis/delete-lifecycle.asciidoc

@@ -30,7 +30,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` cluster privilege to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/explain.asciidoc

@@ -41,7 +41,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 
 You must have the `view_index_metadata` or `manage_ilm` or both privileges on the indices
 being managed to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/get-lifecycle.asciidoc

@@ -30,7 +30,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` or `read_ilm` or both cluster privileges to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/get-status.asciidoc

@@ -28,7 +28,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` or `read_ilm` or both cluster privileges to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/move-to-step.asciidoc

@@ -39,7 +39,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` privileges on the indices being managed to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/put-lifecycle.asciidoc

@@ -36,7 +36,7 @@ You must have the `manage_ilm` cluster privilege to use this API. You must
 also have the `manage` index privilege on all indices being managed by `policy`.
 All operations executed by {ilm} for a policy are executed as the user that
 put the latest version of a policy.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/remove-policy-from-index.asciidoc

@@ -30,7 +30,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` privileges on the indices being managed to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/retry-policy.asciidoc

@@ -30,7 +30,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` privileges on the indices being managed to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/slm-api.asciidoc

@@ -43,7 +43,7 @@ You must have the `manage_slm` cluster privilege to use this API. You must also
 have the `manage` index privilege on all indices being managed by `policy`. All
 operations executed by {slm} for a policy are executed as the user that put the
 latest version of a policy. For more information, see
-{stack-ov}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 ==== Example
 

docs/reference/ilm/apis/start.asciidoc

@@ -27,7 +27,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` cluster privilege to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/stop.asciidoc

@@ -32,7 +32,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` cluster privilege to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/licensing/delete-license.asciidoc

@@ -17,14 +17,14 @@ This API enables you to delete licensing information.
 ==== Description
 
 When your license expires, {xpack} operates in a degraded mode.  For more
-information, see {xpack-ref}/license-expiration.html[License Expiration].
+information, see {stack-ov}/license-expiration.html[License Expiration].
 
 [float]
 ==== Authorization
 
 You must have `manage` cluster privileges to use this API.
 For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/get-basic-status.asciidoc

@@ -25,8 +25,7 @@ https://www.elastic.co/subscriptions.
 ==== Authorization
 
 You must have `monitor` cluster privileges to use this API.
-For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/get-license.asciidoc

@@ -35,8 +35,7 @@ https://www.elastic.co/subscriptions.
 ==== Authorization
 
 You must have `monitor` cluster privileges to use this API.
-For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 
 [float]

docs/reference/licensing/get-trial-status.asciidoc

@@ -32,7 +32,7 @@ https://www.elastic.co/subscriptions.
 
 You must have `monitor` cluster privileges to use this API.
 For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/start-basic.asciidoc

@@ -32,7 +32,7 @@ https://www.elastic.co/subscriptions.
 
 You must have `manage` cluster privileges to use this API.
 For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/start-trial.asciidoc

@@ -35,7 +35,7 @@ https://www.elastic.co/subscriptions.
 
 You must have `manage` cluster privileges to use this API.
 For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/update-license.asciidoc

@@ -162,4 +162,4 @@ curl -XPUT -u elastic 'http://<host>:<port>/_license?acknowledge=true' -H "Conte
 // NOTCONSOLE
 
 For more information about the features that are disabled when you downgrade
-your license, see {xpack-ref}/license-expiration.html[License Expiration].
+your license, see {stack-ov}/license-expiration.html[License Expiration].

docs/reference/ml/anomaly-detection/apis/close-job.asciidoc

@@ -26,7 +26,7 @@ operations, but you can still explore and navigate results.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-close-job-desc]]
 ==== {api-description-title}