Custom properties and observable types #11
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…constants and custom properties used internally be OpenCTI
Member
SamuelHassine
left a comment
SamuelHassine
left a comment
There was a problem hiding this comment.
Thanks a lot for this very good PR. Useful and understandable for all future developers!
Member
|
@jekyc: could you please solve all conflicts in your PR? We will merge it in the next release. |
…constants and custom properties used internally be OpenCTI
…ub.com/jekyc/client-python into custom_properties_and_observable_types
Contributor
Author
|
Thanks for the pull. The conflicts should be resolved now. |
aHenryJard
pushed a commit
to OpenCTI-Platform/opencti
that referenced
this pull request
Nov 12, 2025
…m_properties_and_observable_types Custom properties and observable types (original commit: OpenCTI-Platform/client-python@16b28fc)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This moves the STIX "Custom Properties" (x_opencti_*) and internal "Observable Types" used by OpenCTI to a separate file so it is easier to identify the values used.
These classes can then be used by the connectors to ensure that the proper values are used.
The properties have been attempted commented/documented, but it would be nice with a better explanation of their uses and impact on OpenCTI (and also if they are required - such as x_opencti_observable_type and x_opencti_observable_value).