-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security Solution]Container workload protection showing with None Access to Security Sub Features #163562
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
@amolnater-qasource please review and assign |
Reviewed and assigned to @MadameSheema |
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Not sure about that, I think Rules functionality is available as long as the main Security feature is enabled, it does not have any sub-feature associated. |
@karanbirsingh-qasource The bug talks about |
yes @maxcold you are right, the bug is for Container workload protection not cloud posture benchmark. we have updated the bug |
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
@karanbirsingh-qasource could you check if it was fixed by #163102? |
@karanbirsingh-qasource @sukhwindersingh-qasource can you please validate the fix on latest BC? Thanks! |
We have validated this issue on Kibana/Elasticsearch Stack version
Screen-Cast: Get.started.-.Kibana.Mozilla.Firefox.Private.Browsing.2023-08-25.09-48-05.mp4 |
@machadoum can you please take a look at the above? Thanks! |
Hey! I investigated the issue and discovered that it isn't new. I was able to reproduce it on 8.9 It happens because the menu item is guarded by the general security show capability: But when the page renders it has extra license checks here. So, it isn't related to the menu changes introduced by Sergi. One possible solution is to declare the license type to the link configuration:
But that can be better accessed by the security-defend-workflows team which owns the feature. |
Pinging @elastic/security-defend-workflows (Team:Defend Workflows) |
Maybe I pinged the wrong team. It seems it was introduced here by cloud-native-integrations. |
Thanks for the ping @machadoum! Kibana work that was owned by @elastic/sec-cloudnative-integrations now should go to @elastic/cloud-security @kfirpeled is this on your radar? |
PR is up, needs an approval from security-threat-hunting-explore team. cc @machadoum |
…to csp), also add… (elastic#165376) …ed d4c manage policies link to the list of excluded links when user does not have permission to read policies in security solution ## Summary Fixes: elastic#163562 (cherry picked from commit 7e82607) # Conflicts: # x-pack/packages/security-solution/features/src/constants.ts # x-pack/packages/security-solution/features/src/security/kibana_features.ts
…to csp), also add… (elastic#165376) …ed d4c manage policies link to the list of excluded links when user does not have permission to read policies in security solution ## Summary Fixes: elastic#163562 (cherry picked from commit 7e82607) # Conflicts: # x-pack/packages/security-solution/features/src/constants.ts # x-pack/packages/security-solution/features/src/security/kibana_features.ts
…imilar to csp), also add… (#165376) (#165717) # Backport This will backport the following commits from `main` to `8.10`: - [[Cloud Security] added missing bits for backend route check (similar to csp), also add… (#165376)](#165376) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Karl Godard","email":"karl.godard@elastic.co"},"sourceCommit":{"committedDate":"2023-09-05T14:44:54Z","message":"[Cloud Security] added missing bits for backend route check (similar to csp), also add… (#165376)\n\n…ed d4c manage policies link to the list of excluded links when user\r\ndoes not have permission to read policies in security solution\r\n\r\n## Summary\r\n\r\nFixes: #163562 Security","backport:prev-minor","v8.10.0","v8.11.0"],"number":165376,"url":"#165376 Security] added missing bits for backend route check (similar to csp), also add… (#165376)\n\n…ed d4c manage policies link to the list of excluded links when user\r\ndoes not have permission to read policies in security solution\r\n\r\n## Summary\r\n\r\nFixes: #163562 Security] added missing bits for backend route check (similar to csp), also add… (#165376)\n\n…ed d4c manage policies link to the list of excluded links when user\r\ndoes not have permission to read policies in security solution\r\n\r\n## Summary\r\n\r\nFixes: #163562"}}]}] BACKPORT-->
fix and backport merged to 8.10 so will be ready for QA in the next BC |
…to csp), also add… (elastic#165376) …ed d4c manage policies link to the list of excluded links when user does not have permission to read policies in security solution ## Summary Fixes: elastic#163562
Describe the bug:
Container workload protection showing with None Access to Security Sub Features
Kibana/Elasticsearch Stack version
Version: 8.10.0 SNAPSHOT
Commit: 4637b74
Build: 65796
Browser and Browser OS Version:
Firefox for windows OS
Version: 116.0.2 (64-bit)
Elastic Endpoint Version:
v8.10.0-dev.0
Original install method:
Build summary: https://artifacts-api.elastic.co/v1/search/8.10.0-SNAPSHOT
Functional Area:
Security App side Navigation
Initial Setup:
Steps to reproduce
Additional Observation
Current behavior
Expected behavior:
Screen-shots:
Settings.-.Kibana.Mozilla.Firefox.Private.Browsing.2023-08-10.13-35-28.mp4
Errors in browser console:
Console Logs
Content-Security-Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). manage:286:177238 XHRGET https://973747bc0ef84b97832d269c9bbdcd2d.us-central1.gcp.qa.cld.elstc.co:9243/internal/cloud_defend/status [HTTP/1.1 403 Forbidden 317ms]
XHRGET
https://973747bc0ef84b97832d269c9bbdcd2d.us-central1.gcp.qa.cld.elstc.co:9243/internal/cloud_defend/policies?policy_name=&per_page=10&page=1&sort_field=package_policy.name&sort_order=asc
[HTTP/1.1 403 Forbidden 327ms]
XHRGET
https://973747bc0ef84b97832d269c9bbdcd2d.us-central1.gcp.qa.cld.elstc.co:9243/internal/cloud_defend/status
[HTTP/1.1 403 Forbidden 344ms]
Any additional context (logs, chat logs, magical formulas, etc.):
Cloud_Posture_Benchmark_HAR.zip
The text was updated successfully, but these errors were encountered: