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.

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

Max shareable marking definitions in groups (for export and public dashboard) #7006

Closed
Jipegien opened this issue May 17, 2024 · 0 comments · Fixed by #7107
Closed

Max shareable marking definitions in groups (for export and public dashboard) #7006

Jipegien opened this issue May 17, 2024 · 0 comments · Fixed by #7107
Assignees
Labels
feature use for describing a new feature to develop marking Linked to data segregation via marking definition solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Jipegien
Copy link
Member

Use case

Current situation:

  1. We have the ability to define a max marking definition when exporting an entity or a list (one shot)
  2. We have the ability to restrict marking definition at the platform level for public dashboards (settings)

What we need:

  1. We need to add a settings in the group named "Max shareable marking".
  2. We need to remove the marking definition restriction at the platform level

=> Use the new Max shareable in marking in for public dashboards and also to restrict the list of available max marking when exporting.

By default, when the max shareable marking is not set, the default behavior applies, which means all group markings are available for export and public dashboard.

Some screens

In the parameters of a group:

image

=> Add a new parameter here, "Max shareable marking"

In export:

image

=> This list should be restricted until the max shareable marking

In public dashboards:

image

=> This list should be restricted until the max shareable marking

In Security Policies:

image

=> This settings should be completely removed and not used anymore.

@Jipegien Jipegien added the feature use for describing a new feature to develop label May 17, 2024
@Jipegien Jipegien added this to the Release 6.2.0 milestone May 17, 2024
@Archidoit Archidoit self-assigned this May 17, 2024
Archidoit added a commit that referenced this issue Jun 10, 2024
Archidoit added a commit that referenced this issue Jun 10, 2024
Archidoit added a commit that referenced this issue Jun 10, 2024
Archidoit added a commit that referenced this issue Jun 10, 2024
Archidoit added a commit that referenced this issue Jun 10, 2024
Archidoit added a commit that referenced this issue Jun 10, 2024
Archidoit added a commit that referenced this issue Jun 10, 2024
Archidoit added a commit that referenced this issue Jun 10, 2024
@Archidoit Archidoit added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jun 10, 2024
aHenryJard pushed a commit that referenced this issue Jun 12, 2024
daimyo007 pushed a commit to fbicyber/opencti__opencti that referenced this issue Jun 24, 2024
Goumies pushed a commit that referenced this issue Jun 25, 2024
@Jipegien Jipegien added the marking Linked to data segregation via marking definition label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop marking Linked to data segregation via marking definition solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
3 participants