Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Changes related to the Rubrik Polaris release 1.3.0 #32859

Merged
merged 4 commits into from Feb 12, 2024
Merged

Changes related to the Rubrik Polaris release 1.3.0 #32859

merged 4 commits into from Feb 12, 2024

Conversation

content-bot
Copy link
Collaborator

Original External PR

external pull request

Contributor

@crestdatasystems

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

fixes: link to the issue

Description

  • Added 3 commands:

    • rubrik-sonar-user-access-list
    • rubrik-sonar-user-access-get
    • rubrik-sonar-file-context-list

  • Added 2 new playbooks:

    • Rubrik File Context Analysis - Rubrik Polaris
      • This playbook fetches file context information for the provided file/folder/fileshare name and the object ID to get the policy hits. (Available from Cortex XSOAR 6.5.0).
    • Rubrik User Access Analysis - Rubrik Polaris
      • This playbook fetches user access information for the provided username or email to increase the incident severity if the fetched user has a high risk. (Available from Cortex XSOAR 6.5.0).

Must have

  • Tests
  • Documentation

@crestdatasystems
Changes related to the Rubrik Polaris release 1.3.0 (#32242)
f7f3547 
* Changes related to the Rubrik release 1.3.0

* Updated Docker images tag

* Updated code as per the PR comments

* Fixing autopep8 errors

* Updated the test cases to not use the if conditions

* Changes in playbooks as per the comments to not delete the important data from the context

---------

Co-authored-by: crestdatasystems <crestdatasystems@users.noreply.github.com>
@content-bot content-bot added Contribution Thank you! Contributions are always welcome! docs-approved Partner ready-for-instance-test In contribution PRs, this label will cause a trigger of a build with a modified pack from the PR. pending-demo Demo pending Contribution Form Filled Whether contribution form filled or not. pending-contributor The PR is pending the response of its creator Partner Support Level Indicates that the contribution is for Partner supported pack Internal PR Security Review Partner-Approved labels Feb 12, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 12, 2024 •
edited

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/RubrikPolaris/Integrations/RubrikPolaris
   RubrikPolaris.py13688194%548–549, 551, 645–646, 833, 848–851, 853–854, 906, 1073, 1444, 1470–1474, 1527, 1530, 1532, 1536, 1576, 1578, 1580, 1985, 1990, 2170, 2355, 2361, 2371, 2388, 2589, 2605, 2791, 2796, 2928–2931, 2982, 2986, 2991, 3013, 3053, 3071, 3107, 3111, 3173, 3229, 3233, 3367, 3398, 3400, 3640, 3736–3738, 3740, 3765–3766, 3771–3772, 3799–3800, 3807, 3809–3815, 3817, 3856–3858, 3860, 3862
Packs/RubrikPolaris/Scripts/RubrikSonarSetIncidentSeverityUsingUserRiskLevel
   RubrikSonarSetIncidentSeverityUsingUserRiskLevel.py29389%65–67
TOTAL13978493% 

Tests Skipped Failures Errors Time
8 0 💤 0 ❌ 0 🔥 1.985s ⏱️

@YuvHayun YuvHayun merged commit cc4524d into master Feb 12, 2024
16 checks passed
@YuvHayun YuvHayun deleted the contrib/crestdatasystems_Rubrik-Release-130 branch February 12, 2024 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@YuvHayun YuvHayun YuvHayun approved these changes

Assignees

@melamedbn melamedbn

@YuvHayun YuvHayun

@edik24 edik24

Labels
Contribution Form Filled Whether contribution form filled or not. Contribution Thank you! Contributions are always welcome! docs-approved Internal PR Partner Support Level Indicates that the contribution is for Partner supported pack Partner Partner-Approved pending-contributor The PR is pending the response of its creator pending-demo Demo pending ready-for-instance-test In contribution PRs, this label will cause a trigger of a build with a modified pack from the PR. Security Review
Projects
None yet
Milestone
No milestone
5 participants
@content-bot @YuvHayun @melamedbn @edik24 @crestdatasystems