Skip to content

[Security Solution] Implement rule customization license checks#206079

Merged
xcrzx merged 1 commit intoelastic:mainfrom
xcrzx:licensing
Jan 29, 2025
Merged

[Security Solution] Implement rule customization license checks#206079
xcrzx merged 1 commit intoelastic:mainfrom
xcrzx:licensing

Conversation

@xcrzx
Copy link
Copy Markdown
Contributor

@xcrzx xcrzx commented Jan 9, 2025

Resolves: https://github.com/elastic/security-team/issues/10410

Summary

We want to make Rule Customization available at higher license tiers.

Intended Workflows/UX

Basic/Platinum/Security Essentials License Tiers

  • Editing Prebuilt Rules:

    • Allow the 8.16 behavior: only actions, exceptions, snoozing, and enable/disable options can be modified.

    • On the rule editing page, all tabs except Actions are disabled. Disabled tabs will display a hover explanation:

      • "Upgrade to Enterprise to enable prebuilt rule customization" for ECH.
      • "Upgrade to Security Complete to enable prebuilt rule customization" for Serverless.
        image
    • Rule editing via API is not restricted (tracked separately: https://github.com/elastic/security-team/issues/11504.

  • Bulk Actions:

    • Modifications to rule content via bulk actions are not allowed. Prebuilt rules are excluded from bulk actions if the license level is insufficient. Users will see an explanation for the exclusion.

      • Serverless
        image
      • ECH
    • On the API level (_bulk_action), an error is returned if a user tries to modify a prebuilt rule without the required license. Response in this case looks like this:

      {
        "statusCode": 500,
        "error": "Internal Server Error",
        "message": "Bulk edit failed",
        "attributes": {
           "errors": [
             {
               "message": "Elastic rule can't be edited",
               "status_code": 500,
               "rules": []
             }
           ]
        }
      }
  • Rule Updates:

    • Updates are restricted to Elastic’s incoming updates only.
    • The rule upgrade flyout is in read-only mode.
      image
    • For previously customized rules where customization is now disabled due to insufficient licensing, a notification will appear on the upgrade flyout, clarifying that only an upgrade to Elastic's version is available.
      image
    • On the API level (_perform), only requests with pick_version = target are permitted. Requests with rule.fields values are not allowed.
      API response when pick_version is not target:
      {
        "message": "Only the 'TARGET'  version can be selected for a rule update; received:  'CURRENT'",
        "status_code": 400
      }
      API response when the fields value is provided:
      {
        "message": "Rule field customization is not allowed. Received fields: name, description",
        "status_code": 400
      }
  • Customized Rules:

    • Existing customizations remain intact, and the “Modified” badge is retained

      • On the rule management, monitoring, and update tables:
        image
      • On the rule update flyout:
        image
      • On the rule details page:
        image
    • When we edit a rule with customizations (e.g., change rule's actions), the rule should stay marked as customized

  • Import/Export Scenarios:

Enterprise/Security Complete License Tiers

  • All rules can be fully edited
  • Upgraded prebuilt or customized rules will have an editable view, enabling full customization

@xcrzx xcrzx added release_note:skip Skip the PR/issue when compiling release notes Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area v8.18.0 labels Jan 9, 2025
@xcrzx xcrzx self-assigned this Jan 9, 2025
@xcrzx xcrzx marked this pull request as ready for review January 15, 2025 13:15
@xcrzx xcrzx requested review from a team as code owners January 15, 2025 13:15
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@xcrzx xcrzx added the backport:version Backport to applied version labels label Jan 15, 2025
Copy link
Copy Markdown
Contributor

@jbudz jbudz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.buildkite/ftr_*_configs.yml LGTM

@xcrzx xcrzx added the ui-copy Review of UI copy with docs team is recommended label Jan 16, 2025
Copy link
Copy Markdown
Contributor

@dhurley14 dhurley14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

detection engine changes LGTM just one nit.

@nikitaindik
Copy link
Copy Markdown
Contributor

@xcrzx, thanks for the PR and the walkthrough you gave me over Zoom!

While I'm still reviewing the code, here are my findings from the manual testing.

I have thoroughly tested the changes locally under both ECH and Serverless with the feature flag on and off and with different licenses/tiers.

Main scenarios outlined in the PR description work as expected.
If the feature flag is off or the license level is not sufficient:

  • 🟢 Users can't edit prebuilt rule content via the Rule Editing page
  • 🟢 Users can't edit prebuilt rule content via the bulk actions in UI
  • 🟢 Users can't edit prebuilt rule content via the bulk actions API
  • 🟢 Users can still edit prebuilt rule actions and exception lists via UI and via bulk/CRUD endpoints.
  • 🟢 Users can't apply customizations while upgrading a prebuilt rule via flyout or API. Upgrading to "target" version is allowed.
  • 🟢 Upsell messages appropriate for ECH and Serverless flavours are shown in UI. Not shown if the FF is off.
  • 🟡 Users can still edit prebuilt rule content via CRUD API. Not ideal, but that's out of scope for this PR.

There's an issue with showing "Modified" badges (which depend on is_customized).

  • For example, when you have the FF on and are on ECH Enterprise license, and you customize a rule, it's going to to have rule_source.is_customized: true. If you then downgrade to Basic license and apply another customization via CRUD API, rule_source.is_customized is going to be set to false and you won't be able too see "Modified" badges in UI even though the rule is customized. It seems like now we always set rule_source.is_customized: false if the license is insufficient even though the feature flag is on.
  • Another example for the same issue. Serverless: If you have the FF on and customize a rule while on Complete tier, it's going to have rule_source.is_customized: true. Then if you switch to Essentials and add an action or exception (so no change in rule content), it'll revert to rule_source.is_customized: false and you won't see "Modified" badges. Then if you switch back to Complete and save without making any changes, it'll become "Modified" again, which might be unexpected to users since they haven't really modified it.

Also, we may want to add a line about prebuilt rule customizations to a modal that's displayed when you click on "revert to Basic license" button in ECH (Stack Mgmt -> License management)
converting_to_basic

And I also noticed a copy issue in the bulk actions modal which is probably unrelated to your changes.
rule_actions_bulk

I'll continue taking a look at the code.

Copy link
Copy Markdown
Contributor

@agusruidiazgd agusruidiazgd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM from explore team

@xcrzx
Copy link
Copy Markdown
Contributor Author

xcrzx commented Jan 29, 2025

There's an issue with showing "Modified" badges (which depend on is_customized).

Hey @nikitaindik, thanks for looking into that.

I've updated the logic to recalculate the is_customized field, and it now includes downgrade cases. I tested the following scenarios:

  1. A rule was modified with FF enabled and a sufficient license level. As expected, the rule was marked as "modified"
  2. Downgraded the license level to basic. The rule still displayed the "modified" badge
  3. Added actions to the rule. The "modified" badge now remained
  4. Upgraded the rule to the latest version. All modifications were reset, so the "modified" badge was no longer shown

@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Jest Tests #13 / CustomFieldsForm renders text as default custom field type

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
securitySolution 6625 6628 +3

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 21.4MB 21.4MB +5.1KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
securitySolution 88.3KB 87.9KB -371.0B
securitySolutionEss 11.8KB 12.1KB +296.0B
securitySolutionServerless 26.5KB 26.9KB +453.0B
total +378.0B

History

  • 💔 Build #271177 failed cd361f38585234002557f7f128053e9e41a93138
  • 💔 Build #271099 failed 125748470e07dfb1958a96b255a984d0474ebe3a
  • 💔 Build #271021 failed 2aa6debd7008daa6b41198003e1c54bd6caee78b
  • 💚 Build #267276 succeeded c39fd2831a492d4be270abf5500d9240bccc9fcb
  • 💔 Build #267083 failed b38dd38a04b951266773575b68e4adbacb092493

cc @xcrzx

Copy link
Copy Markdown
Contributor

@nikitaindik nikitaindik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @xcrzx! I have re-tested a few scenarios on ECH and Serverless and can confirm that the bug with is_customized I noticed earlier is fixed.

I have reviewed the code. Thanks for explaining me the bits I didn't fully understand.

I think this PR is good to go! 🎉

@xcrzx xcrzx merged commit 199378c into elastic:main Jan 29, 2025
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/13036820821

@kibanamachine
Copy link
Copy Markdown
Contributor

💔 All backports failed

Status Branch Result
8.x Backport failed because of merge conflicts

You might need to backport the following PRs to 8.x:
- Added Entity Store data view refresh task (#208543)

Manual backport

To create the backport manually run:

node scripts/backport --pr 206079

Questions ?

Please refer to the Backport tool documentation

@xcrzx
Copy link
Copy Markdown
Contributor Author

xcrzx commented Jan 30, 2025

💚 All backports created successfully

Status Branch Result
8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

xcrzx pushed a commit that referenced this pull request Jan 30, 2025
…#206079) (#208893)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution] Implement rule customization license checks
(#206079)](#206079)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Dmitrii
Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-01-29T17:20:47Z","message":"[Security
Solution] Implement rule customization license checks
(#206079)\n\n**Resolves:**
https://github.com/elastic/security-team/issues/10410\n\n##
Summary\n\nWe want to make Rule Customization available at higher
license tiers. \n\n### **Intended Workflows/UX** \n\n####
**Basic/Platinum/Security Essentials License Tiers** \n- **Editing
Prebuilt Rules:** \n- Allow the 8.16 behavior: only actions, exceptions,
snoozing, and\nenable/disable options can be modified.\n- On the rule
editing page, all tabs except *Actions* are disabled.\nDisabled tabs
will display a hover explanation:\n- \"Upgrade to Enterprise to enable
prebuilt rule customization\" for ECH.\n- \"Upgrade to Security Complete
to enable prebuilt rule customization\"\nfor Serverless.\n<img
width=\"356\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/72e60933-aaaf-45a0-9660-4cd066d3afec\"\n/>\n\n-
Rule editing via API is not restricted (tracked
separately:\nhttps://github.com/elastic/security-team/issues/11504.\n\n-
**Bulk Actions:** \n- Modifications to rule content via bulk actions are
not allowed.\nPrebuilt rules are excluded from bulk actions if the
license level is\ninsufficient. Users will see an explanation for the
exclusion.\n - Serverless\n<img width=\"737\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/99fef72f-dd38-4c73-a9e3-7b4c8018b4ed\"\n/>\n
- ECH\n\n- On the API level (`_bulk_action`), an error is returned if a
user\ntries to modify a prebuilt rule without the required license.
Response\nin this case looks like this:\n ```json\n {\n \"statusCode\":
500,\n \"error\": \"Internal Server Error\",\n \"message\": \"Bulk edit
failed\",\n \"attributes\": {\n \"errors\": [\n {\n \"message\":
\"Elastic rule can't be edited\",\n \"status_code\": 500,\n \"rules\":
[]\n }\n ]\n }\n }\n ```\n\n- **Rule Updates:** \n - Updates are
restricted to Elastic’s incoming updates only. \n - The rule upgrade
flyout is in read-only mode.\n<img width=\"949\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/16a56430-63e6-4096-8ffd-b97f828abdd4\"\n/>\n-
For previously customized rules where customization is now disabled\ndue
to insufficient licensing, a notification will appear on the
upgrade\nflyout, clarifying that only an upgrade to Elastic's version
is\navailable.\n\n![image](https://github.com/user-attachments/assets/34ef5168-4fe3-42d0-9444-14180ed86500)\n-
On the API level (`_perform`), only requests with `pick_version
=\ntarget` are permitted. Requests with `rule.fields` values are
not\nallowed.\n API response when `pick_version` is not `target`:\n
```json\n {\n\"message\": \"Only the 'TARGET' version can be selected
for a rule update;\nreceived: 'CURRENT'\",\n \"status_code\": 400\n }\n
```\n API response when the `fields` value is provided:\n ```json\n
{\n\"message\": \"Rule field customization is not allowed. Received
fields:\nname, description\",\n \"status_code\": 400\n }\n ```\n\n-
**Customized Rules:** \n- Existing customizations remain intact, and the
“Modified” badge is\nretained\n - On the rule management, monitoring,
and update
tables:\n\n![image](https://github.com/user-attachments/assets/c7990c8f-5ed3-40ab-b0c6-ddc329e69b09)\n
- On the rule update
flyout:\n\n![image](https://github.com/user-attachments/assets/f74cb0bc-e7e5-49d5-8fec-b447517b5b52)\n
- On the rule details
page:\n\n![image](https://github.com/user-attachments/assets/b28990f1-9e84-481e-b966-0232495f4882)\n\n-
When we edit a rule with customizations (e.g., change rule's
actions),\nthe rule should stay marked as customized\n\n\n-
**Import/Export Scenarios:** \n- These are handled
separately\n(https://github.com/elastic/security-team/issues/11502)\n\n####
**Enterprise/Security Complete License Tiers** \n- All rules can be
fully edited\n- Upgraded prebuilt or customized rules will have an
editable view,\nenabling full
customization","sha":"199378c60c5364a796f99d944989032d5f38bf6e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","ui-copy","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0"],"title":"[Security Solution]
Implement rule customization license
checks","number":206079,"url":"https://github.com/elastic/kibana/pull/206079","mergeCommit":{"message":"[Security
Solution] Implement rule customization license checks
(#206079)\n\n**Resolves:**
https://github.com/elastic/security-team/issues/10410\n\n##
Summary\n\nWe want to make Rule Customization available at higher
license tiers. \n\n### **Intended Workflows/UX** \n\n####
**Basic/Platinum/Security Essentials License Tiers** \n- **Editing
Prebuilt Rules:** \n- Allow the 8.16 behavior: only actions, exceptions,
snoozing, and\nenable/disable options can be modified.\n- On the rule
editing page, all tabs except *Actions* are disabled.\nDisabled tabs
will display a hover explanation:\n- \"Upgrade to Enterprise to enable
prebuilt rule customization\" for ECH.\n- \"Upgrade to Security Complete
to enable prebuilt rule customization\"\nfor Serverless.\n<img
width=\"356\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/72e60933-aaaf-45a0-9660-4cd066d3afec\"\n/>\n\n-
Rule editing via API is not restricted (tracked
separately:\nhttps://github.com/elastic/security-team/issues/11504.\n\n-
**Bulk Actions:** \n- Modifications to rule content via bulk actions are
not allowed.\nPrebuilt rules are excluded from bulk actions if the
license level is\ninsufficient. Users will see an explanation for the
exclusion.\n - Serverless\n<img width=\"737\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/99fef72f-dd38-4c73-a9e3-7b4c8018b4ed\"\n/>\n
- ECH\n\n- On the API level (`_bulk_action`), an error is returned if a
user\ntries to modify a prebuilt rule without the required license.
Response\nin this case looks like this:\n ```json\n {\n \"statusCode\":
500,\n \"error\": \"Internal Server Error\",\n \"message\": \"Bulk edit
failed\",\n \"attributes\": {\n \"errors\": [\n {\n \"message\":
\"Elastic rule can't be edited\",\n \"status_code\": 500,\n \"rules\":
[]\n }\n ]\n }\n }\n ```\n\n- **Rule Updates:** \n - Updates are
restricted to Elastic’s incoming updates only. \n - The rule upgrade
flyout is in read-only mode.\n<img width=\"949\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/16a56430-63e6-4096-8ffd-b97f828abdd4\"\n/>\n-
For previously customized rules where customization is now disabled\ndue
to insufficient licensing, a notification will appear on the
upgrade\nflyout, clarifying that only an upgrade to Elastic's version
is\navailable.\n\n![image](https://github.com/user-attachments/assets/34ef5168-4fe3-42d0-9444-14180ed86500)\n-
On the API level (`_perform`), only requests with `pick_version
=\ntarget` are permitted. Requests with `rule.fields` values are
not\nallowed.\n API response when `pick_version` is not `target`:\n
```json\n {\n\"message\": \"Only the 'TARGET' version can be selected
for a rule update;\nreceived: 'CURRENT'\",\n \"status_code\": 400\n }\n
```\n API response when the `fields` value is provided:\n ```json\n
{\n\"message\": \"Rule field customization is not allowed. Received
fields:\nname, description\",\n \"status_code\": 400\n }\n ```\n\n-
**Customized Rules:** \n- Existing customizations remain intact, and the
“Modified” badge is\nretained\n - On the rule management, monitoring,
and update
tables:\n\n![image](https://github.com/user-attachments/assets/c7990c8f-5ed3-40ab-b0c6-ddc329e69b09)\n
- On the rule update
flyout:\n\n![image](https://github.com/user-attachments/assets/f74cb0bc-e7e5-49d5-8fec-b447517b5b52)\n
- On the rule details
page:\n\n![image](https://github.com/user-attachments/assets/b28990f1-9e84-481e-b966-0232495f4882)\n\n-
When we edit a rule with customizations (e.g., change rule's
actions),\nthe rule should stay marked as customized\n\n\n-
**Import/Export Scenarios:** \n- These are handled
separately\n(https://github.com/elastic/security-team/issues/11502)\n\n####
**Enterprise/Security Complete License Tiers** \n- All rules can be
fully edited\n- Upgraded prebuilt or customized rules will have an
editable view,\nenabling full
customization","sha":"199378c60c5364a796f99d944989032d5f38bf6e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206079","number":206079,"mergeCommit":{"message":"[Security
Solution] Implement rule customization license checks
(#206079)\n\n**Resolves:**
https://github.com/elastic/security-team/issues/10410\n\n##
Summary\n\nWe want to make Rule Customization available at higher
license tiers. \n\n### **Intended Workflows/UX** \n\n####
**Basic/Platinum/Security Essentials License Tiers** \n- **Editing
Prebuilt Rules:** \n- Allow the 8.16 behavior: only actions, exceptions,
snoozing, and\nenable/disable options can be modified.\n- On the rule
editing page, all tabs except *Actions* are disabled.\nDisabled tabs
will display a hover explanation:\n- \"Upgrade to Enterprise to enable
prebuilt rule customization\" for ECH.\n- \"Upgrade to Security Complete
to enable prebuilt rule customization\"\nfor Serverless.\n<img
width=\"356\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/72e60933-aaaf-45a0-9660-4cd066d3afec\"\n/>\n\n-
Rule editing via API is not restricted (tracked
separately:\nhttps://github.com/elastic/security-team/issues/11504.\n\n-
**Bulk Actions:** \n- Modifications to rule content via bulk actions are
not allowed.\nPrebuilt rules are excluded from bulk actions if the
license level is\ninsufficient. Users will see an explanation for the
exclusion.\n - Serverless\n<img width=\"737\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/99fef72f-dd38-4c73-a9e3-7b4c8018b4ed\"\n/>\n
- ECH\n\n- On the API level (`_bulk_action`), an error is returned if a
user\ntries to modify a prebuilt rule without the required license.
Response\nin this case looks like this:\n ```json\n {\n \"statusCode\":
500,\n \"error\": \"Internal Server Error\",\n \"message\": \"Bulk edit
failed\",\n \"attributes\": {\n \"errors\": [\n {\n \"message\":
\"Elastic rule can't be edited\",\n \"status_code\": 500,\n \"rules\":
[]\n }\n ]\n }\n }\n ```\n\n- **Rule Updates:** \n - Updates are
restricted to Elastic’s incoming updates only. \n - The rule upgrade
flyout is in read-only mode.\n<img width=\"949\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/16a56430-63e6-4096-8ffd-b97f828abdd4\"\n/>\n-
For previously customized rules where customization is now disabled\ndue
to insufficient licensing, a notification will appear on the
upgrade\nflyout, clarifying that only an upgrade to Elastic's version
is\navailable.\n\n![image](https://github.com/user-attachments/assets/34ef5168-4fe3-42d0-9444-14180ed86500)\n-
On the API level (`_perform`), only requests with `pick_version
=\ntarget` are permitted. Requests with `rule.fields` values are
not\nallowed.\n API response when `pick_version` is not `target`:\n
```json\n {\n\"message\": \"Only the 'TARGET' version can be selected
for a rule update;\nreceived: 'CURRENT'\",\n \"status_code\": 400\n }\n
```\n API response when the `fields` value is provided:\n ```json\n
{\n\"message\": \"Rule field customization is not allowed. Received
fields:\nname, description\",\n \"status_code\": 400\n }\n ```\n\n-
**Customized Rules:** \n- Existing customizations remain intact, and the
“Modified” badge is\nretained\n - On the rule management, monitoring,
and update
tables:\n\n![image](https://github.com/user-attachments/assets/c7990c8f-5ed3-40ab-b0c6-ddc329e69b09)\n
- On the rule update
flyout:\n\n![image](https://github.com/user-attachments/assets/f74cb0bc-e7e5-49d5-8fec-b447517b5b52)\n
- On the rule details
page:\n\n![image](https://github.com/user-attachments/assets/b28990f1-9e84-481e-b966-0232495f4882)\n\n-
When we edit a rule with customizations (e.g., change rule's
actions),\nthe rule should stay marked as customized\n\n\n-
**Import/Export Scenarios:** \n- These are handled
separately\n(https://github.com/elastic/security-team/issues/11502)\n\n####
**Enterprise/Security Complete License Tiers** \n- All rules can be
fully edited\n- Upgraded prebuilt or customized rules will have an
editable view,\nenabling full
customization","sha":"199378c60c5364a796f99d944989032d5f38bf6e"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
nikitaindik added a commit that referenced this pull request Mar 24, 2025
…reflect licensing changes (#215008)

**Partially addresses: #202068
**Related PR with licensing checks implementation:
#206079

## Summary
This PR updates the Prebuilt Rule Customization test plan to reflect
[recent changes](#206079) related
to licensing.

Changes to rule upgrade scenarios will be handled in a separate PR.
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Mar 24, 2025
…reflect licensing changes (elastic#215008)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Customization test plan to reflect
[recent changes](elastic#206079) related
to licensing.

Changes to rule upgrade scenarios will be handled in a separate PR.

(cherry picked from commit 2929f28)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Mar 24, 2025
…reflect licensing changes (elastic#215008)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Customization test plan to reflect
[recent changes](elastic#206079) related
to licensing.

Changes to rule upgrade scenarios will be handled in a separate PR.

(cherry picked from commit 2929f28)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Mar 24, 2025
…reflect licensing changes (elastic#215008)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Customization test plan to reflect
[recent changes](elastic#206079) related
to licensing.

Changes to rule upgrade scenarios will be handled in a separate PR.

(cherry picked from commit 2929f28)
kibanamachine added a commit that referenced this pull request Mar 24, 2025
…ns to reflect licensing changes (#215008) (#215730)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution] Update prebuilt rule customization test plans to
reflect licensing changes
(#215008)](#215008)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T14:50:34Z","message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing
changes","number":215008,"url":"https://github.com/elastic/kibana/pull/215008","mergeCommit":{"message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215008","number":215008,"mergeCommit":{"message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
kibanamachine added a commit that referenced this pull request Mar 24, 2025
…ans to reflect licensing changes (#215008) (#215727)

# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] Update prebuilt rule customization test plans to
reflect licensing changes
(#215008)](#215008)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T14:50:34Z","message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing
changes","number":215008,"url":"https://github.com/elastic/kibana/pull/215008","mergeCommit":{"message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215008","number":215008,"mergeCommit":{"message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
kibanamachine added a commit that referenced this pull request Mar 24, 2025
…ns to reflect licensing changes (#215008) (#215731)

# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Update prebuilt rule customization test plans to
reflect licensing changes
(#215008)](#215008)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T14:50:34Z","message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing
changes","number":215008,"url":"https://github.com/elastic/kibana/pull/215008","mergeCommit":{"message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215008","number":215008,"mergeCommit":{"message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](#206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
JoseLuisGJ pushed a commit to JoseLuisGJ/kibana that referenced this pull request Mar 24, 2025
…reflect licensing changes (elastic#215008)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Customization test plan to reflect
[recent changes](elastic#206079) related
to licensing.

Changes to rule upgrade scenarios will be handled in a separate PR.
cqliu1 pushed a commit to cqliu1/kibana that referenced this pull request Mar 31, 2025
…reflect licensing changes (elastic#215008)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Customization test plan to reflect
[recent changes](elastic#206079) related
to licensing.

Changes to rule upgrade scenarios will be handled in a separate PR.
nikitaindik added a commit that referenced this pull request May 30, 2025
…s to reflect licensing changes (#216003)

**Partially addresses: #202068
**Related PR with licensing checks implementation:
#206079

## Summary
This PR updates the Prebuilt Rule Upgrade and import/export test plans
to reflect [recent
changes](#206079) related to
licensing.

---------

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request May 30, 2025
…s to reflect licensing changes (elastic#216003)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Upgrade and import/export test plans
to reflect [recent
changes](elastic#206079) related to
licensing.

---------

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
(cherry picked from commit 8f89803)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request May 30, 2025
…s to reflect licensing changes (elastic#216003)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Upgrade and import/export test plans
to reflect [recent
changes](elastic#206079) related to
licensing.

---------

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
(cherry picked from commit 8f89803)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request May 30, 2025
…s to reflect licensing changes (elastic#216003)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Upgrade and import/export test plans
to reflect [recent
changes](elastic#206079) related to
licensing.

---------

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
(cherry picked from commit 8f89803)
kibanamachine added a commit that referenced this pull request May 30, 2025
…t plans to reflect licensing changes (#216003) (#222055)

# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Update prebuilt rule upgrade and import test
plans to reflect licensing changes
(#216003)](#216003)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-05-30T13:21:57Z","message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing
changes","number":216003,"url":"https://github.com/elastic/kibana/pull/216003","mergeCommit":{"message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216003","number":216003,"mergeCommit":{"message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
kibanamachine added a commit that referenced this pull request May 30, 2025
…st plans to reflect licensing changes (#216003) (#222053)

# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] Update prebuilt rule upgrade and import test
plans to reflect licensing changes
(#216003)](#216003)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-05-30T13:21:57Z","message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing
changes","number":216003,"url":"https://github.com/elastic/kibana/pull/216003","mergeCommit":{"message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216003","number":216003,"mergeCommit":{"message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
kibanamachine added a commit that referenced this pull request May 30, 2025
…st plans to reflect licensing changes (#216003) (#222054)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[Security Solution] Update prebuilt rule upgrade and import test
plans to reflect licensing changes
(#216003)](#216003)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-05-30T13:21:57Z","message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing
changes","number":216003,"url":"https://github.com/elastic/kibana/pull/216003","mergeCommit":{"message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216003","number":216003,"mergeCommit":{"message":"[Security
Solution] Update prebuilt rule upgrade and import test plans to reflect
licensing changes (#216003)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com//pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Upgrade and import/export
test plans\nto reflect
[recent\nchanges](#206079) related
to\nlicensing.\n\n---------\n\nCo-authored-by: Maxim Palenov
<maxim.palenov@elastic.co>","sha":"8f898034f9225adf26e0a33ece24bb9c2b3c8199"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
zacharyparikh pushed a commit to zacharyparikh/kibana that referenced this pull request Jun 4, 2025
…s to reflect licensing changes (elastic#216003)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Upgrade and import/export test plans
to reflect [recent
changes](elastic#206079) related to
licensing.

---------

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
nickpeihl pushed a commit to nickpeihl/kibana that referenced this pull request Jun 12, 2025
…s to reflect licensing changes (elastic#216003)

**Partially addresses: elastic#202068
**Related PR with licensing checks implementation:
elastic#206079

## Summary
This PR updates the Prebuilt Rule Upgrade and import/export test plans
to reflect [recent
changes](elastic#206079) related to
licensing.

---------

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area release_note:skip Skip the PR/issue when compiling release notes Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. ui-copy Review of UI copy with docs team is recommended v8.18.0 v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants