-
Notifications
You must be signed in to change notification settings - Fork 191
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Security upgrade guide 7.17-8.x * Replaces component names with attributes * Adds links * Fixes formatting * First round of slight edits. * Apply suggestions from code review Co-authored-by: Benjamin Ironside Goldstein <[email protected]> * Addresses feedback * Merging some feedback * Merging more feedback... * More feedback... * Adding some more feedback... * Typo fix * Adding in Mike's feedback * Two small nits. --------- Co-authored-by: Janeen Roberts <[email protected]> Co-authored-by: Benjamin Ironside Goldstein <[email protected]> Co-authored-by: Janeen Mikell Roberts <[email protected]> (cherry picked from commit cdd1e6e) Co-authored-by: natasha-moore-elastic <[email protected]>
- Loading branch information
1 parent
50e4a39
commit d8fb877
Showing
2 changed files
with
161 additions
and
68 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,158 @@ | ||
| [[upgrade-7.17-8x]] | ||
| == Upgrade from 7.17 to an 8.x version | ||
|
|
||
| [float] | ||
| === Why it's important to upgrade | ||
|
|
||
| Upgrading provides you access to {elastic-sec}'s latest features, enhancements, and bug fixes, many of which enable you to save your organization money, respond faster to potential threats, and improve the tools you use to investigate and analyze your data. For more benefits, check out our blog, https://www.elastic.co/blog/top-5-reasons-to-upgrade-elastic-security[Top 5 reasons to upgrade Elastic Security]. Also, it's important to ensure that your deployment is fully maintained and supported. For more information, refer to https://www.elastic.co/support/eol[Elastic's Product End of Life Dates]. | ||
|
|
||
| [float] | ||
| === Plan for your upgrade | ||
|
|
||
| Before upgrading to {elastic-sec} 8.x, consider the following recommendations: | ||
|
|
||
| * Plan for an appropriate amount of time to complete the upgrade. Depending on your configuration and the size of your cluster, the process can take up to a week to complete. | ||
|
|
||
| * Open a https://support.elastic.co[support case] with Elastic to alert our Elastic Support team of your system change. If you need additional assistance, https://www.elastic.co/consulting[Elastic Consulting Services] provides the technical expertise and step-by-step approach for upgrading your Elastic deployment. | ||
|
|
||
| * Choose a version to upgrade to. We recommend the latest minor and patch version. Be sure to upgrade your development or non-production deployment to the same version as your production deployment. | ||
|
|
||
| * Ensure that you have {kibana-ref}/xpack-monitoring.html[stack monitoring] enabled in {kib}. Take note of your current index and search rate. | ||
|
|
||
| * Review your selected version's features, Elastic connectors, integrations, and detection rules to determine if you can replace any customized content with out-of-the-box functionality. This can help reduce your workload and the complexity of your upgrade. | ||
|
|
||
| * If your organization sends alerts (formerly known as signals) to an external SOAR (security orchestration, automation, and response) platform, you may need to change your workflows to accommodate the new <<alert-schema, alert schema>> used in 8.x. | ||
|
|
||
| * Review release notes, deprecations, and breaking changes for {security-guide}/release-notes.html[{elastic-sec}], {ref}/es-release-notes.html[{es}], {kibana-ref}/release-notes.html[{kib}], and, if applicable, {fleet-guide}/release-notes.html[{fleet} and {agent}], {beats-ref}/release-notes.html[{beats}], and {logstash-ref}/releasenotes.html[{ls}]. Identify any issues that might affect your deployment. Work with your Elastic team on any questions you may have. Start with breaking changes for your solution and platform components, such as {es} and {kib}. | ||
|
|
||
| * Schedule a system maintenance window within your organization. | ||
|
|
||
| [float] | ||
| === Pre-upgrade steps | ||
|
|
||
| To prepare for the upgrade process, follow these steps before you start: | ||
|
|
||
| . Do a software version inventory across your entire Elastic deployment, including {es}, {kib}, {agent}, {beats}, and {ls}. | ||
|
|
||
| . If you're running any versions earlier than 7.17, you must first upgrade them all to the latest 7.17.x patch release before upgrading to 8.x. This enables you to use the Upgrade Assistant to upgrade to 8.x. | ||
| + | ||
| NOTE: If you're managing your deployments using {ece-ref}/ece-upgrade.html[{ece}] (ECE) or {eck-ref}/k8s-upgrading-eck.html[{eck}] (ECK), you may need to upgrade the system clusters first. | ||
|
|
||
| . Note that alerts in 8.x are written using the `kibana_system` user instead of the `current user`, so any user-modified ingest pipelines configured against the alert index (this is uncommon) will use the `kibana_system` user privileges, which may break your ingest pipeline. If you encounter this issue, please do not update your ingest pipeline. Instead, contact your Elastic Support rep for assistance. | ||
|
|
||
| . Run the {kibana-ref}/upgrade-assistant.html[Upgrade Assistant]. Take note of any critical error messages, then work with your Elastic Support rep to resolve them. | ||
| + | ||
| .Requirements | ||
| [sidebar] | ||
| -- | ||
| To run the Upgrade Assistant, you must have the `superuser` role on the cluster. | ||
| -- | ||
|
|
||
| . If you're not using {ref}/snapshots-take-snapshot.html#automate-snapshots-slm[{slm} (SLM)], you must set up and configure a policy, then run the policy to create at least one {ref}/snapshot-restore.html[snapshot] -- a backup of indices taken from a running cluster. If you need to roll back during the upgrade process, use a recent snapshot to avoid data loss. Snapshots are {ref}/snapshot-restore.html#how-snapshots-work[incremental] -- depending on the cluster size and the input/output rate, the initial snapshot may take several hours to complete. If you're using SLM, {ref}/snapshots-take-snapshot.html#check-slm-history[check the SLM history] to ensure that snapshots are completing successfully. | ||
|
|
||
| [float] | ||
| === Perform an 8.x upgrade on a deployment | ||
|
|
||
| IMPORTANT: We strongly recommend performing the following steps on a non-production deployment first to address any potential issues before upgrading your production deployments. If you're using a cross-cluster search environment, upgrade your remote deployments first. | ||
|
|
||
| . If you haven't already done so, back up your cluster data to a {ref}/snapshots-take-snapshot.html[snapshot]. | ||
|
|
||
| . We recommend you <<rules-api-export, export all your custom detection rules>> in case there are issues with the detection engine after the upgrade. | ||
|
|
||
| . Upgrade {es}. | ||
| ** If you're using {ecloud}, we recommend upgrades with no downtime. Refer to {cloud}/ec-upgrade-deployment.html[these instructions]. | ||
| ** If you're using {ece} (ECE), refer to {ece-ref}/ece-upgrade-deployment.html[these instructions]. | ||
| ** If you're using {eck} (ECK), refer to {eck-ref}/k8s-upgrading-stack.html[these instructions]. | ||
| ** If you're upgrading a self-orchestrated deployment, refer to {stack-ref}/upgrading-elasticsearch.html[these instructions] and upgrade the data nodes tier by tier in this order: | ||
| ... Frozen tier | ||
| ... Cold tier | ||
| ... Warm tier | ||
| ... Hot tier | ||
| ... Any other nodes not in a tier | ||
| ... All remaining nodes that are neither master-eligible nor data nodes | ||
| ... Master-eligible nodes | ||
|
|
||
| . Upgrade {kib}. Refer to {stack-ref}/upgrading-kibana.html[these instructions]. | ||
| + | ||
| NOTE: If you're using Elastic Cloud Hosted or {ece}, this is already included in the {es} upgrade. | ||
|
|
||
| . Validate that {es} and {kib} are operating as expected by completing the following checks: | ||
| .. For {es}: | ||
| ... Check the status of your clusters and ensure that they're green by running a `GET _cat/health` API request. For more information, refer to the {ref}/cat-health.html[cat health API documentation]. | ||
| ... Ensure that the index and search rate are close to what they were before upgrading. Go to **Stack Monitoring** -> **{es}** -> **Overview**. | ||
| + | ||
| TIP: You can also check the index document count using the {ref}/cat-indices.html[cat index API]. | ||
| ... Verify that SLM is taking snapshots by {ref}/snapshots-take-snapshot.html#check-slm-history[checking the SLM history]. | ||
| ... If you use {ml}, ensure that it is up and running. | ||
| .. For {kib}: | ||
| ... Ensure that you and your users can successfully log in to {kib} and access desired pages. | ||
| ... Check {kibana-ref}/discover.html[Discover] and verify that the index patterns you typically use are available. | ||
| ... Verify that your commonly used {kibana-ref}/dashboard.html[dashboards] are available and working properly. | ||
| ... If you use any Watcher-based {kib} scheduled {kibana-ref}/reporting-getting-started.html[reporting], ensure that it's working properly. | ||
|
|
||
| . Upgrade your ingest components (such as {ls}, {fleet} and {agent}, {beats}, etc.). For details, refer to the {stack-ref}/upgrading-elastic-stack.html[Elastic Stack upgrade docs]. | ||
|
|
||
| . Validate that Ingest is operating correctly. | ||
| .. Open *Discover*, go through data views for each of your expected ingest data streams, and ensure that data is being ingested in the expected format and volume. | ||
|
|
||
| . Validate that {elastic-sec} is operating correctly. | ||
| .. Re-enable your desired SIEM detection rules (rule management), and ensure that enabled rules are running without errors or warnings (rule monitoring). | ||
| .. Ensure that any SOAR workflows that consume alerts are working. | ||
| .. Verify that any custom dashboards your team has created are working properly, especially if they operate on alert documents. | ||
|
|
||
| . If you performed these steps on a non-production deployment, repeat these same steps on your production environment. If you're using a cross-cluster search environment and performed these steps on your remote clusters, repeat these same steps on your other deployments. | ||
| . Confirm with your appropriate stakeholders that the upgrade process has been successful. | ||
|
|
||
| [float] | ||
| === Post-upgrade steps | ||
|
|
||
| The following sections describe procedures to complete after upgrading {elastic-sec} to 8.x. | ||
|
|
||
| [float] | ||
| [[reenable-rules-upgrade]] | ||
| ==== Re-enable disabled rules | ||
|
|
||
| Any active rules when you upgrade from 7.17 to 8.0.1 or newer are automatically disabled, and a tag named `auto_disabled_8.0` is added to those rules for tracking purposes. Once the upgrade is complete, you can filter rules by the new tag, then use bulk actions to re-enable them: | ||
|
|
||
| . Go to the Rules page (*Detect -> Rules*). | ||
| . From the *Tags* dropdown, search for `auto_disabled_8.0`. | ||
| . Click *Select all _x_ rules*, or individually select the rules you want to re-enable. | ||
| . Click *Bulk actions -> Enable* to re-enable the rules. | ||
|
|
||
| Alternatively, you can use the <<bulk-actions-rules-api, Bulk rule actions>> API to re-enable rules. | ||
|
|
||
| [float] | ||
| [[fda-upgrade]] | ||
| ==== Full Disk Access (FDA) approval for {elastic-endpoint} | ||
|
|
||
| When you manually install {elastic-endpoint}, you must approve a system extension, kernel extension, and enable Full Disk Access (FDA). There is a new FDA requirement in 8.x. Refer to <<elastic-endpoint-deploy-reqs>> to review the required permissions. | ||
|
|
||
| [float] | ||
| [[data-views-upgrade]] | ||
| ==== Requirements to display Data views in the {security-app} | ||
|
|
||
| To make the *Data view* option appear in an environment with legacy alerts, a user with elevated role privileges must visit the {security-app}, open a page that displays alert data (at least one alert must be present), and then refresh the page. The user's role privileges must allow them to enable the detections feature in a {kib} space. For more information, refer to <<enable-detections-ui, Enable and access detections>>. | ||
|
|
||
| [float] | ||
| [[alert-schema-upgrade]] | ||
| ==== New alert schema | ||
|
|
||
| The system index for detection alerts has been renamed from `.siem-signals-<space-id>` to `.alerts-security.alerts-<space-id>` and is now a hidden index. Therefore, the schema used for alert documents in {elastic-sec} has changed. Users that access documents in the `.siem-signals` indices using the {elastic-sec} API must modify their API queries and scripts to operate properly on the new 8.x alert documents. Refer to <<query-alert-indices, how to query alert indices>> and review the new <<alert-schema, Alert schema>>. | ||
|
|
||
| [float] | ||
| [[preview-upgrade]] | ||
| ==== New privileges required to view alerts and preview rules | ||
|
|
||
| * To view alerts, users need `manage`, `write`, `read`, and `view_index_metadata` privileges for two new indices, `.alerts-security.alerts` and `.internal.alerts-security.alerts`. Existing users who are upgrading to 8.x can retain their privileges to the `.siem-signals` index. | ||
|
|
||
| * To <<preview-rules, preview rules>>, users need `read` access to the new `.preview.alerts-security.alerts` index. Refer to <<detections-permissions-section>> for more information. | ||
|
|
||
| [float] | ||
| [[im-rules-upgrade]] | ||
| ==== Updates to indicator match rules | ||
|
|
||
| Changes to the indicator match rule type's <<rule-ui-advanced-params, default threat indicator path>> might require you to update existing rules or create new ones after upgrading to 8.x. Be mindful of the following: | ||
|
|
||
| * If an indicator match rule's default threat indicator path was not defined before the upgrade, it will default to `threatintel.indicator` after the upgrade. This allows the rule to continue using indicator data ingested by {filebeat} version 7.x. If a custom value was defined before the upgrade, the value will not change. | ||
| * If an existing indicator match rule was configured to use threat indicator indices generated from {filebeat} version 7.x, updating the default threat indicator path to `threat.indicator` after you upgrade to {stack} version 8.x and {agent} or {filebeat} version 8.x configures the rule to use threat indicator indices generated by those later versions. | ||
| * You must create separate rules to query threat intelligence indices created by {filebeat} version 7.x and version 8.x because each version requires a different default threat indicator path value. Review the recommendations for <<query-alert-indices, querying alert indices>>. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters