-
Notifications
You must be signed in to change notification settings - Fork 971
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
Marking values order: change TLP:AMBER+STRICT to be hierarchically greater than TLP:AMBER #9450
Labels
bug
use for describing something not working as expected
Comments
romain-filigran
added
bug
use for describing something not working as expected
needs triage
use to identify issue needing triage from Filigran Product team
labels
Dec 23, 2024
nino-filigran
removed
the
needs triage
use to identify issue needing triage from Filigran Product team
label
Jan 2, 2025
you means on first platform start ? Like this => Because after that users can change the marking order in security > Marking definition |
implementation note: initialization of marking is here opencti/opencti-platform/opencti-graphql/src/database/data-initialization.js Lines 137 to 195 in 8a66e8b
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
It seems more logic to differentiate the order between TLP:AMBER and TLP:AMBER+STRICT has the scope is more restricted in TLP:AMBER+STRICT definition.
TLP:AMBER+STRICT should be hierarchically superior to TLP:AMBER
Environment
The text was updated successfully, but these errors were encountered: