anchor.diff:  auditing. For more information, see
   {stack-ov}/elasticsearch-security.html[Securing the {stack}].
   
  -To use {es} {security-features}:
  -
  -. Verify that you are using a license that includes the {security-features}.
  +. Verify that you are using a license that includes the specific
  +{security-features} you want.
   +
   --
  -If you want to try all of the platinum features, you can start a 30-day trial.
  -At the end of the trial period, you can purchase a subscription to keep using
  -the full functionality. For more information, see
  -https://www.elastic.co/subscriptions and
  -{stack-ov}/license-management.html[License Management].
  +For more information, see https://www.elastic.co/subscriptions and
  +{stack-ov}/license-management.html[License management].
   --
   
   . Verify that the `xpack.security.enabled` setting is `true` on each node in
  -your cluster. If you are using a trial license, the default value is `false`.
  -For more information, see {ref}/security-settings.html[Security Settings in {es}].
  +your cluster. If you are using basic or trial licenses, the default value is `false`.
  +For more information, see {ref}/security-settings.html[Security settings in {es}].
   
   . If you plan to run {es} in a Federal Information Processing Standard (FIPS) 
   140-2 enabled JVM, see <<fips-140-compliance>>. 
   
  -. Configure Transport Layer Security (TLS/SSL) for internode-communication.
  +. <<configuring-tls,Configure Transport Layer Security (TLS/SSL) for internode-communication>>.
   +
   --
   NOTE: This requirement applies to clusters with more than one node and to
   clusters with a single node that listens on an external interface. Single-node
   clusters that use a loopback interface do not have this requirement.  For more
   information, see
  -{stack-ov}/encrypting-communications.html[Encrypting Communications].
  +{stack-ov}/encrypting-communications.html[Encrypting communications].
   
   --
  -.. <<node-certificates,Generate node certificates for each of your {es} nodes>>.
  -
  -.. <<tls-transport, Enable TLS on each {es} node>>.
   
   . If it is not already running, start {es}.
   
  
positive.code: Events are logged to a dedicated `<clustername>_audit.json` file in
  `ES_HOME/logs`, on each cluster node.
  --
  
  :edit_url: https://github.com/elastic/elasticsearch/edit/{branch}/docs/reference/security/securing-communications/securing-elasticsearch.asciidoc
  include::{es-repo-dir}/security/securing-communications/securing-elasticsearch.asciidoc[]
  
negative.code: // NOTCONSOLE
  --
  
  . [[enable-auditing]](Optional) Enable auditing to keep track of attempted and
  successful interactions with your {es} cluster:
  +
  --
  TIP: Audit logging is available with specific subscriptions. For more
  information, see https://www.elastic.co/subscriptions.
  
  .. Add the following setting to `elasticsearch.yml` on all nodes in your cluster:
  +
  [source,yaml]
  