-
Notifications
You must be signed in to change notification settings - Fork 799
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
Add organizations restrictions on top of markings to increase data segregation possibilities #2188
Comments
…ase data segregation possibilities (#2188) - Report and intrusion-set
…ase data segregation possibilities (#2188) - Report and intrusion-set
To clarify a bit, its ongoing work, so need to re-define a bit the semantic :) Group = a set of marking. User can be assigned to multiple groups and so get a combination of granted markings The big difference between groups and organizations is that group/markings are exclusive and organizations are inclusive USER01 is part of GROUP_GREEN (TLP:GREEN) - inside organizations COMPANY01 IP adress 8.8.8.8 created with TLP:GREEN Hope this help to understand our vision on this subject. :) |
…data without organization restriction (#2188)
…ase data segregation possibilities (#2188) - Report and intrusion-set
…data without organization restriction (#2188)
- Add filtering implementation in stream
Co-authored-by: Samuel Hassine <samuel.hassine@filigran.io>
Use case
Today, when an entity has marking X:A and marking Y:N, it will be only available to the group that has both marking.
Use case: be able to share an entity with 2 different customers/teams that have X:A on one side and Y:N on the other side.
Current Workaround
Add groups/markings representing all possible permutations.
Proposed Solution
Implement the ability to associated elements to specific organizations that will be only accessible for users that are part of these organizations
The text was updated successfully, but these errors were encountered: