Merge branch 'master' into issue-xxx-preboot-poc

.github/CODEOWNERS

@@ -351,6 +351,21 @@
 /x-pack/test/case_api_integration @elastic/security-threat-hunting
 /x-pack/plugins/lists @elastic/security-detections-response
 
+## Security Solution sub teams - security-onboarding-and-lifecycle-mgt 
+/x-pack/plugins/security_solution/public/management/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/public/common/lib/endpoint*/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/public/common/components/endpoint/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/common/endpoint/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/server/endpoint/routes/trusted_apps/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/server/endpoint/routes/actions/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/server/endpoint/routes/metadata/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/server/endpoint/lib/policy/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/server/lib/license/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/server/fleet_integration/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/scripts/endpoint/event_filters/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/plugins/security_solution/scripts/endpoint/trusted_apps/ @elastic/security-onboarding-and-lifecycle-mgt
+/x-pack/test/security_solution_endpoint/apps/endpoint/ @elastic/security-onboarding-and-lifecycle-mgt
+
 # Security Intelligence And Analytics
 /x-pack/plugins/security_solution/server/lib/detection_engine/rules/prepackaged_rules @elastic/security-intelligence-analytics
 

.i18nrc.json

@@ -16,6 +16,7 @@
     "esUi": "src/plugins/es_ui_shared",
     "devTools": "src/plugins/dev_tools",
     "expressions": "src/plugins/expressions",
+    "expressionError": "src/plugins/expression_error",
     "expressionRevealImage": "src/plugins/expression_reveal_image",
     "inputControl": "src/plugins/input_control_vis",
     "inspector": "src/plugins/inspector",

WORKSPACE.bazel

@@ -10,15 +10,15 @@ load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
 # Fetch Node.js rules
 http_archive(
   name = "build_bazel_rules_nodejs",
-  sha256 = "0fa2d443571c9e02fcb7363a74ae591bdcce2dd76af8677a95965edf329d778a",
-  urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/3.6.0/rules_nodejs-3.6.0.tar.gz"],
+  sha256 = "8f5f192ba02319254aaf2cdcca00ec12eaafeb979a80a1e946773c520ae0a2c9",
+  urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/3.7.0/rules_nodejs-3.7.0.tar.gz"],
 )
 
 # Now that we have the rules let's import from them to complete the work
 load("@build_bazel_rules_nodejs//:index.bzl", "check_rules_nodejs_version", "node_repositories", "yarn_install")
 
 # Assure we have at least a given rules_nodejs version
-check_rules_nodejs_version(minimum_version_string = "3.6.0")
+check_rules_nodejs_version(minimum_version_string = "3.7.0")
 
 # Setup the Node.js toolchain for the architectures we want to support
 #

docs/developer/plugin-list.asciidoc

@@ -72,6 +72,10 @@ This API doesn't support angular, for registering angular dev tools, bootstrap a
 |This plugin contains reusable code in the form of self-contained modules (or libraries). Each of these modules exports a set of functionality relevant to the domain of the module.
 
 
+|{kib-repo}blob/{branch}/src/plugins/expression_error/README.md[expressionError]
+|Expression Error plugin adds an error renderer to the expression plugin. The renderer will display the error image.
+
+
 |{kib-repo}blob/{branch}/src/plugins/expression_reveal_image/README.md[expressionRevealImage]
 |Expression Reveal Image plugin adds a revealImage function to the expression plugin and an associated renderer. The renderer will display the given percentage of a given image.
 

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.exporters.md

@@ -10,5 +10,7 @@
 exporters: {
     datatableToCSV: typeof datatableToCSV;
     CSV_MIME_TYPE: string;
+    cellHasFormulas: (val: string) => boolean;
+    tableHasFormulas: (columns: import("../../expressions").DatatableColumn[], rows: Record<string, any>[]) => boolean;
 }
 ```

docs/management/managing-saved-objects.asciidoc

@@ -37,12 +37,15 @@ and select *Relationships*.
 [[managing-saved-objects-export-objects]]
 === Import and export
 
-Using the import and export commands, you can move objects between different
+Using the import and export actions, you can move objects between different
 {kib} instances. This action is useful when you
 have multiple environments for development and production.
 Import and export also work well when you have a large number
 of objects to update and want to batch the process.
 
+In addition to the user interface, {kib} provides beta <<saved-objects-api-import, import>> and <<saved-objects-api-export, export>> APIs if
+you want to automate this process.
+
 [float]
 ==== Compatibility across versions
 

docs/spaces/index.asciidoc

@@ -12,7 +12,7 @@ spaces, you're asked to choose a space when you log in to Kibana. You can change
 current space at any time by using the menu.
 
 [role="screenshot"]
-image::spaces/images/change-space.png["Change current space menu"]
+image::images/change-space.png["Change current space menu"]
 
 Kibana supports spaces in several ways.  You can:
 
@@ -40,7 +40,7 @@ Open the main menu, then click *Stack Management > Spaces* for an overview of yo
 for you to create, edit, and delete spaces.
 
 [role="screenshot"]
-image::spaces/images/space-management.png["Space management"]
+image::images/space-management.png["Space management"]
 
 [float]
 ==== Create or edit a space
@@ -57,7 +57,7 @@ You cannot change the space identifier once you create the space.
 if you prefer to create spaces programatically.
 
 [role="screenshot"]
-image::spaces/images/edit-space.png["Space management"]
+image::images/edit-space.png["Space management"]
 
 [float]
 ==== Delete a space
@@ -81,7 +81,7 @@ to specific features on a per-user basis, you must configure
 <<xpack-security-authorization, Kibana Security>>.
 
 [role="screenshot"]
-image::spaces/images/edit-space-feature-visibility.png["Controlling features visiblity"]
+image::images/edit-space-feature-visibility.png["Controlling features visiblity"]
 
 [float]
 [[spaces-control-user-access]]
@@ -95,26 +95,13 @@ while analysts or executives might have Dashboard and Canvas with read-only priv
 See <<adding_kibana_privileges>> for details.
 
 [role="screenshot"]
-image::spaces/images/spaces-roles.png["Controlling features visiblity"]
+image::images/spaces-roles.png["Controlling features visiblity"]
 
 [float]
 [[spaces-moving-objects]]
 === Move saved objects between spaces
 
-To <<managing-saved-objects-copy-to-space, copy objects>> from one space to another, open the main menu,
-then click *Stack Management > Saved Objects*.
-
-Alternately, you can move objects using {kib}'s <<managing-saved-objects-export-objects, import and export>>
-interface.
-
-. Navigate to the space that contains your saved objects.
-. Export your saved objects.
-. Navigate to the space where you want to import the objects.
-. Import your saved objects.
-. (Optional) Delete objects in the export space that you no longer need.
-
-{kib} also has beta <<saved-objects-api-import, import>> and
-<<saved-objects-api-export, export>> APIs if you want to automate this process.
+To move saved objects between spaces, you can <<managing-saved-objects-copy-to-space, copy objects>>, or <<managing-saved-objects-export-objects, export and import objects>>.
 
 [float]
 [[spaces-default-route]]
@@ -125,10 +112,10 @@ The landing page can route users to a specific dashboard, application, or saved
 
 To configure the landing page, use the default route setting in
 <<kibana-general-settings, Stack Management > {kib} > Advanced settings>>.
-For example, you might set the default route to `/app/kibana#/dashboards`.
+For example, you might set the default route to `/app/dashboards`.
 
 [role="screenshot"]
-image::spaces/images/spaces-configure-landing-page.png["Configure space-level landing page"]
+image::images/spaces-configure-landing-page.png["Configure space-level landing page"]
 
 
 [float]

docs/user/dashboard/lens.asciidoc

@@ -316,10 +316,16 @@ Each *Layer* in a visualization is associated with an index pattern and mutiple
 You can also change the index pattern for a single *Layer*.
 
 [float]
-[[why-my-field-x-is-missing-from-the-fields-list]]
-===== Why is my field X missing from the fields list?
+[[why-my-field-is-missing-from-the-fields-list]]
+===== Why is my field missing from the fields list?
 
-*Lens* does not support the visualization of full-text fields, therefore it is not showing them in the data summary.
+Fields do not appear in the *Available fields* in the following scenarios:
+* The field is a full-text field.
+* The field is a `geo_point` field
+* The field is a `flattened` field.
+* The field is a `object` field.
+
+Verify if the field appears in the *Empty fields* list. *Lens* uses heuristics to determine if the fields contain values. For sparse data sets, the heuristics are less precise.
 
 [float]
 [[how-to-handle-gaps-in-time-series-visualizations]]
@@ -370,3 +376,9 @@ Here's a short list of few different aspects to check:
 ** If a custom `Number` configuration is used, check that the color stop values are covering the current data range.
 
 ** If a `Percent` configuration is used, and the data range changes, the colors displayed are affected.
+
+[float]
+[[is-it-possible-to-show-icons-in-datatable]]
+===== Is it possible to display icons in data tables?
+
+You can display icons with <<managing-index-patterns, field formatter>> in data tables.

docs/user/introduction.asciidoc

@@ -206,7 +206,7 @@ image::images/rules-and-connectors.png[Rules and Connectors view]
 === Organize your work in spaces
 
 Want to share {kib}’s goodness with other people or teams without overwhelming them? You can do so
-with <<xpack-spaces, Spaces>>, built for organizing your visualizations, dashboards, and indices.
+with <<xpack-spaces, Spaces>>, built for organizing your visualizations, dashboards, and index patterns.
 Think of a space as its own mini {kib} installation&mdash;it’s isolated from all other spaces,
 so you can tailor it to your specific needs without impacting others.
 
@@ -234,15 +234,15 @@ For example, roles with no access to an app will not have access to its alerts.
 ==== Control feature visibility
 
 You can take spaces one step further and control which features are visible
-within each space. For example, you might hide **Dev Tools** in your "Executive"
-space or show **Stack Monitoring** only in your "Admin" space.
+within each space. For example, you might hide **Dev Tools** in your "Marketing"
+space or show **Stack Monitoring** only in your "Engineering" space.
 
 Controlling feature visibility is not a security feature. To secure access
 to specific features on a per-user basis, you must configure
 <<xpack-security-authorization,{kib} Security>>.
 
 [role="screenshot"]
-image::images/features-control.png[Features Controls view]
+image::spaces/images/edit-space-feature-visibility.png[Features Controls view]
 
 [float]
 [[intro-kibana-Security]]
@@ -260,7 +260,7 @@ see <<security-settings-kb,Security settings in {kib}>>.
 allowing you to login using {es}’s built-in realms, or by your own single sign-on provider.
 
 [role="screenshot"]
-image::images/login-screen.png[Login page]
+image::security/images/kibana-login.png[Login page]
 
 [float]
 ==== Secure access
@@ -281,7 +281,7 @@ while analysts or executives might have *Dashboard* and *Canvas* with read-only
 levels, or you can automate role creation via our <<role-management-api,API>>.
 
 [role="screenshot"]
-image::images/roles-and-privileges.png[{kib privileges}]
+image::spaces/images/spaces-roles.png[{kib privileges}]
 
 [float]
 ==== Audit access

docs/user/security/access-agreement.asciidoc

@@ -2,26 +2,31 @@
 [[xpack-security-access-agreement]]
 === Access agreement
 
-Some work environments require you to acknowledge and accept an agreement before you can access {kib}, which can contain sensitive information. The agreement text supports Markdown format and can be specified using the `xpack.security.authc.providers.<provider-type>.<provider-name>.accessAgreement.message` setting.
+Access agreement is a https://www.elastic.co/subscriptions[subscription feature] that requires users to acknowledge and accept an
+agreement before accessing {kib}. The agreement text supports Markdown format and can be specified using the
+`xpack.security.authc.providers.<provider-type>.<provider-name>.accessAgreement.message` setting.
 
 [NOTE]
 ============================================================================
 You need to acknowledge the access agreement only once per session, and {kib} reports the acknowledgement in the audit logs.
 ============================================================================
 
-Here is how your `kibana.yml` can look like if you define an access agreement:
+Here is an example of defining an access agreement in `kibana.yml`:
 
 [source,yaml]
 --------------------------------------------------------------------------------
 xpack.security.authc.providers:
   basic.basic1:
     order: 0
     accessAgreement:
-      message: "**You are accessing a system with a sensitive information** \n\n
-                  By logging in, you acknowledge that (shortened ...)"
+      message: |
+        **You are accessing a system with sensitive information**
+
+        By logging in, you acknowledge that information system usage
+        ...(shortened)
 --------------------------------------------------------------------------------
 
 When you authenticate using `basic.basic1`, you'll see the following agreement that you must acknowledge before you can access {kib}:
 
 [role="screenshot"]
-image::user/security/images/access-agreement.png["Access Agreement UI"]
+image::images/access-agreement.png["Access Agreement UI"]

docs/user/security/api-keys/index.asciidoc

@@ -17,7 +17,7 @@ remote sources, without a live user interaction.
 To manage API keys, open the main menu, then click *Stack Management > API Keys*.
 
 [role="screenshot"]
-image:user/security/api-keys/images/api-keys.png["API Keys UI"]
+image:images/api-keys.png["API Keys UI"]
 
 [float]
 [[api-keys-service]]
@@ -49,7 +49,7 @@ cluster privileges to use API keys in {kib}. To manage roles, open the main menu
 To create an API key, open the main menu, then click *Stack Management > API Keys > Create API key*.
 
 [role="screenshot"]
-image:user/security/api-keys/images/create-api-key.png["Create API Key UI"]
+image:images/create-api-key.png["Create API Key UI"]
 
 Once created, you can copy the API key (Base64 encoded) and use it to send requests to {es} on your behalf. For example:
 

docs/user/security/audit-logging.asciidoc

@@ -2,9 +2,9 @@
 [[xpack-security-audit-logging]]
 === Audit logs
 
-You can enable auditing to keep track of security-related events such as
-authorization success and failures. Logging these events enables you to monitor
-{kib} for suspicious activity and provides evidence in the event of an attack.
+Audit logging is a https://www.elastic.co/subscriptions[subscription feature] that you can enable to keep track of security-related events,
+such as authorization success and failures. Logging these events enables you to monitor {kib} for suspicious activity and provides evidence
+in the event of an attack.
 
 Use the {kib} audit logs in conjunction with {ref}/enable-audit-logging.html[{es} audit logging] to get a
 holistic view of all security related events. {kib} defers to the {es} security