diff --git a/6.2.18/404.html b/6.2.18/404.html deleted file mode 100755 index 354a6b7d..00000000 --- a/6.2.18/404.html +++ /dev/null @@ -1,3826 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- -

404 - Not found

- -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/assets/attribution_propagation.png b/6.2.18/administration/assets/attribution_propagation.png deleted file mode 100755 index f4492112..00000000 Binary files a/6.2.18/administration/assets/attribution_propagation.png and /dev/null differ diff --git a/6.2.18/administration/assets/audit.png b/6.2.18/administration/assets/audit.png deleted file mode 100755 index 58ac12c2..00000000 Binary files a/6.2.18/administration/assets/audit.png and /dev/null differ diff --git a/6.2.18/administration/assets/audit_configuration.png b/6.2.18/administration/assets/audit_configuration.png deleted file mode 100755 index 3314da03..00000000 Binary files a/6.2.18/administration/assets/audit_configuration.png and /dev/null differ diff --git a/6.2.18/administration/assets/authentication-strategies.png b/6.2.18/administration/assets/authentication-strategies.png deleted file mode 100755 index 9cf0f75d..00000000 Binary files a/6.2.18/administration/assets/authentication-strategies.png and /dev/null differ diff --git a/6.2.18/administration/assets/authorize-access.gif b/6.2.18/administration/assets/authorize-access.gif deleted file mode 100755 index 952155c1..00000000 Binary files a/6.2.18/administration/assets/authorize-access.gif and /dev/null differ diff --git a/6.2.18/administration/assets/belonging_propagation.png b/6.2.18/administration/assets/belonging_propagation.png deleted file mode 100755 index 41d1da76..00000000 Binary files a/6.2.18/administration/assets/belonging_propagation.png and /dev/null differ diff --git a/6.2.18/administration/assets/broadcast_message_configuration.png b/6.2.18/administration/assets/broadcast_message_configuration.png deleted file mode 100755 index a399e2f5..00000000 Binary files a/6.2.18/administration/assets/broadcast_message_configuration.png and /dev/null differ diff --git a/6.2.18/administration/assets/broadcast_message_display_dismissible.png b/6.2.18/administration/assets/broadcast_message_display_dismissible.png deleted file mode 100755 index d32572e4..00000000 Binary files a/6.2.18/administration/assets/broadcast_message_display_dismissible.png and /dev/null differ diff --git a/6.2.18/administration/assets/broadcast_message_display_notdismissible.png b/6.2.18/administration/assets/broadcast_message_display_notdismissible.png deleted file mode 100755 index dcdfe558..00000000 Binary files a/6.2.18/administration/assets/broadcast_message_display_notdismissible.png and /dev/null differ diff --git a/6.2.18/administration/assets/case_templates.png b/6.2.18/administration/assets/case_templates.png deleted file mode 100755 index 5572f627..00000000 Binary files a/6.2.18/administration/assets/case_templates.png and /dev/null differ diff --git a/6.2.18/administration/assets/confidence_scale_configuration.png b/6.2.18/administration/assets/confidence_scale_configuration.png deleted file mode 100755 index 2d9bf274..00000000 Binary files a/6.2.18/administration/assets/confidence_scale_configuration.png and /dev/null differ diff --git a/6.2.18/administration/assets/create-entity-marking-filter.png b/6.2.18/administration/assets/create-entity-marking-filter.png deleted file mode 100755 index b13902dc..00000000 Binary files a/6.2.18/administration/assets/create-entity-marking-filter.png and /dev/null differ diff --git a/6.2.18/administration/assets/create-entity-markings.png b/6.2.18/administration/assets/create-entity-markings.png deleted file mode 100755 index d222c0b7..00000000 Binary files a/6.2.18/administration/assets/create-entity-markings.png and /dev/null differ diff --git a/6.2.18/administration/assets/create-marking.gif b/6.2.18/administration/assets/create-marking.gif deleted file mode 100755 index e995d877..00000000 Binary files a/6.2.18/administration/assets/create-marking.gif and /dev/null differ diff --git a/6.2.18/administration/assets/create-role.png b/6.2.18/administration/assets/create-role.png deleted file mode 100755 index 62cc069e..00000000 Binary files a/6.2.18/administration/assets/create-role.png and /dev/null differ diff --git a/6.2.18/administration/assets/create-user-new.png b/6.2.18/administration/assets/create-user-new.png deleted file mode 100755 index a44d574d..00000000 Binary files a/6.2.18/administration/assets/create-user-new.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mapper-attribute.png b/6.2.18/administration/assets/csv-mapper-attribute.png deleted file mode 100755 index 3e9ca584..00000000 Binary files a/6.2.18/administration/assets/csv-mapper-attribute.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mapper-default.png b/6.2.18/administration/assets/csv-mapper-default.png deleted file mode 100755 index 45067a80..00000000 Binary files a/6.2.18/administration/assets/csv-mapper-default.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mapper-settings.png b/6.2.18/administration/assets/csv-mapper-settings.png deleted file mode 100755 index 19d4749f..00000000 Binary files a/6.2.18/administration/assets/csv-mapper-settings.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mappers-create.png b/6.2.18/administration/assets/csv-mappers-create.png deleted file mode 100755 index d33a0b98..00000000 Binary files a/6.2.18/administration/assets/csv-mappers-create.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mappers-default-markings.png b/6.2.18/administration/assets/csv-mappers-default-markings.png deleted file mode 100755 index 0f342135..00000000 Binary files a/6.2.18/administration/assets/csv-mappers-default-markings.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mappers-default-values.png b/6.2.18/administration/assets/csv-mappers-default-values.png deleted file mode 100755 index f0aaf458..00000000 Binary files a/6.2.18/administration/assets/csv-mappers-default-values.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mappers-field-options-1.png b/6.2.18/administration/assets/csv-mappers-field-options-1.png deleted file mode 100755 index 4d55afb1..00000000 Binary files a/6.2.18/administration/assets/csv-mappers-field-options-1.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mappers-invalid.png b/6.2.18/administration/assets/csv-mappers-invalid.png deleted file mode 100755 index 660a5af6..00000000 Binary files a/6.2.18/administration/assets/csv-mappers-invalid.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mappers-rep-1.png b/6.2.18/administration/assets/csv-mappers-rep-1.png deleted file mode 100755 index dcc4765b..00000000 Binary files a/6.2.18/administration/assets/csv-mappers-rep-1.png and /dev/null differ diff --git a/6.2.18/administration/assets/csv-mappers-test.png b/6.2.18/administration/assets/csv-mappers-test.png deleted file mode 100755 index 942798c9..00000000 Binary files a/6.2.18/administration/assets/csv-mappers-test.png and /dev/null differ diff --git a/6.2.18/administration/assets/custom-email-notifier.png b/6.2.18/administration/assets/custom-email-notifier.png deleted file mode 100755 index 9ef061c0..00000000 Binary files a/6.2.18/administration/assets/custom-email-notifier.png and /dev/null differ diff --git a/6.2.18/administration/assets/customization-window.png b/6.2.18/administration/assets/customization-window.png deleted file mode 100755 index 8f21a640..00000000 Binary files a/6.2.18/administration/assets/customization-window.png and /dev/null differ diff --git a/6.2.18/administration/assets/data-access-diagram.png b/6.2.18/administration/assets/data-access-diagram.png deleted file mode 100755 index 629af7c4..00000000 Binary files a/6.2.18/administration/assets/data-access-diagram.png and /dev/null differ diff --git a/6.2.18/administration/assets/decay-rule-created.png b/6.2.18/administration/assets/decay-rule-created.png deleted file mode 100755 index 5ccdbb27..00000000 Binary files a/6.2.18/administration/assets/decay-rule-created.png and /dev/null differ diff --git a/6.2.18/administration/assets/decay-rule-creation-filled.png b/6.2.18/administration/assets/decay-rule-creation-filled.png deleted file mode 100755 index e92010bc..00000000 Binary files a/6.2.18/administration/assets/decay-rule-creation-filled.png and /dev/null differ diff --git a/6.2.18/administration/assets/decay-rule-creation.png b/6.2.18/administration/assets/decay-rule-creation.png deleted file mode 100755 index a7eda456..00000000 Binary files a/6.2.18/administration/assets/decay-rule-creation.png and /dev/null differ diff --git a/6.2.18/administration/assets/decay-rules.png b/6.2.18/administration/assets/decay-rules.png deleted file mode 100755 index 5d9edf58..00000000 Binary files a/6.2.18/administration/assets/decay-rules.png and /dev/null differ diff --git a/6.2.18/administration/assets/default-marking.gif b/6.2.18/administration/assets/default-marking.gif deleted file mode 100755 index 59c8aeeb..00000000 Binary files a/6.2.18/administration/assets/default-marking.gif and /dev/null differ diff --git a/6.2.18/administration/assets/define_organization_admin.png b/6.2.18/administration/assets/define_organization_admin.png deleted file mode 100755 index e9644386..00000000 Binary files a/6.2.18/administration/assets/define_organization_admin.png and /dev/null differ diff --git a/6.2.18/administration/assets/enterprise-activate.png b/6.2.18/administration/assets/enterprise-activate.png deleted file mode 100755 index 3c827cac..00000000 Binary files a/6.2.18/administration/assets/enterprise-activate.png and /dev/null differ diff --git a/6.2.18/administration/assets/enterprise-eula.png b/6.2.18/administration/assets/enterprise-eula.png deleted file mode 100755 index 9b0c6ec4..00000000 Binary files a/6.2.18/administration/assets/enterprise-eula.png and /dev/null differ diff --git a/6.2.18/administration/assets/entity-configuration.png b/6.2.18/administration/assets/entity-configuration.png deleted file mode 100755 index 225007ca..00000000 Binary files a/6.2.18/administration/assets/entity-configuration.png and /dev/null differ diff --git a/6.2.18/administration/assets/file-indexing-monitoring.png b/6.2.18/administration/assets/file-indexing-monitoring.png deleted file mode 100755 index 77d1358f..00000000 Binary files a/6.2.18/administration/assets/file-indexing-monitoring.png and /dev/null differ diff --git a/6.2.18/administration/assets/file-indexing-settings.png b/6.2.18/administration/assets/file-indexing-settings.png deleted file mode 100755 index a9e3a47e..00000000 Binary files a/6.2.18/administration/assets/file-indexing-settings.png and /dev/null differ diff --git a/6.2.18/administration/assets/group-overview-new.png b/6.2.18/administration/assets/group-overview-new.png deleted file mode 100755 index 17592c21..00000000 Binary files a/6.2.18/administration/assets/group-overview-new.png and /dev/null differ diff --git a/6.2.18/administration/assets/hidden_entities_platform.png b/6.2.18/administration/assets/hidden_entities_platform.png deleted file mode 100755 index b26510be..00000000 Binary files a/6.2.18/administration/assets/hidden_entities_platform.png and /dev/null differ diff --git a/6.2.18/administration/assets/hidden_entities_role.png b/6.2.18/administration/assets/hidden_entities_role.png deleted file mode 100755 index dbf308a4..00000000 Binary files a/6.2.18/administration/assets/hidden_entities_role.png and /dev/null differ diff --git a/6.2.18/administration/assets/identities_propagation.png b/6.2.18/administration/assets/identities_propagation.png deleted file mode 100755 index 0c677823..00000000 Binary files a/6.2.18/administration/assets/identities_propagation.png and /dev/null differ diff --git a/6.2.18/administration/assets/incident_on_sighting.png b/6.2.18/administration/assets/incident_on_sighting.png deleted file mode 100755 index 9811dbb9..00000000 Binary files a/6.2.18/administration/assets/incident_on_sighting.png and /dev/null differ diff --git a/6.2.18/administration/assets/items-to-be-deleted.png b/6.2.18/administration/assets/items-to-be-deleted.png deleted file mode 100755 index 4b32901b..00000000 Binary files a/6.2.18/administration/assets/items-to-be-deleted.png and /dev/null differ diff --git a/6.2.18/administration/assets/local-password-policies.png b/6.2.18/administration/assets/local-password-policies.png deleted file mode 100755 index 96171f93..00000000 Binary files a/6.2.18/administration/assets/local-password-policies.png and /dev/null differ diff --git a/6.2.18/administration/assets/location_propagation.png b/6.2.18/administration/assets/location_propagation.png deleted file mode 100755 index 89b7b34f..00000000 Binary files a/6.2.18/administration/assets/location_propagation.png and /dev/null differ diff --git a/6.2.18/administration/assets/locations_propagation_report.png b/6.2.18/administration/assets/locations_propagation_report.png deleted file mode 100755 index 72e61062..00000000 Binary files a/6.2.18/administration/assets/locations_propagation_report.png and /dev/null differ diff --git a/6.2.18/administration/assets/login-message-configuration.png b/6.2.18/administration/assets/login-message-configuration.png deleted file mode 100755 index b3887f60..00000000 Binary files a/6.2.18/administration/assets/login-message-configuration.png and /dev/null differ diff --git a/6.2.18/administration/assets/login-message-illustration.png b/6.2.18/administration/assets/login-message-illustration.png deleted file mode 100755 index 05f16fee..00000000 Binary files a/6.2.18/administration/assets/login-message-illustration.png and /dev/null differ diff --git a/6.2.18/administration/assets/main_entity_selection.png b/6.2.18/administration/assets/main_entity_selection.png deleted file mode 100755 index 75d78723..00000000 Binary files a/6.2.18/administration/assets/main_entity_selection.png and /dev/null differ diff --git a/6.2.18/administration/assets/mandatory_and_default_attributes.png b/6.2.18/administration/assets/mandatory_and_default_attributes.png deleted file mode 100755 index 89a2f9ea..00000000 Binary files a/6.2.18/administration/assets/mandatory_and_default_attributes.png and /dev/null differ diff --git a/6.2.18/administration/assets/marking-pop.gif b/6.2.18/administration/assets/marking-pop.gif deleted file mode 100755 index 1972fff6..00000000 Binary files a/6.2.18/administration/assets/marking-pop.gif and /dev/null differ diff --git a/6.2.18/administration/assets/max-marking-shareable.png b/6.2.18/administration/assets/max-marking-shareable.png deleted file mode 100755 index fa932358..00000000 Binary files a/6.2.18/administration/assets/max-marking-shareable.png and /dev/null differ diff --git a/6.2.18/administration/assets/merge_panel.png b/6.2.18/administration/assets/merge_panel.png deleted file mode 100755 index be892537..00000000 Binary files a/6.2.18/administration/assets/merge_panel.png and /dev/null differ diff --git a/6.2.18/administration/assets/mitre_attack_matrix.png b/6.2.18/administration/assets/mitre_attack_matrix.png deleted file mode 100755 index a10cf7a7..00000000 Binary files a/6.2.18/administration/assets/mitre_attack_matrix.png and /dev/null differ diff --git a/6.2.18/administration/assets/notifier-connectors.png b/6.2.18/administration/assets/notifier-connectors.png deleted file mode 100755 index e8814520..00000000 Binary files a/6.2.18/administration/assets/notifier-connectors.png and /dev/null differ diff --git a/6.2.18/administration/assets/observable_related_to_entities.png b/6.2.18/administration/assets/observable_related_to_entities.png deleted file mode 100755 index f88e47c8..00000000 Binary files a/6.2.18/administration/assets/observable_related_to_entities.png and /dev/null differ diff --git a/6.2.18/administration/assets/observables_propagation.png b/6.2.18/administration/assets/observables_propagation.png deleted file mode 100755 index 30a4c8e0..00000000 Binary files a/6.2.18/administration/assets/observables_propagation.png and /dev/null differ diff --git a/6.2.18/administration/assets/organisation_via_participation.png b/6.2.18/administration/assets/organisation_via_participation.png deleted file mode 100755 index a552df34..00000000 Binary files a/6.2.18/administration/assets/organisation_via_participation.png and /dev/null differ diff --git a/6.2.18/administration/assets/organization_admin_view.png b/6.2.18/administration/assets/organization_admin_view.png deleted file mode 100755 index 3d4f72c2..00000000 Binary files a/6.2.18/administration/assets/organization_admin_view.png and /dev/null differ diff --git a/6.2.18/administration/assets/overview-layout-customization.png b/6.2.18/administration/assets/overview-layout-customization.png deleted file mode 100755 index 81ce233a..00000000 Binary files a/6.2.18/administration/assets/overview-layout-customization.png and /dev/null differ diff --git a/6.2.18/administration/assets/parameters_broadcast_message_dismissible.png b/6.2.18/administration/assets/parameters_broadcast_message_dismissible.png deleted file mode 100755 index ee46654c..00000000 Binary files a/6.2.18/administration/assets/parameters_broadcast_message_dismissible.png and /dev/null differ diff --git a/6.2.18/administration/assets/parameters_broadcast_message_non-dismissible.png b/6.2.18/administration/assets/parameters_broadcast_message_non-dismissible.png deleted file mode 100755 index 52313bff..00000000 Binary files a/6.2.18/administration/assets/parameters_broadcast_message_non-dismissible.png and /dev/null differ diff --git a/6.2.18/administration/assets/parameters_configuration.png b/6.2.18/administration/assets/parameters_configuration.png deleted file mode 100755 index 9ec9cde6..00000000 Binary files a/6.2.18/administration/assets/parameters_configuration.png and /dev/null differ diff --git a/6.2.18/administration/assets/parameters_platform.png b/6.2.18/administration/assets/parameters_platform.png deleted file mode 100755 index 3cdb3f85..00000000 Binary files a/6.2.18/administration/assets/parameters_platform.png and /dev/null differ diff --git a/6.2.18/administration/assets/parameters_theme_customization.png b/6.2.18/administration/assets/parameters_theme_customization.png deleted file mode 100755 index 56413408..00000000 Binary files a/6.2.18/administration/assets/parameters_theme_customization.png and /dev/null differ diff --git a/6.2.18/administration/assets/parameters_tools.png b/6.2.18/administration/assets/parameters_tools.png deleted file mode 100755 index 4336ecb8..00000000 Binary files a/6.2.18/administration/assets/parameters_tools.png and /dev/null differ diff --git a/6.2.18/administration/assets/platform-main-organization.png b/6.2.18/administration/assets/platform-main-organization.png deleted file mode 100755 index bfe05c12..00000000 Binary files a/6.2.18/administration/assets/platform-main-organization.png and /dev/null differ diff --git a/6.2.18/administration/assets/platform_banner.png b/6.2.18/administration/assets/platform_banner.png deleted file mode 100755 index e7bb739a..00000000 Binary files a/6.2.18/administration/assets/platform_banner.png and /dev/null differ diff --git a/6.2.18/administration/assets/platform_message_examples.png b/6.2.18/administration/assets/platform_message_examples.png deleted file mode 100755 index 2711f7a5..00000000 Binary files a/6.2.18/administration/assets/platform_message_examples.png and /dev/null differ diff --git a/6.2.18/administration/assets/rbac.png b/6.2.18/administration/assets/rbac.png deleted file mode 100755 index 1f87e6db..00000000 Binary files a/6.2.18/administration/assets/rbac.png and /dev/null differ diff --git a/6.2.18/administration/assets/retention-policy-parameters.png b/6.2.18/administration/assets/retention-policy-parameters.png deleted file mode 100755 index 131c8d48..00000000 Binary files a/6.2.18/administration/assets/retention-policy-parameters.png and /dev/null differ diff --git a/6.2.18/administration/assets/sighting_from_indicator.png b/6.2.18/administration/assets/sighting_from_indicator.png deleted file mode 100755 index 73a07dd5..00000000 Binary files a/6.2.18/administration/assets/sighting_from_indicator.png and /dev/null differ diff --git a/6.2.18/administration/assets/sighting_from_observable.png b/6.2.18/administration/assets/sighting_from_observable.png deleted file mode 100755 index 94c8849b..00000000 Binary files a/6.2.18/administration/assets/sighting_from_observable.png and /dev/null differ diff --git a/6.2.18/administration/assets/sighting_via_obs_data.png b/6.2.18/administration/assets/sighting_via_obs_data.png deleted file mode 100755 index 42d680b7..00000000 Binary files a/6.2.18/administration/assets/sighting_via_obs_data.png and /dev/null differ diff --git a/6.2.18/administration/assets/status_templates.png b/6.2.18/administration/assets/status_templates.png deleted file mode 100755 index a6589ff5..00000000 Binary files a/6.2.18/administration/assets/status_templates.png and /dev/null differ diff --git a/6.2.18/administration/assets/support-package-overview.png b/6.2.18/administration/assets/support-package-overview.png deleted file mode 100755 index baab6cd2..00000000 Binary files a/6.2.18/administration/assets/support-package-overview.png and /dev/null differ diff --git a/6.2.18/administration/assets/system_settings.png b/6.2.18/administration/assets/system_settings.png deleted file mode 100755 index 448e25c2..00000000 Binary files a/6.2.18/administration/assets/system_settings.png and /dev/null differ diff --git a/6.2.18/administration/assets/targeting_via_attribution.png b/6.2.18/administration/assets/targeting_via_attribution.png deleted file mode 100755 index 247eeee7..00000000 Binary files a/6.2.18/administration/assets/targeting_via_attribution.png and /dev/null differ diff --git a/6.2.18/administration/assets/targeting_via_belonging.png b/6.2.18/administration/assets/targeting_via_belonging.png deleted file mode 100755 index bbb51d38..00000000 Binary files a/6.2.18/administration/assets/targeting_via_belonging.png and /dev/null differ diff --git a/6.2.18/administration/assets/targeting_via_location.png b/6.2.18/administration/assets/targeting_via_location.png deleted file mode 100755 index 6565f8da..00000000 Binary files a/6.2.18/administration/assets/targeting_via_location.png and /dev/null differ diff --git a/6.2.18/administration/assets/targeting_via_sighting.png b/6.2.18/administration/assets/targeting_via_sighting.png deleted file mode 100755 index 76ffff36..00000000 Binary files a/6.2.18/administration/assets/targeting_via_sighting.png and /dev/null differ diff --git a/6.2.18/administration/assets/targeting_when_located.png b/6.2.18/administration/assets/targeting_when_located.png deleted file mode 100755 index 89a0bee4..00000000 Binary files a/6.2.18/administration/assets/targeting_when_located.png and /dev/null differ diff --git a/6.2.18/administration/assets/teams-notifier-sample.png b/6.2.18/administration/assets/teams-notifier-sample.png deleted file mode 100755 index 211f8c28..00000000 Binary files a/6.2.18/administration/assets/teams-notifier-sample.png and /dev/null differ diff --git a/6.2.18/administration/assets/tlp-diagram.png b/6.2.18/administration/assets/tlp-diagram.png deleted file mode 100755 index f970b012..00000000 Binary files a/6.2.18/administration/assets/tlp-diagram.png and /dev/null differ diff --git a/6.2.18/administration/assets/update-group-new.png b/6.2.18/administration/assets/update-group-new.png deleted file mode 100755 index 6f59ee81..00000000 Binary files a/6.2.18/administration/assets/update-group-new.png and /dev/null differ diff --git a/6.2.18/administration/assets/update-role.png b/6.2.18/administration/assets/update-role.png deleted file mode 100755 index 39e353be..00000000 Binary files a/6.2.18/administration/assets/update-role.png and /dev/null differ diff --git a/6.2.18/administration/assets/usage_propagation.png b/6.2.18/administration/assets/usage_propagation.png deleted file mode 100755 index a7c7ee34..00000000 Binary files a/6.2.18/administration/assets/usage_propagation.png and /dev/null differ diff --git a/6.2.18/administration/assets/user-manage.png b/6.2.18/administration/assets/user-manage.png deleted file mode 100755 index 13a79158..00000000 Binary files a/6.2.18/administration/assets/user-manage.png and /dev/null differ diff --git a/6.2.18/administration/assets/user-overveiw-new.png b/6.2.18/administration/assets/user-overveiw-new.png deleted file mode 100755 index 86e64bb7..00000000 Binary files a/6.2.18/administration/assets/user-overveiw-new.png and /dev/null differ diff --git a/6.2.18/administration/assets/vocabularies.png b/6.2.18/administration/assets/vocabularies.png deleted file mode 100755 index f1f45642..00000000 Binary files a/6.2.18/administration/assets/vocabularies.png and /dev/null differ diff --git a/6.2.18/administration/assets/workflow-configuration.png b/6.2.18/administration/assets/workflow-configuration.png deleted file mode 100755 index c16f5238..00000000 Binary files a/6.2.18/administration/assets/workflow-configuration.png and /dev/null differ diff --git a/6.2.18/administration/audit/configuration/index.html b/6.2.18/administration/audit/configuration/index.html deleted file mode 100755 index d6b35760..00000000 --- a/6.2.18/administration/audit/configuration/index.html +++ /dev/null @@ -1,4011 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Configuration - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Configuration

-
-

Enterprise edition

-

Activity unified interface and logging are available under the "OpenCTI Enterprise Edition" license.

-

Please read the dedicated page to have all information

-
-

As explained in the overview page, all administration actions are listened by default. -However, all knowledge are not listened by default due to performance impact on the platform.

-

For this reason you need to explicitly activate extended listening on user / group or organization.

-

Audit interface

-

Listening will start just after the configuration. Every past events will not be taken into account.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/audit/events/index.html b/6.2.18/administration/audit/events/index.html deleted file mode 100755 index c2212934..00000000 --- a/6.2.18/administration/audit/events/index.html +++ /dev/null @@ -1,4083 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Events - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Events

-
-

Enterprise edition

-

Activity unified interface and logging are available under the "OpenCTI Enterprise Edition" license.

-

Please read the dedicated page to have all information

-
-

Description

-

OpenCTI activity capability is the way to unified whats really happen in the platform. -In events section you will have access to the UI that will answer to "who did what, where, and when?" within your data with the maximum level of transparency.

-

Audit interface

-

Include knowledge

-

By default, the events screen only show you the administration actions done by the users.

-

If you want to see also the information about the knowledge, you can simply activate the filter in the bar to get the complete overview of all user actions.

-

Don't hesitate to read again the overview page to have a better understanding of the difference between Audit, Basic/Extended knowledge.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/audit/overview/index.html b/6.2.18/administration/audit/overview/index.html deleted file mode 100755 index 9eebf672..00000000 --- a/6.2.18/administration/audit/overview/index.html +++ /dev/null @@ -1,4794 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Overview - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Overview

- -

Overview

-
-

Enterprise edition

-

Activity unified interface and logging are available under the "OpenCTI Enterprise Edition" license.

-

Please read the dedicated page to have all the information

-
-

OpenCTI activity capability is the way to unify what's really happening in the platform. -With this feature you will be able to answer "who did what, where, and when?" within your data with the maximum level of transparency.

-

Enabling activity helps your security, auditing, and compliance entities monitor platform for possible vulnerabilities or external data misuse.

-

Categories

-

The activity groups 3 different concepts that need to be explained.

-

Basic knowledge

-

The basic knowledge refers to all STIX data knowledge inside OpenCTI. Every create/update/delete action on that knowledge is accessible through the history. That basic activity is handled by the history manager and can also be found directly on each entity.

-

Extended knowledge

-

The extended knowledge refers to extra information data to track specific user activity. As this kind of tracking is expensive, the tracking will only be done for specific users/groups/organizations explicitly configured in the configuration window.

-

Audit knowledge

-

Audit is focusing on user administration or security actions. -Audit will produce console/logs files along with user interface elements.

-
{
-  "auth": "<User information>",
-  "category": "AUDIT",
-  "level": "<info | error>",
-  "message": "<human readable explanation>",
-  "resource": {
-    "type": "<authentication | mutation>",
-    "event_scope": "<depends on type>",
-    "event_access": "<administration>",
-    "data": "<contextual data linked to the event type>",
-    "version": "<version of audit log format>"
-  },
-  "timestamp": "<event date>",
-  "version": "<platform version>"
-}
-
-

Architecture

-

OpenCTI uses different mechanisms to be able to publish actions (audit) or data modification (history)

- - -

Audit knowledge

-
-

Administration or security actions

-

With Enterprise edition activated, Administration and security actions are always written; you can't configure, exclude, or disable them

-

✅ Supported

-

❌ Not supported for now

-

🚫 Not applicable

-
-

Ingestion

- - - - - - - - - - - - - - - - - -
CreateDeleteEdit
Remote OCTI Streams✅✅✅
-

Data sharing

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CreateDeleteEdit
CSV Feeds✅✅✅
TAXII Feeds✅✅✅
Stream Feeds✅✅✅
-

Connectors

- - - - - - - - - - - - - - - - - - - - - - - -
CreateDeleteEdit
Connectors✅✅✅ State reset
Works🚫✅🚫
-

Parameters

- - - - - - - - - - - - - - - - - -
CreateDeleteEdit
Platform parameters🚫🚫✅
-

Security

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CreateDeleteEdit
Roles✅✅✅
Groups✅✅✅
Users✅✅✅
Sessions🚫✅🚫
Policies🚫🚫✅
-

Customization

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CreateDeleteEdit
Entity types🚫🚫✅
Rules engine🚫🚫✅
Retention policies✅✅✅
-

Taxonomies

- - - - - - - - - - - - - - - - - - - - - - - -
CreateDeleteEdit
Status templates✅✅✅
Case templates + tasks✅✅✅
-

Accesses

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Listen
Login (success or fail)✅
Logout✅
Unauthorized access✅
-

Extended knowledge

-
-

Extended knowledge

-

Extented knowledge activity are written only if you activate the feature for a subset of users / groups or organizations

-
-

Data management

-

Some history actions are already included in the "basic knowledge". (basic marker)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ReadCreateDeleteEdit
Platform knowledge✅basicbasicbasic
Background tasks knowledge🚫✅✅🚫
Knowledge files✅basicbasic🚫
Global data import files✅✅✅🚫
Analyst workbenches files🚫✅✅🚫
Triggers🚫✅✅❌
Workspaces✅✅✅❌
Investigations✅✅✅❌
User profile🚫🚫🚫✅
-

User actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Supported
Ask for file import✅
Ask for data enrichment✅
Ask for export generation✅
Execute global search✅
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/audit/triggers/index.html b/6.2.18/administration/audit/triggers/index.html deleted file mode 100755 index d16e5b5e..00000000 --- a/6.2.18/administration/audit/triggers/index.html +++ /dev/null @@ -1,4142 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Activity triggers - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Activity triggers

-
-

Enterprise edition

-

Activity unified interface and logging are available under the "OpenCTI Enterprise Edition" license.

-

Please read the dedicated page to have all information

-
-

Description

-

Having all the history in the user interface (events) is sometimes not enough to have a proactive monitoring. For this reason, you can configure some specific triggers to receive notifications on audit events. -You can configure like personal triggers, lives one that will be sent directly or digest depending on your needs.

-

Configuration

-

In this type of trigger, you will need to configure various options:

-
    -
  • Notification target: user interface or email,
    • -
  • Recipients: the recipient of the notification,
    • -
  • Filters: a set of filters to get only events that really interest you.
    • -
-

Event structure

-

In order to correctly configure the filters, here's a definition of the event structure

-
    -
  • -

    Event type: authentication

    -
      -
    • Event scopes: login and logout
      • -
    -
    • -
  • -

    Event type: read

    -
      -
    • Event scopes: read and unauthorized
      • -
    -
    • -
  • -

    Event type: file

    -
      -
    • Event scopes: read, create and delete
      • -
    -
    • -
  • -

    Event type: mutation

    -
      -
    • Event scopes: unauthorized, update, create and delete
      • -
    -
    • -
  • -

    Event type: command

    -
      -
    • Event scopes: search, enrich, import and export
      • -
    -
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/csv-mappers/index.html b/6.2.18/administration/csv-mappers/index.html deleted file mode 100755 index 71dd869a..00000000 --- a/6.2.18/administration/csv-mappers/index.html +++ /dev/null @@ -1,4340 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - CSV Mappers - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

CSV Mappers

-

In OpenCTI, CSV Mappers allow to parse CSV files in a STIX 2.1 Object. The mappers are created and configured by users with the Manage CSV mapper capability. Then, they are available to users who import CSV files, for instance inside a report or in the global import view.

-

Principles

-

The mapper contains representations of STIX 2.1 entities and relationships, in order for the parser to properly extract them. One mapper is dedicated to parsing a specific CSV file structure, and thus dedicated mappers should be created for every specific CSV structure you might need to ingest in the platform.

-

Create a new CSV Mapper

-

In menu Data, select the submenu Processing, and on the right menu select CSV Mappers. You are presented with a list of all the mappers set in the platform. Note that you can delete or update any mapper from the context menu via the burger button beside each mapper.

-

Click on the button + in the bottom-right corner to add a new Mapper.

-

Enter a name for your mapper and some basic information about your CSV files:

-
    -
  • The line separator used (defaults to the standard comma character)
    • -
  • The presence of a header on the first line
    • -
-
-

Header management

-

The parser will not extract any information from the CSV header if any, it will just skip the first line during parsing.

-
-

Creating a new CSV Mapper

-

Then, you need to create every representation, one per entity and relationship type represented in the CSV file. -Click on the + button to add an empty representation in the list, and click on the chevron to expand the section and configure the representation.

-

Depending on the entity type, the form contains the fields that are either required (input outlined in red) or optional. -For each field, set the corresponding columns mapping (the letter-based index of the column in the CSV table, as presented in common spreadsheet tools).

-

References to other entities should be picked from the list of all the other representations already defined earlier in the mapper.

-

You can do the same for all the relationships between entities that might be defined in this particular CSV file structure.

-

New representation

-

Fields might have options besides the mandatory column index, to help extract relevant data:

-
    -
  • Date values are expected in ISO 8601 format, but you can set your own format to the time parser
    • -
  • Multiple values can be extracted by specifying the separator used inside the cell (e.g. + or |)
    • -
-

Or to set default values in case some data is missing in the imported file.

-

Field options

-

CSV Mapper validity

-

The only parameter required to save a CSV Mapper is a name. The creation and refinement of its representations can be done iteratively.

-

Nonetheless, all CSV Mappers go through a quick validation that checks if all the representations have all their mandatory fields set. -Only valid mappers can be run by the users on their CSV files.

-

Mapper validity is visible in the list of CSV Mappers as shown below.

-

An invalid CSV Mapper

-

Test your CSV mapper

-

In the creation or edition form, hit the button Test to open a dialog. Select a sample CSV file and hit the Test button.

-

The code block contains the raw result of the parsing attempt, in the form of a STIX 2.1 bundle in JSON format.

-

You can then check if the extracted values match the expected entities and relationships.

-

Test a CSV Mapper

-
-

Partial test

-

The test conducted in this window relies only on the translation of CSV data according to the chosen representation in the mapper. It does not take into account checks for accurate entity formatting (e.g. IPv4) or specific entity configurations (e.g. mandatory "description" field on reports). Consequently, the entities visible in the test window may not be created during the actual import process.

-
-
-

Test with a small file

-

We strongly recommend limiting test files to 100 lines and 1MB. Otherwise, the browser may crash.

-
-

Use a mapper for importing a CSV file

-

You can change the default configuration of the import csv connector in your configuration file.

-
"import_csv_built_in_connector": {
-  "enabled": true, 
-  "interval": 10000, 
-  "validate_before_import": false
-},
-
-

In Data import section, or Data tab of an entity, when you upload a CSV, you can select a mapper to apply to the file. -The file will then be parsed following the representation rules set in the mapper.

-

By default, the imported elements will be added in a new Analyst Workbench where you will be able to check the result of the import.

-

Default values for attributes

-

In the case of the CSV file misses some data, you can complete it with default values. To achieve this, you have two possibilities:

-
    -
  • Set default values in the settings of the entities,
    • -
  • Set default values directly in the CSV mapper.
    • -
-

Set default values in the settings of the entities

-
-

Default value mechanisms

-

Note that adding default values in settings have an impact at entity creation globally on the platform, not only on CSV mappers. If you want to apply those default values only at CSV mapper level, please use the second option.

-
-

In settings > Customization, you can select an entity type and then set default values for its attributes.

-

mapper-settings

-

In the configuration of the entity, you have access to the entity's attributes that can be managed.

-

Click on the attribute to add a default value information.

-

mapper-custom

-

Enter the default value in the input and save the update.

-

mapper-attribute

-

The value filled will be used in the case where the CSV file lacks data for this attribute.

-

Set specific default values directly in the CSV mapper

-
-

Information retained in case of default value

-

If you fill a default value in entity settings and the CSV mapper, the one from CSV mapper will be used.

-
-

In the mapper form, you will see next to the column index input a gear icon to add extra information for the attribute. If the attribute can have a customizable default value, then you will be able to set one here.

-

mapper-attribute

-

The example above shows the case of the attribute architecture implementation of a malware. You have some information here. First, it seems we have a default value already set in entity settings for this attribute with the value [powerpc, x86]. However, we want to override this value with another one for our case: [alpha].

-

Specific case of marking definitions

-

For marking definitions, setting a default value is different from other attributes. We are not choosing a particular marking definition to use if none is specified in the CSV file. Instead, we will choose a default policy. Two option are available:

-
    -
  • Use the default marking definitions of the user. In this case the default marking definitions of the connected user importing the CSV file will be used,
    • -
  • Let the user choose marking definitions. Here the user importing the CSV file will choose marking definitions (among the ones they can see) when selecting the CSV mapper.
    • -
-

mapper-attribute

-

Additional resources

-
    -
  • Usefulness: To additional content on entity customization, refers to the Customize entities page in the Administration section of the documentation.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/decay-rules/index.html b/6.2.18/administration/decay-rules/index.html deleted file mode 100755 index cce80a1c..00000000 --- a/6.2.18/administration/decay-rules/index.html +++ /dev/null @@ -1,4087 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Decay rules - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Decay rules

-

Decay rules are used to update automatically indicators score in order to represent their lifecycle.

-

Configuration

-

Decay rules can be configured in the "Settings > Customization > Decay rule" menu.

-

Decay rules

-

There are built-in decay rules that can't be modified and are applied by default to indicators depending on their main observable type. -Decay rules are applied from highest to lowest order (the lowest being 0).

-

You can create new decay rules with higher order to apply them along with (or instead of) the built-in rules.

-

Decay rule creation

-

When you create a decay rule, you can specify on which indicators' main observable types it will apply. If you don't enter any, it will apply to all indicators.

-

You can also add reaction points which represent the scores at which indicators are updated. For example, if you add one reaction point at 60 and another one at 40, indicators that have an initial score of 80 will be updated with a score of 60, then 40, depending on the decay curve.

-

The decay curve is based on two parameters:

-
    -
  • the decay factor, which represents the speed at which the score falls, and
    • -
  • the lifetime, which represents the time (in days) during which the value will be lowered until it reaches 0.
    • -
-

Finally, the revoke score is the score at which the indicator can be revoked automatically.

-

Decay rule creation filled

-

Once you have created a new decay rule, you will be able to view its details, along with a life curve graph showing the score evolution over time.

-

You will also be able to edit your rule, change all its parameters and order, activate or deactivate it (only activated rules are applied), or delete it.

-

Decay rule created

-
-

Indicator decay manager

-

Decay rules are only applied, and indicators score updated, if indicator decay manager is enabled (enabled by default).

-

Please read the dedicated page to have all information

-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/enterprise/index.html b/6.2.18/administration/enterprise/index.html deleted file mode 100755 index 16476a22..00000000 --- a/6.2.18/administration/enterprise/index.html +++ /dev/null @@ -1,4233 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Enterprise edition - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Enterprise edition

- -
-

Filigran

-

Filigran is providing an Enterprise Edition of the platform, whether on-premise or in the SaaS.

-
-

What is OpenCTI EE?

-

OpenCTI Enterprise Edition is based on the open core concept. This means that the source code of OCTI EE remains open source and included in the main GitHub repository of the platform but is published under a specific license. As specified in the GitHub license file:

-
    -
  • The OpenCTI Community Edition is licensed under the Apache License, Version 2.0 (the “Apache License”).
    • -
  • The OpenCTI Enterprise Edition is licensed under the OpenCTI Enterprise Edition License (the “Enterprise Edition Licensee”).
    • -
-

The source files in this repository have a header indicating which license they are under. If no such header is provided, this means that the file belongs to the Community Edition under the Apache License, Version 2.0.

-

We wrote a complete article to explain the enterprise edition, feel free to read it to have more information

-

EE Activation

-

Enterprise edition is easy to activate. You need to go the platform settings and click on the Activate button.

-

OpenCTI activation

-

Then you will need to agree to the Filigran EULA.

-

OpenCTI EE EULA

-

As a reminder:

-
    -
  • OpenCTI EE is free-to-use for development, testing and research purposes as well as for non-profit organizations.
    • -
  • OpenCTI EE is included for all Filigran SaaS customers without additional fee.
    • -
  • For all other usages, OpenCTI EE is reserved to organizations that have signed a Filigran Enterprise agreement.
    • -
-

Available features

-

Activity monitoring

-

Audit logs help you answer "who did what, where, and when?" within your data with the maximum level of transparency. Please read Activity monitoring page to get all information.

-

Playbooks and automation

-

OpenCTI playbooks are flexible automation scenarios which can be fully customized and enabled by platform administrators to enrich, filter and modify the data created or updated in the platform. Please read Playbook automation page to get all information.

-

Organizations management and segregation

-

Organizations segregation is a way to segregate your data considering the organization associated to the users. Useful when your platform aims to share data to multiple organizations that have access to the same OpenCTI platform. Please read Organizations RBAC to get more information.

-

Full text indexing

-

Full text indexing grants improved searches across structured and unstructured data. OpenCTI classic searches are based on metadata fields (e.g. title, description, type) while advanced indexing capability enables searches to be extended to the document’s contents. Please read File indexing to get all information.

-

More to come

-

More features will be available in OpenCTI in the future. Features like:

-
    -
  • Generative AI for correlation and content generation.
    • -
  • Supervised machine learning for natural language processing.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/entities/index.html b/6.2.18/administration/entities/index.html deleted file mode 100755 index 7dea657c..00000000 --- a/6.2.18/administration/entities/index.html +++ /dev/null @@ -1,4251 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Entity types - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Customize entities

-

Introduction

-

A variety of entity customization options are available to optimize data representation, workflow management, and enhance overall user experience. Whether you're fine-tuning processing statuses, configuring entities' attributes, or hiding entities, OpenCTI's customization capabilities provide the flexibility you need to create a tailored environment for your threat intelligence and cybersecurity workflows.

-

The following chapter aims to provide readers with an understanding of the available customization options by entity type. Customize entities can be done in "Settings > Customization".

-

Customization menu

-

Hidden in interface

-

This configuration allows to hide a specific entity type throughout the entire platform. It provides a potent means to simplify the interface and tailor it to your domain expertise. For instance, if you have no interest in disinformation campaigns, you can conceal related entities such as Narratives and Channels from the menus.

-

You can specify which entities to hide on a platform-wide basis from "Settings > Customization" and from "Settings > Parameters", providing you with a list of hidden entities. Furthermore, you can designate hidden entities for specific Groups and Organizations from "Settings > Security > Groups/Organizations" by editing a Group/Organization.

-

An overview of hidden entity types is available in the "Hidden entity types" field in "Settings > Parameters."

-

Automatic references at file upload

-

This configuration enables an entity to automatically construct an external reference from the uploaded file.

-

Enforce references

-

This configuration enables the requirement of a reference message on an entity creation or modification. This option is helpful if you want to keep a strong consistency and traceability of your knowledge and is well suited for manual creation and update.

-

Entity configuration

-

-

Workflow

-

For now, OpenCTI has a simple workflow approach. They're represented by the "Processing status" field embedded in each object. By default, this field is disabled for most objects but can be activated through the platform settings:

-
    -
  1. Navigate to "Settings > Customization > Entity types > [Desired object type]."
    2. -
  2. Click on the small pink pen icon next to "Workflow" to access the object customization window.
    3. -
  3. Add and configure the desired statuses, defining their order within the workflow.
    4. -
-

Workflow status

-

In addition, the available statuses are defined by a collection of status templates visible in "Settings > Taxonomies > Status templates". This collection can be customized.

-

-

Attributes

-

Each attribute in an Entity offers several customization options:

-
    -
  • It can be set as mandatory if not already defined as such in the STIX standard.
    • -
  • A default value can be established to streamline entity creation through the creation forms.
    • -
  • Different thresholds and their corresponding labels for scalable attributes can be defined.
    • -
-

Mandatory attributes and default values

-

Confidence scale configuration

-

Confidence scale can be customized for each entity type by selecting another scale template or by editing directly the scale values. -Once you have customized your scale, click on "Update" to save your configuration.

-

Mandatory attributes and default values

-
-

Max confidence level

-

The above scale also needs to take into account the confidence level per user. To understand the concept, please navigate to this page

-
-

Overview layout customization

-

At the platform level, the Overview layout tab of the containers can be rearranged to fit the users needs. -The widgets can be reordered or extended to their full width.

-

Overview layout customization settings

-

To reset the layout to its default version, click the button next to the section title.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/file-indexing/index.html b/6.2.18/administration/file-indexing/index.html deleted file mode 100755 index e71c2121..00000000 --- a/6.2.18/administration/file-indexing/index.html +++ /dev/null @@ -1,4098 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - File indexing - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

File indexing

-
-

Enterprise edition

-

Platform segregation by organization is available under the "OpenCTI Enterprise Edition" license. Please read the dedicated page to have all the information.

-
-

Files search requirements

-

In order to search in files, we need to extract and index files text content, which requires to have one of these database configurations :

- -

File indexing configuration

-

File indexing can be configured via the File indexing tab in the Settings menu.

-

The configuration and impact panel shows all file types that can be indexed, as well as the volume of storage used.

-

It is also possible to include or exclude files uploaded from the global Data import panel and that are not associated with a specific entity in the platform.

-

Finally, it is possible to set a maximum file size for indexing (5 Mb by default).

-

Currently supported content types : application/pdf, text/plain, text/csv, text/html, application/vnd.ms-excel, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet (excel sheets).

-

file-indexing-settings.png

-

Once indexing has been launched by pressing the Start button, you can follow its progress.

-

You will also be able to Pause it and restart from the beginning by pressing Reset button which deletes all indexed files from the database.

-

If you change the configuration while file indexing is running, you might need to reset in order to include newly impacted files.

-

File indexing runs every 5 minutes to index last uploaded files.

-

file-indexing-monitoring.png

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/introduction/index.html b/6.2.18/administration/introduction/index.html deleted file mode 100755 index 16951c68..00000000 --- a/6.2.18/administration/introduction/index.html +++ /dev/null @@ -1,4032 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Introduction - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Introduction

-

This guide aims to give you a full overview of the OpenCTI features and workflows. The platform can be used in various contexts to handle threats management use cases from a technical to a more strategic level.

-

Administrative Settings

-

The OpenCTI Administrative settings console allows administrators to configure many options dynamically within the system. As an Administrator, you can access this settings console, by clicking the settings link. -Settings Link

-

The Settings Console allows for configuration of various aspects of the system.

-

General Configuration

-
    -
  • Platform Title (Default: OpenCTI - Cyber Threat Intelligence Platform)
    • -
  • Platform Favicon
    • -
  • Platform General Sender email (Default: admin@opencti.io)
    • -
  • Platform Default Theme (Default: Dark)
    • -
  • Language (Default: Automatic Detection)
    • -
  • Hidden Entity Types (Default: None)
    • -
-

Authentication Strategies Display

-
    -
  • This section will show configured and enabled/disabled strategies. The configuration is done in the config/default.json file or via ENV variables detected at launch.
    • -
-

Platform Messages

-
    -
  • Platform Login Message (optional) - if configured this will be displayed on the login page. This is usually used to have a welcome type message for users before login.
    • -
  • Platform Consent Message (optional) - if configured this will be displayed on the login page. This is usually used to display some type of consent message for users to agree to before login. If enabled, a user must check the checkbox displayed to allow login.
    • -
  • Platform Consent Confirm Text (optional) - This is displayed next to the platform consent checkbox, if Platform Consent Message is configured. Users must agree to the checkbox before the login prompt will be displayed. This message can be configured, but by default reads: I have read and comply with the above statement
    • -
-

Platform Messages

-

Dark Theme Color Scheme

-

Various aspects of the Dark Theme can be dynamically configured in this section.

-

Light Theme Color Scheme

-

Various aspects of the Light Theme can be dynamically configured in this section.

-

Tools Configuration Display

-

This section will give general status on the various tools and enabled components of the currently configured OpenCTI deployment.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/merging/index.html b/6.2.18/administration/merging/index.html deleted file mode 100755 index 41c01565..00000000 --- a/6.2.18/administration/merging/index.html +++ /dev/null @@ -1,4128 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Merging and de-duplication - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Merging

-

Data merging

-

Within the OpenCTI platform, the merge capability is present into the "Data > Entities" tab, and is fairly straightforward to use. To execute a merge, select the set of entities to be merged, then click on the Merge icon.

-
-

Merging limitation

-

It is not possible to merge entities of different types, nor is it possible to merge more than 4 entities at a time (it will have to be done in several stages).

-
-

Merge_panel

-

Central to the merging process is the selection of a main entity. This primary entity becomes the anchor, retaining crucial attributes such as name and description. Other entities, while losing specific fields like descriptions, are aliased under the primary entity. This strategic decision preserves vital data while eliminating redundancy.

-

Main_entity_selection

-

Once the choice has been made, simply validate to run the task in the background. Depending on the number of entity relationships, and the current workload on the platform, the merge may take more or less time. In the case of a healthy platform and around a hundred relationships per entity, merge is almost instantaneous.

-

Data preservation and relationship continuity

-

A common concern when merging entities lies in the potential loss of information. In the context of OpenCTI, this worry is alleviated. Even if the merged entities were initially created by distinct sources, the platform ensures that data is not lost. Upon merging, the platform automatically generates relationships directly on the merged entity. This strategic approach ensures that all connections, regardless of their origin, are anchored to the consolidated entity. Post-merge, OpenCTI treats these once-separate entities as a singular, unified entity. Subsequent information from varied sources is channeled directly into the entity resulting from the merger. This unified entity becomes the focal point for all future relationships, ensuring the continuity of data and relationships without any loss or fragmentation.

-

Important considerations

-
    -
  • Irreversible process: It's essential to know that a merge operation is irreversible. Once completed, the merged entities cannot be reverted to their original state. Consequently, careful consideration and validation are crucial before initiating the merge process.
    • -
  • Loss of fields in aliased entities: Fields, such as descriptions, in aliased entities - entities that have not been chosen as the main - will be lost during the merge. Ensuring that essential information is captured in the primary entity is crucial to prevent data loss.
    • -
-

Additional resources

-
    -
  • Usefulness: To understand the benefits of entity merger, refer to the Merge objects page in the User Guide section of the documentation.
    • -
  • Deduplication mechanism: the platform is equipped with deduplication processes that automatically merge data at creation (either manually or by importing data from different sources) if it meets certain conditions.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/notifier-samples/index.html b/6.2.18/administration/notifier-samples/index.html deleted file mode 100755 index 34d26cda..00000000 --- a/6.2.18/administration/notifier-samples/index.html +++ /dev/null @@ -1,4154 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Notifier samples - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Notifier samples

-

Configure Teams webhook

-

To configure a notifier for Teams, allowing to send notifications via Teams messages, we followed the guidelines outlined in the Microsoft documentation.

-

Teams notifier sample

-

Template message for live trigger

-

The Teams template message sent through webhook for a live notification is:

-
{
-        "type": "message",
-        "attachments": [
-            {
-                "contentType": "application/vnd.microsoft.card.thumbnail",
-                "content": {
-                    "subtitle": "Operation : <%=content[0].events[0].operation%>",
-                    "text": "<%=(new Date(notification.created)).toLocaleString()%>",
-                    "title": "<%=content[0].events[0].message%>",
-                    "buttons": [
-                        {
-                            "type": "openUrl",
-                            "title": "See in OpenCTI",
-                            "value": "https://YOUR_OPENCTI_URL/dashboard/id/<%=content[0].events[0].instance_id%>"
-                        }
-                    ]
-                }
-            }
-        ]
-    }
-
-

Template message for digest

-

The Teams template message sent through webhook for a digest notification is:

-
{
-    "type": "message",
-    "attachments": [
-        {
-            "contentType": "application/vnd.microsoft.card.adaptive",
-            "content": {
-                "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
-                "type": "AdaptiveCard",
-                "version": "1.0",
-                "body": [
-                    {
-                        "type": "Container",
-                        "items": [
-                            {
-                                "type": "TextBlock",
-                                "text": "<%=notification.name%>",
-                                "weight": "bolder",
-                                "size": "extraLarge"
-                            }, {
-                                "type": "TextBlock",
-                                "text": "<%=(new Date(notification.created)).toLocaleString()%>",
-                                "size": "medium"
-                            }
-                        ]
-                    },
-                    <% for(var i=0; i<content.length; i++) { %>
-                    {
-                        "type": "Container",
-                        "items": [<% for(var j=0; j<content[i].events.length; j++) { %>
-                            {
-                                "type" : "TextBlock",
-                                "text" : "[<%=content[i].events[j].message%>](https://YOUR_OPENCTI_URL/dashboard/id/<%=content[i].events[j].instance_id%>)"
-                            }<% if(j<(content[i].events.length - 1)) {%>,<% } %>
-                        <% } %>]
-           }<% if(i<(content.length - 1)) {%>,<% } %>
-                    <% } %>
-                ]
-            }
-        }
-    ],
-   "dataString": <%-JSON.stringify(notification)%>
-}
-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/notifiers/index.html b/6.2.18/administration/notifiers/index.html deleted file mode 100755 index 12048bed..00000000 --- a/6.2.18/administration/notifiers/index.html +++ /dev/null @@ -1,4162 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Custom notifiers - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Custom notifiers

-

Leveraging the platform's built-in connectors, users can create custom notifiers tailored to their unique needs. OpenCTI features three built-in connectors: a webhook connector, a simple mailer connector, and a platform mailer connector. These connectors operate based on registered schemas that describe their interaction methods.

-

Notifier connectors

-

Built-In notifier connectors

-

Platform mailer

-

This notifier connector enables customization of notifications raised within the platform. It's simple to configure, requiring only:

-
    -
  • Title: The title for the platform notification.
    • -
  • Template: Specifies the message template for the notification.
    • -
-

Simple mailer

-

This notifier connector offers a straightforward approach to email notifications with simplified configuration options. Users can set:

-
    -
  • Title: The title for the email notification.
    • -
  • Header: Additional content to include at the beginning of the email.
    • -
  • Footer: Additional content to include at the end of the email.
    • -
  • Logo: The option to add a logo to the email.
    • -
  • Background Color: Customize the background color of the email.
    • -
-

Custom email notifier

-

Webhook

-

This notifier connector enables users to send notifications to external applications or services through HTTP requests. Users can specify:

-
    -
  • Verb: Specifies the HTTP method (GET, POST, PUT, DELETE).
    • -
  • URL: Defines the destination URL for the webhook.
    • -
  • Template: Specifies the message template for the notification.
    • -
  • Parameters and Headers: Customizable parameters and headers sent through the webhook request.
    • -
-

OpenCTI provides two notifier samples by default, designed to communicate with Microsoft Teams through a webhook. A documentation page providing details on these samples is available.

-

Configuration and access

-

Custom notifiers are manageable in the "Settings > Customization > Notifiers" window and can be restricted through Role-Based Access Control (RBAC). Administrators can control access, limiting usage to specific Users, Groups, or Organizations.

-

For guidance on configuring notification triggers and exploring the usages of notifiers, refer to the dedicated documentation page.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/ontologies/index.html b/6.2.18/administration/ontologies/index.html deleted file mode 100755 index 140a0e8d..00000000 --- a/6.2.18/administration/ontologies/index.html +++ /dev/null @@ -1,4167 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Taxonomies - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Taxonomies

-

Taxonomies in OpenCTI refer to the structured classification systems that help in organizing and categorizing cyber threat intelligence data. They play a crucial role in the platform by allowing analysts to systematically tag and retrieve information based on predefined categories and terms.

-

Along with the Customization page, these pages allow the administrator to customize the platform.

-

Labels

-

Labels in OpenCTI serve as a powerful tool for organizing, categorizing, and prioritizing data. Here’s how they can be used effectively:

-
    -
  1. Tagging and Categorization: Labels can be used to tag malware, incidents, or indicators (IOCs) with specific categories, making it easier to filter and search through large datasets.
    2. -
  2. Prioritization: By labeling threats based on their severity or impact, security analysts can prioritize their response efforts accordingly.
    3. -
  3. Correlation and Analysis: Labels help in correlating different pieces of intelligence. For example, if multiple indicators are tagged with the same label, it might indicate a larger campaign or a common adversary.
    4. -
  4. Automation and Integration: Labels can trigger automated workflows (also called playbooks) within OpenCTI. For instance, a label might automatically initiate further investigation or escalate an incident.
    5. -
  5. Reporting and Metrics: Labels facilitate the generation of reports and metrics, allowing organizations to track trends through dashboards, measure response effectiveness, and make data-driven decisions.
    6. -
  6. Sharing and Collaboration: When sharing intelligence with other organizations or platforms, labels provide a common language that helps in understanding the context and relevance of the shared data.
    7. -
-
-

Tip

-

In order to achieve effective data labeling methods, it is recommended to establish a clear and consistent criteria for your labeling and document them in a policy or guideline.

-
-

Kill chain phases

-

Kill chain phases are used in OpenCTI to structure and analyze the data related to cyber threats and attacks. They describe the stages of an attack from the perspective of the attacker and provide a framework for identifying, analysing and responding to threats.

-

OpenCTI supports the following kill chain models:

-
    -
  • Lockheed Martin Cyber Kill Chain
    • -
  • MITRE ATT&CK Framework (Entreprise, PRE, Mobile and ICS)
    • -
  • DISARM framework
    • -
-

You can add, edit, or delete kill chain phases in the settings page, and assign them to indicators, attack patterns, incidents, or courses of action in the platform. You can also filter the data by kill chain phase, and view the kill chain phases in a timeline or as a matrix.

-

MITRE ATT&CK matrix of a threat actor

-

Vocabularies

-

Open vocabularies are sets of terms and definitions that are agreed upon by the CTI community. They help to standardize the communication documentation of cyber threat information. -This section allows you to customize a set of available fields by adding vocabulary. Almost all of the drop-down menus available in the entities can be modified from this panel.

-

Open vocabularies in OpenCTI are mainly based on the STIX standard.

-

Vocabularies in OpenCTI

-

Status templates

-

Status templates are predefined statuses that can be assigned to different entities in OpenCTI, such as reports, incidents, or cases (incident responses, requests for information and requests for takedown).

-

They help to track the progress of the analysis and response activities by defining statuses that are used in the workflows.

-

Status templates in OpenCTI

-

Case templates

-

Customizable case templates help to streamline the process of creating cases with predefined lists of tasks.

-

Case templates in OpenCTI

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/organization-segregation/index.html b/6.2.18/administration/organization-segregation/index.html deleted file mode 100755 index 7591ef53..00000000 --- a/6.2.18/administration/organization-segregation/index.html +++ /dev/null @@ -1,4083 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Organization segregation - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Organization segregation

-
-

Enterprise edition

-

Platform segregation by organization is available under the "OpenCTI Enterprise Edition" license. Please read the dedicated page to have all the information.

-
- - - - - - -

Organization administration

-

Platform administrators can promote members of an organization as "Organization administrator". This elevated role grants them the necessary capabilities to create, edit and delete users from the corresponding Organization. Additionally, administrators have the flexibility to define a list of groups that can be granted to newly created members by the organization administrators. This feature simplifies the process of granting appropriate access and privileges to individuals joining the organization.

-

Organization admin Settings view

-

The platform administrator can promote/demote an organization admin through its user edition form.

-

Organization admin promoting/demoting

-
-

Organization admin rights

-

The "Organization admin" has restricted access to Settings. They can only manage the members of the organizations for which they have been promoted as "admins".

-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/parameters/index.html b/6.2.18/administration/parameters/index.html deleted file mode 100755 index 72c5ebbc..00000000 --- a/6.2.18/administration/parameters/index.html +++ /dev/null @@ -1,4218 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Parameters - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Parameters

-

Description

-

This part of the interface wil let you configure global platform settings, like title, favicon, etc.

-

It will also give you important information about the platform.

-

The "Configuration" section

-

parameters_configuration.png

-

This section allows the administrator to edit the following settings:

-
    -
  • Platform title
    • -
  • Platform favicon URL
    • -
  • Sender email address: email address displayed as sender when sending notifications. The technical sender is defined in the SMTP configuration.
    • -
  • Theme
    • -
  • Language
    • -
  • Hidden entity types: allows you to customize which types of entities you want to see or hide in the platform. This can help you focus on the relevant information and avoid cluttering the platform with unnecessary data.
    • -
-

OpenCTI Platform

-

parameters_platform

-

This is where the Enterprise edition can be enabled.

-

This section gives important information about the platform like the used version, the edition, the architecture mode (can be Standalone or Cluster) and the number used nodes.

-

Through the "Remove Filigran logos" toggle, the administrator has the option to hide the Filigran logo on the login page and the sidebar.

-

Platform Announcement

-

This section gives you the possibility to set and display Announcements in the platform. Those announcements will be visible to every user in the platform, on top of the interface.

-

They can be used to inform some of your users or all of important information, like a scheduled downtime, an incoming upgrade, or even to share important tips regarding the usage of the platform.

-

An Announcement can be accompanied by a "Dismiss” button. When clicked by a user, it makes the message disappear for this user.

-

parameters_broadcast_message_dismissible

-

This option can be deactivated to have a permanent announcement.

-

parameters_broadcast_message_non-dismissible -⚠️ Only one announcement is shown at a time, with priority given to dismissible ones. If there are no dismissible announcements, the most recent non-dismissible one is shown.

-

Third-party Analytics

-
-

Enterprise edition

-

Analytics is available under the "OpenCTI Enterprise Edition" license.

-

Please read the dedicated page to have more information

-
-

This is where you can configure analytics providers. At the moment only Google Analytics v4 is supported.

-

Theme customization

-

In this section, the administrator can customize the two OpenCTI themes -parameters_theme_customization

-

Tools

-

This section informs the administrator of the statuses of the different managers used in the Platform. More information about the managers can be found here. -It shows also the used versions of the search engine database, RabbitMQ and Redis.

-

In cluster mode, the fact that a manager appears as enabled means that it is active in at least one node.

-

parameters_tools

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/policies/index.html b/6.2.18/administration/policies/index.html deleted file mode 100755 index 3f1a0b6d..00000000 --- a/6.2.18/administration/policies/index.html +++ /dev/null @@ -1,4222 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Policies - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Policies

-

The Policies configuration window (in "Settings > Security > Policies") encompasses essential settings that govern the organizational sharing, authentication strategies, password policies, login messages, and banner appearance within the OpenCTI platform.

-

Platform main organization

-

Allow to set a main organization for the entire platform. Users belonging to the main organization enjoy unrestricted access to all data stored in the platform. In contrast, users affiliated with other organizations will only have visibility into data explicitly shared with them.

-

Platform main organization

-
-

Numerous repercussions linked to the activation of this feature

-

This feature has implications for the entire platform and must be fully understood before being used. For example, it's mandatory to have organizations set up for each user, otherwise they won't be able to log in. It is also advisable to include connector's users in the platform main organization to avoid import problems.

-
-

Authentication strategies

-

The authentication strategies section provides insights into the configured authentication methods. Additionally, an "Enforce Two-Factor Authentication" button is available, allowing administrators to mandate 2FA activation for users, enhancing overall account security.

-

Please see the Authentication section for further details on available authentication strategies.

-

Authentication strategies

-

Local password policies

-

This section encompasses a comprehensive set of parameters defining the local password policy. Administrators can specify requirements such as minimum/maximum number of characters, symbols, digits, and more to ensure robust password security across the platform. Here are all the parameters available:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterDescription
Number of chars must be greater than or equals toDefine the minimum length required for passwords.
Number of chars must be lower or equals to (0 equals no maximum)Set an upper limit for password length.
Number of symbols must be greater or equals toSpecify the minimum number of symbols required in a password.
Number of digits must be greater or equals toSet the minimum number of numeric characters in a password.
Number of words (split on hyphen, space) must be greater or equals toEnforce a minimum count of words in a password.
Number of lowercase chars must be greater or equals toSpecify the minimum number of lowercase characters.
Number of uppercase chars must be greater or equals toSpecify the minimum number of uppercase characters.
-

Local password policies

-

Login messages

-

Allow to define messages on the login page to customize and highlight your platform's security policy. Three distinct messages can be customized:

-
    -
  • Platform login message: Appears above the login form to convey important information or announcements.
    • -
  • Platform consent message: A consent message that obscures the login form until users check the approval box, ensuring informed user consent.
    • -
  • Platform consent confirm text: A message accompanying the consent box, providing clarity on the consent confirmation process.
    • -
-

Login message configuration

-

Login message illustration

-

Platform banner configuration

-

The platform banner configuration section allows administrators to display a custom banner message at the top and bottom of the screen. This feature enables customization for enhanced visual communication and branding within the OpenCTI platform. It can be used to add a disclaimer or system purpose.

-

This configuration has two parameters:

-
    -
  • Platform banner level: Options defining the banner background color (Green, Red, or Yellow).
    • -
  • Platform banner text: Field referencing the message to be displayed within the banner.
    • -
-

Platform Banner

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/reasoning/index.html b/6.2.18/administration/reasoning/index.html deleted file mode 100755 index 5729a3ab..00000000 --- a/6.2.18/administration/reasoning/index.html +++ /dev/null @@ -1,4793 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Rules engine - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Rules engine

-

Inference rules

-

The rules engine comprises a set of predefined rules (named inference rules) that govern how new relationships are inferred based on existing data. These rules are carefully crafted to ensure logical and accurate relationship creation. Here is the list of existing inference rules:

-

Raise incident based on sighting

- - - - - - - - - - - - - -
ConditionsCreations
A non-revoked Indicator is sighted in an EntityCreation of an Incident linked to the sighted Indicator and the targeted Entity
-

Incident_based_on_sighting

-

Sightings of observables via observed data

- - - - - - - - - - - - - -
ConditionsCreations
An Indicator is based on an Observable contained in an Observed DataCreation of a sighting between the Indicator and the creating Identity of the Observed Data
-

Sighting_via_observed_data

-

Sightings propagation from indicator

- - - - - - - - - - - - - -
ConditionsCreations
An Indicator based on an Observable is sighted in an EntityThe Observable is sighted in the Entity
-

Sighting_prop_from_indicator

-

Sightings propagation from observable

- - - - - - - - - - - - - -
ConditionsCreations
An Indicator is based on an Observable sighted in an EntityThe Indicator is sighted in the Entity
-

Sighting_prop_from_observable

-

Relation propagation via an observable

- - - - - - - - - - - - - -
ConditionsCreations
An observable is related to two EntitiesCreate a related to relationship between the two Entities
-

Observable_related_to_entities

-

Attribution propagation

- - - - - - - - - - - - - -
ConditionsCreations
An Entity A is attributed to an Entity B and this Entity B is itself attributed to an Entity CThe Entity A is attributed to Entity C
-

Attribution_propagation

-

Belonging propagation

- - - - - - - - - - - - - -
ConditionsCreations
An Entity A is part of an Entity B and this Entity B is itself part of an Entity CThe Entity A is part of Entity C
-

Belonging_propagation

-

Location propagation

- - - - - - - - - - - - - -
ConditionsCreations
A Location A is located at a Location B and this Location B is itself located at a Location CThe Location A is located at Location C
-

Location_propagation

-

Organization propagation via participation

- - - - - - - - - - - - - -
ConditionsCreations
A User is affiliated with an Organization B, which is part of an Organization CThe User is affiliated to the Organization C
-

Organisation_via_participation

-

Identities propagation in reports

- - - - - - - - - - - - - -
ConditionsCreations
A Report contains an Identity B and this Identity B is part of an Identity CThe Report contains Identity C, as well as the Relationship between Identity B and Identity C
-

Identities_propagation

-

Locations propagation in reports

- - - - - - - - - - - - - -
ConditionsCreations
A Report contains a Location B and this Location B is located at a Location CThe Report contains Location B, as well as the Relationship between Location B and Location C
-

Locations_propagation_report

-

Observables propagation in reports

- - - - - - - - - - - - - -
ConditionsCreations
A Report contains an Indicator and this Indicator is based on an ObservableThe Report contains the Observable, as well as the Relationship between the Indicator and the Observable
-

Observables_propagation

-

Usage propagation via attribution

- - - - - - - - - - - - - -
ConditionsCreations
An Entity A, attributed to an Entity C, uses an Entity BThe Entity C uses the Entity B
-

Usage_propagation

-

Inference of targeting via a sighting

- - - - - - - - - - - - - -
ConditionsCreations
An Indicator, sighted at an Entity C, indicates an Entity BThe Entity B targets the Entity C
-

Targeting_via_sighting

-

Targeting propagation via attribution

- - - - - - - - - - - - - -
ConditionsCreations
An Entity A, attributed to an Entity C, targets an Entity BThe Entity C targets the Entity B
-

Targeting_via_attribution

-

Targeting propagation via belonging

- - - - - - - - - - - - - -
ConditionsCreations
An Entity A targets an Identity B, part of an Identity CThe Entity A targets the Identity C
-

Targeting_via_belonging

-

Targeting propagation via location

- - - - - - - - - - - - - -
ConditionsCreations
An Entity targets a Location B and this Location B is located at a Location CThe Entity targets the Location C
-

Targeting_via_location

-

Targeting propagation when located

- - - - - - - - - - - - - -
ConditionsCreations
An Entity A targets an Entity B and this target is located at Location D.The Entity A targets the Location D
-

Targeting_when_located

-

Rule execution

-

Rule activation

-

When a rule is activated, a background task is initiated. This task scans all platform data, identifying existing relationships that meet the conditions defined by the rule. Subsequently, it creates new objects (entities and/or relationships), expanding the network of insights within your threat intelligence environment. Then, activated rules operate continuously. Whenever a relationship is created or modified, and this change aligns with the conditions specified in an active rule, the reasoning mechanism is triggered. This ensures real-time relationship inference.

-

Rule deactivation

-

Deactivating a rule leads to the deletion of all objects and relationships created by it. This cleanup process maintains the accuracy and reliability of your threat intelligence database.

-

Access restrictions and data impact

-

Access to the rule engine panel is restricted to administrators only. Regular users do not have visibility into this section of the platform. Administrators possess the authority to activate or deactivate rules.

-

The rules engine empowers OpenCTI with the capability to automatically establish intricate relationships within your data. However, these rules can lead to a very large number of objects created. Even if the operation is reversible, an administrator should consider the impact of activating a rule.

-

Additional resources

-
    -
  • Usefulness: To understand the benefits and results of these rules, refer to the Inferences and reasoning page in the User Guide section of the documentation.
    • -
  • New inference rule: Given the potential impact of a rule on your data, users are not allowed to add new rules. However, users can submit rule suggestions via a GitHub issue for evaluation. These suggestions are carefully evaluated by our team, ensuring continuous improvement and innovation.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/retentions/index.html b/6.2.18/administration/retentions/index.html deleted file mode 100755 index 7b4ec6f5..00000000 --- a/6.2.18/administration/retentions/index.html +++ /dev/null @@ -1,4093 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Retention policies - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Retention policies

-

Retention rules serve the purpose of establishing data retention times, specifying when data should be automatically deleted from the platform. Users can define filters to target specific objects. Any object meeting these criteria that haven't been updated within the designated time frame will be permanently deleted.

-

Note that the data deleted by an active retention policy will not appear in the trash and thus cannot be restored.

-

Configuration

-

Retention rules can be configured in the "Settings > Customization > Retention policies" window. A set of parameters must be configured:

-
    -
  • Maximum retention days: Set the maximum number of days an object can remain unchanged before being eligible for deletion.
    • -
  • Filters: Define filters based on specific criteria to select the types of objects subject to retention rules.
    • -
-

An object will be removed if it meets the specified filters and hasn't been updated for the duration set in the "Maximum retention days" field.

-

Retention policy parameters

-

Verification process

-

Before activating a retention rule, users have the option to verify its impact using the "Verify" button. This action provides insight into the number of objects that currently match the rule's criteria and would be deleted if the rule is activated.

-

Items to be deleted

-
-

Verify before activation

-

Always use the "Verify" feature to assess the potential impact of a retention rule before activating it. Once the rule is activated, data deletion will begin, and retrieval of the deleted data will not be possible.

-
-

Retention rules contribute to maintaining a streamlined and efficient data lifecycle within OpenCTI, ensuring that outdated or irrelevant information is systematically removed from the platform, thereby optimizing disk space usage.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/segregation/index.html b/6.2.18/administration/segregation/index.html deleted file mode 100755 index 12ebdc2b..00000000 --- a/6.2.18/administration/segregation/index.html +++ /dev/null @@ -1,4320 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Marking restriction - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Marking restriction

-

Data segregation in the context of Cyber Threat Intelligence refers to the practice of categorizing and separating different types of data or information related to cybersecurity threats based on specific criteria.

-

This separation helps organizations manage and analyze threat intelligence more effectively and securely and the goal of data segregation is to ensure that only those individuals who are authorized to view a particular set of data have access to that set of data.

-

Practically, "Need-to-know basis" and "classification level" are data segregation measures.

-

Description

-

Marking definitions are essential in the context of data segregation to ensure that data is appropriately categorized and protected based on its sensitivity or classification level. Marking definitions establish a standardized framework for classifying data.

-

Marking Definition objects are unique among STIX objects in the STIX 2.1 standard in that they cannot be versioned. This restriction is in place to prevent the possibility of indirect alterations to the markings associated with a STIX Object.

-

Multiple markings can be added to the same object. Certain categories of marking definitions or trust groups may enforce rules that specify which markings take precedence over others or how some markings can be added to complement existing ones.

-

In OpenCTI, data is segregated based on knowledge marking. The diagram provided below illustrates the manner in which OpenCTI establishes connections between pieces of information to authorize data access for a user:

-

Data access diagram

-

Manage markings

-

Create new markings

-

To create a marking, you must first possess the capability Manage marking definitions. For further information on user administration, please refer to the Users and Role Based Access Control page.

-

Once you have access to the settings, navigate to "Settings > Security > Marking Definitions" to create a new marking.

-

A marking consists of the following attributes:

-
    -
  • Type: Specifies the marking group to which it belongs.
    • -
  • Definition: The name assigned to the marking.
    • -
  • Color: The color associated with the marking.
    • -
  • Order: Determines the hierarchical order among markings of the same type.
    • -
-

Create a marking animation

-

Allowed marking

-

The configuration of authorized markings for a user is determined at the Group level. To access entities and relationships associated with specific markings, the user must belong to a group that has been granted access to those markings.

-

There are two ways in which markings can be accessed:

-
    -
  • The user is a member of a group that has been granted access to the marking.
    • -
  • The user is a member of a group that has access to a marking of the same type, with an equal or higher hierarchical order.
    • -
-
-

Access to an object with several markings

-

Access to all markings attached to an object is required in order to access it (not only one).

-
-
-

Automatically grant access to the new marking

-

To allow a group to automatically access a newly created marking definition, you can check Automatically authorize this group to new marking definition.

-
-

Default marking definitions

-

To apply a default marking when creating a new entity or relationship, you can choose which marking to add by default from the list of allowed markings. You can add only one marking per type, but you can have multiple types. This configuration is also done at the Group level.

-

Add default marking

-
-

Need a configuration change

-

Simply adding markings as default markings is insufficient to display the markings when creating an entity or relationship. You also need to enable default markings in the customization settings of an entity or relationship. For example, to enable default markings for a new report, navigate to "Settings > Customization > Report > Markings" and toggle the option to Activate/Desactivate default values.

-
-

Maximum shareable marking definitions

-

This configuration allows to define, for each type of marking definitions, until which level -we allow to share data externally (via Public dashboard or file export).

-

The marking definitions that can be shared by a group are the ones

-
    -
  • that are allowed for this group
    • -
  • and whose order are inferior or equal to the order of the maximum shareable markings defined for each marking type.
    • -
-

Users with the Bypass capability can share all the markings.

-

By default, every marking of a given marking type is shareable.

-

For example in the capture below, for the type of marking TLP, only data with a marking -definition that is allowed and has a level equal or below GREEN will be shareable. And no data with marking -definition statement will be shared at all.

-

Maximum marking definitions shareable

-

Management of multiple markings

-

In scenarios where multiple markings of the same type but different orders are added, the platform will retain only the marking with the highest order for each type. This consolidation can occurs in various instances:

-
    -
  • During entity creation, if multiple markings are selected.
    • -
  • During entity updates, whether manually or via a connector, if additional markings are introduced.
    • -
  • When multiple entities are merged, their respective markings will be amalgamated.
    • -
-

For example:

-

Create a new report and add markings PAP:AMBER,PAP:RED,TLP:AMBER+STRICT,TLP:CLEAR and a statement CC-BY-SA-4.0 DISARM Foundation

-

Create entity with markings

-

The final markings kept are: PAP:RED, TLP:AMBER+STRICT and CC-BY-SA-4.0 DISARM Foundation

-

Create entity with markings

-

Update an object manually

-

When update an entity or a relationship:

-
    -
  • add a marking with the same type and different orders, a pop-up will be displayed to confirm the choice,
    • -
  • add a marking with the same type and the same order, the marking will be added,
    • -
  • add a marking with different types, the marking will be added.
    • -
-

Update entity with markings, popup dialog

-

Import data from a connector

-

As a result of this mechanism, when importing data from a connector, the connector is unable to downgrade a marking for an entity if a marking of the same type is already present on it.

-

Additional information

-

The Traffic Light Protocol is implemented by default as marking definitions in OpenCTI. It allows you to segregate information by TLP levels in your platform and restrict access to marked data if users are not authorized to see the corresponding marking.

-

The Traffic Light Protocol (TLP) was designed by the Forum of Incident Response and Security Teams (FIRST) to provide a standardized method for classifying and handling sensitive information, based on four categories of sensitivity.

-

For more details, the diagram provided below illustrates how are categorized the marking definitions:

-

TLP diagram

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/support-package/index.html b/6.2.18/administration/support-package/index.html deleted file mode 100755 index c55144ba..00000000 --- a/6.2.18/administration/support-package/index.html +++ /dev/null @@ -1,4107 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Support package - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Support Package

-

Support packages are useful for troubleshooting issue that occurs on OpenCTI platform. -Administrators can request to create and download a support package that contains recent platform error logs and usage statistics.

-
-

Support package content

-

Even if we do our best to prevent logging any data, the support package may contains some sensitive information that you may not want to share with everyone. -Before creating a ticket with your support package takes some time to check if you can safely share the content depending of your security policy.

-
-

Support Package can be requested from "Settings > Support" menu.

-

Support package overview

-

Package generation

-

On a click on "Generate support package", a support event is propagated to every platform instances to request needed information. -Every instance that will receive this message will process the request and send the files to the platform. -During this processing the interface will display the expected support package name in an IN PROGRESS state waiting for completion. -After finishing the process the support package will move to the READY state and the buttons download and delete will be activated.

-

Package download

-

After file generation, using the download button will dynamically create a (zip) containing all instances logs and telemetry.

-

Partial package

-

In case of platform instability, some logs might not be retrieved and the support package will be incomplete.

-

If some instances fail to send their data, you will be able to force download a partial zip only after 1 minute. In case of a support package taking more than 5 minutes, the status will be moved to "timeout".

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/administration/users/index.html b/6.2.18/administration/users/index.html deleted file mode 100755 index 156dbbdf..00000000 --- a/6.2.18/administration/users/index.html +++ /dev/null @@ -1,4554 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Users and RBAC - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - Skip to content - - -
-
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Users and Role Based Access Control

-

Introduction

-

In OpenCTI, the RBAC system not only related to what users can do or cannot do in the platform (aka. Capabilities) but also to the system of data segregation. Also, platform behavior such as default home dashboards, default triggers and digests as well as default hidden menus or entities can be defined across groups and organizations.

-

High level design

-

RBAC

-

Roles

-

Roles are used in the platform to grant the given groups with some capabilities to define what users in those groups can do or cannot do.

-

List of capabilities

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CapabilityDescription
Bypass all capabilitiesJust bypass everything including data segregation and enforcements.
Access knowledgeAccess in read-only to all the knowledge in the platform.
  Access to collaborative creationCreate notes and opinions (and modify its own) on entities and relations.
  Create / Update knowledgeCreate and update existing entities and relationships.
    Restrict organization accessShare entities and relationships with other organizations.
    Delete knowledgeDelete entities and relationships.
    Manage authorized membersRestrict the access to an entity to a user, group or organization.
    Bypass enforced referenceIf external references enforced in a type of entity, be able to bypass the enforcement.
  Upload knowledge filesUpload files in the Data and Content section of entities.
  Import knowledgeTrigger the ingestion of an uploaded file.
  Download knowledge exportDownload the exports generated in the entities (in the Data section).
    Generate knowledge exportTrigger the export of the knowledge of an entity.
  Ask for knowledge enrichmentTrigger an enrichment for a given entity.
Access dashboardsAccess to existing custom dashboards.
  Create / Update dashboardsCreate and update custom dashboards.
    Delete dashboardsDelete existing custom dashboards.
    Manage public dashboardsManage public dashboards.
Access investigationsAccess to existing investigations.
  Create / Update investigationsCreate and update investigations.
    Delete investigationsDelete existing investigations.
Access connectorsRead information in the Data > Connectors section.
  Manage connector stateReset the connector state to restart ingestion from the beginning.
Connectors API usage: register, ping, export push ...Connectors specific permissions for register, ping, push export files, etc.
Access data sharingAccess and consume data such as TAXII collections, CSV feeds and live streams.
  Manage data sharingShare data such as TAXII collections, CSV feeds and live streams or custom dashboards.
Access ingestionAccess (read only) remote OCTI streams, TAXII feeds, RSS feeds, CSV feeds.
  Manage ingestionCreate, update, delete any remote OCTI streams, TAXII feeds, RSS feeds, CSV feeds.
Manage CSV mappersCreate, update and delete CSV mappers.
Access to admin functionalitiesParent capability allowing users to only view the settings.
  Access administration parametersAccess and manage overall parameters of the platform in Settings > Parameters.
  Manage credentialsAccess and manage roles, groups, users, organizations and security policies.
  Manage marking definitionsUpdate and delete marking definitions.
  Manage customizationCustomize entity types, rules, notifiers retention policies and decays rules.
  Manage taxonomiesManage labels, kill chain phases, vocabularies, status templates, cases templates.
  Access to security activityAccess to activity log.
  Access to file indexingManage file indexing.
  Access to supportGenerate and download support packages.
-

Manage roles

-

You can manage the roles in Settings > Security > Roles.

-

To create a role, just click on the + button:

-

Create role

-

Then you will be able to define the capabilities of the role:

-

Update role

-

Users

-

You can manage the users in Settings > Security > Users. If you are using Single-Sign-On (SSO), the users in OpenCTI are automatically created upon login.

-

To create a user, just click on the + button:

-

Create user

-

Manage a user

-

When access to a user, it is possible to:

-
    -
  • Visualize information including the token
    • -
  • Modify it, reset 2FA if necessary
    • -
  • Manage its sessions
    • -
  • Manage its triggers and digests
    • -
  • Visualize the history and operations
    • -
  • Manage its max confidence levels
    • -
-

User overview

-

From this view you can edit the user's information by clicking the "Update" button, which opens a panel with several tabs.

-
    -
  • Overview tab: edit all basic information such as the name or language
    • -
  • Password tab: change the password for this user
    • -
  • Groups tab: select the groups this user belongs to
    • -
  • Organization Admin tab: see Organization administration
    • -
  • Confidences tab: manage the user's maximum confidence level and overrides per entity type
    • -
-

manage user

-
-

Mandatory max confidence level

-

A user without Max confidence level won't have the ability to create, delete or update any data in our platform. Please be sure that your users are always either assigned to group that have a confidence level defined or that have an override of this group confidence level.

-
-

-

Groups

-

Groups are the main way to manage permissions and data segregation as well as platform customization for the given users part of this group. You can manage the groups in Settings > Security > Groups.

-

Here is the description of the group available parameters.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterDescription
Auto new markingsIf a new marking definition is created, this group will automatically be granted to it.
Default membershipIf a new user is created (manually or upon SSO), it will be added to this group.
RolesRoles and capabilities granted to the users belonging to this group.
Default dashboardCustomize the home dashboard for the users belonging to this group.
Default markingsIn Settings > Customization > Entity types, if a default marking definition is enabled, default markings of the group is used.
Allowed markingsGrant access to the group to the defined marking definitions, more details in data segregation.
Max shareable markingsGrant authorization to the group to share marking definitions.
Triggers and digestsDefine defaults triggers and digests for the users belonging to this group.
Max confidence levelDefine the maximum confidence level for the group: it will impact the capacity to update entities, the confidence level of a newly created entity by a user of the group.
-

Group overview

-
-

Max confidence level when a user has multiple groups

-

A user with multiple groups will have the the highest confidence level of all its groups. -For instance, if a user is part of group A (max confidence level = 100) and group B (max confidence level = 50), then the user max confidence level will be 100.

-
-

Manage a group

-

When managing a group, you can define the members and all above configurations.

-

Update a group

-

-

Organizations

-

Users can belong to organizations, which is an additional layer of data segregation and customization. To find out more about this part, please refer to the page on organization segregation.

-

Organization administration

-

Platform administrators can promote members of an organization as "Organization administrator". This elevated role grants them the necessary capabilities to create, edit and delete users from the corresponding Organization. Additionally, administrators have the flexibility to define a list of groups that can be granted to newly created members by the organization administrators. This feature simplifies the process of granting appropriate access and privileges to individuals joining the organization.

-

Organization admin Settings view

-

The platform administrator can promote/demote an organization admin through its user edition form.

-

Organization admin promoting/demoting

-
-

Organization admin rights

-

The "Organization admin" has restricted access to Settings. They can only manage the members of the organizations for which they have been promoted as "admins".

-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/assets/css/custom.css b/6.2.18/assets/css/custom.css deleted file mode 100755 index 39e1f487..00000000 --- a/6.2.18/assets/css/custom.css +++ /dev/null @@ -1,136 +0,0 @@ -/* Color scheme */ - -[data-md-color-scheme="filigran"] { - /* Primary color shades */ - --md-primary-fg-color: #; - --md-primary-fg-color--light: #; - --md-primary-fg-color--dark: #; - --md-primary-bg-color: #; - --md-primary-bg-color--light: #; - - /* Accent color shades */ - --md-accent-fg-color: #1bb6ff; - --md-accent-fg-color--transparent: #; - --md-accent-bg-color: #; - --md-accent-bg-color--light: #; - - /* Default color shades */ - --md-default-fg-color: #00b1ff; - --md-default-fg-color--light: #697a94; - --md-default-fg-color--lighter: #3d4e66; - --md-default-fg-color--lightest: #03305d; - --md-default-bg-color: #070d19; - --md-default-bg-color--light: #0f1e38; - --md-default-bg-color--lighter: #152849; - --md-default-bg-color--lightest: #09101e; - - /* Code color shades */ - --md-code-fg-color: #ffffff; - --md-code-fg-color--light: #1bb6ff; - --md-code-bg-color: #001e3c; - --md-code-bg-color--light: #001e3c; - --md-code-bg-color--lighter: #001e3c; - - /* Code highlighting color shades */ - --md-code-hl-operator-color: #9ccc65; - --md-code-hl-punctuation-color: #cddc39; - --md-code-hl-comment-color: #3d4e66; - --md-code-hl-variable-color: #9ccc65; - --md-code-hl-name-color: #ffb300; - - /* Typeset color shades */ - --md-typeset-color: #ffffff; - - /* Typeset `a` color shades */ - --md-typeset-a-color: #0fbcff; - - /* Typeset `mark` color shades */ - --md-typeset-mark-color: #; - - /* Typeset `del` and `ins` color shades */ - --md-typeset-del-color: #; - --md-typeset-ins-color: #; - - /* Typeset `kbd` color shades */ - --md-typeset-kbd-color: #; - --md-typeset-kbd-accent-color: #; - --md-typeset-kbd-border-color: #; - - /* Typeset `table` color shades */ - --md-typeset-table-color: #0082d1; - --md-typeset-table-color--light: #051629; - - /* Admonition color shades */ - --md-admonition-fg-color: #ffffff; - --md-admonition-bg-color: var(--md-default-bg-color); - - /* Warning color shades */ - --md-warning-fg-color: #; - --md-warning-bg-color: #; - - /* Footer color shades */ - --md-footer-fg-color: #; - --md-footer-fg-color--light: #; - --md-footer-fg-color--lighter: #; - --md-footer-bg-color: #011222; - --md-footer-bg-color--dark: #09101e; -} - -/* Header */ -.md-header, .md-tabs { - background-color: #09101e !important; -} - -/* Cards */ -.md-typeset .grid.cards>ol>li,.md-typeset .grid.cards>ul>li,.md-typeset .grid>.card { - border: none !important; - background-color: #001e3c !important; - border-radius: 10px; -} - -.md-typeset .grid.cards>ol>li:focus-within,.md-typeset .grid.cards>ol>li:hover,.md-typeset .grid.cards>ul>li:focus-within,.md-typeset .grid.cards>ul>li:hover,.md-typeset .grid>.card:focus-within,.md-typeset .grid>.card:hover { - border: none !important; - background-color: #001e3c !important; - border-radius: 10px; -} - -html .md-footer-meta.md-typeset a:focus,html .md-footer-meta.md-typeset a:hover { - color: #0fbcff !important; -} - -.middle { - margin: -5px 5px 0 0 !important; -} - -.md-header__button.md-logo img,.md-header__button.md-logo svg { - height: 1.5rem; -} - -.grid { - column-gap: 0.8rem !important; -} - -.md-typeset__table { - min-width: 100%; -} - -.md-typeset table:not([class]) { - display: table; -} - -.md-typeset__table td, th { - white-space: nowrap; -} - - -/* Works on Chrome, Edge, and Safari */ -html, body { - scrollbar-color: #070d19 #0f1e38; - scrollbarWidth: thin; - WebkitFontSmoothing: auto; -} - -.glightbox img { - border: 1px solid #273d5f; - border-radius: 4.8px; -} \ No newline at end of file diff --git a/6.2.18/assets/images/favicon.png b/6.2.18/assets/images/favicon.png deleted file mode 100755 index 17010cb5..00000000 Binary files a/6.2.18/assets/images/favicon.png and /dev/null differ diff --git a/6.2.18/assets/javascripts/bundle.56dfad97.min.js b/6.2.18/assets/javascripts/bundle.56dfad97.min.js deleted file mode 100755 index 1df62cd7..00000000 --- a/6.2.18/assets/javascripts/bundle.56dfad97.min.js +++ /dev/null @@ -1,16 +0,0 @@ -"use strict";(()=>{var Fi=Object.create;var gr=Object.defineProperty;var Wi=Object.getOwnPropertyDescriptor;var Ui=Object.getOwnPropertyNames,Vt=Object.getOwnPropertySymbols,Di=Object.getPrototypeOf,yr=Object.prototype.hasOwnProperty,io=Object.prototype.propertyIsEnumerable;var no=(e,t,r)=>t in e?gr(e,t,{enumerable:!0,configurable:!0,writable:!0,value:r}):e[t]=r,$=(e,t)=>{for(var r in t||(t={}))yr.call(t,r)&&no(e,r,t[r]);if(Vt)for(var r of Vt(t))io.call(t,r)&&no(e,r,t[r]);return e};var ao=(e,t)=>{var r={};for(var o in e)yr.call(e,o)&&t.indexOf(o)<0&&(r[o]=e[o]);if(e!=null&&Vt)for(var o of Vt(e))t.indexOf(o)<0&&io.call(e,o)&&(r[o]=e[o]);return r};var xr=(e,t)=>()=>(t||e((t={exports:{}}).exports,t),t.exports);var Vi=(e,t,r,o)=>{if(t&&typeof t=="object"||typeof t=="function")for(let n of Ui(t))!yr.call(e,n)&&n!==r&&gr(e,n,{get:()=>t[n],enumerable:!(o=Wi(t,n))||o.enumerable});return e};var Lt=(e,t,r)=>(r=e!=null?Fi(Di(e)):{},Vi(t||!e||!e.__esModule?gr(r,"default",{value:e,enumerable:!0}):r,e));var so=(e,t,r)=>new Promise((o,n)=>{var i=p=>{try{s(r.next(p))}catch(c){n(c)}},a=p=>{try{s(r.throw(p))}catch(c){n(c)}},s=p=>p.done?o(p.value):Promise.resolve(p.value).then(i,a);s((r=r.apply(e,t)).next())});var po=xr((Er,co)=>{(function(e,t){typeof Er=="object"&&typeof co!="undefined"?t():typeof define=="function"&&define.amd?define(t):t()})(Er,function(){"use strict";function e(r){var o=!0,n=!1,i=null,a={text:!0,search:!0,url:!0,tel:!0,email:!0,password:!0,number:!0,date:!0,month:!0,week:!0,time:!0,datetime:!0,"datetime-local":!0};function s(k){return!!(k&&k!==document&&k.nodeName!=="HTML"&&k.nodeName!=="BODY"&&"classList"in k&&"contains"in k.classList)}function p(k){var ft=k.type,qe=k.tagName;return!!(qe==="INPUT"&&a[ft]&&!k.readOnly||qe==="TEXTAREA"&&!k.readOnly||k.isContentEditable)}function c(k){k.classList.contains("focus-visible")||(k.classList.add("focus-visible"),k.setAttribute("data-focus-visible-added",""))}function l(k){k.hasAttribute("data-focus-visible-added")&&(k.classList.remove("focus-visible"),k.removeAttribute("data-focus-visible-added"))}function f(k){k.metaKey||k.altKey||k.ctrlKey||(s(r.activeElement)&&c(r.activeElement),o=!0)}function u(k){o=!1}function d(k){s(k.target)&&(o||p(k.target))&&c(k.target)}function y(k){s(k.target)&&(k.target.classList.contains("focus-visible")||k.target.hasAttribute("data-focus-visible-added"))&&(n=!0,window.clearTimeout(i),i=window.setTimeout(function(){n=!1},100),l(k.target))}function M(k){document.visibilityState==="hidden"&&(n&&(o=!0),X())}function X(){document.addEventListener("mousemove",J),document.addEventListener("mousedown",J),document.addEventListener("mouseup",J),document.addEventListener("pointermove",J),document.addEventListener("pointerdown",J),document.addEventListener("pointerup",J),document.addEventListener("touchmove",J),document.addEventListener("touchstart",J),document.addEventListener("touchend",J)}function te(){document.removeEventListener("mousemove",J),document.removeEventListener("mousedown",J),document.removeEventListener("mouseup",J),document.removeEventListener("pointermove",J),document.removeEventListener("pointerdown",J),document.removeEventListener("pointerup",J),document.removeEventListener("touchmove",J),document.removeEventListener("touchstart",J),document.removeEventListener("touchend",J)}function J(k){k.target.nodeName&&k.target.nodeName.toLowerCase()==="html"||(o=!1,te())}document.addEventListener("keydown",f,!0),document.addEventListener("mousedown",u,!0),document.addEventListener("pointerdown",u,!0),document.addEventListener("touchstart",u,!0),document.addEventListener("visibilitychange",M,!0),X(),r.addEventListener("focus",d,!0),r.addEventListener("blur",y,!0),r.nodeType===Node.DOCUMENT_FRAGMENT_NODE&&r.host?r.host.setAttribute("data-js-focus-visible",""):r.nodeType===Node.DOCUMENT_NODE&&(document.documentElement.classList.add("js-focus-visible"),document.documentElement.setAttribute("data-js-focus-visible",""))}if(typeof window!="undefined"&&typeof document!="undefined"){window.applyFocusVisiblePolyfill=e;var t;try{t=new CustomEvent("focus-visible-polyfill-ready")}catch(r){t=document.createEvent("CustomEvent"),t.initCustomEvent("focus-visible-polyfill-ready",!1,!1,{})}window.dispatchEvent(t)}typeof document!="undefined"&&e(document)})});var qr=xr((ly,Sn)=>{"use strict";/*! - * escape-html - * Copyright(c) 2012-2013 TJ Holowaychuk - * Copyright(c) 2015 Andreas Lubbe - * Copyright(c) 2015 Tiancheng "Timothy" Gu - * MIT Licensed - */var ka=/["'&<>]/;Sn.exports=Ha;function Ha(e){var t=""+e,r=ka.exec(t);if(!r)return t;var o,n="",i=0,a=0;for(i=r.index;i{/*! - * clipboard.js v2.0.11 - * https://clipboardjs.com/ - * - * Licensed MIT © Zeno Rocha - */(function(t,r){typeof It=="object"&&typeof Yr=="object"?Yr.exports=r():typeof define=="function"&&define.amd?define([],r):typeof It=="object"?It.ClipboardJS=r():t.ClipboardJS=r()})(It,function(){return function(){var e={686:function(o,n,i){"use strict";i.d(n,{default:function(){return ji}});var a=i(279),s=i.n(a),p=i(370),c=i.n(p),l=i(817),f=i.n(l);function u(V){try{return document.execCommand(V)}catch(A){return!1}}var d=function(A){var L=f()(A);return u("cut"),L},y=d;function M(V){var A=document.documentElement.getAttribute("dir")==="rtl",L=document.createElement("textarea");L.style.fontSize="12pt",L.style.border="0",L.style.padding="0",L.style.margin="0",L.style.position="absolute",L.style[A?"right":"left"]="-9999px";var F=window.pageYOffset||document.documentElement.scrollTop;return L.style.top="".concat(F,"px"),L.setAttribute("readonly",""),L.value=V,L}var X=function(A,L){var F=M(A);L.container.appendChild(F);var D=f()(F);return u("copy"),F.remove(),D},te=function(A){var L=arguments.length>1&&arguments[1]!==void 0?arguments[1]:{container:document.body},F="";return typeof A=="string"?F=X(A,L):A instanceof HTMLInputElement&&!["text","search","url","tel","password"].includes(A==null?void 0:A.type)?F=X(A.value,L):(F=f()(A),u("copy")),F},J=te;function k(V){"@babel/helpers - typeof";return typeof Symbol=="function"&&typeof Symbol.iterator=="symbol"?k=function(L){return typeof L}:k=function(L){return L&&typeof Symbol=="function"&&L.constructor===Symbol&&L!==Symbol.prototype?"symbol":typeof L},k(V)}var ft=function(){var A=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{},L=A.action,F=L===void 0?"copy":L,D=A.container,Y=A.target,$e=A.text;if(F!=="copy"&&F!=="cut")throw new Error('Invalid "action" value, use either "copy" or "cut"');if(Y!==void 0)if(Y&&k(Y)==="object"&&Y.nodeType===1){if(F==="copy"&&Y.hasAttribute("disabled"))throw new Error('Invalid "target" attribute. Please use "readonly" instead of "disabled" attribute');if(F==="cut"&&(Y.hasAttribute("readonly")||Y.hasAttribute("disabled")))throw new Error(`Invalid "target" attribute. You can't cut text from elements with "readonly" or "disabled" attributes`)}else throw new Error('Invalid "target" value, use a valid Element');if($e)return J($e,{container:D});if(Y)return F==="cut"?y(Y):J(Y,{container:D})},qe=ft;function Fe(V){"@babel/helpers - typeof";return typeof Symbol=="function"&&typeof Symbol.iterator=="symbol"?Fe=function(L){return typeof L}:Fe=function(L){return L&&typeof Symbol=="function"&&L.constructor===Symbol&&L!==Symbol.prototype?"symbol":typeof L},Fe(V)}function Ai(V,A){if(!(V instanceof A))throw new TypeError("Cannot call a class as a function")}function oo(V,A){for(var L=0;L0&&arguments[0]!==void 0?arguments[0]:{};this.action=typeof D.action=="function"?D.action:this.defaultAction,this.target=typeof D.target=="function"?D.target:this.defaultTarget,this.text=typeof D.text=="function"?D.text:this.defaultText,this.container=Fe(D.container)==="object"?D.container:document.body}},{key:"listenClick",value:function(D){var Y=this;this.listener=c()(D,"click",function($e){return Y.onClick($e)})}},{key:"onClick",value:function(D){var Y=D.delegateTarget||D.currentTarget,$e=this.action(Y)||"copy",Dt=qe({action:$e,container:this.container,target:this.target(Y),text:this.text(Y)});this.emit(Dt?"success":"error",{action:$e,text:Dt,trigger:Y,clearSelection:function(){Y&&Y.focus(),window.getSelection().removeAllRanges()}})}},{key:"defaultAction",value:function(D){return vr("action",D)}},{key:"defaultTarget",value:function(D){var Y=vr("target",D);if(Y)return document.querySelector(Y)}},{key:"defaultText",value:function(D){return vr("text",D)}},{key:"destroy",value:function(){this.listener.destroy()}}],[{key:"copy",value:function(D){var Y=arguments.length>1&&arguments[1]!==void 0?arguments[1]:{container:document.body};return J(D,Y)}},{key:"cut",value:function(D){return y(D)}},{key:"isSupported",value:function(){var D=arguments.length>0&&arguments[0]!==void 0?arguments[0]:["copy","cut"],Y=typeof D=="string"?[D]:D,$e=!!document.queryCommandSupported;return Y.forEach(function(Dt){$e=$e&&!!document.queryCommandSupported(Dt)}),$e}}]),L}(s()),ji=Ii},828:function(o){var n=9;if(typeof Element!="undefined"&&!Element.prototype.matches){var i=Element.prototype;i.matches=i.matchesSelector||i.mozMatchesSelector||i.msMatchesSelector||i.oMatchesSelector||i.webkitMatchesSelector}function a(s,p){for(;s&&s.nodeType!==n;){if(typeof s.matches=="function"&&s.matches(p))return s;s=s.parentNode}}o.exports=a},438:function(o,n,i){var a=i(828);function s(l,f,u,d,y){var M=c.apply(this,arguments);return l.addEventListener(u,M,y),{destroy:function(){l.removeEventListener(u,M,y)}}}function p(l,f,u,d,y){return typeof l.addEventListener=="function"?s.apply(null,arguments):typeof u=="function"?s.bind(null,document).apply(null,arguments):(typeof l=="string"&&(l=document.querySelectorAll(l)),Array.prototype.map.call(l,function(M){return s(M,f,u,d,y)}))}function c(l,f,u,d){return function(y){y.delegateTarget=a(y.target,f),y.delegateTarget&&d.call(l,y)}}o.exports=p},879:function(o,n){n.node=function(i){return i!==void 0&&i instanceof HTMLElement&&i.nodeType===1},n.nodeList=function(i){var a=Object.prototype.toString.call(i);return i!==void 0&&(a==="[object NodeList]"||a==="[object HTMLCollection]")&&"length"in i&&(i.length===0||n.node(i[0]))},n.string=function(i){return typeof i=="string"||i instanceof String},n.fn=function(i){var a=Object.prototype.toString.call(i);return a==="[object Function]"}},370:function(o,n,i){var a=i(879),s=i(438);function p(u,d,y){if(!u&&!d&&!y)throw new Error("Missing required arguments");if(!a.string(d))throw new TypeError("Second argument must be a String");if(!a.fn(y))throw new TypeError("Third argument must be a Function");if(a.node(u))return c(u,d,y);if(a.nodeList(u))return l(u,d,y);if(a.string(u))return f(u,d,y);throw new TypeError("First argument must be a String, HTMLElement, HTMLCollection, or NodeList")}function c(u,d,y){return u.addEventListener(d,y),{destroy:function(){u.removeEventListener(d,y)}}}function l(u,d,y){return Array.prototype.forEach.call(u,function(M){M.addEventListener(d,y)}),{destroy:function(){Array.prototype.forEach.call(u,function(M){M.removeEventListener(d,y)})}}}function f(u,d,y){return s(document.body,u,d,y)}o.exports=p},817:function(o){function n(i){var a;if(i.nodeName==="SELECT")i.focus(),a=i.value;else if(i.nodeName==="INPUT"||i.nodeName==="TEXTAREA"){var s=i.hasAttribute("readonly");s||i.setAttribute("readonly",""),i.select(),i.setSelectionRange(0,i.value.length),s||i.removeAttribute("readonly"),a=i.value}else{i.hasAttribute("contenteditable")&&i.focus();var p=window.getSelection(),c=document.createRange();c.selectNodeContents(i),p.removeAllRanges(),p.addRange(c),a=p.toString()}return a}o.exports=n},279:function(o){function n(){}n.prototype={on:function(i,a,s){var p=this.e||(this.e={});return(p[i]||(p[i]=[])).push({fn:a,ctx:s}),this},once:function(i,a,s){var p=this;function c(){p.off(i,c),a.apply(s,arguments)}return c._=a,this.on(i,c,s)},emit:function(i){var a=[].slice.call(arguments,1),s=((this.e||(this.e={}))[i]||[]).slice(),p=0,c=s.length;for(p;p0&&i[i.length-1])&&(c[0]===6||c[0]===2)){r=0;continue}if(c[0]===3&&(!i||c[1]>i[0]&&c[1]=e.length&&(e=void 0),{value:e&&e[o++],done:!e}}};throw new TypeError(t?"Object is not iterable.":"Symbol.iterator is not defined.")}function N(e,t){var r=typeof Symbol=="function"&&e[Symbol.iterator];if(!r)return e;var o=r.call(e),n,i=[],a;try{for(;(t===void 0||t-- >0)&&!(n=o.next()).done;)i.push(n.value)}catch(s){a={error:s}}finally{try{n&&!n.done&&(r=o.return)&&r.call(o)}finally{if(a)throw a.error}}return i}function q(e,t,r){if(r||arguments.length===2)for(var o=0,n=t.length,i;o1||p(d,M)})},y&&(n[d]=y(n[d])))}function p(d,y){try{c(o[d](y))}catch(M){u(i[0][3],M)}}function c(d){d.value instanceof nt?Promise.resolve(d.value.v).then(l,f):u(i[0][2],d)}function l(d){p("next",d)}function f(d){p("throw",d)}function u(d,y){d(y),i.shift(),i.length&&p(i[0][0],i[0][1])}}function fo(e){if(!Symbol.asyncIterator)throw new TypeError("Symbol.asyncIterator is not defined.");var t=e[Symbol.asyncIterator],r;return t?t.call(e):(e=typeof he=="function"?he(e):e[Symbol.iterator](),r={},o("next"),o("throw"),o("return"),r[Symbol.asyncIterator]=function(){return this},r);function o(i){r[i]=e[i]&&function(a){return new Promise(function(s,p){a=e[i](a),n(s,p,a.done,a.value)})}}function n(i,a,s,p){Promise.resolve(p).then(function(c){i({value:c,done:s})},a)}}function H(e){return typeof e=="function"}function ut(e){var t=function(o){Error.call(o),o.stack=new Error().stack},r=e(t);return r.prototype=Object.create(Error.prototype),r.prototype.constructor=r,r}var zt=ut(function(e){return function(r){e(this),this.message=r?r.length+` errors occurred during unsubscription: -`+r.map(function(o,n){return n+1+") "+o.toString()}).join(` - `):"",this.name="UnsubscriptionError",this.errors=r}});function Qe(e,t){if(e){var r=e.indexOf(t);0<=r&&e.splice(r,1)}}var We=function(){function e(t){this.initialTeardown=t,this.closed=!1,this._parentage=null,this._finalizers=null}return e.prototype.unsubscribe=function(){var t,r,o,n,i;if(!this.closed){this.closed=!0;var a=this._parentage;if(a)if(this._parentage=null,Array.isArray(a))try{for(var s=he(a),p=s.next();!p.done;p=s.next()){var c=p.value;c.remove(this)}}catch(M){t={error:M}}finally{try{p&&!p.done&&(r=s.return)&&r.call(s)}finally{if(t)throw t.error}}else a.remove(this);var l=this.initialTeardown;if(H(l))try{l()}catch(M){i=M instanceof zt?M.errors:[M]}var f=this._finalizers;if(f){this._finalizers=null;try{for(var u=he(f),d=u.next();!d.done;d=u.next()){var y=d.value;try{uo(y)}catch(M){i=i!=null?i:[],M instanceof zt?i=q(q([],N(i)),N(M.errors)):i.push(M)}}}catch(M){o={error:M}}finally{try{d&&!d.done&&(n=u.return)&&n.call(u)}finally{if(o)throw o.error}}}if(i)throw new zt(i)}},e.prototype.add=function(t){var r;if(t&&t!==this)if(this.closed)uo(t);else{if(t instanceof e){if(t.closed||t._hasParent(this))return;t._addParent(this)}(this._finalizers=(r=this._finalizers)!==null&&r!==void 0?r:[]).push(t)}},e.prototype._hasParent=function(t){var r=this._parentage;return r===t||Array.isArray(r)&&r.includes(t)},e.prototype._addParent=function(t){var r=this._parentage;this._parentage=Array.isArray(r)?(r.push(t),r):r?[r,t]:t},e.prototype._removeParent=function(t){var r=this._parentage;r===t?this._parentage=null:Array.isArray(r)&&Qe(r,t)},e.prototype.remove=function(t){var r=this._finalizers;r&&Qe(r,t),t instanceof e&&t._removeParent(this)},e.EMPTY=function(){var t=new e;return t.closed=!0,t}(),e}();var Tr=We.EMPTY;function qt(e){return e instanceof We||e&&"closed"in e&&H(e.remove)&&H(e.add)&&H(e.unsubscribe)}function uo(e){H(e)?e():e.unsubscribe()}var Pe={onUnhandledError:null,onStoppedNotification:null,Promise:void 0,useDeprecatedSynchronousErrorHandling:!1,useDeprecatedNextContext:!1};var dt={setTimeout:function(e,t){for(var r=[],o=2;o0},enumerable:!1,configurable:!0}),t.prototype._trySubscribe=function(r){return this._throwIfClosed(),e.prototype._trySubscribe.call(this,r)},t.prototype._subscribe=function(r){return this._throwIfClosed(),this._checkFinalizedStatuses(r),this._innerSubscribe(r)},t.prototype._innerSubscribe=function(r){var o=this,n=this,i=n.hasError,a=n.isStopped,s=n.observers;return i||a?Tr:(this.currentObservers=null,s.push(r),new We(function(){o.currentObservers=null,Qe(s,r)}))},t.prototype._checkFinalizedStatuses=function(r){var o=this,n=o.hasError,i=o.thrownError,a=o.isStopped;n?r.error(i):a&&r.complete()},t.prototype.asObservable=function(){var r=new j;return r.source=this,r},t.create=function(r,o){return new wo(r,o)},t}(j);var wo=function(e){oe(t,e);function t(r,o){var n=e.call(this)||this;return n.destination=r,n.source=o,n}return t.prototype.next=function(r){var o,n;(n=(o=this.destination)===null||o===void 0?void 0:o.next)===null||n===void 0||n.call(o,r)},t.prototype.error=function(r){var o,n;(n=(o=this.destination)===null||o===void 0?void 0:o.error)===null||n===void 0||n.call(o,r)},t.prototype.complete=function(){var r,o;(o=(r=this.destination)===null||r===void 0?void 0:r.complete)===null||o===void 0||o.call(r)},t.prototype._subscribe=function(r){var o,n;return(n=(o=this.source)===null||o===void 0?void 0:o.subscribe(r))!==null&&n!==void 0?n:Tr},t}(g);var _r=function(e){oe(t,e);function t(r){var o=e.call(this)||this;return o._value=r,o}return Object.defineProperty(t.prototype,"value",{get:function(){return this.getValue()},enumerable:!1,configurable:!0}),t.prototype._subscribe=function(r){var o=e.prototype._subscribe.call(this,r);return!o.closed&&r.next(this._value),o},t.prototype.getValue=function(){var r=this,o=r.hasError,n=r.thrownError,i=r._value;if(o)throw n;return this._throwIfClosed(),i},t.prototype.next=function(r){e.prototype.next.call(this,this._value=r)},t}(g);var At={now:function(){return(At.delegate||Date).now()},delegate:void 0};var Ct=function(e){oe(t,e);function t(r,o,n){r===void 0&&(r=1/0),o===void 0&&(o=1/0),n===void 0&&(n=At);var i=e.call(this)||this;return i._bufferSize=r,i._windowTime=o,i._timestampProvider=n,i._buffer=[],i._infiniteTimeWindow=!0,i._infiniteTimeWindow=o===1/0,i._bufferSize=Math.max(1,r),i._windowTime=Math.max(1,o),i}return t.prototype.next=function(r){var o=this,n=o.isStopped,i=o._buffer,a=o._infiniteTimeWindow,s=o._timestampProvider,p=o._windowTime;n||(i.push(r),!a&&i.push(s.now()+p)),this._trimBuffer(),e.prototype.next.call(this,r)},t.prototype._subscribe=function(r){this._throwIfClosed(),this._trimBuffer();for(var o=this._innerSubscribe(r),n=this,i=n._infiniteTimeWindow,a=n._buffer,s=a.slice(),p=0;p0?e.prototype.schedule.call(this,r,o):(this.delay=o,this.state=r,this.scheduler.flush(this),this)},t.prototype.execute=function(r,o){return o>0||this.closed?e.prototype.execute.call(this,r,o):this._execute(r,o)},t.prototype.requestAsyncId=function(r,o,n){return n===void 0&&(n=0),n!=null&&n>0||n==null&&this.delay>0?e.prototype.requestAsyncId.call(this,r,o,n):(r.flush(this),0)},t}(gt);var Oo=function(e){oe(t,e);function t(){return e!==null&&e.apply(this,arguments)||this}return t}(yt);var kr=new Oo(So);var Mo=function(e){oe(t,e);function t(r,o){var n=e.call(this,r,o)||this;return n.scheduler=r,n.work=o,n}return t.prototype.requestAsyncId=function(r,o,n){return n===void 0&&(n=0),n!==null&&n>0?e.prototype.requestAsyncId.call(this,r,o,n):(r.actions.push(this),r._scheduled||(r._scheduled=vt.requestAnimationFrame(function(){return r.flush(void 0)})))},t.prototype.recycleAsyncId=function(r,o,n){var i;if(n===void 0&&(n=0),n!=null?n>0:this.delay>0)return e.prototype.recycleAsyncId.call(this,r,o,n);var a=r.actions;o!=null&&((i=a[a.length-1])===null||i===void 0?void 0:i.id)!==o&&(vt.cancelAnimationFrame(o),r._scheduled=void 0)},t}(gt);var Lo=function(e){oe(t,e);function t(){return e!==null&&e.apply(this,arguments)||this}return t.prototype.flush=function(r){this._active=!0;var o=this._scheduled;this._scheduled=void 0;var n=this.actions,i;r=r||n.shift();do if(i=r.execute(r.state,r.delay))break;while((r=n[0])&&r.id===o&&n.shift());if(this._active=!1,i){for(;(r=n[0])&&r.id===o&&n.shift();)r.unsubscribe();throw i}},t}(yt);var me=new Lo(Mo);var S=new j(function(e){return e.complete()});function Yt(e){return e&&H(e.schedule)}function Hr(e){return e[e.length-1]}function Xe(e){return H(Hr(e))?e.pop():void 0}function ke(e){return Yt(Hr(e))?e.pop():void 0}function Bt(e,t){return typeof Hr(e)=="number"?e.pop():t}var xt=function(e){return e&&typeof e.length=="number"&&typeof e!="function"};function Gt(e){return H(e==null?void 0:e.then)}function Jt(e){return H(e[bt])}function Xt(e){return Symbol.asyncIterator&&H(e==null?void 0:e[Symbol.asyncIterator])}function Zt(e){return new TypeError("You provided "+(e!==null&&typeof e=="object"?"an invalid object":"'"+e+"'")+" where a stream was expected. You can provide an Observable, Promise, ReadableStream, Array, AsyncIterable, or Iterable.")}function Ji(){return typeof Symbol!="function"||!Symbol.iterator?"@@iterator":Symbol.iterator}var er=Ji();function tr(e){return H(e==null?void 0:e[er])}function rr(e){return mo(this,arguments,function(){var r,o,n,i;return Nt(this,function(a){switch(a.label){case 0:r=e.getReader(),a.label=1;case 1:a.trys.push([1,,9,10]),a.label=2;case 2:return[4,nt(r.read())];case 3:return o=a.sent(),n=o.value,i=o.done,i?[4,nt(void 0)]:[3,5];case 4:return[2,a.sent()];case 5:return[4,nt(n)];case 6:return[4,a.sent()];case 7:return a.sent(),[3,2];case 8:return[3,10];case 9:return r.releaseLock(),[7];case 10:return[2]}})})}function or(e){return H(e==null?void 0:e.getReader)}function W(e){if(e instanceof j)return e;if(e!=null){if(Jt(e))return Xi(e);if(xt(e))return Zi(e);if(Gt(e))return ea(e);if(Xt(e))return _o(e);if(tr(e))return ta(e);if(or(e))return ra(e)}throw Zt(e)}function Xi(e){return new j(function(t){var r=e[bt]();if(H(r.subscribe))return r.subscribe(t);throw new TypeError("Provided object does not correctly implement Symbol.observable")})}function Zi(e){return new j(function(t){for(var r=0;r=2;return function(o){return o.pipe(e?b(function(n,i){return e(n,i,o)}):le,Te(1),r?De(t):qo(function(){return new ir}))}}function jr(e){return e<=0?function(){return S}:E(function(t,r){var o=[];t.subscribe(T(r,function(n){o.push(n),e=2,!0))}function pe(e){e===void 0&&(e={});var t=e.connector,r=t===void 0?function(){return new g}:t,o=e.resetOnError,n=o===void 0?!0:o,i=e.resetOnComplete,a=i===void 0?!0:i,s=e.resetOnRefCountZero,p=s===void 0?!0:s;return function(c){var l,f,u,d=0,y=!1,M=!1,X=function(){f==null||f.unsubscribe(),f=void 0},te=function(){X(),l=u=void 0,y=M=!1},J=function(){var k=l;te(),k==null||k.unsubscribe()};return E(function(k,ft){d++,!M&&!y&&X();var qe=u=u!=null?u:r();ft.add(function(){d--,d===0&&!M&&!y&&(f=Wr(J,p))}),qe.subscribe(ft),!l&&d>0&&(l=new at({next:function(Fe){return qe.next(Fe)},error:function(Fe){M=!0,X(),f=Wr(te,n,Fe),qe.error(Fe)},complete:function(){y=!0,X(),f=Wr(te,a),qe.complete()}}),W(k).subscribe(l))})(c)}}function Wr(e,t){for(var r=[],o=2;oe.next(document)),e}function P(e,t=document){return Array.from(t.querySelectorAll(e))}function R(e,t=document){let r=fe(e,t);if(typeof r=="undefined")throw new ReferenceError(`Missing element: expected "${e}" to be present`);return r}function fe(e,t=document){return t.querySelector(e)||void 0}function Ie(){var e,t,r,o;return(o=(r=(t=(e=document.activeElement)==null?void 0:e.shadowRoot)==null?void 0:t.activeElement)!=null?r:document.activeElement)!=null?o:void 0}var xa=O(h(document.body,"focusin"),h(document.body,"focusout")).pipe(_e(1),Q(void 0),m(()=>Ie()||document.body),G(1));function et(e){return xa.pipe(m(t=>e.contains(t)),K())}function $t(e,t){return C(()=>O(h(e,"mouseenter").pipe(m(()=>!0)),h(e,"mouseleave").pipe(m(()=>!1))).pipe(t?Ht(r=>Me(+!r*t)):le,Q(e.matches(":hover"))))}function Go(e,t){if(typeof t=="string"||typeof t=="number")e.innerHTML+=t.toString();else if(t instanceof Node)e.appendChild(t);else if(Array.isArray(t))for(let r of t)Go(e,r)}function x(e,t,...r){let o=document.createElement(e);if(t)for(let n of Object.keys(t))typeof t[n]!="undefined"&&(typeof t[n]!="boolean"?o.setAttribute(n,t[n]):o.setAttribute(n,""));for(let n of r)Go(o,n);return o}function sr(e){if(e>999){let t=+((e-950)%1e3>99);return`${((e+1e-6)/1e3).toFixed(t)}k`}else return e.toString()}function Tt(e){let t=x("script",{src:e});return C(()=>(document.head.appendChild(t),O(h(t,"load"),h(t,"error").pipe(v(()=>$r(()=>new ReferenceError(`Invalid script: ${e}`))))).pipe(m(()=>{}),_(()=>document.head.removeChild(t)),Te(1))))}var Jo=new g,Ea=C(()=>typeof ResizeObserver=="undefined"?Tt("https://unpkg.com/resize-observer-polyfill"):I(void 0)).pipe(m(()=>new ResizeObserver(e=>e.forEach(t=>Jo.next(t)))),v(e=>O(Ye,I(e)).pipe(_(()=>e.disconnect()))),G(1));function ce(e){return{width:e.offsetWidth,height:e.offsetHeight}}function ge(e){let t=e;for(;t.clientWidth===0&&t.parentElement;)t=t.parentElement;return Ea.pipe(w(r=>r.observe(t)),v(r=>Jo.pipe(b(o=>o.target===t),_(()=>r.unobserve(t)))),m(()=>ce(e)),Q(ce(e)))}function St(e){return{width:e.scrollWidth,height:e.scrollHeight}}function cr(e){let t=e.parentElement;for(;t&&(e.scrollWidth<=t.scrollWidth&&e.scrollHeight<=t.scrollHeight);)t=(e=t).parentElement;return t?e:void 0}function Xo(e){let t=[],r=e.parentElement;for(;r;)(e.clientWidth>r.clientWidth||e.clientHeight>r.clientHeight)&&t.push(r),r=(e=r).parentElement;return t.length===0&&t.push(document.documentElement),t}function Ve(e){return{x:e.offsetLeft,y:e.offsetTop}}function Zo(e){let t=e.getBoundingClientRect();return{x:t.x+window.scrollX,y:t.y+window.scrollY}}function en(e){return O(h(window,"load"),h(window,"resize")).pipe(Le(0,me),m(()=>Ve(e)),Q(Ve(e)))}function pr(e){return{x:e.scrollLeft,y:e.scrollTop}}function Ne(e){return O(h(e,"scroll"),h(window,"scroll"),h(window,"resize")).pipe(Le(0,me),m(()=>pr(e)),Q(pr(e)))}var tn=new g,wa=C(()=>I(new IntersectionObserver(e=>{for(let t of e)tn.next(t)},{threshold:0}))).pipe(v(e=>O(Ye,I(e)).pipe(_(()=>e.disconnect()))),G(1));function tt(e){return wa.pipe(w(t=>t.observe(e)),v(t=>tn.pipe(b(({target:r})=>r===e),_(()=>t.unobserve(e)),m(({isIntersecting:r})=>r))))}function rn(e,t=16){return Ne(e).pipe(m(({y:r})=>{let o=ce(e),n=St(e);return r>=n.height-o.height-t}),K())}var lr={drawer:R("[data-md-toggle=drawer]"),search:R("[data-md-toggle=search]")};function on(e){return lr[e].checked}function Je(e,t){lr[e].checked!==t&&lr[e].click()}function ze(e){let t=lr[e];return h(t,"change").pipe(m(()=>t.checked),Q(t.checked))}function Ta(e,t){switch(e.constructor){case HTMLInputElement:return e.type==="radio"?/^Arrow/.test(t):!0;case HTMLSelectElement:case HTMLTextAreaElement:return!0;default:return e.isContentEditable}}function Sa(){return O(h(window,"compositionstart").pipe(m(()=>!0)),h(window,"compositionend").pipe(m(()=>!1))).pipe(Q(!1))}function nn(){let e=h(window,"keydown").pipe(b(t=>!(t.metaKey||t.ctrlKey)),m(t=>({mode:on("search")?"search":"global",type:t.key,claim(){t.preventDefault(),t.stopPropagation()}})),b(({mode:t,type:r})=>{if(t==="global"){let o=Ie();if(typeof o!="undefined")return!Ta(o,r)}return!0}),pe());return Sa().pipe(v(t=>t?S:e))}function ye(){return new URL(location.href)}function lt(e,t=!1){if(B("navigation.instant")&&!t){let r=x("a",{href:e.href});document.body.appendChild(r),r.click(),r.remove()}else location.href=e.href}function an(){return new g}function sn(){return location.hash.slice(1)}function cn(e){let t=x("a",{href:e});t.addEventListener("click",r=>r.stopPropagation()),t.click()}function Oa(e){return O(h(window,"hashchange"),e).pipe(m(sn),Q(sn()),b(t=>t.length>0),G(1))}function pn(e){return Oa(e).pipe(m(t=>fe(`[id="${t}"]`)),b(t=>typeof t!="undefined"))}function Pt(e){let t=matchMedia(e);return ar(r=>t.addListener(()=>r(t.matches))).pipe(Q(t.matches))}function ln(){let e=matchMedia("print");return O(h(window,"beforeprint").pipe(m(()=>!0)),h(window,"afterprint").pipe(m(()=>!1))).pipe(Q(e.matches))}function Nr(e,t){return e.pipe(v(r=>r?t():S))}function zr(e,t){return new j(r=>{let o=new XMLHttpRequest;return o.open("GET",`${e}`),o.responseType="blob",o.addEventListener("load",()=>{o.status>=200&&o.status<300?(r.next(o.response),r.complete()):r.error(new Error(o.statusText))}),o.addEventListener("error",()=>{r.error(new Error("Network error"))}),o.addEventListener("abort",()=>{r.complete()}),typeof(t==null?void 0:t.progress$)!="undefined"&&(o.addEventListener("progress",n=>{var i;if(n.lengthComputable)t.progress$.next(n.loaded/n.total*100);else{let a=(i=o.getResponseHeader("Content-Length"))!=null?i:0;t.progress$.next(n.loaded/+a*100)}}),t.progress$.next(5)),o.send(),()=>o.abort()})}function je(e,t){return zr(e,t).pipe(v(r=>r.text()),m(r=>JSON.parse(r)),G(1))}function mn(e,t){let r=new DOMParser;return zr(e,t).pipe(v(o=>o.text()),m(o=>r.parseFromString(o,"text/html")),G(1))}function fn(e,t){let r=new DOMParser;return zr(e,t).pipe(v(o=>o.text()),m(o=>r.parseFromString(o,"text/xml")),G(1))}function un(){return{x:Math.max(0,scrollX),y:Math.max(0,scrollY)}}function dn(){return O(h(window,"scroll",{passive:!0}),h(window,"resize",{passive:!0})).pipe(m(un),Q(un()))}function hn(){return{width:innerWidth,height:innerHeight}}function bn(){return h(window,"resize",{passive:!0}).pipe(m(hn),Q(hn()))}function vn(){return z([dn(),bn()]).pipe(m(([e,t])=>({offset:e,size:t})),G(1))}function mr(e,{viewport$:t,header$:r}){let o=t.pipe(ee("size")),n=z([o,r]).pipe(m(()=>Ve(e)));return z([r,t,n]).pipe(m(([{height:i},{offset:a,size:s},{x:p,y:c}])=>({offset:{x:a.x-p,y:a.y-c+i},size:s})))}function Ma(e){return h(e,"message",t=>t.data)}function La(e){let t=new g;return t.subscribe(r=>e.postMessage(r)),t}function gn(e,t=new Worker(e)){let r=Ma(t),o=La(t),n=new g;n.subscribe(o);let i=o.pipe(Z(),ie(!0));return n.pipe(Z(),Re(r.pipe(U(i))),pe())}var _a=R("#__config"),Ot=JSON.parse(_a.textContent);Ot.base=`${new URL(Ot.base,ye())}`;function xe(){return Ot}function B(e){return Ot.features.includes(e)}function Ee(e,t){return typeof t!="undefined"?Ot.translations[e].replace("#",t.toString()):Ot.translations[e]}function Se(e,t=document){return R(`[data-md-component=${e}]`,t)}function ae(e,t=document){return P(`[data-md-component=${e}]`,t)}function Aa(e){let t=R(".md-typeset > :first-child",e);return h(t,"click",{once:!0}).pipe(m(()=>R(".md-typeset",e)),m(r=>({hash:__md_hash(r.innerHTML)})))}function yn(e){if(!B("announce.dismiss")||!e.childElementCount)return S;if(!e.hidden){let t=R(".md-typeset",e);__md_hash(t.innerHTML)===__md_get("__announce")&&(e.hidden=!0)}return C(()=>{let t=new g;return t.subscribe(({hash:r})=>{e.hidden=!0,__md_set("__announce",r)}),Aa(e).pipe(w(r=>t.next(r)),_(()=>t.complete()),m(r=>$({ref:e},r)))})}function Ca(e,{target$:t}){return t.pipe(m(r=>({hidden:r!==e})))}function xn(e,t){let r=new g;return r.subscribe(({hidden:o})=>{e.hidden=o}),Ca(e,t).pipe(w(o=>r.next(o)),_(()=>r.complete()),m(o=>$({ref:e},o)))}function Rt(e,t){return t==="inline"?x("div",{class:"md-tooltip md-tooltip--inline",id:e,role:"tooltip"},x("div",{class:"md-tooltip__inner md-typeset"})):x("div",{class:"md-tooltip",id:e,role:"tooltip"},x("div",{class:"md-tooltip__inner md-typeset"}))}function En(...e){return x("div",{class:"md-tooltip2",role:"tooltip"},x("div",{class:"md-tooltip2__inner md-typeset"},e))}function wn(e,t){if(t=t?`${t}_annotation_${e}`:void 0,t){let r=t?`#${t}`:void 0;return x("aside",{class:"md-annotation",tabIndex:0},Rt(t),x("a",{href:r,class:"md-annotation__index",tabIndex:-1},x("span",{"data-md-annotation-id":e})))}else return x("aside",{class:"md-annotation",tabIndex:0},Rt(t),x("span",{class:"md-annotation__index",tabIndex:-1},x("span",{"data-md-annotation-id":e})))}function Tn(e){return x("button",{class:"md-clipboard md-icon",title:Ee("clipboard.copy"),"data-clipboard-target":`#${e} > code`})}var On=Lt(qr());function Qr(e,t){let r=t&2,o=t&1,n=Object.keys(e.terms).filter(p=>!e.terms[p]).reduce((p,c)=>[...p,x("del",null,(0,On.default)(c))," "],[]).slice(0,-1),i=xe(),a=new URL(e.location,i.base);B("search.highlight")&&a.searchParams.set("h",Object.entries(e.terms).filter(([,p])=>p).reduce((p,[c])=>`${p} ${c}`.trim(),""));let{tags:s}=xe();return x("a",{href:`${a}`,class:"md-search-result__link",tabIndex:-1},x("article",{class:"md-search-result__article md-typeset","data-md-score":e.score.toFixed(2)},r>0&&x("div",{class:"md-search-result__icon md-icon"}),r>0&&x("h1",null,e.title),r<=0&&x("h2",null,e.title),o>0&&e.text.length>0&&e.text,e.tags&&e.tags.map(p=>{let c=s?p in s?`md-tag-icon md-tag--${s[p]}`:"md-tag-icon":"";return x("span",{class:`md-tag ${c}`},p)}),o>0&&n.length>0&&x("p",{class:"md-search-result__terms"},Ee("search.result.term.missing"),": ",...n)))}function Mn(e){let t=e[0].score,r=[...e],o=xe(),n=r.findIndex(l=>!`${new URL(l.location,o.base)}`.includes("#")),[i]=r.splice(n,1),a=r.findIndex(l=>l.scoreQr(l,1)),...p.length?[x("details",{class:"md-search-result__more"},x("summary",{tabIndex:-1},x("div",null,p.length>0&&p.length===1?Ee("search.result.more.one"):Ee("search.result.more.other",p.length))),...p.map(l=>Qr(l,1)))]:[]];return x("li",{class:"md-search-result__item"},c)}function Ln(e){return x("ul",{class:"md-source__facts"},Object.entries(e).map(([t,r])=>x("li",{class:`md-source__fact md-source__fact--${t}`},typeof r=="number"?sr(r):r)))}function Kr(e){let t=`tabbed-control tabbed-control--${e}`;return x("div",{class:t,hidden:!0},x("button",{class:"tabbed-button",tabIndex:-1,"aria-hidden":"true"}))}function _n(e){return x("div",{class:"md-typeset__scrollwrap"},x("div",{class:"md-typeset__table"},e))}function $a(e){var o;let t=xe(),r=new URL(`../${e.version}/`,t.base);return x("li",{class:"md-version__item"},x("a",{href:`${r}`,class:"md-version__link"},e.title,((o=t.version)==null?void 0:o.alias)&&e.aliases.length>0&&x("span",{class:"md-version__alias"},e.aliases[0])))}function An(e,t){var o;let r=xe();return e=e.filter(n=>{var i;return!((i=n.properties)!=null&&i.hidden)}),x("div",{class:"md-version"},x("button",{class:"md-version__current","aria-label":Ee("select.version")},t.title,((o=r.version)==null?void 0:o.alias)&&t.aliases.length>0&&x("span",{class:"md-version__alias"},t.aliases[0])),x("ul",{class:"md-version__list"},e.map($a)))}var Pa=0;function Ra(e){let t=z([et(e),$t(e)]).pipe(m(([o,n])=>o||n),K()),r=C(()=>Xo(e)).pipe(ne(Ne),pt(1),He(t),m(()=>Zo(e)));return t.pipe(Ae(o=>o),v(()=>z([t,r])),m(([o,n])=>({active:o,offset:n})),pe())}function Ia(e,t){let{content$:r,viewport$:o}=t,n=`__tooltip2_${Pa++}`;return C(()=>{let i=new g,a=new _r(!1);i.pipe(Z(),ie(!1)).subscribe(a);let s=a.pipe(Ht(c=>Me(+!c*250,kr)),K(),v(c=>c?r:S),w(c=>c.id=n),pe());z([i.pipe(m(({active:c})=>c)),s.pipe(v(c=>$t(c,250)),Q(!1))]).pipe(m(c=>c.some(l=>l))).subscribe(a);let p=a.pipe(b(c=>c),re(s,o),m(([c,l,{size:f}])=>{let u=e.getBoundingClientRect(),d=u.width/2;if(l.role==="tooltip")return{x:d,y:8+u.height};if(u.y>=f.height/2){let{height:y}=ce(l);return{x:d,y:-16-y}}else return{x:d,y:16+u.height}}));return z([s,i,p]).subscribe(([c,{offset:l},f])=>{c.style.setProperty("--md-tooltip-host-x",`${l.x}px`),c.style.setProperty("--md-tooltip-host-y",`${l.y}px`),c.style.setProperty("--md-tooltip-x",`${f.x}px`),c.style.setProperty("--md-tooltip-y",`${f.y}px`),c.classList.toggle("md-tooltip2--top",f.y<0),c.classList.toggle("md-tooltip2--bottom",f.y>=0)}),a.pipe(b(c=>c),re(s,(c,l)=>l),b(c=>c.role==="tooltip")).subscribe(c=>{let l=ce(R(":scope > *",c));c.style.setProperty("--md-tooltip-width",`${l.width}px`),c.style.setProperty("--md-tooltip-tail","0px")}),a.pipe(K(),ve(me),re(s)).subscribe(([c,l])=>{l.classList.toggle("md-tooltip2--active",c)}),z([a.pipe(b(c=>c)),s]).subscribe(([c,l])=>{l.role==="dialog"?(e.setAttribute("aria-controls",n),e.setAttribute("aria-haspopup","dialog")):e.setAttribute("aria-describedby",n)}),a.pipe(b(c=>!c)).subscribe(()=>{e.removeAttribute("aria-controls"),e.removeAttribute("aria-describedby"),e.removeAttribute("aria-haspopup")}),Ra(e).pipe(w(c=>i.next(c)),_(()=>i.complete()),m(c=>$({ref:e},c)))})}function mt(e,{viewport$:t},r=document.body){return Ia(e,{content$:new j(o=>{let n=e.title,i=En(n);return o.next(i),e.removeAttribute("title"),r.append(i),()=>{i.remove(),e.setAttribute("title",n)}}),viewport$:t})}function ja(e,t){let r=C(()=>z([en(e),Ne(t)])).pipe(m(([{x:o,y:n},i])=>{let{width:a,height:s}=ce(e);return{x:o-i.x+a/2,y:n-i.y+s/2}}));return et(e).pipe(v(o=>r.pipe(m(n=>({active:o,offset:n})),Te(+!o||1/0))))}function Cn(e,t,{target$:r}){let[o,n]=Array.from(e.children);return C(()=>{let i=new g,a=i.pipe(Z(),ie(!0));return i.subscribe({next({offset:s}){e.style.setProperty("--md-tooltip-x",`${s.x}px`),e.style.setProperty("--md-tooltip-y",`${s.y}px`)},complete(){e.style.removeProperty("--md-tooltip-x"),e.style.removeProperty("--md-tooltip-y")}}),tt(e).pipe(U(a)).subscribe(s=>{e.toggleAttribute("data-md-visible",s)}),O(i.pipe(b(({active:s})=>s)),i.pipe(_e(250),b(({active:s})=>!s))).subscribe({next({active:s}){s?e.prepend(o):o.remove()},complete(){e.prepend(o)}}),i.pipe(Le(16,me)).subscribe(({active:s})=>{o.classList.toggle("md-tooltip--active",s)}),i.pipe(pt(125,me),b(()=>!!e.offsetParent),m(()=>e.offsetParent.getBoundingClientRect()),m(({x:s})=>s)).subscribe({next(s){s?e.style.setProperty("--md-tooltip-0",`${-s}px`):e.style.removeProperty("--md-tooltip-0")},complete(){e.style.removeProperty("--md-tooltip-0")}}),h(n,"click").pipe(U(a),b(s=>!(s.metaKey||s.ctrlKey))).subscribe(s=>{s.stopPropagation(),s.preventDefault()}),h(n,"mousedown").pipe(U(a),re(i)).subscribe(([s,{active:p}])=>{var c;if(s.button!==0||s.metaKey||s.ctrlKey)s.preventDefault();else if(p){s.preventDefault();let l=e.parentElement.closest(".md-annotation");l instanceof HTMLElement?l.focus():(c=Ie())==null||c.blur()}}),r.pipe(U(a),b(s=>s===o),Ge(125)).subscribe(()=>e.focus()),ja(e,t).pipe(w(s=>i.next(s)),_(()=>i.complete()),m(s=>$({ref:e},s)))})}function Fa(e){return e.tagName==="CODE"?P(".c, .c1, .cm",e):[e]}function Wa(e){let t=[];for(let r of Fa(e)){let o=[],n=document.createNodeIterator(r,NodeFilter.SHOW_TEXT);for(let i=n.nextNode();i;i=n.nextNode())o.push(i);for(let i of o){let a;for(;a=/(\(\d+\))(!)?/.exec(i.textContent);){let[,s,p]=a;if(typeof p=="undefined"){let c=i.splitText(a.index);i=c.splitText(s.length),t.push(c)}else{i.textContent=s,t.push(i);break}}}}return t}function kn(e,t){t.append(...Array.from(e.childNodes))}function fr(e,t,{target$:r,print$:o}){let n=t.closest("[id]"),i=n==null?void 0:n.id,a=new Map;for(let s of Wa(t)){let[,p]=s.textContent.match(/\((\d+)\)/);fe(`:scope > li:nth-child(${p})`,e)&&(a.set(p,wn(p,i)),s.replaceWith(a.get(p)))}return a.size===0?S:C(()=>{let s=new g,p=s.pipe(Z(),ie(!0)),c=[];for(let[l,f]of a)c.push([R(".md-typeset",f),R(`:scope > li:nth-child(${l})`,e)]);return o.pipe(U(p)).subscribe(l=>{e.hidden=!l,e.classList.toggle("md-annotation-list",l);for(let[f,u]of c)l?kn(f,u):kn(u,f)}),O(...[...a].map(([,l])=>Cn(l,t,{target$:r}))).pipe(_(()=>s.complete()),pe())})}function Hn(e){if(e.nextElementSibling){let t=e.nextElementSibling;if(t.tagName==="OL")return t;if(t.tagName==="P"&&!t.children.length)return Hn(t)}}function $n(e,t){return C(()=>{let r=Hn(e);return typeof r!="undefined"?fr(r,e,t):S})}var Pn=Lt(Br());var Ua=0;function Rn(e){if(e.nextElementSibling){let t=e.nextElementSibling;if(t.tagName==="OL")return t;if(t.tagName==="P"&&!t.children.length)return Rn(t)}}function Da(e){return ge(e).pipe(m(({width:t})=>({scrollable:St(e).width>t})),ee("scrollable"))}function In(e,t){let{matches:r}=matchMedia("(hover)"),o=C(()=>{let n=new g,i=n.pipe(jr(1));n.subscribe(({scrollable:c})=>{c&&r?e.setAttribute("tabindex","0"):e.removeAttribute("tabindex")});let a=[];if(Pn.default.isSupported()&&(e.closest(".copy")||B("content.code.copy")&&!e.closest(".no-copy"))){let c=e.closest("pre");c.id=`__code_${Ua++}`;let l=Tn(c.id);c.insertBefore(l,e),B("content.tooltips")&&a.push(mt(l,{viewport$}))}let s=e.closest(".highlight");if(s instanceof HTMLElement){let c=Rn(s);if(typeof c!="undefined"&&(s.classList.contains("annotate")||B("content.code.annotate"))){let l=fr(c,e,t);a.push(ge(s).pipe(U(i),m(({width:f,height:u})=>f&&u),K(),v(f=>f?l:S)))}}return P(":scope > span[id]",e).length&&e.classList.add("md-code__content"),Da(e).pipe(w(c=>n.next(c)),_(()=>n.complete()),m(c=>$({ref:e},c)),Re(...a))});return B("content.lazy")?tt(e).pipe(b(n=>n),Te(1),v(()=>o)):o}function Va(e,{target$:t,print$:r}){let o=!0;return O(t.pipe(m(n=>n.closest("details:not([open])")),b(n=>e===n),m(()=>({action:"open",reveal:!0}))),r.pipe(b(n=>n||!o),w(()=>o=e.open),m(n=>({action:n?"open":"close"}))))}function jn(e,t){return C(()=>{let r=new g;return r.subscribe(({action:o,reveal:n})=>{e.toggleAttribute("open",o==="open"),n&&e.scrollIntoView()}),Va(e,t).pipe(w(o=>r.next(o)),_(()=>r.complete()),m(o=>$({ref:e},o)))})}var Fn=".node circle,.node ellipse,.node path,.node polygon,.node rect{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}marker{fill:var(--md-mermaid-edge-color)!important}.edgeLabel .label rect{fill:#0000}.label{color:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.label foreignObject{line-height:normal;overflow:visible}.label div .edgeLabel{color:var(--md-mermaid-label-fg-color)}.edgeLabel,.edgeLabel p,.label div .edgeLabel{background-color:var(--md-mermaid-label-bg-color)}.edgeLabel,.edgeLabel p{fill:var(--md-mermaid-label-bg-color);color:var(--md-mermaid-edge-color)}.edgePath .path,.flowchart-link{stroke:var(--md-mermaid-edge-color);stroke-width:.05rem}.edgePath .arrowheadPath{fill:var(--md-mermaid-edge-color);stroke:none}.cluster rect{fill:var(--md-default-fg-color--lightest);stroke:var(--md-default-fg-color--lighter)}.cluster span{color:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}g #flowchart-circleEnd,g #flowchart-circleStart,g #flowchart-crossEnd,g #flowchart-crossStart,g #flowchart-pointEnd,g #flowchart-pointStart{stroke:none}g.classGroup line,g.classGroup rect{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}g.classGroup text{fill:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.classLabel .box{fill:var(--md-mermaid-label-bg-color);background-color:var(--md-mermaid-label-bg-color);opacity:1}.classLabel .label{fill:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.node .divider{stroke:var(--md-mermaid-node-fg-color)}.relation{stroke:var(--md-mermaid-edge-color)}.cardinality{fill:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.cardinality text{fill:inherit!important}defs #classDiagram-compositionEnd,defs #classDiagram-compositionStart,defs #classDiagram-dependencyEnd,defs #classDiagram-dependencyStart,defs #classDiagram-extensionEnd,defs #classDiagram-extensionStart{fill:var(--md-mermaid-edge-color)!important;stroke:var(--md-mermaid-edge-color)!important}defs #classDiagram-aggregationEnd,defs #classDiagram-aggregationStart{fill:var(--md-mermaid-label-bg-color)!important;stroke:var(--md-mermaid-edge-color)!important}g.stateGroup rect{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}g.stateGroup .state-title{fill:var(--md-mermaid-label-fg-color)!important;font-family:var(--md-mermaid-font-family)}g.stateGroup .composit{fill:var(--md-mermaid-label-bg-color)}.nodeLabel,.nodeLabel p{color:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}a .nodeLabel{text-decoration:underline}.node circle.state-end,.node circle.state-start,.start-state{fill:var(--md-mermaid-edge-color);stroke:none}.end-state-inner,.end-state-outer{fill:var(--md-mermaid-edge-color)}.end-state-inner,.node circle.state-end{stroke:var(--md-mermaid-label-bg-color)}.transition{stroke:var(--md-mermaid-edge-color)}[id^=state-fork] rect,[id^=state-join] rect{fill:var(--md-mermaid-edge-color)!important;stroke:none!important}.statediagram-cluster.statediagram-cluster .inner{fill:var(--md-default-bg-color)}.statediagram-cluster rect{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}.statediagram-state rect.divider{fill:var(--md-default-fg-color--lightest);stroke:var(--md-default-fg-color--lighter)}defs #statediagram-barbEnd{stroke:var(--md-mermaid-edge-color)}.attributeBoxEven,.attributeBoxOdd{fill:var(--md-mermaid-node-bg-color);stroke:var(--md-mermaid-node-fg-color)}.entityBox{fill:var(--md-mermaid-label-bg-color);stroke:var(--md-mermaid-node-fg-color)}.entityLabel{fill:var(--md-mermaid-label-fg-color);font-family:var(--md-mermaid-font-family)}.relationshipLabelBox{fill:var(--md-mermaid-label-bg-color);fill-opacity:1;background-color:var(--md-mermaid-label-bg-color);opacity:1}.relationshipLabel{fill:var(--md-mermaid-label-fg-color)}.relationshipLine{stroke:var(--md-mermaid-edge-color)}defs #ONE_OR_MORE_END *,defs #ONE_OR_MORE_START *,defs #ONLY_ONE_END *,defs #ONLY_ONE_START *,defs #ZERO_OR_MORE_END *,defs #ZERO_OR_MORE_START *,defs #ZERO_OR_ONE_END *,defs #ZERO_OR_ONE_START *{stroke:var(--md-mermaid-edge-color)!important}defs #ZERO_OR_MORE_END circle,defs #ZERO_OR_MORE_START circle{fill:var(--md-mermaid-label-bg-color)}.actor{fill:var(--md-mermaid-sequence-actor-bg-color);stroke:var(--md-mermaid-sequence-actor-border-color)}text.actor>tspan{fill:var(--md-mermaid-sequence-actor-fg-color);font-family:var(--md-mermaid-font-family)}line{stroke:var(--md-mermaid-sequence-actor-line-color)}.actor-man circle,.actor-man line{fill:var(--md-mermaid-sequence-actorman-bg-color);stroke:var(--md-mermaid-sequence-actorman-line-color)}.messageLine0,.messageLine1{stroke:var(--md-mermaid-sequence-message-line-color)}.note{fill:var(--md-mermaid-sequence-note-bg-color);stroke:var(--md-mermaid-sequence-note-border-color)}.loopText,.loopText>tspan,.messageText,.noteText>tspan{stroke:none;font-family:var(--md-mermaid-font-family)!important}.messageText{fill:var(--md-mermaid-sequence-message-fg-color)}.loopText,.loopText>tspan{fill:var(--md-mermaid-sequence-loop-fg-color)}.noteText>tspan{fill:var(--md-mermaid-sequence-note-fg-color)}#arrowhead path{fill:var(--md-mermaid-sequence-message-line-color);stroke:none}.loopLine{fill:var(--md-mermaid-sequence-loop-bg-color);stroke:var(--md-mermaid-sequence-loop-border-color)}.labelBox{fill:var(--md-mermaid-sequence-label-bg-color);stroke:none}.labelText,.labelText>span{fill:var(--md-mermaid-sequence-label-fg-color);font-family:var(--md-mermaid-font-family)}.sequenceNumber{fill:var(--md-mermaid-sequence-number-fg-color)}rect.rect{fill:var(--md-mermaid-sequence-box-bg-color);stroke:none}rect.rect+text.text{fill:var(--md-mermaid-sequence-box-fg-color)}defs #sequencenumber{fill:var(--md-mermaid-sequence-number-bg-color)!important}";var Gr,za=0;function qa(){return typeof mermaid=="undefined"||mermaid instanceof Element?Tt("https://unpkg.com/mermaid@11/dist/mermaid.min.js"):I(void 0)}function Wn(e){return e.classList.remove("mermaid"),Gr||(Gr=qa().pipe(w(()=>mermaid.initialize({startOnLoad:!1,themeCSS:Fn,sequence:{actorFontSize:"16px",messageFontSize:"16px",noteFontSize:"16px"}})),m(()=>{}),G(1))),Gr.subscribe(()=>so(this,null,function*(){e.classList.add("mermaid");let t=`__mermaid_${za++}`,r=x("div",{class:"mermaid"}),o=e.textContent,{svg:n,fn:i}=yield mermaid.render(t,o),a=r.attachShadow({mode:"closed"});a.innerHTML=n,e.replaceWith(r),i==null||i(a)})),Gr.pipe(m(()=>({ref:e})))}var Un=x("table");function Dn(e){return e.replaceWith(Un),Un.replaceWith(_n(e)),I({ref:e})}function Qa(e){let t=e.find(r=>r.checked)||e[0];return O(...e.map(r=>h(r,"change").pipe(m(()=>R(`label[for="${r.id}"]`))))).pipe(Q(R(`label[for="${t.id}"]`)),m(r=>({active:r})))}function Vn(e,{viewport$:t,target$:r}){let o=R(".tabbed-labels",e),n=P(":scope > input",e),i=Kr("prev");e.append(i);let a=Kr("next");return e.append(a),C(()=>{let s=new g,p=s.pipe(Z(),ie(!0));z([s,ge(e),tt(e)]).pipe(U(p),Le(1,me)).subscribe({next([{active:c},l]){let f=Ve(c),{width:u}=ce(c);e.style.setProperty("--md-indicator-x",`${f.x}px`),e.style.setProperty("--md-indicator-width",`${u}px`);let d=pr(o);(f.xd.x+l.width)&&o.scrollTo({left:Math.max(0,f.x-16),behavior:"smooth"})},complete(){e.style.removeProperty("--md-indicator-x"),e.style.removeProperty("--md-indicator-width")}}),z([Ne(o),ge(o)]).pipe(U(p)).subscribe(([c,l])=>{let f=St(o);i.hidden=c.x<16,a.hidden=c.x>f.width-l.width-16}),O(h(i,"click").pipe(m(()=>-1)),h(a,"click").pipe(m(()=>1))).pipe(U(p)).subscribe(c=>{let{width:l}=ce(o);o.scrollBy({left:l*c,behavior:"smooth"})}),r.pipe(U(p),b(c=>n.includes(c))).subscribe(c=>c.click()),o.classList.add("tabbed-labels--linked");for(let c of n){let l=R(`label[for="${c.id}"]`);l.replaceChildren(x("a",{href:`#${l.htmlFor}`,tabIndex:-1},...Array.from(l.childNodes))),h(l.firstElementChild,"click").pipe(U(p),b(f=>!(f.metaKey||f.ctrlKey)),w(f=>{f.preventDefault(),f.stopPropagation()})).subscribe(()=>{history.replaceState({},"",`#${l.htmlFor}`),l.click()})}return B("content.tabs.link")&&s.pipe(Ce(1),re(t)).subscribe(([{active:c},{offset:l}])=>{let f=c.innerText.trim();if(c.hasAttribute("data-md-switching"))c.removeAttribute("data-md-switching");else{let u=e.offsetTop-l.y;for(let y of P("[data-tabs]"))for(let M of P(":scope > input",y)){let X=R(`label[for="${M.id}"]`);if(X!==c&&X.innerText.trim()===f){X.setAttribute("data-md-switching",""),M.click();break}}window.scrollTo({top:e.offsetTop-u});let d=__md_get("__tabs")||[];__md_set("__tabs",[...new Set([f,...d])])}}),s.pipe(U(p)).subscribe(()=>{for(let c of P("audio, video",e))c.pause()}),Qa(n).pipe(w(c=>s.next(c)),_(()=>s.complete()),m(c=>$({ref:e},c)))}).pipe(Ke(se))}function Nn(e,{viewport$:t,target$:r,print$:o}){return O(...P(".annotate:not(.highlight)",e).map(n=>$n(n,{target$:r,print$:o})),...P("pre:not(.mermaid) > code",e).map(n=>In(n,{target$:r,print$:o})),...P("pre.mermaid",e).map(n=>Wn(n)),...P("table:not([class])",e).map(n=>Dn(n)),...P("details",e).map(n=>jn(n,{target$:r,print$:o})),...P("[data-tabs]",e).map(n=>Vn(n,{viewport$:t,target$:r})),...P("[title]",e).filter(()=>B("content.tooltips")).map(n=>mt(n,{viewport$:t})))}function Ka(e,{alert$:t}){return t.pipe(v(r=>O(I(!0),I(!1).pipe(Ge(2e3))).pipe(m(o=>({message:r,active:o})))))}function zn(e,t){let r=R(".md-typeset",e);return C(()=>{let o=new g;return o.subscribe(({message:n,active:i})=>{e.classList.toggle("md-dialog--active",i),r.textContent=n}),Ka(e,t).pipe(w(n=>o.next(n)),_(()=>o.complete()),m(n=>$({ref:e},n)))})}var Ya=0;function Ba(e,t){document.body.append(e);let{width:r}=ce(e);e.style.setProperty("--md-tooltip-width",`${r}px`),e.remove();let o=cr(t),n=typeof o!="undefined"?Ne(o):I({x:0,y:0}),i=O(et(t),$t(t)).pipe(K());return z([i,n]).pipe(m(([a,s])=>{let{x:p,y:c}=Ve(t),l=ce(t),f=t.closest("table");return f&&t.parentElement&&(p+=f.offsetLeft+t.parentElement.offsetLeft,c+=f.offsetTop+t.parentElement.offsetTop),{active:a,offset:{x:p-s.x+l.width/2-r/2,y:c-s.y+l.height+8}}}))}function qn(e){let t=e.title;if(!t.length)return S;let r=`__tooltip_${Ya++}`,o=Rt(r,"inline"),n=R(".md-typeset",o);return n.innerHTML=t,C(()=>{let i=new g;return i.subscribe({next({offset:a}){o.style.setProperty("--md-tooltip-x",`${a.x}px`),o.style.setProperty("--md-tooltip-y",`${a.y}px`)},complete(){o.style.removeProperty("--md-tooltip-x"),o.style.removeProperty("--md-tooltip-y")}}),O(i.pipe(b(({active:a})=>a)),i.pipe(_e(250),b(({active:a})=>!a))).subscribe({next({active:a}){a?(e.insertAdjacentElement("afterend",o),e.setAttribute("aria-describedby",r),e.removeAttribute("title")):(o.remove(),e.removeAttribute("aria-describedby"),e.setAttribute("title",t))},complete(){o.remove(),e.removeAttribute("aria-describedby"),e.setAttribute("title",t)}}),i.pipe(Le(16,me)).subscribe(({active:a})=>{o.classList.toggle("md-tooltip--active",a)}),i.pipe(pt(125,me),b(()=>!!e.offsetParent),m(()=>e.offsetParent.getBoundingClientRect()),m(({x:a})=>a)).subscribe({next(a){a?o.style.setProperty("--md-tooltip-0",`${-a}px`):o.style.removeProperty("--md-tooltip-0")},complete(){o.style.removeProperty("--md-tooltip-0")}}),Ba(o,e).pipe(w(a=>i.next(a)),_(()=>i.complete()),m(a=>$({ref:e},a)))}).pipe(Ke(se))}function Ga({viewport$:e}){if(!B("header.autohide"))return I(!1);let t=e.pipe(m(({offset:{y:n}})=>n),Be(2,1),m(([n,i])=>[nMath.abs(i-n.y)>100),m(([,[n]])=>n),K()),o=ze("search");return z([e,o]).pipe(m(([{offset:n},i])=>n.y>400&&!i),K(),v(n=>n?r:I(!1)),Q(!1))}function Qn(e,t){return C(()=>z([ge(e),Ga(t)])).pipe(m(([{height:r},o])=>({height:r,hidden:o})),K((r,o)=>r.height===o.height&&r.hidden===o.hidden),G(1))}function Kn(e,{header$:t,main$:r}){return C(()=>{let o=new g,n=o.pipe(Z(),ie(!0));o.pipe(ee("active"),He(t)).subscribe(([{active:a},{hidden:s}])=>{e.classList.toggle("md-header--shadow",a&&!s),e.hidden=s});let i=ue(P("[title]",e)).pipe(b(()=>B("content.tooltips")),ne(a=>qn(a)));return r.subscribe(o),t.pipe(U(n),m(a=>$({ref:e},a)),Re(i.pipe(U(n))))})}function Ja(e,{viewport$:t,header$:r}){return mr(e,{viewport$:t,header$:r}).pipe(m(({offset:{y:o}})=>{let{height:n}=ce(e);return{active:o>=n}}),ee("active"))}function Yn(e,t){return C(()=>{let r=new g;r.subscribe({next({active:n}){e.classList.toggle("md-header__title--active",n)},complete(){e.classList.remove("md-header__title--active")}});let o=fe(".md-content h1");return typeof o=="undefined"?S:Ja(o,t).pipe(w(n=>r.next(n)),_(()=>r.complete()),m(n=>$({ref:e},n)))})}function Bn(e,{viewport$:t,header$:r}){let o=r.pipe(m(({height:i})=>i),K()),n=o.pipe(v(()=>ge(e).pipe(m(({height:i})=>({top:e.offsetTop,bottom:e.offsetTop+i})),ee("bottom"))));return z([o,n,t]).pipe(m(([i,{top:a,bottom:s},{offset:{y:p},size:{height:c}}])=>(c=Math.max(0,c-Math.max(0,a-p,i)-Math.max(0,c+p-s)),{offset:a-i,height:c,active:a-i<=p})),K((i,a)=>i.offset===a.offset&&i.height===a.height&&i.active===a.active))}function Xa(e){let t=__md_get("__palette")||{index:e.findIndex(o=>matchMedia(o.getAttribute("data-md-color-media")).matches)},r=Math.max(0,Math.min(t.index,e.length-1));return I(...e).pipe(ne(o=>h(o,"change").pipe(m(()=>o))),Q(e[r]),m(o=>({index:e.indexOf(o),color:{media:o.getAttribute("data-md-color-media"),scheme:o.getAttribute("data-md-color-scheme"),primary:o.getAttribute("data-md-color-primary"),accent:o.getAttribute("data-md-color-accent")}})),G(1))}function Gn(e){let t=P("input",e),r=x("meta",{name:"theme-color"});document.head.appendChild(r);let o=x("meta",{name:"color-scheme"});document.head.appendChild(o);let n=Pt("(prefers-color-scheme: light)");return C(()=>{let i=new g;return i.subscribe(a=>{if(document.body.setAttribute("data-md-color-switching",""),a.color.media==="(prefers-color-scheme)"){let s=matchMedia("(prefers-color-scheme: light)"),p=document.querySelector(s.matches?"[data-md-color-media='(prefers-color-scheme: light)']":"[data-md-color-media='(prefers-color-scheme: dark)']");a.color.scheme=p.getAttribute("data-md-color-scheme"),a.color.primary=p.getAttribute("data-md-color-primary"),a.color.accent=p.getAttribute("data-md-color-accent")}for(let[s,p]of Object.entries(a.color))document.body.setAttribute(`data-md-color-${s}`,p);for(let s=0;sa.key==="Enter"),re(i,(a,s)=>s)).subscribe(({index:a})=>{a=(a+1)%t.length,t[a].click(),t[a].focus()}),i.pipe(m(()=>{let a=Se("header"),s=window.getComputedStyle(a);return o.content=s.colorScheme,s.backgroundColor.match(/\d+/g).map(p=>(+p).toString(16).padStart(2,"0")).join("")})).subscribe(a=>r.content=`#${a}`),i.pipe(ve(se)).subscribe(()=>{document.body.removeAttribute("data-md-color-switching")}),Xa(t).pipe(U(n.pipe(Ce(1))),ct(),w(a=>i.next(a)),_(()=>i.complete()),m(a=>$({ref:e},a)))})}function Jn(e,{progress$:t}){return C(()=>{let r=new g;return r.subscribe(({value:o})=>{e.style.setProperty("--md-progress-value",`${o}`)}),t.pipe(w(o=>r.next({value:o})),_(()=>r.complete()),m(o=>({ref:e,value:o})))})}var Jr=Lt(Br());function Za(e){e.setAttribute("data-md-copying","");let t=e.closest("[data-copy]"),r=t?t.getAttribute("data-copy"):e.innerText;return e.removeAttribute("data-md-copying"),r.trimEnd()}function Xn({alert$:e}){Jr.default.isSupported()&&new j(t=>{new Jr.default("[data-clipboard-target], [data-clipboard-text]",{text:r=>r.getAttribute("data-clipboard-text")||Za(R(r.getAttribute("data-clipboard-target")))}).on("success",r=>t.next(r))}).pipe(w(t=>{t.trigger.focus()}),m(()=>Ee("clipboard.copied"))).subscribe(e)}function Zn(e,t){return e.protocol=t.protocol,e.hostname=t.hostname,e}function es(e,t){let r=new Map;for(let o of P("url",e)){let n=R("loc",o),i=[Zn(new URL(n.textContent),t)];r.set(`${i[0]}`,i);for(let a of P("[rel=alternate]",o)){let s=a.getAttribute("href");s!=null&&i.push(Zn(new URL(s),t))}}return r}function ur(e){return fn(new URL("sitemap.xml",e)).pipe(m(t=>es(t,new URL(e))),de(()=>I(new Map)))}function ts(e,t){if(!(e.target instanceof Element))return S;let r=e.target.closest("a");if(r===null)return S;if(r.target||e.metaKey||e.ctrlKey)return S;let o=new URL(r.href);return o.search=o.hash="",t.has(`${o}`)?(e.preventDefault(),I(new URL(r.href))):S}function ei(e){let t=new Map;for(let r of P(":scope > *",e.head))t.set(r.outerHTML,r);return t}function ti(e){for(let t of P("[href], [src]",e))for(let r of["href","src"]){let o=t.getAttribute(r);if(o&&!/^(?:[a-z]+:)?\/\//i.test(o)){t[r]=t[r];break}}return I(e)}function rs(e){for(let o of["[data-md-component=announce]","[data-md-component=container]","[data-md-component=header-topic]","[data-md-component=outdated]","[data-md-component=logo]","[data-md-component=skip]",...B("navigation.tabs.sticky")?["[data-md-component=tabs]"]:[]]){let n=fe(o),i=fe(o,e);typeof n!="undefined"&&typeof i!="undefined"&&n.replaceWith(i)}let t=ei(document);for(let[o,n]of ei(e))t.has(o)?t.delete(o):document.head.appendChild(n);for(let o of t.values()){let n=o.getAttribute("name");n!=="theme-color"&&n!=="color-scheme"&&o.remove()}let r=Se("container");return Ue(P("script",r)).pipe(v(o=>{let n=e.createElement("script");if(o.src){for(let i of o.getAttributeNames())n.setAttribute(i,o.getAttribute(i));return o.replaceWith(n),new j(i=>{n.onload=()=>i.complete()})}else return n.textContent=o.textContent,o.replaceWith(n),S}),Z(),ie(document))}function ri({location$:e,viewport$:t,progress$:r}){let o=xe();if(location.protocol==="file:")return S;let n=ur(o.base);I(document).subscribe(ti);let i=h(document.body,"click").pipe(He(n),v(([p,c])=>ts(p,c)),pe()),a=h(window,"popstate").pipe(m(ye),pe());i.pipe(re(t)).subscribe(([p,{offset:c}])=>{history.replaceState(c,""),history.pushState(null,"",p)}),O(i,a).subscribe(e);let s=e.pipe(ee("pathname"),v(p=>mn(p,{progress$:r}).pipe(de(()=>(lt(p,!0),S)))),v(ti),v(rs),pe());return O(s.pipe(re(e,(p,c)=>c)),s.pipe(v(()=>e),ee("pathname"),v(()=>e),ee("hash")),e.pipe(K((p,c)=>p.pathname===c.pathname&&p.hash===c.hash),v(()=>i),w(()=>history.back()))).subscribe(p=>{var c,l;history.state!==null||!p.hash?window.scrollTo(0,(l=(c=history.state)==null?void 0:c.y)!=null?l:0):(history.scrollRestoration="auto",cn(p.hash),history.scrollRestoration="manual")}),e.subscribe(()=>{history.scrollRestoration="manual"}),h(window,"beforeunload").subscribe(()=>{history.scrollRestoration="auto"}),t.pipe(ee("offset"),_e(100)).subscribe(({offset:p})=>{history.replaceState(p,"")}),s}var oi=Lt(qr());function ni(e){let t=e.separator.split("|").map(n=>n.replace(/(\(\?[!=<][^)]+\))/g,"").length===0?"\uFFFD":n).join("|"),r=new RegExp(t,"img"),o=(n,i,a)=>`${i}${a}`;return n=>{n=n.replace(/[\s*+\-:~^]+/g," ").trim();let i=new RegExp(`(^|${e.separator}|)(${n.replace(/[|\\{}()[\]^$+*?.-]/g,"\\$&").replace(r,"|")})`,"img");return a=>(0,oi.default)(a).replace(i,o).replace(/<\/mark>(\s+)]*>/img,"$1")}}function jt(e){return e.type===1}function dr(e){return e.type===3}function ii(e,t){let r=gn(e);return O(I(location.protocol!=="file:"),ze("search")).pipe(Ae(o=>o),v(()=>t)).subscribe(({config:o,docs:n})=>r.next({type:0,data:{config:o,docs:n,options:{suggest:B("search.suggest")}}})),r}function ai({document$:e}){let t=xe(),r=je(new URL("../versions.json",t.base)).pipe(de(()=>S)),o=r.pipe(m(n=>{let[,i]=t.base.match(/([^/]+)\/?$/);return n.find(({version:a,aliases:s})=>a===i||s.includes(i))||n[0]}));r.pipe(m(n=>new Map(n.map(i=>[`${new URL(`../${i.version}/`,t.base)}`,i]))),v(n=>h(document.body,"click").pipe(b(i=>!i.metaKey&&!i.ctrlKey),re(o),v(([i,a])=>{if(i.target instanceof Element){let s=i.target.closest("a");if(s&&!s.target&&n.has(s.href)){let p=s.href;return!i.target.closest(".md-version")&&n.get(p)===a?S:(i.preventDefault(),I(p))}}return S}),v(i=>ur(new URL(i)).pipe(m(a=>{let p=ye().href.replace(t.base,i);return a.has(p.split("#")[0])?new URL(p):new URL(i)})))))).subscribe(n=>lt(n,!0)),z([r,o]).subscribe(([n,i])=>{R(".md-header__topic").appendChild(An(n,i))}),e.pipe(v(()=>o)).subscribe(n=>{var a;let i=__md_get("__outdated",sessionStorage);if(i===null){i=!0;let s=((a=t.version)==null?void 0:a.default)||"latest";Array.isArray(s)||(s=[s]);e:for(let p of s)for(let c of n.aliases.concat(n.version))if(new RegExp(p,"i").test(c)){i=!1;break e}__md_set("__outdated",i,sessionStorage)}if(i)for(let s of ae("outdated"))s.hidden=!1})}function is(e,{worker$:t}){let{searchParams:r}=ye();r.has("q")&&(Je("search",!0),e.value=r.get("q"),e.focus(),ze("search").pipe(Ae(i=>!i)).subscribe(()=>{let i=ye();i.searchParams.delete("q"),history.replaceState({},"",`${i}`)}));let o=et(e),n=O(t.pipe(Ae(jt)),h(e,"keyup"),o).pipe(m(()=>e.value),K());return z([n,o]).pipe(m(([i,a])=>({value:i,focus:a})),G(1))}function si(e,{worker$:t}){let r=new g,o=r.pipe(Z(),ie(!0));z([t.pipe(Ae(jt)),r],(i,a)=>a).pipe(ee("value")).subscribe(({value:i})=>t.next({type:2,data:i})),r.pipe(ee("focus")).subscribe(({focus:i})=>{i&&Je("search",i)}),h(e.form,"reset").pipe(U(o)).subscribe(()=>e.focus());let n=R("header [for=__search]");return h(n,"click").subscribe(()=>e.focus()),is(e,{worker$:t}).pipe(w(i=>r.next(i)),_(()=>r.complete()),m(i=>$({ref:e},i)),G(1))}function ci(e,{worker$:t,query$:r}){let o=new g,n=rn(e.parentElement).pipe(b(Boolean)),i=e.parentElement,a=R(":scope > :first-child",e),s=R(":scope > :last-child",e);ze("search").subscribe(l=>s.setAttribute("role",l?"list":"presentation")),o.pipe(re(r),Ur(t.pipe(Ae(jt)))).subscribe(([{items:l},{value:f}])=>{switch(l.length){case 0:a.textContent=f.length?Ee("search.result.none"):Ee("search.result.placeholder");break;case 1:a.textContent=Ee("search.result.one");break;default:let u=sr(l.length);a.textContent=Ee("search.result.other",u)}});let p=o.pipe(w(()=>s.innerHTML=""),v(({items:l})=>O(I(...l.slice(0,10)),I(...l.slice(10)).pipe(Be(4),Vr(n),v(([f])=>f)))),m(Mn),pe());return p.subscribe(l=>s.appendChild(l)),p.pipe(ne(l=>{let f=fe("details",l);return typeof f=="undefined"?S:h(f,"toggle").pipe(U(o),m(()=>f))})).subscribe(l=>{l.open===!1&&l.offsetTop<=i.scrollTop&&i.scrollTo({top:l.offsetTop})}),t.pipe(b(dr),m(({data:l})=>l)).pipe(w(l=>o.next(l)),_(()=>o.complete()),m(l=>$({ref:e},l)))}function as(e,{query$:t}){return t.pipe(m(({value:r})=>{let o=ye();return o.hash="",r=r.replace(/\s+/g,"+").replace(/&/g,"%26").replace(/=/g,"%3D"),o.search=`q=${r}`,{url:o}}))}function pi(e,t){let r=new g,o=r.pipe(Z(),ie(!0));return r.subscribe(({url:n})=>{e.setAttribute("data-clipboard-text",e.href),e.href=`${n}`}),h(e,"click").pipe(U(o)).subscribe(n=>n.preventDefault()),as(e,t).pipe(w(n=>r.next(n)),_(()=>r.complete()),m(n=>$({ref:e},n)))}function li(e,{worker$:t,keyboard$:r}){let o=new g,n=Se("search-query"),i=O(h(n,"keydown"),h(n,"focus")).pipe(ve(se),m(()=>n.value),K());return o.pipe(He(i),m(([{suggest:s},p])=>{let c=p.split(/([\s-]+)/);if(s!=null&&s.length&&c[c.length-1]){let l=s[s.length-1];l.startsWith(c[c.length-1])&&(c[c.length-1]=l)}else c.length=0;return c})).subscribe(s=>e.innerHTML=s.join("").replace(/\s/g," ")),r.pipe(b(({mode:s})=>s==="search")).subscribe(s=>{switch(s.type){case"ArrowRight":e.innerText.length&&n.selectionStart===n.value.length&&(n.value=e.innerText);break}}),t.pipe(b(dr),m(({data:s})=>s)).pipe(w(s=>o.next(s)),_(()=>o.complete()),m(()=>({ref:e})))}function mi(e,{index$:t,keyboard$:r}){let o=xe();try{let n=ii(o.search,t),i=Se("search-query",e),a=Se("search-result",e);h(e,"click").pipe(b(({target:p})=>p instanceof Element&&!!p.closest("a"))).subscribe(()=>Je("search",!1)),r.pipe(b(({mode:p})=>p==="search")).subscribe(p=>{let c=Ie();switch(p.type){case"Enter":if(c===i){let l=new Map;for(let f of P(":first-child [href]",a)){let u=f.firstElementChild;l.set(f,parseFloat(u.getAttribute("data-md-score")))}if(l.size){let[[f]]=[...l].sort(([,u],[,d])=>d-u);f.click()}p.claim()}break;case"Escape":case"Tab":Je("search",!1),i.blur();break;case"ArrowUp":case"ArrowDown":if(typeof c=="undefined")i.focus();else{let l=[i,...P(":not(details) > [href], summary, details[open] [href]",a)],f=Math.max(0,(Math.max(0,l.indexOf(c))+l.length+(p.type==="ArrowUp"?-1:1))%l.length);l[f].focus()}p.claim();break;default:i!==Ie()&&i.focus()}}),r.pipe(b(({mode:p})=>p==="global")).subscribe(p=>{switch(p.type){case"f":case"s":case"/":i.focus(),i.select(),p.claim();break}});let s=si(i,{worker$:n});return O(s,ci(a,{worker$:n,query$:s})).pipe(Re(...ae("search-share",e).map(p=>pi(p,{query$:s})),...ae("search-suggest",e).map(p=>li(p,{worker$:n,keyboard$:r}))))}catch(n){return e.hidden=!0,Ye}}function fi(e,{index$:t,location$:r}){return z([t,r.pipe(Q(ye()),b(o=>!!o.searchParams.get("h")))]).pipe(m(([o,n])=>ni(o.config)(n.searchParams.get("h"))),m(o=>{var a;let n=new Map,i=document.createNodeIterator(e,NodeFilter.SHOW_TEXT);for(let s=i.nextNode();s;s=i.nextNode())if((a=s.parentElement)!=null&&a.offsetHeight){let p=s.textContent,c=o(p);c.length>p.length&&n.set(s,c)}for(let[s,p]of n){let{childNodes:c}=x("span",null,p);s.replaceWith(...Array.from(c))}return{ref:e,nodes:n}}))}function ss(e,{viewport$:t,main$:r}){let o=e.closest(".md-grid"),n=o.offsetTop-o.parentElement.offsetTop;return z([r,t]).pipe(m(([{offset:i,height:a},{offset:{y:s}}])=>(a=a+Math.min(n,Math.max(0,s-i))-n,{height:a,locked:s>=i+n})),K((i,a)=>i.height===a.height&&i.locked===a.locked))}function Xr(e,o){var n=o,{header$:t}=n,r=ao(n,["header$"]);let i=R(".md-sidebar__scrollwrap",e),{y:a}=Ve(i);return C(()=>{let s=new g,p=s.pipe(Z(),ie(!0)),c=s.pipe(Le(0,me));return c.pipe(re(t)).subscribe({next([{height:l},{height:f}]){i.style.height=`${l-2*a}px`,e.style.top=`${f}px`},complete(){i.style.height="",e.style.top=""}}),c.pipe(Ae()).subscribe(()=>{for(let l of P(".md-nav__link--active[href]",e)){if(!l.clientHeight)continue;let f=l.closest(".md-sidebar__scrollwrap");if(typeof f!="undefined"){let u=l.offsetTop-f.offsetTop,{height:d}=ce(f);f.scrollTo({top:u-d/2})}}}),ue(P("label[tabindex]",e)).pipe(ne(l=>h(l,"click").pipe(ve(se),m(()=>l),U(p)))).subscribe(l=>{let f=R(`[id="${l.htmlFor}"]`);R(`[aria-labelledby="${l.id}"]`).setAttribute("aria-expanded",`${f.checked}`)}),ss(e,r).pipe(w(l=>s.next(l)),_(()=>s.complete()),m(l=>$({ref:e},l)))})}function ui(e,t){if(typeof t!="undefined"){let r=`https://api.github.com/repos/${e}/${t}`;return st(je(`${r}/releases/latest`).pipe(de(()=>S),m(o=>({version:o.tag_name})),De({})),je(r).pipe(de(()=>S),m(o=>({stars:o.stargazers_count,forks:o.forks_count})),De({}))).pipe(m(([o,n])=>$($({},o),n)))}else{let r=`https://api.github.com/users/${e}`;return je(r).pipe(m(o=>({repositories:o.public_repos})),De({}))}}function di(e,t){let r=`https://${e}/api/v4/projects/${encodeURIComponent(t)}`;return st(je(`${r}/releases/permalink/latest`).pipe(de(()=>S),m(({tag_name:o})=>({version:o})),De({})),je(r).pipe(de(()=>S),m(({star_count:o,forks_count:n})=>({stars:o,forks:n})),De({}))).pipe(m(([o,n])=>$($({},o),n)))}function hi(e){let t=e.match(/^.+github\.com\/([^/]+)\/?([^/]+)?/i);if(t){let[,r,o]=t;return ui(r,o)}if(t=e.match(/^.+?([^/]*gitlab[^/]+)\/(.+?)\/?$/i),t){let[,r,o]=t;return di(r,o)}return S}var cs;function ps(e){return cs||(cs=C(()=>{let t=__md_get("__source",sessionStorage);if(t)return I(t);if(ae("consent").length){let o=__md_get("__consent");if(!(o&&o.github))return S}return hi(e.href).pipe(w(o=>__md_set("__source",o,sessionStorage)))}).pipe(de(()=>S),b(t=>Object.keys(t).length>0),m(t=>({facts:t})),G(1)))}function bi(e){let t=R(":scope > :last-child",e);return C(()=>{let r=new g;return r.subscribe(({facts:o})=>{t.appendChild(Ln(o)),t.classList.add("md-source__repository--active")}),ps(e).pipe(w(o=>r.next(o)),_(()=>r.complete()),m(o=>$({ref:e},o)))})}function ls(e,{viewport$:t,header$:r}){return ge(document.body).pipe(v(()=>mr(e,{header$:r,viewport$:t})),m(({offset:{y:o}})=>({hidden:o>=10})),ee("hidden"))}function vi(e,t){return C(()=>{let r=new g;return r.subscribe({next({hidden:o}){e.hidden=o},complete(){e.hidden=!1}}),(B("navigation.tabs.sticky")?I({hidden:!1}):ls(e,t)).pipe(w(o=>r.next(o)),_(()=>r.complete()),m(o=>$({ref:e},o)))})}function ms(e,{viewport$:t,header$:r}){let o=new Map,n=P(".md-nav__link",e);for(let s of n){let p=decodeURIComponent(s.hash.substring(1)),c=fe(`[id="${p}"]`);typeof c!="undefined"&&o.set(s,c)}let i=r.pipe(ee("height"),m(({height:s})=>{let p=Se("main"),c=R(":scope > :first-child",p);return s+.8*(c.offsetTop-p.offsetTop)}),pe());return ge(document.body).pipe(ee("height"),v(s=>C(()=>{let p=[];return I([...o].reduce((c,[l,f])=>{for(;p.length&&o.get(p[p.length-1]).tagName>=f.tagName;)p.pop();let u=f.offsetTop;for(;!u&&f.parentElement;)f=f.parentElement,u=f.offsetTop;let d=f.offsetParent;for(;d;d=d.offsetParent)u+=d.offsetTop;return c.set([...p=[...p,l]].reverse(),u)},new Map))}).pipe(m(p=>new Map([...p].sort(([,c],[,l])=>c-l))),He(i),v(([p,c])=>t.pipe(Fr(([l,f],{offset:{y:u},size:d})=>{let y=u+d.height>=Math.floor(s.height);for(;f.length;){let[,M]=f[0];if(M-c=u&&!y)f=[l.pop(),...f];else break}return[l,f]},[[],[...p]]),K((l,f)=>l[0]===f[0]&&l[1]===f[1])))))).pipe(m(([s,p])=>({prev:s.map(([c])=>c),next:p.map(([c])=>c)})),Q({prev:[],next:[]}),Be(2,1),m(([s,p])=>s.prev.length{let i=new g,a=i.pipe(Z(),ie(!0));if(i.subscribe(({prev:s,next:p})=>{for(let[c]of p)c.classList.remove("md-nav__link--passed"),c.classList.remove("md-nav__link--active");for(let[c,[l]]of s.entries())l.classList.add("md-nav__link--passed"),l.classList.toggle("md-nav__link--active",c===s.length-1)}),B("toc.follow")){let s=O(t.pipe(_e(1),m(()=>{})),t.pipe(_e(250),m(()=>"smooth")));i.pipe(b(({prev:p})=>p.length>0),He(o.pipe(ve(se))),re(s)).subscribe(([[{prev:p}],c])=>{let[l]=p[p.length-1];if(l.offsetHeight){let f=cr(l);if(typeof f!="undefined"){let u=l.offsetTop-f.offsetTop,{height:d}=ce(f);f.scrollTo({top:u-d/2,behavior:c})}}})}return B("navigation.tracking")&&t.pipe(U(a),ee("offset"),_e(250),Ce(1),U(n.pipe(Ce(1))),ct({delay:250}),re(i)).subscribe(([,{prev:s}])=>{let p=ye(),c=s[s.length-1];if(c&&c.length){let[l]=c,{hash:f}=new URL(l.href);p.hash!==f&&(p.hash=f,history.replaceState({},"",`${p}`))}else p.hash="",history.replaceState({},"",`${p}`)}),ms(e,{viewport$:t,header$:r}).pipe(w(s=>i.next(s)),_(()=>i.complete()),m(s=>$({ref:e},s)))})}function fs(e,{viewport$:t,main$:r,target$:o}){let n=t.pipe(m(({offset:{y:a}})=>a),Be(2,1),m(([a,s])=>a>s&&s>0),K()),i=r.pipe(m(({active:a})=>a));return z([i,n]).pipe(m(([a,s])=>!(a&&s)),K(),U(o.pipe(Ce(1))),ie(!0),ct({delay:250}),m(a=>({hidden:a})))}function yi(e,{viewport$:t,header$:r,main$:o,target$:n}){let i=new g,a=i.pipe(Z(),ie(!0));return i.subscribe({next({hidden:s}){e.hidden=s,s?(e.setAttribute("tabindex","-1"),e.blur()):e.removeAttribute("tabindex")},complete(){e.style.top="",e.hidden=!0,e.removeAttribute("tabindex")}}),r.pipe(U(a),ee("height")).subscribe(({height:s})=>{e.style.top=`${s+16}px`}),h(e,"click").subscribe(s=>{s.preventDefault(),window.scrollTo({top:0})}),fs(e,{viewport$:t,main$:o,target$:n}).pipe(w(s=>i.next(s)),_(()=>i.complete()),m(s=>$({ref:e},s)))}function xi({document$:e,viewport$:t}){e.pipe(v(()=>P(".md-ellipsis")),ne(r=>tt(r).pipe(U(e.pipe(Ce(1))),b(o=>o),m(()=>r),Te(1))),b(r=>r.offsetWidth{let o=r.innerText,n=r.closest("a")||r;return n.title=o,B("content.tooltips")?mt(n,{viewport$:t}).pipe(U(e.pipe(Ce(1))),_(()=>n.removeAttribute("title"))):S})).subscribe(),B("content.tooltips")&&e.pipe(v(()=>P(".md-status")),ne(r=>mt(r,{viewport$:t}))).subscribe()}function Ei({document$:e,tablet$:t}){e.pipe(v(()=>P(".md-toggle--indeterminate")),w(r=>{r.indeterminate=!0,r.checked=!1}),ne(r=>h(r,"change").pipe(Dr(()=>r.classList.contains("md-toggle--indeterminate")),m(()=>r))),re(t)).subscribe(([r,o])=>{r.classList.remove("md-toggle--indeterminate"),o&&(r.checked=!1)})}function us(){return/(iPad|iPhone|iPod)/.test(navigator.userAgent)}function wi({document$:e}){e.pipe(v(()=>P("[data-md-scrollfix]")),w(t=>t.removeAttribute("data-md-scrollfix")),b(us),ne(t=>h(t,"touchstart").pipe(m(()=>t)))).subscribe(t=>{let r=t.scrollTop;r===0?t.scrollTop=1:r+t.offsetHeight===t.scrollHeight&&(t.scrollTop=r-1)})}function Ti({viewport$:e,tablet$:t}){z([ze("search"),t]).pipe(m(([r,o])=>r&&!o),v(r=>I(r).pipe(Ge(r?400:100))),re(e)).subscribe(([r,{offset:{y:o}}])=>{if(r)document.body.setAttribute("data-md-scrolllock",""),document.body.style.top=`-${o}px`;else{let n=-1*parseInt(document.body.style.top,10);document.body.removeAttribute("data-md-scrolllock"),document.body.style.top="",n&&window.scrollTo(0,n)}})}Object.entries||(Object.entries=function(e){let t=[];for(let r of Object.keys(e))t.push([r,e[r]]);return t});Object.values||(Object.values=function(e){let t=[];for(let r of Object.keys(e))t.push(e[r]);return t});typeof Element!="undefined"&&(Element.prototype.scrollTo||(Element.prototype.scrollTo=function(e,t){typeof e=="object"?(this.scrollLeft=e.left,this.scrollTop=e.top):(this.scrollLeft=e,this.scrollTop=t)}),Element.prototype.replaceWith||(Element.prototype.replaceWith=function(...e){let t=this.parentNode;if(t){e.length===0&&t.removeChild(this);for(let r=e.length-1;r>=0;r--){let o=e[r];typeof o=="string"?o=document.createTextNode(o):o.parentNode&&o.parentNode.removeChild(o),r?t.insertBefore(this.previousSibling,o):t.replaceChild(o,this)}}}));function ds(){return location.protocol==="file:"?Tt(`${new URL("search/search_index.js",Zr.base)}`).pipe(m(()=>__index),G(1)):je(new URL("search/search_index.json",Zr.base))}document.documentElement.classList.remove("no-js");document.documentElement.classList.add("js");var ot=Bo(),Wt=an(),Mt=pn(Wt),eo=nn(),Oe=vn(),hr=Pt("(min-width: 960px)"),Oi=Pt("(min-width: 1220px)"),Mi=ln(),Zr=xe(),Li=document.forms.namedItem("search")?ds():Ye,to=new g;Xn({alert$:to});var ro=new g;B("navigation.instant")&&ri({location$:Wt,viewport$:Oe,progress$:ro}).subscribe(ot);var Si;((Si=Zr.version)==null?void 0:Si.provider)==="mike"&&ai({document$:ot});O(Wt,Mt).pipe(Ge(125)).subscribe(()=>{Je("drawer",!1),Je("search",!1)});eo.pipe(b(({mode:e})=>e==="global")).subscribe(e=>{switch(e.type){case"p":case",":let t=fe("link[rel=prev]");typeof t!="undefined"&<(t);break;case"n":case".":let r=fe("link[rel=next]");typeof r!="undefined"&<(r);break;case"Enter":let o=Ie();o instanceof HTMLLabelElement&&o.click()}});xi({viewport$:Oe,document$:ot});Ei({document$:ot,tablet$:hr});wi({document$:ot});Ti({viewport$:Oe,tablet$:hr});var rt=Qn(Se("header"),{viewport$:Oe}),Ft=ot.pipe(m(()=>Se("main")),v(e=>Bn(e,{viewport$:Oe,header$:rt})),G(1)),hs=O(...ae("consent").map(e=>xn(e,{target$:Mt})),...ae("dialog").map(e=>zn(e,{alert$:to})),...ae("header").map(e=>Kn(e,{viewport$:Oe,header$:rt,main$:Ft})),...ae("palette").map(e=>Gn(e)),...ae("progress").map(e=>Jn(e,{progress$:ro})),...ae("search").map(e=>mi(e,{index$:Li,keyboard$:eo})),...ae("source").map(e=>bi(e))),bs=C(()=>O(...ae("announce").map(e=>yn(e)),...ae("content").map(e=>Nn(e,{viewport$:Oe,target$:Mt,print$:Mi})),...ae("content").map(e=>B("search.highlight")?fi(e,{index$:Li,location$:Wt}):S),...ae("header-title").map(e=>Yn(e,{viewport$:Oe,header$:rt})),...ae("sidebar").map(e=>e.getAttribute("data-md-type")==="navigation"?Nr(Oi,()=>Xr(e,{viewport$:Oe,header$:rt,main$:Ft})):Nr(hr,()=>Xr(e,{viewport$:Oe,header$:rt,main$:Ft}))),...ae("tabs").map(e=>vi(e,{viewport$:Oe,header$:rt})),...ae("toc").map(e=>gi(e,{viewport$:Oe,header$:rt,main$:Ft,target$:Mt})),...ae("top").map(e=>yi(e,{viewport$:Oe,header$:rt,main$:Ft,target$:Mt})))),_i=ot.pipe(v(()=>bs),Re(hs),G(1));_i.subscribe();window.document$=ot;window.location$=Wt;window.target$=Mt;window.keyboard$=eo;window.viewport$=Oe;window.tablet$=hr;window.screen$=Oi;window.print$=Mi;window.alert$=to;window.progress$=ro;window.component$=_i;})(); -//# sourceMappingURL=bundle.56dfad97.min.js.map - diff --git a/6.2.18/assets/javascripts/bundle.56dfad97.min.js.map b/6.2.18/assets/javascripts/bundle.56dfad97.min.js.map deleted file mode 100755 index eb83bdb3..00000000 --- a/6.2.18/assets/javascripts/bundle.56dfad97.min.js.map +++ /dev/null @@ -1,7 +0,0 @@ -{ - "version": 3, - "sources": ["node_modules/focus-visible/dist/focus-visible.js", "node_modules/escape-html/index.js", "node_modules/clipboard/dist/clipboard.js", "src/templates/assets/javascripts/bundle.ts", "node_modules/tslib/tslib.es6.mjs", "node_modules/rxjs/src/internal/util/isFunction.ts", "node_modules/rxjs/src/internal/util/createErrorClass.ts", "node_modules/rxjs/src/internal/util/UnsubscriptionError.ts", "node_modules/rxjs/src/internal/util/arrRemove.ts", "node_modules/rxjs/src/internal/Subscription.ts", "node_modules/rxjs/src/internal/config.ts", "node_modules/rxjs/src/internal/scheduler/timeoutProvider.ts", "node_modules/rxjs/src/internal/util/reportUnhandledError.ts", "node_modules/rxjs/src/internal/util/noop.ts", "node_modules/rxjs/src/internal/NotificationFactories.ts", "node_modules/rxjs/src/internal/util/errorContext.ts", "node_modules/rxjs/src/internal/Subscriber.ts", "node_modules/rxjs/src/internal/symbol/observable.ts", "node_modules/rxjs/src/internal/util/identity.ts", "node_modules/rxjs/src/internal/util/pipe.ts", "node_modules/rxjs/src/internal/Observable.ts", "node_modules/rxjs/src/internal/util/lift.ts", "node_modules/rxjs/src/internal/operators/OperatorSubscriber.ts", "node_modules/rxjs/src/internal/scheduler/animationFrameProvider.ts", "node_modules/rxjs/src/internal/util/ObjectUnsubscribedError.ts", "node_modules/rxjs/src/internal/Subject.ts", "node_modules/rxjs/src/internal/BehaviorSubject.ts", "node_modules/rxjs/src/internal/scheduler/dateTimestampProvider.ts", "node_modules/rxjs/src/internal/ReplaySubject.ts", "node_modules/rxjs/src/internal/scheduler/Action.ts", "node_modules/rxjs/src/internal/scheduler/intervalProvider.ts", "node_modules/rxjs/src/internal/scheduler/AsyncAction.ts", "node_modules/rxjs/src/internal/Scheduler.ts", "node_modules/rxjs/src/internal/scheduler/AsyncScheduler.ts", "node_modules/rxjs/src/internal/scheduler/async.ts", "node_modules/rxjs/src/internal/scheduler/QueueAction.ts", "node_modules/rxjs/src/internal/scheduler/QueueScheduler.ts", "node_modules/rxjs/src/internal/scheduler/queue.ts", "node_modules/rxjs/src/internal/scheduler/AnimationFrameAction.ts", "node_modules/rxjs/src/internal/scheduler/AnimationFrameScheduler.ts", "node_modules/rxjs/src/internal/scheduler/animationFrame.ts", "node_modules/rxjs/src/internal/observable/empty.ts", "node_modules/rxjs/src/internal/util/isScheduler.ts", "node_modules/rxjs/src/internal/util/args.ts", "node_modules/rxjs/src/internal/util/isArrayLike.ts", "node_modules/rxjs/src/internal/util/isPromise.ts", "node_modules/rxjs/src/internal/util/isInteropObservable.ts", "node_modules/rxjs/src/internal/util/isAsyncIterable.ts", "node_modules/rxjs/src/internal/util/throwUnobservableError.ts", "node_modules/rxjs/src/internal/symbol/iterator.ts", "node_modules/rxjs/src/internal/util/isIterable.ts", "node_modules/rxjs/src/internal/util/isReadableStreamLike.ts", "node_modules/rxjs/src/internal/observable/innerFrom.ts", "node_modules/rxjs/src/internal/util/executeSchedule.ts", "node_modules/rxjs/src/internal/operators/observeOn.ts", "node_modules/rxjs/src/internal/operators/subscribeOn.ts", "node_modules/rxjs/src/internal/scheduled/scheduleObservable.ts", "node_modules/rxjs/src/internal/scheduled/schedulePromise.ts", "node_modules/rxjs/src/internal/scheduled/scheduleArray.ts", "node_modules/rxjs/src/internal/scheduled/scheduleIterable.ts", "node_modules/rxjs/src/internal/scheduled/scheduleAsyncIterable.ts", "node_modules/rxjs/src/internal/scheduled/scheduleReadableStreamLike.ts", "node_modules/rxjs/src/internal/scheduled/scheduled.ts", "node_modules/rxjs/src/internal/observable/from.ts", "node_modules/rxjs/src/internal/observable/of.ts", "node_modules/rxjs/src/internal/observable/throwError.ts", "node_modules/rxjs/src/internal/util/EmptyError.ts", "node_modules/rxjs/src/internal/util/isDate.ts", "node_modules/rxjs/src/internal/operators/map.ts", "node_modules/rxjs/src/internal/util/mapOneOrManyArgs.ts", "node_modules/rxjs/src/internal/util/argsArgArrayOrObject.ts", "node_modules/rxjs/src/internal/util/createObject.ts", "node_modules/rxjs/src/internal/observable/combineLatest.ts", "node_modules/rxjs/src/internal/operators/mergeInternals.ts", "node_modules/rxjs/src/internal/operators/mergeMap.ts", "node_modules/rxjs/src/internal/operators/mergeAll.ts", "node_modules/rxjs/src/internal/operators/concatAll.ts", "node_modules/rxjs/src/internal/observable/concat.ts", "node_modules/rxjs/src/internal/observable/defer.ts", "node_modules/rxjs/src/internal/observable/fromEvent.ts", "node_modules/rxjs/src/internal/observable/fromEventPattern.ts", "node_modules/rxjs/src/internal/observable/timer.ts", "node_modules/rxjs/src/internal/observable/merge.ts", "node_modules/rxjs/src/internal/observable/never.ts", "node_modules/rxjs/src/internal/util/argsOrArgArray.ts", "node_modules/rxjs/src/internal/operators/filter.ts", "node_modules/rxjs/src/internal/observable/zip.ts", "node_modules/rxjs/src/internal/operators/audit.ts", "node_modules/rxjs/src/internal/operators/auditTime.ts", "node_modules/rxjs/src/internal/operators/bufferCount.ts", "node_modules/rxjs/src/internal/operators/catchError.ts", "node_modules/rxjs/src/internal/operators/scanInternals.ts", "node_modules/rxjs/src/internal/operators/combineLatest.ts", "node_modules/rxjs/src/internal/operators/combineLatestWith.ts", "node_modules/rxjs/src/internal/operators/debounce.ts", "node_modules/rxjs/src/internal/operators/debounceTime.ts", "node_modules/rxjs/src/internal/operators/defaultIfEmpty.ts", "node_modules/rxjs/src/internal/operators/take.ts", "node_modules/rxjs/src/internal/operators/ignoreElements.ts", "node_modules/rxjs/src/internal/operators/mapTo.ts", "node_modules/rxjs/src/internal/operators/delayWhen.ts", "node_modules/rxjs/src/internal/operators/delay.ts", "node_modules/rxjs/src/internal/operators/distinctUntilChanged.ts", "node_modules/rxjs/src/internal/operators/distinctUntilKeyChanged.ts", "node_modules/rxjs/src/internal/operators/throwIfEmpty.ts", "node_modules/rxjs/src/internal/operators/endWith.ts", "node_modules/rxjs/src/internal/operators/finalize.ts", "node_modules/rxjs/src/internal/operators/first.ts", "node_modules/rxjs/src/internal/operators/takeLast.ts", "node_modules/rxjs/src/internal/operators/merge.ts", "node_modules/rxjs/src/internal/operators/mergeWith.ts", "node_modules/rxjs/src/internal/operators/repeat.ts", "node_modules/rxjs/src/internal/operators/scan.ts", "node_modules/rxjs/src/internal/operators/share.ts", "node_modules/rxjs/src/internal/operators/shareReplay.ts", "node_modules/rxjs/src/internal/operators/skip.ts", "node_modules/rxjs/src/internal/operators/skipUntil.ts", "node_modules/rxjs/src/internal/operators/startWith.ts", "node_modules/rxjs/src/internal/operators/switchMap.ts", "node_modules/rxjs/src/internal/operators/takeUntil.ts", "node_modules/rxjs/src/internal/operators/takeWhile.ts", "node_modules/rxjs/src/internal/operators/tap.ts", "node_modules/rxjs/src/internal/operators/throttle.ts", "node_modules/rxjs/src/internal/operators/throttleTime.ts", "node_modules/rxjs/src/internal/operators/withLatestFrom.ts", "node_modules/rxjs/src/internal/operators/zip.ts", "node_modules/rxjs/src/internal/operators/zipWith.ts", "src/templates/assets/javascripts/browser/document/index.ts", "src/templates/assets/javascripts/browser/element/_/index.ts", "src/templates/assets/javascripts/browser/element/focus/index.ts", "src/templates/assets/javascripts/browser/element/hover/index.ts", "src/templates/assets/javascripts/utilities/h/index.ts", "src/templates/assets/javascripts/utilities/round/index.ts", "src/templates/assets/javascripts/browser/script/index.ts", "src/templates/assets/javascripts/browser/element/size/_/index.ts", "src/templates/assets/javascripts/browser/element/size/content/index.ts", "src/templates/assets/javascripts/browser/element/offset/_/index.ts", "src/templates/assets/javascripts/browser/element/offset/content/index.ts", "src/templates/assets/javascripts/browser/element/visibility/index.ts", "src/templates/assets/javascripts/browser/toggle/index.ts", "src/templates/assets/javascripts/browser/keyboard/index.ts", "src/templates/assets/javascripts/browser/location/_/index.ts", "src/templates/assets/javascripts/browser/location/hash/index.ts", "src/templates/assets/javascripts/browser/media/index.ts", "src/templates/assets/javascripts/browser/request/index.ts", "src/templates/assets/javascripts/browser/viewport/offset/index.ts", "src/templates/assets/javascripts/browser/viewport/size/index.ts", "src/templates/assets/javascripts/browser/viewport/_/index.ts", "src/templates/assets/javascripts/browser/viewport/at/index.ts", "src/templates/assets/javascripts/browser/worker/index.ts", "src/templates/assets/javascripts/_/index.ts", "src/templates/assets/javascripts/components/_/index.ts", "src/templates/assets/javascripts/components/announce/index.ts", "src/templates/assets/javascripts/components/consent/index.ts", "src/templates/assets/javascripts/templates/tooltip/index.tsx", "src/templates/assets/javascripts/templates/annotation/index.tsx", "src/templates/assets/javascripts/templates/clipboard/index.tsx", "src/templates/assets/javascripts/templates/search/index.tsx", "src/templates/assets/javascripts/templates/source/index.tsx", "src/templates/assets/javascripts/templates/tabbed/index.tsx", "src/templates/assets/javascripts/templates/table/index.tsx", "src/templates/assets/javascripts/templates/version/index.tsx", "src/templates/assets/javascripts/components/tooltip2/index.ts", "src/templates/assets/javascripts/components/content/annotation/_/index.ts", "src/templates/assets/javascripts/components/content/annotation/list/index.ts", "src/templates/assets/javascripts/components/content/annotation/block/index.ts", "src/templates/assets/javascripts/components/content/code/_/index.ts", "src/templates/assets/javascripts/components/content/details/index.ts", "src/templates/assets/javascripts/components/content/mermaid/index.css", "src/templates/assets/javascripts/components/content/mermaid/index.ts", "src/templates/assets/javascripts/components/content/table/index.ts", "src/templates/assets/javascripts/components/content/tabs/index.ts", "src/templates/assets/javascripts/components/content/_/index.ts", "src/templates/assets/javascripts/components/dialog/index.ts", "src/templates/assets/javascripts/components/tooltip/index.ts", "src/templates/assets/javascripts/components/header/_/index.ts", "src/templates/assets/javascripts/components/header/title/index.ts", "src/templates/assets/javascripts/components/main/index.ts", "src/templates/assets/javascripts/components/palette/index.ts", "src/templates/assets/javascripts/components/progress/index.ts", "src/templates/assets/javascripts/integrations/clipboard/index.ts", "src/templates/assets/javascripts/integrations/sitemap/index.ts", "src/templates/assets/javascripts/integrations/instant/index.ts", "src/templates/assets/javascripts/integrations/search/highlighter/index.ts", "src/templates/assets/javascripts/integrations/search/worker/message/index.ts", "src/templates/assets/javascripts/integrations/search/worker/_/index.ts", "src/templates/assets/javascripts/integrations/version/index.ts", "src/templates/assets/javascripts/components/search/query/index.ts", "src/templates/assets/javascripts/components/search/result/index.ts", "src/templates/assets/javascripts/components/search/share/index.ts", "src/templates/assets/javascripts/components/search/suggest/index.ts", "src/templates/assets/javascripts/components/search/_/index.ts", "src/templates/assets/javascripts/components/search/highlight/index.ts", "src/templates/assets/javascripts/components/sidebar/index.ts", "src/templates/assets/javascripts/components/source/facts/github/index.ts", "src/templates/assets/javascripts/components/source/facts/gitlab/index.ts", "src/templates/assets/javascripts/components/source/facts/_/index.ts", "src/templates/assets/javascripts/components/source/_/index.ts", "src/templates/assets/javascripts/components/tabs/index.ts", "src/templates/assets/javascripts/components/toc/index.ts", "src/templates/assets/javascripts/components/top/index.ts", "src/templates/assets/javascripts/patches/ellipsis/index.ts", "src/templates/assets/javascripts/patches/indeterminate/index.ts", "src/templates/assets/javascripts/patches/scrollfix/index.ts", "src/templates/assets/javascripts/patches/scrolllock/index.ts", "src/templates/assets/javascripts/polyfills/index.ts"], - "sourcesContent": ["(function (global, factory) {\n typeof exports === 'object' && typeof module !== 'undefined' ? factory() :\n typeof define === 'function' && define.amd ? define(factory) :\n (factory());\n}(this, (function () { 'use strict';\n\n /**\n * Applies the :focus-visible polyfill at the given scope.\n * A scope in this case is either the top-level Document or a Shadow Root.\n *\n * @param {(Document|ShadowRoot)} scope\n * @see https://github.com/WICG/focus-visible\n */\n function applyFocusVisiblePolyfill(scope) {\n var hadKeyboardEvent = true;\n var hadFocusVisibleRecently = false;\n var hadFocusVisibleRecentlyTimeout = null;\n\n var inputTypesAllowlist = {\n text: true,\n search: true,\n url: true,\n tel: true,\n email: true,\n password: true,\n number: true,\n date: true,\n month: true,\n week: true,\n time: true,\n datetime: true,\n 'datetime-local': true\n };\n\n /**\n * Helper function for legacy browsers and iframes which sometimes focus\n * elements like document, body, and non-interactive SVG.\n * @param {Element} el\n */\n function isValidFocusTarget(el) {\n if (\n el &&\n el !== document &&\n el.nodeName !== 'HTML' &&\n el.nodeName !== 'BODY' &&\n 'classList' in el &&\n 'contains' in el.classList\n ) {\n return true;\n }\n return false;\n }\n\n /**\n * Computes whether the given element should automatically trigger the\n * `focus-visible` class being added, i.e. whether it should always match\n * `:focus-visible` when focused.\n * @param {Element} el\n * @return {boolean}\n */\n function focusTriggersKeyboardModality(el) {\n var type = el.type;\n var tagName = el.tagName;\n\n if (tagName === 'INPUT' && inputTypesAllowlist[type] && !el.readOnly) {\n return true;\n }\n\n if (tagName === 'TEXTAREA' && !el.readOnly) {\n return true;\n }\n\n if (el.isContentEditable) {\n return true;\n }\n\n return false;\n }\n\n /**\n * Add the `focus-visible` class to the given element if it was not added by\n * the author.\n * @param {Element} el\n */\n function addFocusVisibleClass(el) {\n if (el.classList.contains('focus-visible')) {\n return;\n }\n el.classList.add('focus-visible');\n el.setAttribute('data-focus-visible-added', '');\n }\n\n /**\n * Remove the `focus-visible` class from the given element if it was not\n * originally added by the author.\n * @param {Element} el\n */\n function removeFocusVisibleClass(el) {\n if (!el.hasAttribute('data-focus-visible-added')) {\n return;\n }\n el.classList.remove('focus-visible');\n el.removeAttribute('data-focus-visible-added');\n }\n\n /**\n * If the most recent user interaction was via the keyboard;\n * and the key press did not include a meta, alt/option, or control key;\n * then the modality is keyboard. Otherwise, the modality is not keyboard.\n * Apply `focus-visible` to any current active element and keep track\n * of our keyboard modality state with `hadKeyboardEvent`.\n * @param {KeyboardEvent} e\n */\n function onKeyDown(e) {\n if (e.metaKey || e.altKey || e.ctrlKey) {\n return;\n }\n\n if (isValidFocusTarget(scope.activeElement)) {\n addFocusVisibleClass(scope.activeElement);\n }\n\n hadKeyboardEvent = true;\n }\n\n /**\n * If at any point a user clicks with a pointing device, ensure that we change\n * the modality away from keyboard.\n * This avoids the situation where a user presses a key on an already focused\n * element, and then clicks on a different element, focusing it with a\n * pointing device, while we still think we're in keyboard modality.\n * @param {Event} e\n */\n function onPointerDown(e) {\n hadKeyboardEvent = false;\n }\n\n /**\n * On `focus`, add the `focus-visible` class to the target if:\n * - the target received focus as a result of keyboard navigation, or\n * - the event target is an element that will likely require interaction\n * via the keyboard (e.g. a text box)\n * @param {Event} e\n */\n function onFocus(e) {\n // Prevent IE from focusing the document or HTML element.\n if (!isValidFocusTarget(e.target)) {\n return;\n }\n\n if (hadKeyboardEvent || focusTriggersKeyboardModality(e.target)) {\n addFocusVisibleClass(e.target);\n }\n }\n\n /**\n * On `blur`, remove the `focus-visible` class from the target.\n * @param {Event} e\n */\n function onBlur(e) {\n if (!isValidFocusTarget(e.target)) {\n return;\n }\n\n if (\n e.target.classList.contains('focus-visible') ||\n e.target.hasAttribute('data-focus-visible-added')\n ) {\n // To detect a tab/window switch, we look for a blur event followed\n // rapidly by a visibility change.\n // If we don't see a visibility change within 100ms, it's probably a\n // regular focus change.\n hadFocusVisibleRecently = true;\n window.clearTimeout(hadFocusVisibleRecentlyTimeout);\n hadFocusVisibleRecentlyTimeout = window.setTimeout(function() {\n hadFocusVisibleRecently = false;\n }, 100);\n removeFocusVisibleClass(e.target);\n }\n }\n\n /**\n * If the user changes tabs, keep track of whether or not the previously\n * focused element had .focus-visible.\n * @param {Event} e\n */\n function onVisibilityChange(e) {\n if (document.visibilityState === 'hidden') {\n // If the tab becomes active again, the browser will handle calling focus\n // on the element (Safari actually calls it twice).\n // If this tab change caused a blur on an element with focus-visible,\n // re-apply the class when the user switches back to the tab.\n if (hadFocusVisibleRecently) {\n hadKeyboardEvent = true;\n }\n addInitialPointerMoveListeners();\n }\n }\n\n /**\n * Add a group of listeners to detect usage of any pointing devices.\n * These listeners will be added when the polyfill first loads, and anytime\n * the window is blurred, so that they are active when the window regains\n * focus.\n */\n function addInitialPointerMoveListeners() {\n document.addEventListener('mousemove', onInitialPointerMove);\n document.addEventListener('mousedown', onInitialPointerMove);\n document.addEventListener('mouseup', onInitialPointerMove);\n document.addEventListener('pointermove', onInitialPointerMove);\n document.addEventListener('pointerdown', onInitialPointerMove);\n document.addEventListener('pointerup', onInitialPointerMove);\n document.addEventListener('touchmove', onInitialPointerMove);\n document.addEventListener('touchstart', onInitialPointerMove);\n document.addEventListener('touchend', onInitialPointerMove);\n }\n\n function removeInitialPointerMoveListeners() {\n document.removeEventListener('mousemove', onInitialPointerMove);\n document.removeEventListener('mousedown', onInitialPointerMove);\n document.removeEventListener('mouseup', onInitialPointerMove);\n document.removeEventListener('pointermove', onInitialPointerMove);\n document.removeEventListener('pointerdown', onInitialPointerMove);\n document.removeEventListener('pointerup', onInitialPointerMove);\n document.removeEventListener('touchmove', onInitialPointerMove);\n document.removeEventListener('touchstart', onInitialPointerMove);\n document.removeEventListener('touchend', onInitialPointerMove);\n }\n\n /**\n * When the polfyill first loads, assume the user is in keyboard modality.\n * If any event is received from a pointing device (e.g. mouse, pointer,\n * touch), turn off keyboard modality.\n * This accounts for situations where focus enters the page from the URL bar.\n * @param {Event} e\n */\n function onInitialPointerMove(e) {\n // Work around a Safari quirk that fires a mousemove on whenever the\n // window blurs, even if you're tabbing out of the page. \u00AF\\_(\u30C4)_/\u00AF\n if (e.target.nodeName && e.target.nodeName.toLowerCase() === 'html') {\n return;\n }\n\n hadKeyboardEvent = false;\n removeInitialPointerMoveListeners();\n }\n\n // For some kinds of state, we are interested in changes at the global scope\n // only. For example, global pointer input, global key presses and global\n // visibility change should affect the state at every scope:\n document.addEventListener('keydown', onKeyDown, true);\n document.addEventListener('mousedown', onPointerDown, true);\n document.addEventListener('pointerdown', onPointerDown, true);\n document.addEventListener('touchstart', onPointerDown, true);\n document.addEventListener('visibilitychange', onVisibilityChange, true);\n\n addInitialPointerMoveListeners();\n\n // For focus and blur, we specifically care about state changes in the local\n // scope. This is because focus / blur events that originate from within a\n // shadow root are not re-dispatched from the host element if it was already\n // the active element in its own scope:\n scope.addEventListener('focus', onFocus, true);\n scope.addEventListener('blur', onBlur, true);\n\n // We detect that a node is a ShadowRoot by ensuring that it is a\n // DocumentFragment and also has a host property. This check covers native\n // implementation and polyfill implementation transparently. If we only cared\n // about the native implementation, we could just check if the scope was\n // an instance of a ShadowRoot.\n if (scope.nodeType === Node.DOCUMENT_FRAGMENT_NODE && scope.host) {\n // Since a ShadowRoot is a special kind of DocumentFragment, it does not\n // have a root element to add a class to. So, we add this attribute to the\n // host element instead:\n scope.host.setAttribute('data-js-focus-visible', '');\n } else if (scope.nodeType === Node.DOCUMENT_NODE) {\n document.documentElement.classList.add('js-focus-visible');\n document.documentElement.setAttribute('data-js-focus-visible', '');\n }\n }\n\n // It is important to wrap all references to global window and document in\n // these checks to support server-side rendering use cases\n // @see https://github.com/WICG/focus-visible/issues/199\n if (typeof window !== 'undefined' && typeof document !== 'undefined') {\n // Make the polyfill helper globally available. This can be used as a signal\n // to interested libraries that wish to coordinate with the polyfill for e.g.,\n // applying the polyfill to a shadow root:\n window.applyFocusVisiblePolyfill = applyFocusVisiblePolyfill;\n\n // Notify interested libraries of the polyfill's presence, in case the\n // polyfill was loaded lazily:\n var event;\n\n try {\n event = new CustomEvent('focus-visible-polyfill-ready');\n } catch (error) {\n // IE11 does not support using CustomEvent as a constructor directly:\n event = document.createEvent('CustomEvent');\n event.initCustomEvent('focus-visible-polyfill-ready', false, false, {});\n }\n\n window.dispatchEvent(event);\n }\n\n if (typeof document !== 'undefined') {\n // Apply the polyfill to the global document, so that no JavaScript\n // coordination is required to use the polyfill in the top-level document:\n applyFocusVisiblePolyfill(document);\n }\n\n})));\n", "/*!\n * escape-html\n * Copyright(c) 2012-2013 TJ Holowaychuk\n * Copyright(c) 2015 Andreas Lubbe\n * Copyright(c) 2015 Tiancheng \"Timothy\" Gu\n * MIT Licensed\n */\n\n'use strict';\n\n/**\n * Module variables.\n * @private\n */\n\nvar matchHtmlRegExp = /[\"'&<>]/;\n\n/**\n * Module exports.\n * @public\n */\n\nmodule.exports = escapeHtml;\n\n/**\n * Escape special characters in the given string of html.\n *\n * @param {string} string The string to escape for inserting into HTML\n * @return {string}\n * @public\n */\n\nfunction escapeHtml(string) {\n var str = '' + string;\n var match = matchHtmlRegExp.exec(str);\n\n if (!match) {\n return str;\n }\n\n var escape;\n var html = '';\n var index = 0;\n var lastIndex = 0;\n\n for (index = match.index; index < str.length; index++) {\n switch (str.charCodeAt(index)) {\n case 34: // \"\n escape = '"';\n break;\n case 38: // &\n escape = '&';\n break;\n case 39: // '\n escape = ''';\n break;\n case 60: // <\n escape = '<';\n break;\n case 62: // >\n escape = '>';\n break;\n default:\n continue;\n }\n\n if (lastIndex !== index) {\n html += str.substring(lastIndex, index);\n }\n\n lastIndex = index + 1;\n html += escape;\n }\n\n return lastIndex !== index\n ? html + str.substring(lastIndex, index)\n : html;\n}\n", "/*!\n * clipboard.js v2.0.11\n * https://clipboardjs.com/\n *\n * Licensed MIT \u00A9 Zeno Rocha\n */\n(function webpackUniversalModuleDefinition(root, factory) {\n\tif(typeof exports === 'object' && typeof module === 'object')\n\t\tmodule.exports = factory();\n\telse if(typeof define === 'function' && define.amd)\n\t\tdefine([], factory);\n\telse if(typeof exports === 'object')\n\t\texports[\"ClipboardJS\"] = factory();\n\telse\n\t\troot[\"ClipboardJS\"] = factory();\n})(this, function() {\nreturn /******/ (function() { // webpackBootstrap\n/******/ \tvar __webpack_modules__ = ({\n\n/***/ 686:\n/***/ (function(__unused_webpack_module, __webpack_exports__, __webpack_require__) {\n\n\"use strict\";\n\n// EXPORTS\n__webpack_require__.d(__webpack_exports__, {\n \"default\": function() { return /* binding */ clipboard; }\n});\n\n// EXTERNAL MODULE: ./node_modules/tiny-emitter/index.js\nvar tiny_emitter = __webpack_require__(279);\nvar tiny_emitter_default = /*#__PURE__*/__webpack_require__.n(tiny_emitter);\n// EXTERNAL MODULE: ./node_modules/good-listener/src/listen.js\nvar listen = __webpack_require__(370);\nvar listen_default = /*#__PURE__*/__webpack_require__.n(listen);\n// EXTERNAL MODULE: ./node_modules/select/src/select.js\nvar src_select = __webpack_require__(817);\nvar select_default = /*#__PURE__*/__webpack_require__.n(src_select);\n;// CONCATENATED MODULE: ./src/common/command.js\n/**\n * Executes a given operation type.\n * @param {String} type\n * @return {Boolean}\n */\nfunction command(type) {\n try {\n return document.execCommand(type);\n } catch (err) {\n return false;\n }\n}\n;// CONCATENATED MODULE: ./src/actions/cut.js\n\n\n/**\n * Cut action wrapper.\n * @param {String|HTMLElement} target\n * @return {String}\n */\n\nvar ClipboardActionCut = function ClipboardActionCut(target) {\n var selectedText = select_default()(target);\n command('cut');\n return selectedText;\n};\n\n/* harmony default export */ var actions_cut = (ClipboardActionCut);\n;// CONCATENATED MODULE: ./src/common/create-fake-element.js\n/**\n * Creates a fake textarea element with a value.\n * @param {String} value\n * @return {HTMLElement}\n */\nfunction createFakeElement(value) {\n var isRTL = document.documentElement.getAttribute('dir') === 'rtl';\n var fakeElement = document.createElement('textarea'); // Prevent zooming on iOS\n\n fakeElement.style.fontSize = '12pt'; // Reset box model\n\n fakeElement.style.border = '0';\n fakeElement.style.padding = '0';\n fakeElement.style.margin = '0'; // Move element out of screen horizontally\n\n fakeElement.style.position = 'absolute';\n fakeElement.style[isRTL ? 'right' : 'left'] = '-9999px'; // Move element to the same position vertically\n\n var yPosition = window.pageYOffset || document.documentElement.scrollTop;\n fakeElement.style.top = \"\".concat(yPosition, \"px\");\n fakeElement.setAttribute('readonly', '');\n fakeElement.value = value;\n return fakeElement;\n}\n;// CONCATENATED MODULE: ./src/actions/copy.js\n\n\n\n/**\n * Create fake copy action wrapper using a fake element.\n * @param {String} target\n * @param {Object} options\n * @return {String}\n */\n\nvar fakeCopyAction = function fakeCopyAction(value, options) {\n var fakeElement = createFakeElement(value);\n options.container.appendChild(fakeElement);\n var selectedText = select_default()(fakeElement);\n command('copy');\n fakeElement.remove();\n return selectedText;\n};\n/**\n * Copy action wrapper.\n * @param {String|HTMLElement} target\n * @param {Object} options\n * @return {String}\n */\n\n\nvar ClipboardActionCopy = function ClipboardActionCopy(target) {\n var options = arguments.length > 1 && arguments[1] !== undefined ? arguments[1] : {\n container: document.body\n };\n var selectedText = '';\n\n if (typeof target === 'string') {\n selectedText = fakeCopyAction(target, options);\n } else if (target instanceof HTMLInputElement && !['text', 'search', 'url', 'tel', 'password'].includes(target === null || target === void 0 ? void 0 : target.type)) {\n // If input type doesn't support `setSelectionRange`. Simulate it. https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/setSelectionRange\n selectedText = fakeCopyAction(target.value, options);\n } else {\n selectedText = select_default()(target);\n command('copy');\n }\n\n return selectedText;\n};\n\n/* harmony default export */ var actions_copy = (ClipboardActionCopy);\n;// CONCATENATED MODULE: ./src/actions/default.js\nfunction _typeof(obj) { \"@babel/helpers - typeof\"; if (typeof Symbol === \"function\" && typeof Symbol.iterator === \"symbol\") { _typeof = function _typeof(obj) { return typeof obj; }; } else { _typeof = function _typeof(obj) { return obj && typeof Symbol === \"function\" && obj.constructor === Symbol && obj !== Symbol.prototype ? \"symbol\" : typeof obj; }; } return _typeof(obj); }\n\n\n\n/**\n * Inner function which performs selection from either `text` or `target`\n * properties and then executes copy or cut operations.\n * @param {Object} options\n */\n\nvar ClipboardActionDefault = function ClipboardActionDefault() {\n var options = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};\n // Defines base properties passed from constructor.\n var _options$action = options.action,\n action = _options$action === void 0 ? 'copy' : _options$action,\n container = options.container,\n target = options.target,\n text = options.text; // Sets the `action` to be performed which can be either 'copy' or 'cut'.\n\n if (action !== 'copy' && action !== 'cut') {\n throw new Error('Invalid \"action\" value, use either \"copy\" or \"cut\"');\n } // Sets the `target` property using an element that will be have its content copied.\n\n\n if (target !== undefined) {\n if (target && _typeof(target) === 'object' && target.nodeType === 1) {\n if (action === 'copy' && target.hasAttribute('disabled')) {\n throw new Error('Invalid \"target\" attribute. Please use \"readonly\" instead of \"disabled\" attribute');\n }\n\n if (action === 'cut' && (target.hasAttribute('readonly') || target.hasAttribute('disabled'))) {\n throw new Error('Invalid \"target\" attribute. You can\\'t cut text from elements with \"readonly\" or \"disabled\" attributes');\n }\n } else {\n throw new Error('Invalid \"target\" value, use a valid Element');\n }\n } // Define selection strategy based on `text` property.\n\n\n if (text) {\n return actions_copy(text, {\n container: container\n });\n } // Defines which selection strategy based on `target` property.\n\n\n if (target) {\n return action === 'cut' ? actions_cut(target) : actions_copy(target, {\n container: container\n });\n }\n};\n\n/* harmony default export */ var actions_default = (ClipboardActionDefault);\n;// CONCATENATED MODULE: ./src/clipboard.js\nfunction clipboard_typeof(obj) { \"@babel/helpers - typeof\"; if (typeof Symbol === \"function\" && typeof Symbol.iterator === \"symbol\") { clipboard_typeof = function _typeof(obj) { return typeof obj; }; } else { clipboard_typeof = function _typeof(obj) { return obj && typeof Symbol === \"function\" && obj.constructor === Symbol && obj !== Symbol.prototype ? \"symbol\" : typeof obj; }; } return clipboard_typeof(obj); }\n\nfunction _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError(\"Cannot call a class as a function\"); } }\n\nfunction _defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if (\"value\" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } }\n\nfunction _createClass(Constructor, protoProps, staticProps) { if (protoProps) _defineProperties(Constructor.prototype, protoProps); if (staticProps) _defineProperties(Constructor, staticProps); return Constructor; }\n\nfunction _inherits(subClass, superClass) { if (typeof superClass !== \"function\" && superClass !== null) { throw new TypeError(\"Super expression must either be null or a function\"); } subClass.prototype = Object.create(superClass && superClass.prototype, { constructor: { value: subClass, writable: true, configurable: true } }); if (superClass) _setPrototypeOf(subClass, superClass); }\n\nfunction _setPrototypeOf(o, p) { _setPrototypeOf = Object.setPrototypeOf || function _setPrototypeOf(o, p) { o.__proto__ = p; return o; }; return _setPrototypeOf(o, p); }\n\nfunction _createSuper(Derived) { var hasNativeReflectConstruct = _isNativeReflectConstruct(); return function _createSuperInternal() { var Super = _getPrototypeOf(Derived), result; if (hasNativeReflectConstruct) { var NewTarget = _getPrototypeOf(this).constructor; result = Reflect.construct(Super, arguments, NewTarget); } else { result = Super.apply(this, arguments); } return _possibleConstructorReturn(this, result); }; }\n\nfunction _possibleConstructorReturn(self, call) { if (call && (clipboard_typeof(call) === \"object\" || typeof call === \"function\")) { return call; } return _assertThisInitialized(self); }\n\nfunction _assertThisInitialized(self) { if (self === void 0) { throw new ReferenceError(\"this hasn't been initialised - super() hasn't been called\"); } return self; }\n\nfunction _isNativeReflectConstruct() { if (typeof Reflect === \"undefined\" || !Reflect.construct) return false; if (Reflect.construct.sham) return false; if (typeof Proxy === \"function\") return true; try { Date.prototype.toString.call(Reflect.construct(Date, [], function () {})); return true; } catch (e) { return false; } }\n\nfunction _getPrototypeOf(o) { _getPrototypeOf = Object.setPrototypeOf ? Object.getPrototypeOf : function _getPrototypeOf(o) { return o.__proto__ || Object.getPrototypeOf(o); }; return _getPrototypeOf(o); }\n\n\n\n\n\n\n/**\n * Helper function to retrieve attribute value.\n * @param {String} suffix\n * @param {Element} element\n */\n\nfunction getAttributeValue(suffix, element) {\n var attribute = \"data-clipboard-\".concat(suffix);\n\n if (!element.hasAttribute(attribute)) {\n return;\n }\n\n return element.getAttribute(attribute);\n}\n/**\n * Base class which takes one or more elements, adds event listeners to them,\n * and instantiates a new `ClipboardAction` on each click.\n */\n\n\nvar Clipboard = /*#__PURE__*/function (_Emitter) {\n _inherits(Clipboard, _Emitter);\n\n var _super = _createSuper(Clipboard);\n\n /**\n * @param {String|HTMLElement|HTMLCollection|NodeList} trigger\n * @param {Object} options\n */\n function Clipboard(trigger, options) {\n var _this;\n\n _classCallCheck(this, Clipboard);\n\n _this = _super.call(this);\n\n _this.resolveOptions(options);\n\n _this.listenClick(trigger);\n\n return _this;\n }\n /**\n * Defines if attributes would be resolved using internal setter functions\n * or custom functions that were passed in the constructor.\n * @param {Object} options\n */\n\n\n _createClass(Clipboard, [{\n key: \"resolveOptions\",\n value: function resolveOptions() {\n var options = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : {};\n this.action = typeof options.action === 'function' ? options.action : this.defaultAction;\n this.target = typeof options.target === 'function' ? options.target : this.defaultTarget;\n this.text = typeof options.text === 'function' ? options.text : this.defaultText;\n this.container = clipboard_typeof(options.container) === 'object' ? options.container : document.body;\n }\n /**\n * Adds a click event listener to the passed trigger.\n * @param {String|HTMLElement|HTMLCollection|NodeList} trigger\n */\n\n }, {\n key: \"listenClick\",\n value: function listenClick(trigger) {\n var _this2 = this;\n\n this.listener = listen_default()(trigger, 'click', function (e) {\n return _this2.onClick(e);\n });\n }\n /**\n * Defines a new `ClipboardAction` on each click event.\n * @param {Event} e\n */\n\n }, {\n key: \"onClick\",\n value: function onClick(e) {\n var trigger = e.delegateTarget || e.currentTarget;\n var action = this.action(trigger) || 'copy';\n var text = actions_default({\n action: action,\n container: this.container,\n target: this.target(trigger),\n text: this.text(trigger)\n }); // Fires an event based on the copy operation result.\n\n this.emit(text ? 'success' : 'error', {\n action: action,\n text: text,\n trigger: trigger,\n clearSelection: function clearSelection() {\n if (trigger) {\n trigger.focus();\n }\n\n window.getSelection().removeAllRanges();\n }\n });\n }\n /**\n * Default `action` lookup function.\n * @param {Element} trigger\n */\n\n }, {\n key: \"defaultAction\",\n value: function defaultAction(trigger) {\n return getAttributeValue('action', trigger);\n }\n /**\n * Default `target` lookup function.\n * @param {Element} trigger\n */\n\n }, {\n key: \"defaultTarget\",\n value: function defaultTarget(trigger) {\n var selector = getAttributeValue('target', trigger);\n\n if (selector) {\n return document.querySelector(selector);\n }\n }\n /**\n * Allow fire programmatically a copy action\n * @param {String|HTMLElement} target\n * @param {Object} options\n * @returns Text copied.\n */\n\n }, {\n key: \"defaultText\",\n\n /**\n * Default `text` lookup function.\n * @param {Element} trigger\n */\n value: function defaultText(trigger) {\n return getAttributeValue('text', trigger);\n }\n /**\n * Destroy lifecycle.\n */\n\n }, {\n key: \"destroy\",\n value: function destroy() {\n this.listener.destroy();\n }\n }], [{\n key: \"copy\",\n value: function copy(target) {\n var options = arguments.length > 1 && arguments[1] !== undefined ? arguments[1] : {\n container: document.body\n };\n return actions_copy(target, options);\n }\n /**\n * Allow fire programmatically a cut action\n * @param {String|HTMLElement} target\n * @returns Text cutted.\n */\n\n }, {\n key: \"cut\",\n value: function cut(target) {\n return actions_cut(target);\n }\n /**\n * Returns the support of the given action, or all actions if no action is\n * given.\n * @param {String} [action]\n */\n\n }, {\n key: \"isSupported\",\n value: function isSupported() {\n var action = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : ['copy', 'cut'];\n var actions = typeof action === 'string' ? [action] : action;\n var support = !!document.queryCommandSupported;\n actions.forEach(function (action) {\n support = support && !!document.queryCommandSupported(action);\n });\n return support;\n }\n }]);\n\n return Clipboard;\n}((tiny_emitter_default()));\n\n/* harmony default export */ var clipboard = (Clipboard);\n\n/***/ }),\n\n/***/ 828:\n/***/ (function(module) {\n\nvar DOCUMENT_NODE_TYPE = 9;\n\n/**\n * A polyfill for Element.matches()\n */\nif (typeof Element !== 'undefined' && !Element.prototype.matches) {\n var proto = Element.prototype;\n\n proto.matches = proto.matchesSelector ||\n proto.mozMatchesSelector ||\n proto.msMatchesSelector ||\n proto.oMatchesSelector ||\n proto.webkitMatchesSelector;\n}\n\n/**\n * Finds the closest parent that matches a selector.\n *\n * @param {Element} element\n * @param {String} selector\n * @return {Function}\n */\nfunction closest (element, selector) {\n while (element && element.nodeType !== DOCUMENT_NODE_TYPE) {\n if (typeof element.matches === 'function' &&\n element.matches(selector)) {\n return element;\n }\n element = element.parentNode;\n }\n}\n\nmodule.exports = closest;\n\n\n/***/ }),\n\n/***/ 438:\n/***/ (function(module, __unused_webpack_exports, __webpack_require__) {\n\nvar closest = __webpack_require__(828);\n\n/**\n * Delegates event to a selector.\n *\n * @param {Element} element\n * @param {String} selector\n * @param {String} type\n * @param {Function} callback\n * @param {Boolean} useCapture\n * @return {Object}\n */\nfunction _delegate(element, selector, type, callback, useCapture) {\n var listenerFn = listener.apply(this, arguments);\n\n element.addEventListener(type, listenerFn, useCapture);\n\n return {\n destroy: function() {\n element.removeEventListener(type, listenerFn, useCapture);\n }\n }\n}\n\n/**\n * Delegates event to a selector.\n *\n * @param {Element|String|Array} [elements]\n * @param {String} selector\n * @param {String} type\n * @param {Function} callback\n * @param {Boolean} useCapture\n * @return {Object}\n */\nfunction delegate(elements, selector, type, callback, useCapture) {\n // Handle the regular Element usage\n if (typeof elements.addEventListener === 'function') {\n return _delegate.apply(null, arguments);\n }\n\n // Handle Element-less usage, it defaults to global delegation\n if (typeof type === 'function') {\n // Use `document` as the first parameter, then apply arguments\n // This is a short way to .unshift `arguments` without running into deoptimizations\n return _delegate.bind(null, document).apply(null, arguments);\n }\n\n // Handle Selector-based usage\n if (typeof elements === 'string') {\n elements = document.querySelectorAll(elements);\n }\n\n // Handle Array-like based usage\n return Array.prototype.map.call(elements, function (element) {\n return _delegate(element, selector, type, callback, useCapture);\n });\n}\n\n/**\n * Finds closest match and invokes callback.\n *\n * @param {Element} element\n * @param {String} selector\n * @param {String} type\n * @param {Function} callback\n * @return {Function}\n */\nfunction listener(element, selector, type, callback) {\n return function(e) {\n e.delegateTarget = closest(e.target, selector);\n\n if (e.delegateTarget) {\n callback.call(element, e);\n }\n }\n}\n\nmodule.exports = delegate;\n\n\n/***/ }),\n\n/***/ 879:\n/***/ (function(__unused_webpack_module, exports) {\n\n/**\n * Check if argument is a HTML element.\n *\n * @param {Object} value\n * @return {Boolean}\n */\nexports.node = function(value) {\n return value !== undefined\n && value instanceof HTMLElement\n && value.nodeType === 1;\n};\n\n/**\n * Check if argument is a list of HTML elements.\n *\n * @param {Object} value\n * @return {Boolean}\n */\nexports.nodeList = function(value) {\n var type = Object.prototype.toString.call(value);\n\n return value !== undefined\n && (type === '[object NodeList]' || type === '[object HTMLCollection]')\n && ('length' in value)\n && (value.length === 0 || exports.node(value[0]));\n};\n\n/**\n * Check if argument is a string.\n *\n * @param {Object} value\n * @return {Boolean}\n */\nexports.string = function(value) {\n return typeof value === 'string'\n || value instanceof String;\n};\n\n/**\n * Check if argument is a function.\n *\n * @param {Object} value\n * @return {Boolean}\n */\nexports.fn = function(value) {\n var type = Object.prototype.toString.call(value);\n\n return type === '[object Function]';\n};\n\n\n/***/ }),\n\n/***/ 370:\n/***/ (function(module, __unused_webpack_exports, __webpack_require__) {\n\nvar is = __webpack_require__(879);\nvar delegate = __webpack_require__(438);\n\n/**\n * Validates all params and calls the right\n * listener function based on its target type.\n *\n * @param {String|HTMLElement|HTMLCollection|NodeList} target\n * @param {String} type\n * @param {Function} callback\n * @return {Object}\n */\nfunction listen(target, type, callback) {\n if (!target && !type && !callback) {\n throw new Error('Missing required arguments');\n }\n\n if (!is.string(type)) {\n throw new TypeError('Second argument must be a String');\n }\n\n if (!is.fn(callback)) {\n throw new TypeError('Third argument must be a Function');\n }\n\n if (is.node(target)) {\n return listenNode(target, type, callback);\n }\n else if (is.nodeList(target)) {\n return listenNodeList(target, type, callback);\n }\n else if (is.string(target)) {\n return listenSelector(target, type, callback);\n }\n else {\n throw new TypeError('First argument must be a String, HTMLElement, HTMLCollection, or NodeList');\n }\n}\n\n/**\n * Adds an event listener to a HTML element\n * and returns a remove listener function.\n *\n * @param {HTMLElement} node\n * @param {String} type\n * @param {Function} callback\n * @return {Object}\n */\nfunction listenNode(node, type, callback) {\n node.addEventListener(type, callback);\n\n return {\n destroy: function() {\n node.removeEventListener(type, callback);\n }\n }\n}\n\n/**\n * Add an event listener to a list of HTML elements\n * and returns a remove listener function.\n *\n * @param {NodeList|HTMLCollection} nodeList\n * @param {String} type\n * @param {Function} callback\n * @return {Object}\n */\nfunction listenNodeList(nodeList, type, callback) {\n Array.prototype.forEach.call(nodeList, function(node) {\n node.addEventListener(type, callback);\n });\n\n return {\n destroy: function() {\n Array.prototype.forEach.call(nodeList, function(node) {\n node.removeEventListener(type, callback);\n });\n }\n }\n}\n\n/**\n * Add an event listener to a selector\n * and returns a remove listener function.\n *\n * @param {String} selector\n * @param {String} type\n * @param {Function} callback\n * @return {Object}\n */\nfunction listenSelector(selector, type, callback) {\n return delegate(document.body, selector, type, callback);\n}\n\nmodule.exports = listen;\n\n\n/***/ }),\n\n/***/ 817:\n/***/ (function(module) {\n\nfunction select(element) {\n var selectedText;\n\n if (element.nodeName === 'SELECT') {\n element.focus();\n\n selectedText = element.value;\n }\n else if (element.nodeName === 'INPUT' || element.nodeName === 'TEXTAREA') {\n var isReadOnly = element.hasAttribute('readonly');\n\n if (!isReadOnly) {\n element.setAttribute('readonly', '');\n }\n\n element.select();\n element.setSelectionRange(0, element.value.length);\n\n if (!isReadOnly) {\n element.removeAttribute('readonly');\n }\n\n selectedText = element.value;\n }\n else {\n if (element.hasAttribute('contenteditable')) {\n element.focus();\n }\n\n var selection = window.getSelection();\n var range = document.createRange();\n\n range.selectNodeContents(element);\n selection.removeAllRanges();\n selection.addRange(range);\n\n selectedText = selection.toString();\n }\n\n return selectedText;\n}\n\nmodule.exports = select;\n\n\n/***/ }),\n\n/***/ 279:\n/***/ (function(module) {\n\nfunction E () {\n // Keep this empty so it's easier to inherit from\n // (via https://github.com/lipsmack from https://github.com/scottcorgan/tiny-emitter/issues/3)\n}\n\nE.prototype = {\n on: function (name, callback, ctx) {\n var e = this.e || (this.e = {});\n\n (e[name] || (e[name] = [])).push({\n fn: callback,\n ctx: ctx\n });\n\n return this;\n },\n\n once: function (name, callback, ctx) {\n var self = this;\n function listener () {\n self.off(name, listener);\n callback.apply(ctx, arguments);\n };\n\n listener._ = callback\n return this.on(name, listener, ctx);\n },\n\n emit: function (name) {\n var data = [].slice.call(arguments, 1);\n var evtArr = ((this.e || (this.e = {}))[name] || []).slice();\n var i = 0;\n var len = evtArr.length;\n\n for (i; i < len; i++) {\n evtArr[i].fn.apply(evtArr[i].ctx, data);\n }\n\n return this;\n },\n\n off: function (name, callback) {\n var e = this.e || (this.e = {});\n var evts = e[name];\n var liveEvents = [];\n\n if (evts && callback) {\n for (var i = 0, len = evts.length; i < len; i++) {\n if (evts[i].fn !== callback && evts[i].fn._ !== callback)\n liveEvents.push(evts[i]);\n }\n }\n\n // Remove event from queue to prevent memory leak\n // Suggested by https://github.com/lazd\n // Ref: https://github.com/scottcorgan/tiny-emitter/commit/c6ebfaa9bc973b33d110a84a307742b7cf94c953#commitcomment-5024910\n\n (liveEvents.length)\n ? e[name] = liveEvents\n : delete e[name];\n\n return this;\n }\n};\n\nmodule.exports = E;\nmodule.exports.TinyEmitter = E;\n\n\n/***/ })\n\n/******/ \t});\n/************************************************************************/\n/******/ \t// The module cache\n/******/ \tvar __webpack_module_cache__ = {};\n/******/ \t\n/******/ \t// The require function\n/******/ \tfunction __webpack_require__(moduleId) {\n/******/ \t\t// Check if module is in cache\n/******/ \t\tif(__webpack_module_cache__[moduleId]) {\n/******/ \t\t\treturn __webpack_module_cache__[moduleId].exports;\n/******/ \t\t}\n/******/ \t\t// Create a new module (and put it into the cache)\n/******/ \t\tvar module = __webpack_module_cache__[moduleId] = {\n/******/ \t\t\t// no module.id needed\n/******/ \t\t\t// no module.loaded needed\n/******/ \t\t\texports: {}\n/******/ \t\t};\n/******/ \t\n/******/ \t\t// Execute the module function\n/******/ \t\t__webpack_modules__[moduleId](module, module.exports, __webpack_require__);\n/******/ \t\n/******/ \t\t// Return the exports of the module\n/******/ \t\treturn module.exports;\n/******/ \t}\n/******/ \t\n/************************************************************************/\n/******/ \t/* webpack/runtime/compat get default export */\n/******/ \t!function() {\n/******/ \t\t// getDefaultExport function for compatibility with non-harmony modules\n/******/ \t\t__webpack_require__.n = function(module) {\n/******/ \t\t\tvar getter = module && module.__esModule ?\n/******/ \t\t\t\tfunction() { return module['default']; } :\n/******/ \t\t\t\tfunction() { return module; };\n/******/ \t\t\t__webpack_require__.d(getter, { a: getter });\n/******/ \t\t\treturn getter;\n/******/ \t\t};\n/******/ \t}();\n/******/ \t\n/******/ \t/* webpack/runtime/define property getters */\n/******/ \t!function() {\n/******/ \t\t// define getter functions for harmony exports\n/******/ \t\t__webpack_require__.d = function(exports, definition) {\n/******/ \t\t\tfor(var key in definition) {\n/******/ \t\t\t\tif(__webpack_require__.o(definition, key) && !__webpack_require__.o(exports, key)) {\n/******/ \t\t\t\t\tObject.defineProperty(exports, key, { enumerable: true, get: definition[key] });\n/******/ \t\t\t\t}\n/******/ \t\t\t}\n/******/ \t\t};\n/******/ \t}();\n/******/ \t\n/******/ \t/* webpack/runtime/hasOwnProperty shorthand */\n/******/ \t!function() {\n/******/ \t\t__webpack_require__.o = function(obj, prop) { return Object.prototype.hasOwnProperty.call(obj, prop); }\n/******/ \t}();\n/******/ \t\n/************************************************************************/\n/******/ \t// module exports must be returned from runtime so entry inlining is disabled\n/******/ \t// startup\n/******/ \t// Load entry module and return exports\n/******/ \treturn __webpack_require__(686);\n/******/ })()\n.default;\n});", "/*\n * Copyright (c) 2016-2024 Martin Donath \n *\n * Permission is hereby granted, free of charge, to any person obtaining a copy\n * of this software and associated documentation files (the \"Software\"), to\n * deal in the Software without restriction, including without limitation the\n * rights to use, copy, modify, merge, publish, distribute, sublicense, and/or\n * sell copies of the Software, and to permit persons to whom the Software is\n * furnished to do so, subject to the following conditions:\n *\n * The above copyright notice and this permission notice shall be included in\n * all copies or substantial portions of the Software.\n *\n * THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE\n * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\n * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS\n * IN THE SOFTWARE.\n */\n\nimport \"focus-visible\"\n\nimport {\n EMPTY,\n NEVER,\n Observable,\n Subject,\n defer,\n delay,\n filter,\n map,\n merge,\n mergeWith,\n shareReplay,\n switchMap\n} from \"rxjs\"\n\nimport { configuration, feature } from \"./_\"\nimport {\n at,\n getActiveElement,\n getOptionalElement,\n requestJSON,\n setLocation,\n setToggle,\n watchDocument,\n watchKeyboard,\n watchLocation,\n watchLocationTarget,\n watchMedia,\n watchPrint,\n watchScript,\n watchViewport\n} from \"./browser\"\nimport {\n getComponentElement,\n getComponentElements,\n mountAnnounce,\n mountBackToTop,\n mountConsent,\n mountContent,\n mountDialog,\n mountHeader,\n mountHeaderTitle,\n mountPalette,\n mountProgress,\n mountSearch,\n mountSearchHiglight,\n mountSidebar,\n mountSource,\n mountTableOfContents,\n mountTabs,\n watchHeader,\n watchMain\n} from \"./components\"\nimport {\n SearchIndex,\n setupClipboardJS,\n setupInstantNavigation,\n setupVersionSelector\n} from \"./integrations\"\nimport {\n patchEllipsis,\n patchIndeterminate,\n patchScrollfix,\n patchScrolllock\n} from \"./patches\"\nimport \"./polyfills\"\n\n/* ----------------------------------------------------------------------------\n * Functions - @todo refactor\n * ------------------------------------------------------------------------- */\n\n/**\n * Fetch search index\n *\n * @returns Search index observable\n */\nfunction fetchSearchIndex(): Observable {\n if (location.protocol === \"file:\") {\n return watchScript(\n `${new URL(\"search/search_index.js\", config.base)}`\n )\n .pipe(\n // @ts-ignore - @todo fix typings\n map(() => __index),\n shareReplay(1)\n )\n } else {\n return requestJSON(\n new URL(\"search/search_index.json\", config.base)\n )\n }\n}\n\n/* ----------------------------------------------------------------------------\n * Application\n * ------------------------------------------------------------------------- */\n\n/* Yay, JavaScript is available */\ndocument.documentElement.classList.remove(\"no-js\")\ndocument.documentElement.classList.add(\"js\")\n\n/* Set up navigation observables and subjects */\nconst document$ = watchDocument()\nconst location$ = watchLocation()\nconst target$ = watchLocationTarget(location$)\nconst keyboard$ = watchKeyboard()\n\n/* Set up media observables */\nconst viewport$ = watchViewport()\nconst tablet$ = watchMedia(\"(min-width: 960px)\")\nconst screen$ = watchMedia(\"(min-width: 1220px)\")\nconst print$ = watchPrint()\n\n/* Retrieve search index, if search is enabled */\nconst config = configuration()\nconst index$ = document.forms.namedItem(\"search\")\n ? fetchSearchIndex()\n : NEVER\n\n/* Set up Clipboard.js integration */\nconst alert$ = new Subject()\nsetupClipboardJS({ alert$ })\n\n/* Set up progress indicator */\nconst progress$ = new Subject()\n\n/* Set up instant navigation, if enabled */\nif (feature(\"navigation.instant\"))\n setupInstantNavigation({ location$, viewport$, progress$ })\n .subscribe(document$)\n\n/* Set up version selector */\nif (config.version?.provider === \"mike\")\n setupVersionSelector({ document$ })\n\n/* Always close drawer and search on navigation */\nmerge(location$, target$)\n .pipe(\n delay(125)\n )\n .subscribe(() => {\n setToggle(\"drawer\", false)\n setToggle(\"search\", false)\n })\n\n/* Set up global keyboard handlers */\nkeyboard$\n .pipe(\n filter(({ mode }) => mode === \"global\")\n )\n .subscribe(key => {\n switch (key.type) {\n\n /* Go to previous page */\n case \"p\":\n case \",\":\n const prev = getOptionalElement(\"link[rel=prev]\")\n if (typeof prev !== \"undefined\")\n setLocation(prev)\n break\n\n /* Go to next page */\n case \"n\":\n case \".\":\n const next = getOptionalElement(\"link[rel=next]\")\n if (typeof next !== \"undefined\")\n setLocation(next)\n break\n\n /* Expand navigation, see https://bit.ly/3ZjG5io */\n case \"Enter\":\n const active = getActiveElement()\n if (active instanceof HTMLLabelElement)\n active.click()\n }\n })\n\n/* Set up patches */\npatchEllipsis({ viewport$, document$ })\npatchIndeterminate({ document$, tablet$ })\npatchScrollfix({ document$ })\npatchScrolllock({ viewport$, tablet$ })\n\n/* Set up header and main area observable */\nconst header$ = watchHeader(getComponentElement(\"header\"), { viewport$ })\nconst main$ = document$\n .pipe(\n map(() => getComponentElement(\"main\")),\n switchMap(el => watchMain(el, { viewport$, header$ })),\n shareReplay(1)\n )\n\n/* Set up control component observables */\nconst control$ = merge(\n\n /* Consent */\n ...getComponentElements(\"consent\")\n .map(el => mountConsent(el, { target$ })),\n\n /* Dialog */\n ...getComponentElements(\"dialog\")\n .map(el => mountDialog(el, { alert$ })),\n\n /* Header */\n ...getComponentElements(\"header\")\n .map(el => mountHeader(el, { viewport$, header$, main$ })),\n\n /* Color palette */\n ...getComponentElements(\"palette\")\n .map(el => mountPalette(el)),\n\n /* Progress bar */\n ...getComponentElements(\"progress\")\n .map(el => mountProgress(el, { progress$ })),\n\n /* Search */\n ...getComponentElements(\"search\")\n .map(el => mountSearch(el, { index$, keyboard$ })),\n\n /* Repository information */\n ...getComponentElements(\"source\")\n .map(el => mountSource(el))\n)\n\n/* Set up content component observables */\nconst content$ = defer(() => merge(\n\n /* Announcement bar */\n ...getComponentElements(\"announce\")\n .map(el => mountAnnounce(el)),\n\n /* Content */\n ...getComponentElements(\"content\")\n .map(el => mountContent(el, { viewport$, target$, print$ })),\n\n /* Search highlighting */\n ...getComponentElements(\"content\")\n .map(el => feature(\"search.highlight\")\n ? mountSearchHiglight(el, { index$, location$ })\n : EMPTY\n ),\n\n /* Header title */\n ...getComponentElements(\"header-title\")\n .map(el => mountHeaderTitle(el, { viewport$, header$ })),\n\n /* Sidebar */\n ...getComponentElements(\"sidebar\")\n .map(el => el.getAttribute(\"data-md-type\") === \"navigation\"\n ? at(screen$, () => mountSidebar(el, { viewport$, header$, main$ }))\n : at(tablet$, () => mountSidebar(el, { viewport$, header$, main$ }))\n ),\n\n /* Navigation tabs */\n ...getComponentElements(\"tabs\")\n .map(el => mountTabs(el, { viewport$, header$ })),\n\n /* Table of contents */\n ...getComponentElements(\"toc\")\n .map(el => mountTableOfContents(el, {\n viewport$, header$, main$, target$\n })),\n\n /* Back-to-top button */\n ...getComponentElements(\"top\")\n .map(el => mountBackToTop(el, { viewport$, header$, main$, target$ }))\n))\n\n/* Set up component observables */\nconst component$ = document$\n .pipe(\n switchMap(() => content$),\n mergeWith(control$),\n shareReplay(1)\n )\n\n/* Subscribe to all components */\ncomponent$.subscribe()\n\n/* ----------------------------------------------------------------------------\n * Exports\n * ------------------------------------------------------------------------- */\n\nwindow.document$ = document$ /* Document observable */\nwindow.location$ = location$ /* Location subject */\nwindow.target$ = target$ /* Location target observable */\nwindow.keyboard$ = keyboard$ /* Keyboard observable */\nwindow.viewport$ = viewport$ /* Viewport observable */\nwindow.tablet$ = tablet$ /* Media tablet observable */\nwindow.screen$ = screen$ /* Media screen observable */\nwindow.print$ = print$ /* Media print observable */\nwindow.alert$ = alert$ /* Alert subject */\nwindow.progress$ = progress$ /* Progress indicator subject */\nwindow.component$ = component$ /* Component observable */\n", "/******************************************************************************\nCopyright (c) Microsoft Corporation.\n\nPermission to use, copy, modify, and/or distribute this software for any\npurpose with or without fee is hereby granted.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH\nREGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY\nAND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,\nINDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM\nLOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR\nOTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR\nPERFORMANCE OF THIS SOFTWARE.\n***************************************************************************** */\n/* global Reflect, Promise, SuppressedError, Symbol, Iterator */\n\nvar extendStatics = function(d, b) {\n extendStatics = Object.setPrototypeOf ||\n ({ __proto__: [] } instanceof Array && function (d, b) { d.__proto__ = b; }) ||\n function (d, b) { for (var p in b) if (Object.prototype.hasOwnProperty.call(b, p)) d[p] = b[p]; };\n return extendStatics(d, b);\n};\n\nexport function __extends(d, b) {\n if (typeof b !== \"function\" && b !== null)\n throw new TypeError(\"Class extends value \" + String(b) + \" is not a constructor or null\");\n extendStatics(d, b);\n function __() { this.constructor = d; }\n d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());\n}\n\nexport var __assign = function() {\n __assign = Object.assign || function __assign(t) {\n for (var s, i = 1, n = arguments.length; i < n; i++) {\n s = arguments[i];\n for (var p in s) if (Object.prototype.hasOwnProperty.call(s, p)) t[p] = s[p];\n }\n return t;\n }\n return __assign.apply(this, arguments);\n}\n\nexport function __rest(s, e) {\n var t = {};\n for (var p in s) if (Object.prototype.hasOwnProperty.call(s, p) && e.indexOf(p) < 0)\n t[p] = s[p];\n if (s != null && typeof Object.getOwnPropertySymbols === \"function\")\n for (var i = 0, p = Object.getOwnPropertySymbols(s); i < p.length; i++) {\n if (e.indexOf(p[i]) < 0 && Object.prototype.propertyIsEnumerable.call(s, p[i]))\n t[p[i]] = s[p[i]];\n }\n return t;\n}\n\nexport function __decorate(decorators, target, key, desc) {\n var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;\n if (typeof Reflect === \"object\" && typeof Reflect.decorate === \"function\") r = Reflect.decorate(decorators, target, key, desc);\n else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;\n return c > 3 && r && Object.defineProperty(target, key, r), r;\n}\n\nexport function __param(paramIndex, decorator) {\n return function (target, key) { decorator(target, key, paramIndex); }\n}\n\nexport function __esDecorate(ctor, descriptorIn, decorators, contextIn, initializers, extraInitializers) {\n function accept(f) { if (f !== void 0 && typeof f !== \"function\") throw new TypeError(\"Function expected\"); return f; }\n var kind = contextIn.kind, key = kind === \"getter\" ? \"get\" : kind === \"setter\" ? \"set\" : \"value\";\n var target = !descriptorIn && ctor ? contextIn[\"static\"] ? ctor : ctor.prototype : null;\n var descriptor = descriptorIn || (target ? Object.getOwnPropertyDescriptor(target, contextIn.name) : {});\n var _, done = false;\n for (var i = decorators.length - 1; i >= 0; i--) {\n var context = {};\n for (var p in contextIn) context[p] = p === \"access\" ? {} : contextIn[p];\n for (var p in contextIn.access) context.access[p] = contextIn.access[p];\n context.addInitializer = function (f) { if (done) throw new TypeError(\"Cannot add initializers after decoration has completed\"); extraInitializers.push(accept(f || null)); };\n var result = (0, decorators[i])(kind === \"accessor\" ? { get: descriptor.get, set: descriptor.set } : descriptor[key], context);\n if (kind === \"accessor\") {\n if (result === void 0) continue;\n if (result === null || typeof result !== \"object\") throw new TypeError(\"Object expected\");\n if (_ = accept(result.get)) descriptor.get = _;\n if (_ = accept(result.set)) descriptor.set = _;\n if (_ = accept(result.init)) initializers.unshift(_);\n }\n else if (_ = accept(result)) {\n if (kind === \"field\") initializers.unshift(_);\n else descriptor[key] = _;\n }\n }\n if (target) Object.defineProperty(target, contextIn.name, descriptor);\n done = true;\n};\n\nexport function __runInitializers(thisArg, initializers, value) {\n var useValue = arguments.length > 2;\n for (var i = 0; i < initializers.length; i++) {\n value = useValue ? initializers[i].call(thisArg, value) : initializers[i].call(thisArg);\n }\n return useValue ? value : void 0;\n};\n\nexport function __propKey(x) {\n return typeof x === \"symbol\" ? x : \"\".concat(x);\n};\n\nexport function __setFunctionName(f, name, prefix) {\n if (typeof name === \"symbol\") name = name.description ? \"[\".concat(name.description, \"]\") : \"\";\n return Object.defineProperty(f, \"name\", { configurable: true, value: prefix ? \"\".concat(prefix, \" \", name) : name });\n};\n\nexport function __metadata(metadataKey, metadataValue) {\n if (typeof Reflect === \"object\" && typeof Reflect.metadata === \"function\") return Reflect.metadata(metadataKey, metadataValue);\n}\n\nexport function __awaiter(thisArg, _arguments, P, generator) {\n function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }\n return new (P || (P = Promise))(function (resolve, reject) {\n function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }\n function rejected(value) { try { step(generator[\"throw\"](value)); } catch (e) { reject(e); } }\n function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }\n step((generator = generator.apply(thisArg, _arguments || [])).next());\n });\n}\n\nexport function __generator(thisArg, body) {\n var _ = { label: 0, sent: function() { if (t[0] & 1) throw t[1]; return t[1]; }, trys: [], ops: [] }, f, y, t, g = Object.create((typeof Iterator === \"function\" ? Iterator : Object).prototype);\n return g.next = verb(0), g[\"throw\"] = verb(1), g[\"return\"] = verb(2), typeof Symbol === \"function\" && (g[Symbol.iterator] = function() { return this; }), g;\n function verb(n) { return function (v) { return step([n, v]); }; }\n function step(op) {\n if (f) throw new TypeError(\"Generator is already executing.\");\n while (g && (g = 0, op[0] && (_ = 0)), _) try {\n if (f = 1, y && (t = op[0] & 2 ? y[\"return\"] : op[0] ? y[\"throw\"] || ((t = y[\"return\"]) && t.call(y), 0) : y.next) && !(t = t.call(y, op[1])).done) return t;\n if (y = 0, t) op = [op[0] & 2, t.value];\n switch (op[0]) {\n case 0: case 1: t = op; break;\n case 4: _.label++; return { value: op[1], done: false };\n case 5: _.label++; y = op[1]; op = [0]; continue;\n case 7: op = _.ops.pop(); _.trys.pop(); continue;\n default:\n if (!(t = _.trys, t = t.length > 0 && t[t.length - 1]) && (op[0] === 6 || op[0] === 2)) { _ = 0; continue; }\n if (op[0] === 3 && (!t || (op[1] > t[0] && op[1] < t[3]))) { _.label = op[1]; break; }\n if (op[0] === 6 && _.label < t[1]) { _.label = t[1]; t = op; break; }\n if (t && _.label < t[2]) { _.label = t[2]; _.ops.push(op); break; }\n if (t[2]) _.ops.pop();\n _.trys.pop(); continue;\n }\n op = body.call(thisArg, _);\n } catch (e) { op = [6, e]; y = 0; } finally { f = t = 0; }\n if (op[0] & 5) throw op[1]; return { value: op[0] ? op[1] : void 0, done: true };\n }\n}\n\nexport var __createBinding = Object.create ? (function(o, m, k, k2) {\n if (k2 === undefined) k2 = k;\n var desc = Object.getOwnPropertyDescriptor(m, k);\n if (!desc || (\"get\" in desc ? !m.__esModule : desc.writable || desc.configurable)) {\n desc = { enumerable: true, get: function() { return m[k]; } };\n }\n Object.defineProperty(o, k2, desc);\n}) : (function(o, m, k, k2) {\n if (k2 === undefined) k2 = k;\n o[k2] = m[k];\n});\n\nexport function __exportStar(m, o) {\n for (var p in m) if (p !== \"default\" && !Object.prototype.hasOwnProperty.call(o, p)) __createBinding(o, m, p);\n}\n\nexport function __values(o) {\n var s = typeof Symbol === \"function\" && Symbol.iterator, m = s && o[s], i = 0;\n if (m) return m.call(o);\n if (o && typeof o.length === \"number\") return {\n next: function () {\n if (o && i >= o.length) o = void 0;\n return { value: o && o[i++], done: !o };\n }\n };\n throw new TypeError(s ? \"Object is not iterable.\" : \"Symbol.iterator is not defined.\");\n}\n\nexport function __read(o, n) {\n var m = typeof Symbol === \"function\" && o[Symbol.iterator];\n if (!m) return o;\n var i = m.call(o), r, ar = [], e;\n try {\n while ((n === void 0 || n-- > 0) && !(r = i.next()).done) ar.push(r.value);\n }\n catch (error) { e = { error: error }; }\n finally {\n try {\n if (r && !r.done && (m = i[\"return\"])) m.call(i);\n }\n finally { if (e) throw e.error; }\n }\n return ar;\n}\n\n/** @deprecated */\nexport function __spread() {\n for (var ar = [], i = 0; i < arguments.length; i++)\n ar = ar.concat(__read(arguments[i]));\n return ar;\n}\n\n/** @deprecated */\nexport function __spreadArrays() {\n for (var s = 0, i = 0, il = arguments.length; i < il; i++) s += arguments[i].length;\n for (var r = Array(s), k = 0, i = 0; i < il; i++)\n for (var a = arguments[i], j = 0, jl = a.length; j < jl; j++, k++)\n r[k] = a[j];\n return r;\n}\n\nexport function __spreadArray(to, from, pack) {\n if (pack || arguments.length === 2) for (var i = 0, l = from.length, ar; i < l; i++) {\n if (ar || !(i in from)) {\n if (!ar) ar = Array.prototype.slice.call(from, 0, i);\n ar[i] = from[i];\n }\n }\n return to.concat(ar || Array.prototype.slice.call(from));\n}\n\nexport function __await(v) {\n return this instanceof __await ? (this.v = v, this) : new __await(v);\n}\n\nexport function __asyncGenerator(thisArg, _arguments, generator) {\n if (!Symbol.asyncIterator) throw new TypeError(\"Symbol.asyncIterator is not defined.\");\n var g = generator.apply(thisArg, _arguments || []), i, q = [];\n return i = Object.create((typeof AsyncIterator === \"function\" ? AsyncIterator : Object).prototype), verb(\"next\"), verb(\"throw\"), verb(\"return\", awaitReturn), i[Symbol.asyncIterator] = function () { return this; }, i;\n function awaitReturn(f) { return function (v) { return Promise.resolve(v).then(f, reject); }; }\n function verb(n, f) { if (g[n]) { i[n] = function (v) { return new Promise(function (a, b) { q.push([n, v, a, b]) > 1 || resume(n, v); }); }; if (f) i[n] = f(i[n]); } }\n function resume(n, v) { try { step(g[n](v)); } catch (e) { settle(q[0][3], e); } }\n function step(r) { r.value instanceof __await ? Promise.resolve(r.value.v).then(fulfill, reject) : settle(q[0][2], r); }\n function fulfill(value) { resume(\"next\", value); }\n function reject(value) { resume(\"throw\", value); }\n function settle(f, v) { if (f(v), q.shift(), q.length) resume(q[0][0], q[0][1]); }\n}\n\nexport function __asyncDelegator(o) {\n var i, p;\n return i = {}, verb(\"next\"), verb(\"throw\", function (e) { throw e; }), verb(\"return\"), i[Symbol.iterator] = function () { return this; }, i;\n function verb(n, f) { i[n] = o[n] ? function (v) { return (p = !p) ? { value: __await(o[n](v)), done: false } : f ? f(v) : v; } : f; }\n}\n\nexport function __asyncValues(o) {\n if (!Symbol.asyncIterator) throw new TypeError(\"Symbol.asyncIterator is not defined.\");\n var m = o[Symbol.asyncIterator], i;\n return m ? m.call(o) : (o = typeof __values === \"function\" ? __values(o) : o[Symbol.iterator](), i = {}, verb(\"next\"), verb(\"throw\"), verb(\"return\"), i[Symbol.asyncIterator] = function () { return this; }, i);\n function verb(n) { i[n] = o[n] && function (v) { return new Promise(function (resolve, reject) { v = o[n](v), settle(resolve, reject, v.done, v.value); }); }; }\n function settle(resolve, reject, d, v) { Promise.resolve(v).then(function(v) { resolve({ value: v, done: d }); }, reject); }\n}\n\nexport function __makeTemplateObject(cooked, raw) {\n if (Object.defineProperty) { Object.defineProperty(cooked, \"raw\", { value: raw }); } else { cooked.raw = raw; }\n return cooked;\n};\n\nvar __setModuleDefault = Object.create ? (function(o, v) {\n Object.defineProperty(o, \"default\", { enumerable: true, value: v });\n}) : function(o, v) {\n o[\"default\"] = v;\n};\n\nexport function __importStar(mod) {\n if (mod && mod.__esModule) return mod;\n var result = {};\n if (mod != null) for (var k in mod) if (k !== \"default\" && Object.prototype.hasOwnProperty.call(mod, k)) __createBinding(result, mod, k);\n __setModuleDefault(result, mod);\n return result;\n}\n\nexport function __importDefault(mod) {\n return (mod && mod.__esModule) ? mod : { default: mod };\n}\n\nexport function __classPrivateFieldGet(receiver, state, kind, f) {\n if (kind === \"a\" && !f) throw new TypeError(\"Private accessor was defined without a getter\");\n if (typeof state === \"function\" ? receiver !== state || !f : !state.has(receiver)) throw new TypeError(\"Cannot read private member from an object whose class did not declare it\");\n return kind === \"m\" ? f : kind === \"a\" ? f.call(receiver) : f ? f.value : state.get(receiver);\n}\n\nexport function __classPrivateFieldSet(receiver, state, value, kind, f) {\n if (kind === \"m\") throw new TypeError(\"Private method is not writable\");\n if (kind === \"a\" && !f) throw new TypeError(\"Private accessor was defined without a setter\");\n if (typeof state === \"function\" ? receiver !== state || !f : !state.has(receiver)) throw new TypeError(\"Cannot write private member to an object whose class did not declare it\");\n return (kind === \"a\" ? f.call(receiver, value) : f ? f.value = value : state.set(receiver, value)), value;\n}\n\nexport function __classPrivateFieldIn(state, receiver) {\n if (receiver === null || (typeof receiver !== \"object\" && typeof receiver !== \"function\")) throw new TypeError(\"Cannot use 'in' operator on non-object\");\n return typeof state === \"function\" ? receiver === state : state.has(receiver);\n}\n\nexport function __addDisposableResource(env, value, async) {\n if (value !== null && value !== void 0) {\n if (typeof value !== \"object\" && typeof value !== \"function\") throw new TypeError(\"Object expected.\");\n var dispose, inner;\n if (async) {\n if (!Symbol.asyncDispose) throw new TypeError(\"Symbol.asyncDispose is not defined.\");\n dispose = value[Symbol.asyncDispose];\n }\n if (dispose === void 0) {\n if (!Symbol.dispose) throw new TypeError(\"Symbol.dispose is not defined.\");\n dispose = value[Symbol.dispose];\n if (async) inner = dispose;\n }\n if (typeof dispose !== \"function\") throw new TypeError(\"Object not disposable.\");\n if (inner) dispose = function() { try { inner.call(this); } catch (e) { return Promise.reject(e); } };\n env.stack.push({ value: value, dispose: dispose, async: async });\n }\n else if (async) {\n env.stack.push({ async: true });\n }\n return value;\n}\n\nvar _SuppressedError = typeof SuppressedError === \"function\" ? SuppressedError : function (error, suppressed, message) {\n var e = new Error(message);\n return e.name = \"SuppressedError\", e.error = error, e.suppressed = suppressed, e;\n};\n\nexport function __disposeResources(env) {\n function fail(e) {\n env.error = env.hasError ? new _SuppressedError(e, env.error, \"An error was suppressed during disposal.\") : e;\n env.hasError = true;\n }\n var r, s = 0;\n function next() {\n while (r = env.stack.pop()) {\n try {\n if (!r.async && s === 1) return s = 0, env.stack.push(r), Promise.resolve().then(next);\n if (r.dispose) {\n var result = r.dispose.call(r.value);\n if (r.async) return s |= 2, Promise.resolve(result).then(next, function(e) { fail(e); return next(); });\n }\n else s |= 1;\n }\n catch (e) {\n fail(e);\n }\n }\n if (s === 1) return env.hasError ? Promise.reject(env.error) : Promise.resolve();\n if (env.hasError) throw env.error;\n }\n return next();\n}\n\nexport default {\n __extends,\n __assign,\n __rest,\n __decorate,\n __param,\n __metadata,\n __awaiter,\n __generator,\n __createBinding,\n __exportStar,\n __values,\n __read,\n __spread,\n __spreadArrays,\n __spreadArray,\n __await,\n __asyncGenerator,\n __asyncDelegator,\n __asyncValues,\n __makeTemplateObject,\n __importStar,\n __importDefault,\n __classPrivateFieldGet,\n __classPrivateFieldSet,\n __classPrivateFieldIn,\n __addDisposableResource,\n __disposeResources,\n};\n", "/**\n * Returns true if the object is a function.\n * @param value The value to check\n */\nexport function isFunction(value: any): value is (...args: any[]) => any {\n return typeof value === 'function';\n}\n", "/**\n * Used to create Error subclasses until the community moves away from ES5.\n *\n * This is because compiling from TypeScript down to ES5 has issues with subclassing Errors\n * as well as other built-in types: https://github.com/Microsoft/TypeScript/issues/12123\n *\n * @param createImpl A factory function to create the actual constructor implementation. The returned\n * function should be a named function that calls `_super` internally.\n */\nexport function createErrorClass(createImpl: (_super: any) => any): T {\n const _super = (instance: any) => {\n Error.call(instance);\n instance.stack = new Error().stack;\n };\n\n const ctorFunc = createImpl(_super);\n ctorFunc.prototype = Object.create(Error.prototype);\n ctorFunc.prototype.constructor = ctorFunc;\n return ctorFunc;\n}\n", "import { createErrorClass } from './createErrorClass';\n\nexport interface UnsubscriptionError extends Error {\n readonly errors: any[];\n}\n\nexport interface UnsubscriptionErrorCtor {\n /**\n * @deprecated Internal implementation detail. Do not construct error instances.\n * Cannot be tagged as internal: https://github.com/ReactiveX/rxjs/issues/6269\n */\n new (errors: any[]): UnsubscriptionError;\n}\n\n/**\n * An error thrown when one or more errors have occurred during the\n * `unsubscribe` of a {@link Subscription}.\n */\nexport const UnsubscriptionError: UnsubscriptionErrorCtor = createErrorClass(\n (_super) =>\n function UnsubscriptionErrorImpl(this: any, errors: (Error | string)[]) {\n _super(this);\n this.message = errors\n ? `${errors.length} errors occurred during unsubscription:\n${errors.map((err, i) => `${i + 1}) ${err.toString()}`).join('\\n ')}`\n : '';\n this.name = 'UnsubscriptionError';\n this.errors = errors;\n }\n);\n", "/**\n * Removes an item from an array, mutating it.\n * @param arr The array to remove the item from\n * @param item The item to remove\n */\nexport function arrRemove(arr: T[] | undefined | null, item: T) {\n if (arr) {\n const index = arr.indexOf(item);\n 0 <= index && arr.splice(index, 1);\n }\n}\n", "import { isFunction } from './util/isFunction';\nimport { UnsubscriptionError } from './util/UnsubscriptionError';\nimport { SubscriptionLike, TeardownLogic, Unsubscribable } from './types';\nimport { arrRemove } from './util/arrRemove';\n\n/**\n * Represents a disposable resource, such as the execution of an Observable. A\n * Subscription has one important method, `unsubscribe`, that takes no argument\n * and just disposes the resource held by the subscription.\n *\n * Additionally, subscriptions may be grouped together through the `add()`\n * method, which will attach a child Subscription to the current Subscription.\n * When a Subscription is unsubscribed, all its children (and its grandchildren)\n * will be unsubscribed as well.\n *\n * @class Subscription\n */\nexport class Subscription implements SubscriptionLike {\n /** @nocollapse */\n public static EMPTY = (() => {\n const empty = new Subscription();\n empty.closed = true;\n return empty;\n })();\n\n /**\n * A flag to indicate whether this Subscription has already been unsubscribed.\n */\n public closed = false;\n\n private _parentage: Subscription[] | Subscription | null = null;\n\n /**\n * The list of registered finalizers to execute upon unsubscription. Adding and removing from this\n * list occurs in the {@link #add} and {@link #remove} methods.\n */\n private _finalizers: Exclude[] | null = null;\n\n /**\n * @param initialTeardown A function executed first as part of the finalization\n * process that is kicked off when {@link #unsubscribe} is called.\n */\n constructor(private initialTeardown?: () => void) {}\n\n /**\n * Disposes the resources held by the subscription. May, for instance, cancel\n * an ongoing Observable execution or cancel any other type of work that\n * started when the Subscription was created.\n * @return {void}\n */\n unsubscribe(): void {\n let errors: any[] | undefined;\n\n if (!this.closed) {\n this.closed = true;\n\n // Remove this from it's parents.\n const { _parentage } = this;\n if (_parentage) {\n this._parentage = null;\n if (Array.isArray(_parentage)) {\n for (const parent of _parentage) {\n parent.remove(this);\n }\n } else {\n _parentage.remove(this);\n }\n }\n\n const { initialTeardown: initialFinalizer } = this;\n if (isFunction(initialFinalizer)) {\n try {\n initialFinalizer();\n } catch (e) {\n errors = e instanceof UnsubscriptionError ? e.errors : [e];\n }\n }\n\n const { _finalizers } = this;\n if (_finalizers) {\n this._finalizers = null;\n for (const finalizer of _finalizers) {\n try {\n execFinalizer(finalizer);\n } catch (err) {\n errors = errors ?? [];\n if (err instanceof UnsubscriptionError) {\n errors = [...errors, ...err.errors];\n } else {\n errors.push(err);\n }\n }\n }\n }\n\n if (errors) {\n throw new UnsubscriptionError(errors);\n }\n }\n }\n\n /**\n * Adds a finalizer to this subscription, so that finalization will be unsubscribed/called\n * when this subscription is unsubscribed. If this subscription is already {@link #closed},\n * because it has already been unsubscribed, then whatever finalizer is passed to it\n * will automatically be executed (unless the finalizer itself is also a closed subscription).\n *\n * Closed Subscriptions cannot be added as finalizers to any subscription. Adding a closed\n * subscription to a any subscription will result in no operation. (A noop).\n *\n * Adding a subscription to itself, or adding `null` or `undefined` will not perform any\n * operation at all. (A noop).\n *\n * `Subscription` instances that are added to this instance will automatically remove themselves\n * if they are unsubscribed. Functions and {@link Unsubscribable} objects that you wish to remove\n * will need to be removed manually with {@link #remove}\n *\n * @param teardown The finalization logic to add to this subscription.\n */\n add(teardown: TeardownLogic): void {\n // Only add the finalizer if it's not undefined\n // and don't add a subscription to itself.\n if (teardown && teardown !== this) {\n if (this.closed) {\n // If this subscription is already closed,\n // execute whatever finalizer is handed to it automatically.\n execFinalizer(teardown);\n } else {\n if (teardown instanceof Subscription) {\n // We don't add closed subscriptions, and we don't add the same subscription\n // twice. Subscription unsubscribe is idempotent.\n if (teardown.closed || teardown._hasParent(this)) {\n return;\n }\n teardown._addParent(this);\n }\n (this._finalizers = this._finalizers ?? []).push(teardown);\n }\n }\n }\n\n /**\n * Checks to see if a this subscription already has a particular parent.\n * This will signal that this subscription has already been added to the parent in question.\n * @param parent the parent to check for\n */\n private _hasParent(parent: Subscription) {\n const { _parentage } = this;\n return _parentage === parent || (Array.isArray(_parentage) && _parentage.includes(parent));\n }\n\n /**\n * Adds a parent to this subscription so it can be removed from the parent if it\n * unsubscribes on it's own.\n *\n * NOTE: THIS ASSUMES THAT {@link _hasParent} HAS ALREADY BEEN CHECKED.\n * @param parent The parent subscription to add\n */\n private _addParent(parent: Subscription) {\n const { _parentage } = this;\n this._parentage = Array.isArray(_parentage) ? (_parentage.push(parent), _parentage) : _parentage ? [_parentage, parent] : parent;\n }\n\n /**\n * Called on a child when it is removed via {@link #remove}.\n * @param parent The parent to remove\n */\n private _removeParent(parent: Subscription) {\n const { _parentage } = this;\n if (_parentage === parent) {\n this._parentage = null;\n } else if (Array.isArray(_parentage)) {\n arrRemove(_parentage, parent);\n }\n }\n\n /**\n * Removes a finalizer from this subscription that was previously added with the {@link #add} method.\n *\n * Note that `Subscription` instances, when unsubscribed, will automatically remove themselves\n * from every other `Subscription` they have been added to. This means that using the `remove` method\n * is not a common thing and should be used thoughtfully.\n *\n * If you add the same finalizer instance of a function or an unsubscribable object to a `Subscription` instance\n * more than once, you will need to call `remove` the same number of times to remove all instances.\n *\n * All finalizer instances are removed to free up memory upon unsubscription.\n *\n * @param teardown The finalizer to remove from this subscription\n */\n remove(teardown: Exclude): void {\n const { _finalizers } = this;\n _finalizers && arrRemove(_finalizers, teardown);\n\n if (teardown instanceof Subscription) {\n teardown._removeParent(this);\n }\n }\n}\n\nexport const EMPTY_SUBSCRIPTION = Subscription.EMPTY;\n\nexport function isSubscription(value: any): value is Subscription {\n return (\n value instanceof Subscription ||\n (value && 'closed' in value && isFunction(value.remove) && isFunction(value.add) && isFunction(value.unsubscribe))\n );\n}\n\nfunction execFinalizer(finalizer: Unsubscribable | (() => void)) {\n if (isFunction(finalizer)) {\n finalizer();\n } else {\n finalizer.unsubscribe();\n }\n}\n", "import { Subscriber } from './Subscriber';\nimport { ObservableNotification } from './types';\n\n/**\n * The {@link GlobalConfig} object for RxJS. It is used to configure things\n * like how to react on unhandled errors.\n */\nexport const config: GlobalConfig = {\n onUnhandledError: null,\n onStoppedNotification: null,\n Promise: undefined,\n useDeprecatedSynchronousErrorHandling: false,\n useDeprecatedNextContext: false,\n};\n\n/**\n * The global configuration object for RxJS, used to configure things\n * like how to react on unhandled errors. Accessible via {@link config}\n * object.\n */\nexport interface GlobalConfig {\n /**\n * A registration point for unhandled errors from RxJS. These are errors that\n * cannot were not handled by consuming code in the usual subscription path. For\n * example, if you have this configured, and you subscribe to an observable without\n * providing an error handler, errors from that subscription will end up here. This\n * will _always_ be called asynchronously on another job in the runtime. This is because\n * we do not want errors thrown in this user-configured handler to interfere with the\n * behavior of the library.\n */\n onUnhandledError: ((err: any) => void) | null;\n\n /**\n * A registration point for notifications that cannot be sent to subscribers because they\n * have completed, errored or have been explicitly unsubscribed. By default, next, complete\n * and error notifications sent to stopped subscribers are noops. However, sometimes callers\n * might want a different behavior. For example, with sources that attempt to report errors\n * to stopped subscribers, a caller can configure RxJS to throw an unhandled error instead.\n * This will _always_ be called asynchronously on another job in the runtime. This is because\n * we do not want errors thrown in this user-configured handler to interfere with the\n * behavior of the library.\n */\n onStoppedNotification: ((notification: ObservableNotification, subscriber: Subscriber) => void) | null;\n\n /**\n * The promise constructor used by default for {@link Observable#toPromise toPromise} and {@link Observable#forEach forEach}\n * methods.\n *\n * @deprecated As of version 8, RxJS will no longer support this sort of injection of a\n * Promise constructor. If you need a Promise implementation other than native promises,\n * please polyfill/patch Promise as you see appropriate. Will be removed in v8.\n */\n Promise?: PromiseConstructorLike;\n\n /**\n * If true, turns on synchronous error rethrowing, which is a deprecated behavior\n * in v6 and higher. This behavior enables bad patterns like wrapping a subscribe\n * call in a try/catch block. It also enables producer interference, a nasty bug\n * where a multicast can be broken for all observers by a downstream consumer with\n * an unhandled error. DO NOT USE THIS FLAG UNLESS IT'S NEEDED TO BUY TIME\n * FOR MIGRATION REASONS.\n *\n * @deprecated As of version 8, RxJS will no longer support synchronous throwing\n * of unhandled errors. All errors will be thrown on a separate call stack to prevent bad\n * behaviors described above. Will be removed in v8.\n */\n useDeprecatedSynchronousErrorHandling: boolean;\n\n /**\n * If true, enables an as-of-yet undocumented feature from v5: The ability to access\n * `unsubscribe()` via `this` context in `next` functions created in observers passed\n * to `subscribe`.\n *\n * This is being removed because the performance was severely problematic, and it could also cause\n * issues when types other than POJOs are passed to subscribe as subscribers, as they will likely have\n * their `this` context overwritten.\n *\n * @deprecated As of version 8, RxJS will no longer support altering the\n * context of next functions provided as part of an observer to Subscribe. Instead,\n * you will have access to a subscription or a signal or token that will allow you to do things like\n * unsubscribe and test closed status. Will be removed in v8.\n */\n useDeprecatedNextContext: boolean;\n}\n", "import type { TimerHandle } from './timerHandle';\ntype SetTimeoutFunction = (handler: () => void, timeout?: number, ...args: any[]) => TimerHandle;\ntype ClearTimeoutFunction = (handle: TimerHandle) => void;\n\ninterface TimeoutProvider {\n setTimeout: SetTimeoutFunction;\n clearTimeout: ClearTimeoutFunction;\n delegate:\n | {\n setTimeout: SetTimeoutFunction;\n clearTimeout: ClearTimeoutFunction;\n }\n | undefined;\n}\n\nexport const timeoutProvider: TimeoutProvider = {\n // When accessing the delegate, use the variable rather than `this` so that\n // the functions can be called without being bound to the provider.\n setTimeout(handler: () => void, timeout?: number, ...args) {\n const { delegate } = timeoutProvider;\n if (delegate?.setTimeout) {\n return delegate.setTimeout(handler, timeout, ...args);\n }\n return setTimeout(handler, timeout, ...args);\n },\n clearTimeout(handle) {\n const { delegate } = timeoutProvider;\n return (delegate?.clearTimeout || clearTimeout)(handle as any);\n },\n delegate: undefined,\n};\n", "import { config } from '../config';\nimport { timeoutProvider } from '../scheduler/timeoutProvider';\n\n/**\n * Handles an error on another job either with the user-configured {@link onUnhandledError},\n * or by throwing it on that new job so it can be picked up by `window.onerror`, `process.on('error')`, etc.\n *\n * This should be called whenever there is an error that is out-of-band with the subscription\n * or when an error hits a terminal boundary of the subscription and no error handler was provided.\n *\n * @param err the error to report\n */\nexport function reportUnhandledError(err: any) {\n timeoutProvider.setTimeout(() => {\n const { onUnhandledError } = config;\n if (onUnhandledError) {\n // Execute the user-configured error handler.\n onUnhandledError(err);\n } else {\n // Throw so it is picked up by the runtime's uncaught error mechanism.\n throw err;\n }\n });\n}\n", "/* tslint:disable:no-empty */\nexport function noop() { }\n", "import { CompleteNotification, NextNotification, ErrorNotification } from './types';\n\n/**\n * A completion object optimized for memory use and created to be the\n * same \"shape\" as other notifications in v8.\n * @internal\n */\nexport const COMPLETE_NOTIFICATION = (() => createNotification('C', undefined, undefined) as CompleteNotification)();\n\n/**\n * Internal use only. Creates an optimized error notification that is the same \"shape\"\n * as other notifications.\n * @internal\n */\nexport function errorNotification(error: any): ErrorNotification {\n return createNotification('E', undefined, error) as any;\n}\n\n/**\n * Internal use only. Creates an optimized next notification that is the same \"shape\"\n * as other notifications.\n * @internal\n */\nexport function nextNotification(value: T) {\n return createNotification('N', value, undefined) as NextNotification;\n}\n\n/**\n * Ensures that all notifications created internally have the same \"shape\" in v8.\n *\n * TODO: This is only exported to support a crazy legacy test in `groupBy`.\n * @internal\n */\nexport function createNotification(kind: 'N' | 'E' | 'C', value: any, error: any) {\n return {\n kind,\n value,\n error,\n };\n}\n", "import { config } from '../config';\n\nlet context: { errorThrown: boolean; error: any } | null = null;\n\n/**\n * Handles dealing with errors for super-gross mode. Creates a context, in which\n * any synchronously thrown errors will be passed to {@link captureError}. Which\n * will record the error such that it will be rethrown after the call back is complete.\n * TODO: Remove in v8\n * @param cb An immediately executed function.\n */\nexport function errorContext(cb: () => void) {\n if (config.useDeprecatedSynchronousErrorHandling) {\n const isRoot = !context;\n if (isRoot) {\n context = { errorThrown: false, error: null };\n }\n cb();\n if (isRoot) {\n const { errorThrown, error } = context!;\n context = null;\n if (errorThrown) {\n throw error;\n }\n }\n } else {\n // This is the general non-deprecated path for everyone that\n // isn't crazy enough to use super-gross mode (useDeprecatedSynchronousErrorHandling)\n cb();\n }\n}\n\n/**\n * Captures errors only in super-gross mode.\n * @param err the error to capture\n */\nexport function captureError(err: any) {\n if (config.useDeprecatedSynchronousErrorHandling && context) {\n context.errorThrown = true;\n context.error = err;\n }\n}\n", "import { isFunction } from './util/isFunction';\nimport { Observer, ObservableNotification } from './types';\nimport { isSubscription, Subscription } from './Subscription';\nimport { config } from './config';\nimport { reportUnhandledError } from './util/reportUnhandledError';\nimport { noop } from './util/noop';\nimport { nextNotification, errorNotification, COMPLETE_NOTIFICATION } from './NotificationFactories';\nimport { timeoutProvider } from './scheduler/timeoutProvider';\nimport { captureError } from './util/errorContext';\n\n/**\n * Implements the {@link Observer} interface and extends the\n * {@link Subscription} class. While the {@link Observer} is the public API for\n * consuming the values of an {@link Observable}, all Observers get converted to\n * a Subscriber, in order to provide Subscription-like capabilities such as\n * `unsubscribe`. Subscriber is a common type in RxJS, and crucial for\n * implementing operators, but it is rarely used as a public API.\n *\n * @class Subscriber\n */\nexport class Subscriber extends Subscription implements Observer {\n /**\n * A static factory for a Subscriber, given a (potentially partial) definition\n * of an Observer.\n * @param next The `next` callback of an Observer.\n * @param error The `error` callback of an\n * Observer.\n * @param complete The `complete` callback of an\n * Observer.\n * @return A Subscriber wrapping the (partially defined)\n * Observer represented by the given arguments.\n * @nocollapse\n * @deprecated Do not use. Will be removed in v8. There is no replacement for this\n * method, and there is no reason to be creating instances of `Subscriber` directly.\n * If you have a specific use case, please file an issue.\n */\n static create(next?: (x?: T) => void, error?: (e?: any) => void, complete?: () => void): Subscriber {\n return new SafeSubscriber(next, error, complete);\n }\n\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n protected isStopped: boolean = false;\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n protected destination: Subscriber | Observer; // this `any` is the escape hatch to erase extra type param (e.g. R)\n\n /**\n * @deprecated Internal implementation detail, do not use directly. Will be made internal in v8.\n * There is no reason to directly create an instance of Subscriber. This type is exported for typings reasons.\n */\n constructor(destination?: Subscriber | Observer) {\n super();\n if (destination) {\n this.destination = destination;\n // Automatically chain subscriptions together here.\n // if destination is a Subscription, then it is a Subscriber.\n if (isSubscription(destination)) {\n destination.add(this);\n }\n } else {\n this.destination = EMPTY_OBSERVER;\n }\n }\n\n /**\n * The {@link Observer} callback to receive notifications of type `next` from\n * the Observable, with a value. The Observable may call this method 0 or more\n * times.\n * @param {T} [value] The `next` value.\n * @return {void}\n */\n next(value?: T): void {\n if (this.isStopped) {\n handleStoppedNotification(nextNotification(value), this);\n } else {\n this._next(value!);\n }\n }\n\n /**\n * The {@link Observer} callback to receive notifications of type `error` from\n * the Observable, with an attached `Error`. Notifies the Observer that\n * the Observable has experienced an error condition.\n * @param {any} [err] The `error` exception.\n * @return {void}\n */\n error(err?: any): void {\n if (this.isStopped) {\n handleStoppedNotification(errorNotification(err), this);\n } else {\n this.isStopped = true;\n this._error(err);\n }\n }\n\n /**\n * The {@link Observer} callback to receive a valueless notification of type\n * `complete` from the Observable. Notifies the Observer that the Observable\n * has finished sending push-based notifications.\n * @return {void}\n */\n complete(): void {\n if (this.isStopped) {\n handleStoppedNotification(COMPLETE_NOTIFICATION, this);\n } else {\n this.isStopped = true;\n this._complete();\n }\n }\n\n unsubscribe(): void {\n if (!this.closed) {\n this.isStopped = true;\n super.unsubscribe();\n this.destination = null!;\n }\n }\n\n protected _next(value: T): void {\n this.destination.next(value);\n }\n\n protected _error(err: any): void {\n try {\n this.destination.error(err);\n } finally {\n this.unsubscribe();\n }\n }\n\n protected _complete(): void {\n try {\n this.destination.complete();\n } finally {\n this.unsubscribe();\n }\n }\n}\n\n/**\n * This bind is captured here because we want to be able to have\n * compatibility with monoid libraries that tend to use a method named\n * `bind`. In particular, a library called Monio requires this.\n */\nconst _bind = Function.prototype.bind;\n\nfunction bind any>(fn: Fn, thisArg: any): Fn {\n return _bind.call(fn, thisArg);\n}\n\n/**\n * Internal optimization only, DO NOT EXPOSE.\n * @internal\n */\nclass ConsumerObserver implements Observer {\n constructor(private partialObserver: Partial>) {}\n\n next(value: T): void {\n const { partialObserver } = this;\n if (partialObserver.next) {\n try {\n partialObserver.next(value);\n } catch (error) {\n handleUnhandledError(error);\n }\n }\n }\n\n error(err: any): void {\n const { partialObserver } = this;\n if (partialObserver.error) {\n try {\n partialObserver.error(err);\n } catch (error) {\n handleUnhandledError(error);\n }\n } else {\n handleUnhandledError(err);\n }\n }\n\n complete(): void {\n const { partialObserver } = this;\n if (partialObserver.complete) {\n try {\n partialObserver.complete();\n } catch (error) {\n handleUnhandledError(error);\n }\n }\n }\n}\n\nexport class SafeSubscriber extends Subscriber {\n constructor(\n observerOrNext?: Partial> | ((value: T) => void) | null,\n error?: ((e?: any) => void) | null,\n complete?: (() => void) | null\n ) {\n super();\n\n let partialObserver: Partial>;\n if (isFunction(observerOrNext) || !observerOrNext) {\n // The first argument is a function, not an observer. The next\n // two arguments *could* be observers, or they could be empty.\n partialObserver = {\n next: (observerOrNext ?? undefined) as (((value: T) => void) | undefined),\n error: error ?? undefined,\n complete: complete ?? undefined,\n };\n } else {\n // The first argument is a partial observer.\n let context: any;\n if (this && config.useDeprecatedNextContext) {\n // This is a deprecated path that made `this.unsubscribe()` available in\n // next handler functions passed to subscribe. This only exists behind a flag\n // now, as it is *very* slow.\n context = Object.create(observerOrNext);\n context.unsubscribe = () => this.unsubscribe();\n partialObserver = {\n next: observerOrNext.next && bind(observerOrNext.next, context),\n error: observerOrNext.error && bind(observerOrNext.error, context),\n complete: observerOrNext.complete && bind(observerOrNext.complete, context),\n };\n } else {\n // The \"normal\" path. Just use the partial observer directly.\n partialObserver = observerOrNext;\n }\n }\n\n // Wrap the partial observer to ensure it's a full observer, and\n // make sure proper error handling is accounted for.\n this.destination = new ConsumerObserver(partialObserver);\n }\n}\n\nfunction handleUnhandledError(error: any) {\n if (config.useDeprecatedSynchronousErrorHandling) {\n captureError(error);\n } else {\n // Ideal path, we report this as an unhandled error,\n // which is thrown on a new call stack.\n reportUnhandledError(error);\n }\n}\n\n/**\n * An error handler used when no error handler was supplied\n * to the SafeSubscriber -- meaning no error handler was supplied\n * do the `subscribe` call on our observable.\n * @param err The error to handle\n */\nfunction defaultErrorHandler(err: any) {\n throw err;\n}\n\n/**\n * A handler for notifications that cannot be sent to a stopped subscriber.\n * @param notification The notification being sent\n * @param subscriber The stopped subscriber\n */\nfunction handleStoppedNotification(notification: ObservableNotification, subscriber: Subscriber) {\n const { onStoppedNotification } = config;\n onStoppedNotification && timeoutProvider.setTimeout(() => onStoppedNotification(notification, subscriber));\n}\n\n/**\n * The observer used as a stub for subscriptions where the user did not\n * pass any arguments to `subscribe`. Comes with the default error handling\n * behavior.\n */\nexport const EMPTY_OBSERVER: Readonly> & { closed: true } = {\n closed: true,\n next: noop,\n error: defaultErrorHandler,\n complete: noop,\n};\n", "/**\n * Symbol.observable or a string \"@@observable\". Used for interop\n *\n * @deprecated We will no longer be exporting this symbol in upcoming versions of RxJS.\n * Instead polyfill and use Symbol.observable directly *or* use https://www.npmjs.com/package/symbol-observable\n */\nexport const observable: string | symbol = (() => (typeof Symbol === 'function' && Symbol.observable) || '@@observable')();\n", "/**\n * This function takes one parameter and just returns it. Simply put,\n * this is like `(x: T): T => x`.\n *\n * ## Examples\n *\n * This is useful in some cases when using things like `mergeMap`\n *\n * ```ts\n * import { interval, take, map, range, mergeMap, identity } from 'rxjs';\n *\n * const source$ = interval(1000).pipe(take(5));\n *\n * const result$ = source$.pipe(\n * map(i => range(i)),\n * mergeMap(identity) // same as mergeMap(x => x)\n * );\n *\n * result$.subscribe({\n * next: console.log\n * });\n * ```\n *\n * Or when you want to selectively apply an operator\n *\n * ```ts\n * import { interval, take, identity } from 'rxjs';\n *\n * const shouldLimit = () => Math.random() < 0.5;\n *\n * const source$ = interval(1000);\n *\n * const result$ = source$.pipe(shouldLimit() ? take(5) : identity);\n *\n * result$.subscribe({\n * next: console.log\n * });\n * ```\n *\n * @param x Any value that is returned by this function\n * @returns The value passed as the first parameter to this function\n */\nexport function identity(x: T): T {\n return x;\n}\n", "import { identity } from './identity';\nimport { UnaryFunction } from '../types';\n\nexport function pipe(): typeof identity;\nexport function pipe(fn1: UnaryFunction): UnaryFunction;\nexport function pipe(fn1: UnaryFunction, fn2: UnaryFunction): UnaryFunction;\nexport function pipe(fn1: UnaryFunction, fn2: UnaryFunction, fn3: UnaryFunction): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction,\n fn7: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction,\n fn7: UnaryFunction,\n fn8: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction,\n fn7: UnaryFunction,\n fn8: UnaryFunction,\n fn9: UnaryFunction\n): UnaryFunction;\nexport function pipe(\n fn1: UnaryFunction,\n fn2: UnaryFunction,\n fn3: UnaryFunction,\n fn4: UnaryFunction,\n fn5: UnaryFunction,\n fn6: UnaryFunction,\n fn7: UnaryFunction,\n fn8: UnaryFunction,\n fn9: UnaryFunction,\n ...fns: UnaryFunction[]\n): UnaryFunction;\n\n/**\n * pipe() can be called on one or more functions, each of which can take one argument (\"UnaryFunction\")\n * and uses it to return a value.\n * It returns a function that takes one argument, passes it to the first UnaryFunction, and then\n * passes the result to the next one, passes that result to the next one, and so on. \n */\nexport function pipe(...fns: Array>): UnaryFunction {\n return pipeFromArray(fns);\n}\n\n/** @internal */\nexport function pipeFromArray(fns: Array>): UnaryFunction {\n if (fns.length === 0) {\n return identity as UnaryFunction;\n }\n\n if (fns.length === 1) {\n return fns[0];\n }\n\n return function piped(input: T): R {\n return fns.reduce((prev: any, fn: UnaryFunction) => fn(prev), input as any);\n };\n}\n", "import { Operator } from './Operator';\nimport { SafeSubscriber, Subscriber } from './Subscriber';\nimport { isSubscription, Subscription } from './Subscription';\nimport { TeardownLogic, OperatorFunction, Subscribable, Observer } from './types';\nimport { observable as Symbol_observable } from './symbol/observable';\nimport { pipeFromArray } from './util/pipe';\nimport { config } from './config';\nimport { isFunction } from './util/isFunction';\nimport { errorContext } from './util/errorContext';\n\n/**\n * A representation of any set of values over any amount of time. This is the most basic building block\n * of RxJS.\n *\n * @class Observable\n */\nexport class Observable implements Subscribable {\n /**\n * @deprecated Internal implementation detail, do not use directly. Will be made internal in v8.\n */\n source: Observable | undefined;\n\n /**\n * @deprecated Internal implementation detail, do not use directly. Will be made internal in v8.\n */\n operator: Operator | undefined;\n\n /**\n * @constructor\n * @param {Function} subscribe the function that is called when the Observable is\n * initially subscribed to. This function is given a Subscriber, to which new values\n * can be `next`ed, or an `error` method can be called to raise an error, or\n * `complete` can be called to notify of a successful completion.\n */\n constructor(subscribe?: (this: Observable, subscriber: Subscriber) => TeardownLogic) {\n if (subscribe) {\n this._subscribe = subscribe;\n }\n }\n\n // HACK: Since TypeScript inherits static properties too, we have to\n // fight against TypeScript here so Subject can have a different static create signature\n /**\n * Creates a new Observable by calling the Observable constructor\n * @owner Observable\n * @method create\n * @param {Function} subscribe? the subscriber function to be passed to the Observable constructor\n * @return {Observable} a new observable\n * @nocollapse\n * @deprecated Use `new Observable()` instead. Will be removed in v8.\n */\n static create: (...args: any[]) => any = (subscribe?: (subscriber: Subscriber) => TeardownLogic) => {\n return new Observable(subscribe);\n };\n\n /**\n * Creates a new Observable, with this Observable instance as the source, and the passed\n * operator defined as the new observable's operator.\n * @method lift\n * @param operator the operator defining the operation to take on the observable\n * @return a new observable with the Operator applied\n * @deprecated Internal implementation detail, do not use directly. Will be made internal in v8.\n * If you have implemented an operator using `lift`, it is recommended that you create an\n * operator by simply returning `new Observable()` directly. See \"Creating new operators from\n * scratch\" section here: https://rxjs.dev/guide/operators\n */\n lift(operator?: Operator): Observable {\n const observable = new Observable();\n observable.source = this;\n observable.operator = operator;\n return observable;\n }\n\n subscribe(observerOrNext?: Partial> | ((value: T) => void)): Subscription;\n /** @deprecated Instead of passing separate callback arguments, use an observer argument. Signatures taking separate callback arguments will be removed in v8. Details: https://rxjs.dev/deprecations/subscribe-arguments */\n subscribe(next?: ((value: T) => void) | null, error?: ((error: any) => void) | null, complete?: (() => void) | null): Subscription;\n /**\n * Invokes an execution of an Observable and registers Observer handlers for notifications it will emit.\n *\n * Use it when you have all these Observables, but still nothing is happening.\n *\n * `subscribe` is not a regular operator, but a method that calls Observable's internal `subscribe` function. It\n * might be for example a function that you passed to Observable's constructor, but most of the time it is\n * a library implementation, which defines what will be emitted by an Observable, and when it be will emitted. This means\n * that calling `subscribe` is actually the moment when Observable starts its work, not when it is created, as it is often\n * the thought.\n *\n * Apart from starting the execution of an Observable, this method allows you to listen for values\n * that an Observable emits, as well as for when it completes or errors. You can achieve this in two\n * of the following ways.\n *\n * The first way is creating an object that implements {@link Observer} interface. It should have methods\n * defined by that interface, but note that it should be just a regular JavaScript object, which you can create\n * yourself in any way you want (ES6 class, classic function constructor, object literal etc.). In particular, do\n * not attempt to use any RxJS implementation details to create Observers - you don't need them. Remember also\n * that your object does not have to implement all methods. If you find yourself creating a method that doesn't\n * do anything, you can simply omit it. Note however, if the `error` method is not provided and an error happens,\n * it will be thrown asynchronously. Errors thrown asynchronously cannot be caught using `try`/`catch`. Instead,\n * use the {@link onUnhandledError} configuration option or use a runtime handler (like `window.onerror` or\n * `process.on('error)`) to be notified of unhandled errors. Because of this, it's recommended that you provide\n * an `error` method to avoid missing thrown errors.\n *\n * The second way is to give up on Observer object altogether and simply provide callback functions in place of its methods.\n * This means you can provide three functions as arguments to `subscribe`, where the first function is equivalent\n * of a `next` method, the second of an `error` method and the third of a `complete` method. Just as in case of an Observer,\n * if you do not need to listen for something, you can omit a function by passing `undefined` or `null`,\n * since `subscribe` recognizes these functions by where they were placed in function call. When it comes\n * to the `error` function, as with an Observer, if not provided, errors emitted by an Observable will be thrown asynchronously.\n *\n * You can, however, subscribe with no parameters at all. This may be the case where you're not interested in terminal events\n * and you also handled emissions internally by using operators (e.g. using `tap`).\n *\n * Whichever style of calling `subscribe` you use, in both cases it returns a Subscription object.\n * This object allows you to call `unsubscribe` on it, which in turn will stop the work that an Observable does and will clean\n * up all resources that an Observable used. Note that cancelling a subscription will not call `complete` callback\n * provided to `subscribe` function, which is reserved for a regular completion signal that comes from an Observable.\n *\n * Remember that callbacks provided to `subscribe` are not guaranteed to be called asynchronously.\n * It is an Observable itself that decides when these functions will be called. For example {@link of}\n * by default emits all its values synchronously. Always check documentation for how given Observable\n * will behave when subscribed and if its default behavior can be modified with a `scheduler`.\n *\n * #### Examples\n *\n * Subscribe with an {@link guide/observer Observer}\n *\n * ```ts\n * import { of } from 'rxjs';\n *\n * const sumObserver = {\n * sum: 0,\n * next(value) {\n * console.log('Adding: ' + value);\n * this.sum = this.sum + value;\n * },\n * error() {\n * // We actually could just remove this method,\n * // since we do not really care about errors right now.\n * },\n * complete() {\n * console.log('Sum equals: ' + this.sum);\n * }\n * };\n *\n * of(1, 2, 3) // Synchronously emits 1, 2, 3 and then completes.\n * .subscribe(sumObserver);\n *\n * // Logs:\n * // 'Adding: 1'\n * // 'Adding: 2'\n * // 'Adding: 3'\n * // 'Sum equals: 6'\n * ```\n *\n * Subscribe with functions ({@link deprecations/subscribe-arguments deprecated})\n *\n * ```ts\n * import { of } from 'rxjs'\n *\n * let sum = 0;\n *\n * of(1, 2, 3).subscribe(\n * value => {\n * console.log('Adding: ' + value);\n * sum = sum + value;\n * },\n * undefined,\n * () => console.log('Sum equals: ' + sum)\n * );\n *\n * // Logs:\n * // 'Adding: 1'\n * // 'Adding: 2'\n * // 'Adding: 3'\n * // 'Sum equals: 6'\n * ```\n *\n * Cancel a subscription\n *\n * ```ts\n * import { interval } from 'rxjs';\n *\n * const subscription = interval(1000).subscribe({\n * next(num) {\n * console.log(num)\n * },\n * complete() {\n * // Will not be called, even when cancelling subscription.\n * console.log('completed!');\n * }\n * });\n *\n * setTimeout(() => {\n * subscription.unsubscribe();\n * console.log('unsubscribed!');\n * }, 2500);\n *\n * // Logs:\n * // 0 after 1s\n * // 1 after 2s\n * // 'unsubscribed!' after 2.5s\n * ```\n *\n * @param {Observer|Function} observerOrNext (optional) Either an observer with methods to be called,\n * or the first of three possible handlers, which is the handler for each value emitted from the subscribed\n * Observable.\n * @param {Function} error (optional) A handler for a terminal event resulting from an error. If no error handler is provided,\n * the error will be thrown asynchronously as unhandled.\n * @param {Function} complete (optional) A handler for a terminal event resulting from successful completion.\n * @return {Subscription} a subscription reference to the registered handlers\n * @method subscribe\n */\n subscribe(\n observerOrNext?: Partial> | ((value: T) => void) | null,\n error?: ((error: any) => void) | null,\n complete?: (() => void) | null\n ): Subscription {\n const subscriber = isSubscriber(observerOrNext) ? observerOrNext : new SafeSubscriber(observerOrNext, error, complete);\n\n errorContext(() => {\n const { operator, source } = this;\n subscriber.add(\n operator\n ? // We're dealing with a subscription in the\n // operator chain to one of our lifted operators.\n operator.call(subscriber, source)\n : source\n ? // If `source` has a value, but `operator` does not, something that\n // had intimate knowledge of our API, like our `Subject`, must have\n // set it. We're going to just call `_subscribe` directly.\n this._subscribe(subscriber)\n : // In all other cases, we're likely wrapping a user-provided initializer\n // function, so we need to catch errors and handle them appropriately.\n this._trySubscribe(subscriber)\n );\n });\n\n return subscriber;\n }\n\n /** @internal */\n protected _trySubscribe(sink: Subscriber): TeardownLogic {\n try {\n return this._subscribe(sink);\n } catch (err) {\n // We don't need to return anything in this case,\n // because it's just going to try to `add()` to a subscription\n // above.\n sink.error(err);\n }\n }\n\n /**\n * Used as a NON-CANCELLABLE means of subscribing to an observable, for use with\n * APIs that expect promises, like `async/await`. You cannot unsubscribe from this.\n *\n * **WARNING**: Only use this with observables you *know* will complete. If the source\n * observable does not complete, you will end up with a promise that is hung up, and\n * potentially all of the state of an async function hanging out in memory. To avoid\n * this situation, look into adding something like {@link timeout}, {@link take},\n * {@link takeWhile}, or {@link takeUntil} amongst others.\n *\n * #### Example\n *\n * ```ts\n * import { interval, take } from 'rxjs';\n *\n * const source$ = interval(1000).pipe(take(4));\n *\n * async function getTotal() {\n * let total = 0;\n *\n * await source$.forEach(value => {\n * total += value;\n * console.log('observable -> ' + value);\n * });\n *\n * return total;\n * }\n *\n * getTotal().then(\n * total => console.log('Total: ' + total)\n * );\n *\n * // Expected:\n * // 'observable -> 0'\n * // 'observable -> 1'\n * // 'observable -> 2'\n * // 'observable -> 3'\n * // 'Total: 6'\n * ```\n *\n * @param next a handler for each value emitted by the observable\n * @return a promise that either resolves on observable completion or\n * rejects with the handled error\n */\n forEach(next: (value: T) => void): Promise;\n\n /**\n * @param next a handler for each value emitted by the observable\n * @param promiseCtor a constructor function used to instantiate the Promise\n * @return a promise that either resolves on observable completion or\n * rejects with the handled error\n * @deprecated Passing a Promise constructor will no longer be available\n * in upcoming versions of RxJS. This is because it adds weight to the library, for very\n * little benefit. If you need this functionality, it is recommended that you either\n * polyfill Promise, or you create an adapter to convert the returned native promise\n * to whatever promise implementation you wanted. Will be removed in v8.\n */\n forEach(next: (value: T) => void, promiseCtor: PromiseConstructorLike): Promise;\n\n forEach(next: (value: T) => void, promiseCtor?: PromiseConstructorLike): Promise {\n promiseCtor = getPromiseCtor(promiseCtor);\n\n return new promiseCtor((resolve, reject) => {\n const subscriber = new SafeSubscriber({\n next: (value) => {\n try {\n next(value);\n } catch (err) {\n reject(err);\n subscriber.unsubscribe();\n }\n },\n error: reject,\n complete: resolve,\n });\n this.subscribe(subscriber);\n }) as Promise;\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): TeardownLogic {\n return this.source?.subscribe(subscriber);\n }\n\n /**\n * An interop point defined by the es7-observable spec https://github.com/zenparsing/es-observable\n * @method Symbol.observable\n * @return {Observable} this instance of the observable\n */\n [Symbol_observable]() {\n return this;\n }\n\n /* tslint:disable:max-line-length */\n pipe(): Observable;\n pipe(op1: OperatorFunction): Observable;\n pipe(op1: OperatorFunction, op2: OperatorFunction): Observable;\n pipe(op1: OperatorFunction, op2: OperatorFunction, op3: OperatorFunction): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction,\n op7: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction,\n op7: OperatorFunction,\n op8: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction,\n op7: OperatorFunction,\n op8: OperatorFunction,\n op9: OperatorFunction\n ): Observable;\n pipe(\n op1: OperatorFunction,\n op2: OperatorFunction,\n op3: OperatorFunction,\n op4: OperatorFunction,\n op5: OperatorFunction,\n op6: OperatorFunction,\n op7: OperatorFunction,\n op8: OperatorFunction,\n op9: OperatorFunction,\n ...operations: OperatorFunction[]\n ): Observable;\n /* tslint:enable:max-line-length */\n\n /**\n * Used to stitch together functional operators into a chain.\n * @method pipe\n * @return {Observable} the Observable result of all of the operators having\n * been called in the order they were passed in.\n *\n * ## Example\n *\n * ```ts\n * import { interval, filter, map, scan } from 'rxjs';\n *\n * interval(1000)\n * .pipe(\n * filter(x => x % 2 === 0),\n * map(x => x + x),\n * scan((acc, x) => acc + x)\n * )\n * .subscribe(x => console.log(x));\n * ```\n */\n pipe(...operations: OperatorFunction[]): Observable {\n return pipeFromArray(operations)(this);\n }\n\n /* tslint:disable:max-line-length */\n /** @deprecated Replaced with {@link firstValueFrom} and {@link lastValueFrom}. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise */\n toPromise(): Promise;\n /** @deprecated Replaced with {@link firstValueFrom} and {@link lastValueFrom}. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise */\n toPromise(PromiseCtor: typeof Promise): Promise;\n /** @deprecated Replaced with {@link firstValueFrom} and {@link lastValueFrom}. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise */\n toPromise(PromiseCtor: PromiseConstructorLike): Promise;\n /* tslint:enable:max-line-length */\n\n /**\n * Subscribe to this Observable and get a Promise resolving on\n * `complete` with the last emission (if any).\n *\n * **WARNING**: Only use this with observables you *know* will complete. If the source\n * observable does not complete, you will end up with a promise that is hung up, and\n * potentially all of the state of an async function hanging out in memory. To avoid\n * this situation, look into adding something like {@link timeout}, {@link take},\n * {@link takeWhile}, or {@link takeUntil} amongst others.\n *\n * @method toPromise\n * @param [promiseCtor] a constructor function used to instantiate\n * the Promise\n * @return A Promise that resolves with the last value emit, or\n * rejects on an error. If there were no emissions, Promise\n * resolves with undefined.\n * @deprecated Replaced with {@link firstValueFrom} and {@link lastValueFrom}. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise\n */\n toPromise(promiseCtor?: PromiseConstructorLike): Promise {\n promiseCtor = getPromiseCtor(promiseCtor);\n\n return new promiseCtor((resolve, reject) => {\n let value: T | undefined;\n this.subscribe(\n (x: T) => (value = x),\n (err: any) => reject(err),\n () => resolve(value)\n );\n }) as Promise;\n }\n}\n\n/**\n * Decides between a passed promise constructor from consuming code,\n * A default configured promise constructor, and the native promise\n * constructor and returns it. If nothing can be found, it will throw\n * an error.\n * @param promiseCtor The optional promise constructor to passed by consuming code\n */\nfunction getPromiseCtor(promiseCtor: PromiseConstructorLike | undefined) {\n return promiseCtor ?? config.Promise ?? Promise;\n}\n\nfunction isObserver(value: any): value is Observer {\n return value && isFunction(value.next) && isFunction(value.error) && isFunction(value.complete);\n}\n\nfunction isSubscriber(value: any): value is Subscriber {\n return (value && value instanceof Subscriber) || (isObserver(value) && isSubscription(value));\n}\n", "import { Observable } from '../Observable';\nimport { Subscriber } from '../Subscriber';\nimport { OperatorFunction } from '../types';\nimport { isFunction } from './isFunction';\n\n/**\n * Used to determine if an object is an Observable with a lift function.\n */\nexport function hasLift(source: any): source is { lift: InstanceType['lift'] } {\n return isFunction(source?.lift);\n}\n\n/**\n * Creates an `OperatorFunction`. Used to define operators throughout the library in a concise way.\n * @param init The logic to connect the liftedSource to the subscriber at the moment of subscription.\n */\nexport function operate(\n init: (liftedSource: Observable, subscriber: Subscriber) => (() => void) | void\n): OperatorFunction {\n return (source: Observable) => {\n if (hasLift(source)) {\n return source.lift(function (this: Subscriber, liftedSource: Observable) {\n try {\n return init(liftedSource, this);\n } catch (err) {\n this.error(err);\n }\n });\n }\n throw new TypeError('Unable to lift unknown Observable type');\n };\n}\n", "import { Subscriber } from '../Subscriber';\n\n/**\n * Creates an instance of an `OperatorSubscriber`.\n * @param destination The downstream subscriber.\n * @param onNext Handles next values, only called if this subscriber is not stopped or closed. Any\n * error that occurs in this function is caught and sent to the `error` method of this subscriber.\n * @param onError Handles errors from the subscription, any errors that occur in this handler are caught\n * and send to the `destination` error handler.\n * @param onComplete Handles completion notification from the subscription. Any errors that occur in\n * this handler are sent to the `destination` error handler.\n * @param onFinalize Additional teardown logic here. This will only be called on teardown if the\n * subscriber itself is not already closed. This is called after all other teardown logic is executed.\n */\nexport function createOperatorSubscriber(\n destination: Subscriber,\n onNext?: (value: T) => void,\n onComplete?: () => void,\n onError?: (err: any) => void,\n onFinalize?: () => void\n): Subscriber {\n return new OperatorSubscriber(destination, onNext, onComplete, onError, onFinalize);\n}\n\n/**\n * A generic helper for allowing operators to be created with a Subscriber and\n * use closures to capture necessary state from the operator function itself.\n */\nexport class OperatorSubscriber extends Subscriber {\n /**\n * Creates an instance of an `OperatorSubscriber`.\n * @param destination The downstream subscriber.\n * @param onNext Handles next values, only called if this subscriber is not stopped or closed. Any\n * error that occurs in this function is caught and sent to the `error` method of this subscriber.\n * @param onError Handles errors from the subscription, any errors that occur in this handler are caught\n * and send to the `destination` error handler.\n * @param onComplete Handles completion notification from the subscription. Any errors that occur in\n * this handler are sent to the `destination` error handler.\n * @param onFinalize Additional finalization logic here. This will only be called on finalization if the\n * subscriber itself is not already closed. This is called after all other finalization logic is executed.\n * @param shouldUnsubscribe An optional check to see if an unsubscribe call should truly unsubscribe.\n * NOTE: This currently **ONLY** exists to support the strange behavior of {@link groupBy}, where unsubscription\n * to the resulting observable does not actually disconnect from the source if there are active subscriptions\n * to any grouped observable. (DO NOT EXPOSE OR USE EXTERNALLY!!!)\n */\n constructor(\n destination: Subscriber,\n onNext?: (value: T) => void,\n onComplete?: () => void,\n onError?: (err: any) => void,\n private onFinalize?: () => void,\n private shouldUnsubscribe?: () => boolean\n ) {\n // It's important - for performance reasons - that all of this class's\n // members are initialized and that they are always initialized in the same\n // order. This will ensure that all OperatorSubscriber instances have the\n // same hidden class in V8. This, in turn, will help keep the number of\n // hidden classes involved in property accesses within the base class as\n // low as possible. If the number of hidden classes involved exceeds four,\n // the property accesses will become megamorphic and performance penalties\n // will be incurred - i.e. inline caches won't be used.\n //\n // The reasons for ensuring all instances have the same hidden class are\n // further discussed in this blog post from Benedikt Meurer:\n // https://benediktmeurer.de/2018/03/23/impact-of-polymorphism-on-component-based-frameworks-like-react/\n super(destination);\n this._next = onNext\n ? function (this: OperatorSubscriber, value: T) {\n try {\n onNext(value);\n } catch (err) {\n destination.error(err);\n }\n }\n : super._next;\n this._error = onError\n ? function (this: OperatorSubscriber, err: any) {\n try {\n onError(err);\n } catch (err) {\n // Send any errors that occur down stream.\n destination.error(err);\n } finally {\n // Ensure finalization.\n this.unsubscribe();\n }\n }\n : super._error;\n this._complete = onComplete\n ? function (this: OperatorSubscriber) {\n try {\n onComplete();\n } catch (err) {\n // Send any errors that occur down stream.\n destination.error(err);\n } finally {\n // Ensure finalization.\n this.unsubscribe();\n }\n }\n : super._complete;\n }\n\n unsubscribe() {\n if (!this.shouldUnsubscribe || this.shouldUnsubscribe()) {\n const { closed } = this;\n super.unsubscribe();\n // Execute additional teardown if we have any and we didn't already do so.\n !closed && this.onFinalize?.();\n }\n }\n}\n", "import { Subscription } from '../Subscription';\n\ninterface AnimationFrameProvider {\n schedule(callback: FrameRequestCallback): Subscription;\n requestAnimationFrame: typeof requestAnimationFrame;\n cancelAnimationFrame: typeof cancelAnimationFrame;\n delegate:\n | {\n requestAnimationFrame: typeof requestAnimationFrame;\n cancelAnimationFrame: typeof cancelAnimationFrame;\n }\n | undefined;\n}\n\nexport const animationFrameProvider: AnimationFrameProvider = {\n // When accessing the delegate, use the variable rather than `this` so that\n // the functions can be called without being bound to the provider.\n schedule(callback) {\n let request = requestAnimationFrame;\n let cancel: typeof cancelAnimationFrame | undefined = cancelAnimationFrame;\n const { delegate } = animationFrameProvider;\n if (delegate) {\n request = delegate.requestAnimationFrame;\n cancel = delegate.cancelAnimationFrame;\n }\n const handle = request((timestamp) => {\n // Clear the cancel function. The request has been fulfilled, so\n // attempting to cancel the request upon unsubscription would be\n // pointless.\n cancel = undefined;\n callback(timestamp);\n });\n return new Subscription(() => cancel?.(handle));\n },\n requestAnimationFrame(...args) {\n const { delegate } = animationFrameProvider;\n return (delegate?.requestAnimationFrame || requestAnimationFrame)(...args);\n },\n cancelAnimationFrame(...args) {\n const { delegate } = animationFrameProvider;\n return (delegate?.cancelAnimationFrame || cancelAnimationFrame)(...args);\n },\n delegate: undefined,\n};\n", "import { createErrorClass } from './createErrorClass';\n\nexport interface ObjectUnsubscribedError extends Error {}\n\nexport interface ObjectUnsubscribedErrorCtor {\n /**\n * @deprecated Internal implementation detail. Do not construct error instances.\n * Cannot be tagged as internal: https://github.com/ReactiveX/rxjs/issues/6269\n */\n new (): ObjectUnsubscribedError;\n}\n\n/**\n * An error thrown when an action is invalid because the object has been\n * unsubscribed.\n *\n * @see {@link Subject}\n * @see {@link BehaviorSubject}\n *\n * @class ObjectUnsubscribedError\n */\nexport const ObjectUnsubscribedError: ObjectUnsubscribedErrorCtor = createErrorClass(\n (_super) =>\n function ObjectUnsubscribedErrorImpl(this: any) {\n _super(this);\n this.name = 'ObjectUnsubscribedError';\n this.message = 'object unsubscribed';\n }\n);\n", "import { Operator } from './Operator';\nimport { Observable } from './Observable';\nimport { Subscriber } from './Subscriber';\nimport { Subscription, EMPTY_SUBSCRIPTION } from './Subscription';\nimport { Observer, SubscriptionLike, TeardownLogic } from './types';\nimport { ObjectUnsubscribedError } from './util/ObjectUnsubscribedError';\nimport { arrRemove } from './util/arrRemove';\nimport { errorContext } from './util/errorContext';\n\n/**\n * A Subject is a special type of Observable that allows values to be\n * multicasted to many Observers. Subjects are like EventEmitters.\n *\n * Every Subject is an Observable and an Observer. You can subscribe to a\n * Subject, and you can call next to feed values as well as error and complete.\n */\nexport class Subject extends Observable implements SubscriptionLike {\n closed = false;\n\n private currentObservers: Observer[] | null = null;\n\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n observers: Observer[] = [];\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n isStopped = false;\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n hasError = false;\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n thrownError: any = null;\n\n /**\n * Creates a \"subject\" by basically gluing an observer to an observable.\n *\n * @nocollapse\n * @deprecated Recommended you do not use. Will be removed at some point in the future. Plans for replacement still under discussion.\n */\n static create: (...args: any[]) => any = (destination: Observer, source: Observable): AnonymousSubject => {\n return new AnonymousSubject(destination, source);\n };\n\n constructor() {\n // NOTE: This must be here to obscure Observable's constructor.\n super();\n }\n\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n lift(operator: Operator): Observable {\n const subject = new AnonymousSubject(this, this);\n subject.operator = operator as any;\n return subject as any;\n }\n\n /** @internal */\n protected _throwIfClosed() {\n if (this.closed) {\n throw new ObjectUnsubscribedError();\n }\n }\n\n next(value: T) {\n errorContext(() => {\n this._throwIfClosed();\n if (!this.isStopped) {\n if (!this.currentObservers) {\n this.currentObservers = Array.from(this.observers);\n }\n for (const observer of this.currentObservers) {\n observer.next(value);\n }\n }\n });\n }\n\n error(err: any) {\n errorContext(() => {\n this._throwIfClosed();\n if (!this.isStopped) {\n this.hasError = this.isStopped = true;\n this.thrownError = err;\n const { observers } = this;\n while (observers.length) {\n observers.shift()!.error(err);\n }\n }\n });\n }\n\n complete() {\n errorContext(() => {\n this._throwIfClosed();\n if (!this.isStopped) {\n this.isStopped = true;\n const { observers } = this;\n while (observers.length) {\n observers.shift()!.complete();\n }\n }\n });\n }\n\n unsubscribe() {\n this.isStopped = this.closed = true;\n this.observers = this.currentObservers = null!;\n }\n\n get observed() {\n return this.observers?.length > 0;\n }\n\n /** @internal */\n protected _trySubscribe(subscriber: Subscriber): TeardownLogic {\n this._throwIfClosed();\n return super._trySubscribe(subscriber);\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): Subscription {\n this._throwIfClosed();\n this._checkFinalizedStatuses(subscriber);\n return this._innerSubscribe(subscriber);\n }\n\n /** @internal */\n protected _innerSubscribe(subscriber: Subscriber) {\n const { hasError, isStopped, observers } = this;\n if (hasError || isStopped) {\n return EMPTY_SUBSCRIPTION;\n }\n this.currentObservers = null;\n observers.push(subscriber);\n return new Subscription(() => {\n this.currentObservers = null;\n arrRemove(observers, subscriber);\n });\n }\n\n /** @internal */\n protected _checkFinalizedStatuses(subscriber: Subscriber) {\n const { hasError, thrownError, isStopped } = this;\n if (hasError) {\n subscriber.error(thrownError);\n } else if (isStopped) {\n subscriber.complete();\n }\n }\n\n /**\n * Creates a new Observable with this Subject as the source. You can do this\n * to create custom Observer-side logic of the Subject and conceal it from\n * code that uses the Observable.\n * @return {Observable} Observable that the Subject casts to\n */\n asObservable(): Observable {\n const observable: any = new Observable();\n observable.source = this;\n return observable;\n }\n}\n\n/**\n * @class AnonymousSubject\n */\nexport class AnonymousSubject extends Subject {\n constructor(\n /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */\n public destination?: Observer,\n source?: Observable\n ) {\n super();\n this.source = source;\n }\n\n next(value: T) {\n this.destination?.next?.(value);\n }\n\n error(err: any) {\n this.destination?.error?.(err);\n }\n\n complete() {\n this.destination?.complete?.();\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): Subscription {\n return this.source?.subscribe(subscriber) ?? EMPTY_SUBSCRIPTION;\n }\n}\n", "import { Subject } from './Subject';\nimport { Subscriber } from './Subscriber';\nimport { Subscription } from './Subscription';\n\n/**\n * A variant of Subject that requires an initial value and emits its current\n * value whenever it is subscribed to.\n *\n * @class BehaviorSubject\n */\nexport class BehaviorSubject extends Subject {\n constructor(private _value: T) {\n super();\n }\n\n get value(): T {\n return this.getValue();\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): Subscription {\n const subscription = super._subscribe(subscriber);\n !subscription.closed && subscriber.next(this._value);\n return subscription;\n }\n\n getValue(): T {\n const { hasError, thrownError, _value } = this;\n if (hasError) {\n throw thrownError;\n }\n this._throwIfClosed();\n return _value;\n }\n\n next(value: T): void {\n super.next((this._value = value));\n }\n}\n", "import { TimestampProvider } from '../types';\n\ninterface DateTimestampProvider extends TimestampProvider {\n delegate: TimestampProvider | undefined;\n}\n\nexport const dateTimestampProvider: DateTimestampProvider = {\n now() {\n // Use the variable rather than `this` so that the function can be called\n // without being bound to the provider.\n return (dateTimestampProvider.delegate || Date).now();\n },\n delegate: undefined,\n};\n", "import { Subject } from './Subject';\nimport { TimestampProvider } from './types';\nimport { Subscriber } from './Subscriber';\nimport { Subscription } from './Subscription';\nimport { dateTimestampProvider } from './scheduler/dateTimestampProvider';\n\n/**\n * A variant of {@link Subject} that \"replays\" old values to new subscribers by emitting them when they first subscribe.\n *\n * `ReplaySubject` has an internal buffer that will store a specified number of values that it has observed. Like `Subject`,\n * `ReplaySubject` \"observes\" values by having them passed to its `next` method. When it observes a value, it will store that\n * value for a time determined by the configuration of the `ReplaySubject`, as passed to its constructor.\n *\n * When a new subscriber subscribes to the `ReplaySubject` instance, it will synchronously emit all values in its buffer in\n * a First-In-First-Out (FIFO) manner. The `ReplaySubject` will also complete, if it has observed completion; and it will\n * error if it has observed an error.\n *\n * There are two main configuration items to be concerned with:\n *\n * 1. `bufferSize` - This will determine how many items are stored in the buffer, defaults to infinite.\n * 2. `windowTime` - The amount of time to hold a value in the buffer before removing it from the buffer.\n *\n * Both configurations may exist simultaneously. So if you would like to buffer a maximum of 3 values, as long as the values\n * are less than 2 seconds old, you could do so with a `new ReplaySubject(3, 2000)`.\n *\n * ### Differences with BehaviorSubject\n *\n * `BehaviorSubject` is similar to `new ReplaySubject(1)`, with a couple of exceptions:\n *\n * 1. `BehaviorSubject` comes \"primed\" with a single value upon construction.\n * 2. `ReplaySubject` will replay values, even after observing an error, where `BehaviorSubject` will not.\n *\n * @see {@link Subject}\n * @see {@link BehaviorSubject}\n * @see {@link shareReplay}\n */\nexport class ReplaySubject extends Subject {\n private _buffer: (T | number)[] = [];\n private _infiniteTimeWindow = true;\n\n /**\n * @param bufferSize The size of the buffer to replay on subscription\n * @param windowTime The amount of time the buffered items will stay buffered\n * @param timestampProvider An object with a `now()` method that provides the current timestamp. This is used to\n * calculate the amount of time something has been buffered.\n */\n constructor(\n private _bufferSize = Infinity,\n private _windowTime = Infinity,\n private _timestampProvider: TimestampProvider = dateTimestampProvider\n ) {\n super();\n this._infiniteTimeWindow = _windowTime === Infinity;\n this._bufferSize = Math.max(1, _bufferSize);\n this._windowTime = Math.max(1, _windowTime);\n }\n\n next(value: T): void {\n const { isStopped, _buffer, _infiniteTimeWindow, _timestampProvider, _windowTime } = this;\n if (!isStopped) {\n _buffer.push(value);\n !_infiniteTimeWindow && _buffer.push(_timestampProvider.now() + _windowTime);\n }\n this._trimBuffer();\n super.next(value);\n }\n\n /** @internal */\n protected _subscribe(subscriber: Subscriber): Subscription {\n this._throwIfClosed();\n this._trimBuffer();\n\n const subscription = this._innerSubscribe(subscriber);\n\n const { _infiniteTimeWindow, _buffer } = this;\n // We use a copy here, so reentrant code does not mutate our array while we're\n // emitting it to a new subscriber.\n const copy = _buffer.slice();\n for (let i = 0; i < copy.length && !subscriber.closed; i += _infiniteTimeWindow ? 1 : 2) {\n subscriber.next(copy[i] as T);\n }\n\n this._checkFinalizedStatuses(subscriber);\n\n return subscription;\n }\n\n private _trimBuffer() {\n const { _bufferSize, _timestampProvider, _buffer, _infiniteTimeWindow } = this;\n // If we don't have an infinite buffer size, and we're over the length,\n // use splice to truncate the old buffer values off. Note that we have to\n // double the size for instances where we're not using an infinite time window\n // because we're storing the values and the timestamps in the same array.\n const adjustedBufferSize = (_infiniteTimeWindow ? 1 : 2) * _bufferSize;\n _bufferSize < Infinity && adjustedBufferSize < _buffer.length && _buffer.splice(0, _buffer.length - adjustedBufferSize);\n\n // Now, if we're not in an infinite time window, remove all values where the time is\n // older than what is allowed.\n if (!_infiniteTimeWindow) {\n const now = _timestampProvider.now();\n let last = 0;\n // Search the array for the first timestamp that isn't expired and\n // truncate the buffer up to that point.\n for (let i = 1; i < _buffer.length && (_buffer[i] as number) <= now; i += 2) {\n last = i;\n }\n last && _buffer.splice(0, last + 1);\n }\n }\n}\n", "import { Scheduler } from '../Scheduler';\nimport { Subscription } from '../Subscription';\nimport { SchedulerAction } from '../types';\n\n/**\n * A unit of work to be executed in a `scheduler`. An action is typically\n * created from within a {@link SchedulerLike} and an RxJS user does not need to concern\n * themselves about creating and manipulating an Action.\n *\n * ```ts\n * class Action extends Subscription {\n * new (scheduler: Scheduler, work: (state?: T) => void);\n * schedule(state?: T, delay: number = 0): Subscription;\n * }\n * ```\n *\n * @class Action\n */\nexport class Action extends Subscription {\n constructor(scheduler: Scheduler, work: (this: SchedulerAction, state?: T) => void) {\n super();\n }\n /**\n * Schedules this action on its parent {@link SchedulerLike} for execution. May be passed\n * some context object, `state`. May happen at some point in the future,\n * according to the `delay` parameter, if specified.\n * @param {T} [state] Some contextual data that the `work` function uses when\n * called by the Scheduler.\n * @param {number} [delay] Time to wait before executing the work, where the\n * time unit is implicit and defined by the Scheduler.\n * @return {void}\n */\n public schedule(state?: T, delay: number = 0): Subscription {\n return this;\n }\n}\n", "import type { TimerHandle } from './timerHandle';\ntype SetIntervalFunction = (handler: () => void, timeout?: number, ...args: any[]) => TimerHandle;\ntype ClearIntervalFunction = (handle: TimerHandle) => void;\n\ninterface IntervalProvider {\n setInterval: SetIntervalFunction;\n clearInterval: ClearIntervalFunction;\n delegate:\n | {\n setInterval: SetIntervalFunction;\n clearInterval: ClearIntervalFunction;\n }\n | undefined;\n}\n\nexport const intervalProvider: IntervalProvider = {\n // When accessing the delegate, use the variable rather than `this` so that\n // the functions can be called without being bound to the provider.\n setInterval(handler: () => void, timeout?: number, ...args) {\n const { delegate } = intervalProvider;\n if (delegate?.setInterval) {\n return delegate.setInterval(handler, timeout, ...args);\n }\n return setInterval(handler, timeout, ...args);\n },\n clearInterval(handle) {\n const { delegate } = intervalProvider;\n return (delegate?.clearInterval || clearInterval)(handle as any);\n },\n delegate: undefined,\n};\n", "import { Action } from './Action';\nimport { SchedulerAction } from '../types';\nimport { Subscription } from '../Subscription';\nimport { AsyncScheduler } from './AsyncScheduler';\nimport { intervalProvider } from './intervalProvider';\nimport { arrRemove } from '../util/arrRemove';\nimport { TimerHandle } from './timerHandle';\n\nexport class AsyncAction extends Action {\n public id: TimerHandle | undefined;\n public state?: T;\n // @ts-ignore: Property has no initializer and is not definitely assigned\n public delay: number;\n protected pending: boolean = false;\n\n constructor(protected scheduler: AsyncScheduler, protected work: (this: SchedulerAction, state?: T) => void) {\n super(scheduler, work);\n }\n\n public schedule(state?: T, delay: number = 0): Subscription {\n if (this.closed) {\n return this;\n }\n\n // Always replace the current state with the new state.\n this.state = state;\n\n const id = this.id;\n const scheduler = this.scheduler;\n\n //\n // Important implementation note:\n //\n // Actions only execute once by default, unless rescheduled from within the\n // scheduled callback. This allows us to implement single and repeat\n // actions via the same code path, without adding API surface area, as well\n // as mimic traditional recursion but across asynchronous boundaries.\n //\n // However, JS runtimes and timers distinguish between intervals achieved by\n // serial `setTimeout` calls vs. a single `setInterval` call. An interval of\n // serial `setTimeout` calls can be individually delayed, which delays\n // scheduling the next `setTimeout`, and so on. `setInterval` attempts to\n // guarantee the interval callback will be invoked more precisely to the\n // interval period, regardless of load.\n //\n // Therefore, we use `setInterval` to schedule single and repeat actions.\n // If the action reschedules itself with the same delay, the interval is not\n // canceled. If the action doesn't reschedule, or reschedules with a\n // different delay, the interval will be canceled after scheduled callback\n // execution.\n //\n if (id != null) {\n this.id = this.recycleAsyncId(scheduler, id, delay);\n }\n\n // Set the pending flag indicating that this action has been scheduled, or\n // has recursively rescheduled itself.\n this.pending = true;\n\n this.delay = delay;\n // If this action has already an async Id, don't request a new one.\n this.id = this.id ?? this.requestAsyncId(scheduler, this.id, delay);\n\n return this;\n }\n\n protected requestAsyncId(scheduler: AsyncScheduler, _id?: TimerHandle, delay: number = 0): TimerHandle {\n return intervalProvider.setInterval(scheduler.flush.bind(scheduler, this), delay);\n }\n\n protected recycleAsyncId(_scheduler: AsyncScheduler, id?: TimerHandle, delay: number | null = 0): TimerHandle | undefined {\n // If this action is rescheduled with the same delay time, don't clear the interval id.\n if (delay != null && this.delay === delay && this.pending === false) {\n return id;\n }\n // Otherwise, if the action's delay time is different from the current delay,\n // or the action has been rescheduled before it's executed, clear the interval id\n if (id != null) {\n intervalProvider.clearInterval(id);\n }\n\n return undefined;\n }\n\n /**\n * Immediately executes this action and the `work` it contains.\n * @return {any}\n */\n public execute(state: T, delay: number): any {\n if (this.closed) {\n return new Error('executing a cancelled action');\n }\n\n this.pending = false;\n const error = this._execute(state, delay);\n if (error) {\n return error;\n } else if (this.pending === false && this.id != null) {\n // Dequeue if the action didn't reschedule itself. Don't call\n // unsubscribe(), because the action could reschedule later.\n // For example:\n // ```\n // scheduler.schedule(function doWork(counter) {\n // /* ... I'm a busy worker bee ... */\n // var originalAction = this;\n // /* wait 100ms before rescheduling the action */\n // setTimeout(function () {\n // originalAction.schedule(counter + 1);\n // }, 100);\n // }, 1000);\n // ```\n this.id = this.recycleAsyncId(this.scheduler, this.id, null);\n }\n }\n\n protected _execute(state: T, _delay: number): any {\n let errored: boolean = false;\n let errorValue: any;\n try {\n this.work(state);\n } catch (e) {\n errored = true;\n // HACK: Since code elsewhere is relying on the \"truthiness\" of the\n // return here, we can't have it return \"\" or 0 or false.\n // TODO: Clean this up when we refactor schedulers mid-version-8 or so.\n errorValue = e ? e : new Error('Scheduled action threw falsy error');\n }\n if (errored) {\n this.unsubscribe();\n return errorValue;\n }\n }\n\n unsubscribe() {\n if (!this.closed) {\n const { id, scheduler } = this;\n const { actions } = scheduler;\n\n this.work = this.state = this.scheduler = null!;\n this.pending = false;\n\n arrRemove(actions, this);\n if (id != null) {\n this.id = this.recycleAsyncId(scheduler, id, null);\n }\n\n this.delay = null!;\n super.unsubscribe();\n }\n }\n}\n", "import { Action } from './scheduler/Action';\nimport { Subscription } from './Subscription';\nimport { SchedulerLike, SchedulerAction } from './types';\nimport { dateTimestampProvider } from './scheduler/dateTimestampProvider';\n\n/**\n * An execution context and a data structure to order tasks and schedule their\n * execution. Provides a notion of (potentially virtual) time, through the\n * `now()` getter method.\n *\n * Each unit of work in a Scheduler is called an `Action`.\n *\n * ```ts\n * class Scheduler {\n * now(): number;\n * schedule(work, delay?, state?): Subscription;\n * }\n * ```\n *\n * @class Scheduler\n * @deprecated Scheduler is an internal implementation detail of RxJS, and\n * should not be used directly. Rather, create your own class and implement\n * {@link SchedulerLike}. Will be made internal in v8.\n */\nexport class Scheduler implements SchedulerLike {\n public static now: () => number = dateTimestampProvider.now;\n\n constructor(private schedulerActionCtor: typeof Action, now: () => number = Scheduler.now) {\n this.now = now;\n }\n\n /**\n * A getter method that returns a number representing the current time\n * (at the time this function was called) according to the scheduler's own\n * internal clock.\n * @return {number} A number that represents the current time. May or may not\n * have a relation to wall-clock time. May or may not refer to a time unit\n * (e.g. milliseconds).\n */\n public now: () => number;\n\n /**\n * Schedules a function, `work`, for execution. May happen at some point in\n * the future, according to the `delay` parameter, if specified. May be passed\n * some context object, `state`, which will be passed to the `work` function.\n *\n * The given arguments will be processed an stored as an Action object in a\n * queue of actions.\n *\n * @param {function(state: ?T): ?Subscription} work A function representing a\n * task, or some unit of work to be executed by the Scheduler.\n * @param {number} [delay] Time to wait before executing the work, where the\n * time unit is implicit and defined by the Scheduler itself.\n * @param {T} [state] Some contextual data that the `work` function uses when\n * called by the Scheduler.\n * @return {Subscription} A subscription in order to be able to unsubscribe\n * the scheduled work.\n */\n public schedule(work: (this: SchedulerAction, state?: T) => void, delay: number = 0, state?: T): Subscription {\n return new this.schedulerActionCtor(this, work).schedule(state, delay);\n }\n}\n", "import { Scheduler } from '../Scheduler';\nimport { Action } from './Action';\nimport { AsyncAction } from './AsyncAction';\nimport { TimerHandle } from './timerHandle';\n\nexport class AsyncScheduler extends Scheduler {\n public actions: Array> = [];\n /**\n * A flag to indicate whether the Scheduler is currently executing a batch of\n * queued actions.\n * @type {boolean}\n * @internal\n */\n public _active: boolean = false;\n /**\n * An internal ID used to track the latest asynchronous task such as those\n * coming from `setTimeout`, `setInterval`, `requestAnimationFrame`, and\n * others.\n * @type {any}\n * @internal\n */\n public _scheduled: TimerHandle | undefined;\n\n constructor(SchedulerAction: typeof Action, now: () => number = Scheduler.now) {\n super(SchedulerAction, now);\n }\n\n public flush(action: AsyncAction): void {\n const { actions } = this;\n\n if (this._active) {\n actions.push(action);\n return;\n }\n\n let error: any;\n this._active = true;\n\n do {\n if ((error = action.execute(action.state, action.delay))) {\n break;\n }\n } while ((action = actions.shift()!)); // exhaust the scheduler queue\n\n this._active = false;\n\n if (error) {\n while ((action = actions.shift()!)) {\n action.unsubscribe();\n }\n throw error;\n }\n }\n}\n", "import { AsyncAction } from './AsyncAction';\nimport { AsyncScheduler } from './AsyncScheduler';\n\n/**\n *\n * Async Scheduler\n *\n * Schedule task as if you used setTimeout(task, duration)\n *\n * `async` scheduler schedules tasks asynchronously, by putting them on the JavaScript\n * event loop queue. It is best used to delay tasks in time or to schedule tasks repeating\n * in intervals.\n *\n * If you just want to \"defer\" task, that is to perform it right after currently\n * executing synchronous code ends (commonly achieved by `setTimeout(deferredTask, 0)`),\n * better choice will be the {@link asapScheduler} scheduler.\n *\n * ## Examples\n * Use async scheduler to delay task\n * ```ts\n * import { asyncScheduler } from 'rxjs';\n *\n * const task = () => console.log('it works!');\n *\n * asyncScheduler.schedule(task, 2000);\n *\n * // After 2 seconds logs:\n * // \"it works!\"\n * ```\n *\n * Use async scheduler to repeat task in intervals\n * ```ts\n * import { asyncScheduler } from 'rxjs';\n *\n * function task(state) {\n * console.log(state);\n * this.schedule(state + 1, 1000); // `this` references currently executing Action,\n * // which we reschedule with new state and delay\n * }\n *\n * asyncScheduler.schedule(task, 3000, 0);\n *\n * // Logs:\n * // 0 after 3s\n * // 1 after 4s\n * // 2 after 5s\n * // 3 after 6s\n * ```\n */\n\nexport const asyncScheduler = new AsyncScheduler(AsyncAction);\n\n/**\n * @deprecated Renamed to {@link asyncScheduler}. Will be removed in v8.\n */\nexport const async = asyncScheduler;\n", "import { AsyncAction } from './AsyncAction';\nimport { Subscription } from '../Subscription';\nimport { QueueScheduler } from './QueueScheduler';\nimport { SchedulerAction } from '../types';\nimport { TimerHandle } from './timerHandle';\n\nexport class QueueAction extends AsyncAction {\n constructor(protected scheduler: QueueScheduler, protected work: (this: SchedulerAction, state?: T) => void) {\n super(scheduler, work);\n }\n\n public schedule(state?: T, delay: number = 0): Subscription {\n if (delay > 0) {\n return super.schedule(state, delay);\n }\n this.delay = delay;\n this.state = state;\n this.scheduler.flush(this);\n return this;\n }\n\n public execute(state: T, delay: number): any {\n return delay > 0 || this.closed ? super.execute(state, delay) : this._execute(state, delay);\n }\n\n protected requestAsyncId(scheduler: QueueScheduler, id?: TimerHandle, delay: number = 0): TimerHandle {\n // If delay exists and is greater than 0, or if the delay is null (the\n // action wasn't rescheduled) but was originally scheduled as an async\n // action, then recycle as an async action.\n\n if ((delay != null && delay > 0) || (delay == null && this.delay > 0)) {\n return super.requestAsyncId(scheduler, id, delay);\n }\n\n // Otherwise flush the scheduler starting with this action.\n scheduler.flush(this);\n\n // HACK: In the past, this was returning `void`. However, `void` isn't a valid\n // `TimerHandle`, and generally the return value here isn't really used. So the\n // compromise is to return `0` which is both \"falsy\" and a valid `TimerHandle`,\n // as opposed to refactoring every other instanceo of `requestAsyncId`.\n return 0;\n }\n}\n", "import { AsyncScheduler } from './AsyncScheduler';\n\nexport class QueueScheduler extends AsyncScheduler {\n}\n", "import { QueueAction } from './QueueAction';\nimport { QueueScheduler } from './QueueScheduler';\n\n/**\n *\n * Queue Scheduler\n *\n * Put every next task on a queue, instead of executing it immediately\n *\n * `queue` scheduler, when used with delay, behaves the same as {@link asyncScheduler} scheduler.\n *\n * When used without delay, it schedules given task synchronously - executes it right when\n * it is scheduled. However when called recursively, that is when inside the scheduled task,\n * another task is scheduled with queue scheduler, instead of executing immediately as well,\n * that task will be put on a queue and wait for current one to finish.\n *\n * This means that when you execute task with `queue` scheduler, you are sure it will end\n * before any other task scheduled with that scheduler will start.\n *\n * ## Examples\n * Schedule recursively first, then do something\n * ```ts\n * import { queueScheduler } from 'rxjs';\n *\n * queueScheduler.schedule(() => {\n * queueScheduler.schedule(() => console.log('second')); // will not happen now, but will be put on a queue\n *\n * console.log('first');\n * });\n *\n * // Logs:\n * // \"first\"\n * // \"second\"\n * ```\n *\n * Reschedule itself recursively\n * ```ts\n * import { queueScheduler } from 'rxjs';\n *\n * queueScheduler.schedule(function(state) {\n * if (state !== 0) {\n * console.log('before', state);\n * this.schedule(state - 1); // `this` references currently executing Action,\n * // which we reschedule with new state\n * console.log('after', state);\n * }\n * }, 0, 3);\n *\n * // In scheduler that runs recursively, you would expect:\n * // \"before\", 3\n * // \"before\", 2\n * // \"before\", 1\n * // \"after\", 1\n * // \"after\", 2\n * // \"after\", 3\n *\n * // But with queue it logs:\n * // \"before\", 3\n * // \"after\", 3\n * // \"before\", 2\n * // \"after\", 2\n * // \"before\", 1\n * // \"after\", 1\n * ```\n */\n\nexport const queueScheduler = new QueueScheduler(QueueAction);\n\n/**\n * @deprecated Renamed to {@link queueScheduler}. Will be removed in v8.\n */\nexport const queue = queueScheduler;\n", "import { AsyncAction } from './AsyncAction';\nimport { AnimationFrameScheduler } from './AnimationFrameScheduler';\nimport { SchedulerAction } from '../types';\nimport { animationFrameProvider } from './animationFrameProvider';\nimport { TimerHandle } from './timerHandle';\n\nexport class AnimationFrameAction extends AsyncAction {\n constructor(protected scheduler: AnimationFrameScheduler, protected work: (this: SchedulerAction, state?: T) => void) {\n super(scheduler, work);\n }\n\n protected requestAsyncId(scheduler: AnimationFrameScheduler, id?: TimerHandle, delay: number = 0): TimerHandle {\n // If delay is greater than 0, request as an async action.\n if (delay !== null && delay > 0) {\n return super.requestAsyncId(scheduler, id, delay);\n }\n // Push the action to the end of the scheduler queue.\n scheduler.actions.push(this);\n // If an animation frame has already been requested, don't request another\n // one. If an animation frame hasn't been requested yet, request one. Return\n // the current animation frame request id.\n return scheduler._scheduled || (scheduler._scheduled = animationFrameProvider.requestAnimationFrame(() => scheduler.flush(undefined)));\n }\n\n protected recycleAsyncId(scheduler: AnimationFrameScheduler, id?: TimerHandle, delay: number = 0): TimerHandle | undefined {\n // If delay exists and is greater than 0, or if the delay is null (the\n // action wasn't rescheduled) but was originally scheduled as an async\n // action, then recycle as an async action.\n if (delay != null ? delay > 0 : this.delay > 0) {\n return super.recycleAsyncId(scheduler, id, delay);\n }\n // If the scheduler queue has no remaining actions with the same async id,\n // cancel the requested animation frame and set the scheduled flag to\n // undefined so the next AnimationFrameAction will request its own.\n const { actions } = scheduler;\n if (id != null && actions[actions.length - 1]?.id !== id) {\n animationFrameProvider.cancelAnimationFrame(id as number);\n scheduler._scheduled = undefined;\n }\n // Return undefined so the action knows to request a new async id if it's rescheduled.\n return undefined;\n }\n}\n", "import { AsyncAction } from './AsyncAction';\nimport { AsyncScheduler } from './AsyncScheduler';\n\nexport class AnimationFrameScheduler extends AsyncScheduler {\n public flush(action?: AsyncAction): void {\n this._active = true;\n // The async id that effects a call to flush is stored in _scheduled.\n // Before executing an action, it's necessary to check the action's async\n // id to determine whether it's supposed to be executed in the current\n // flush.\n // Previous implementations of this method used a count to determine this,\n // but that was unsound, as actions that are unsubscribed - i.e. cancelled -\n // are removed from the actions array and that can shift actions that are\n // scheduled to be executed in a subsequent flush into positions at which\n // they are executed within the current flush.\n const flushId = this._scheduled;\n this._scheduled = undefined;\n\n const { actions } = this;\n let error: any;\n action = action || actions.shift()!;\n\n do {\n if ((error = action.execute(action.state, action.delay))) {\n break;\n }\n } while ((action = actions[0]) && action.id === flushId && actions.shift());\n\n this._active = false;\n\n if (error) {\n while ((action = actions[0]) && action.id === flushId && actions.shift()) {\n action.unsubscribe();\n }\n throw error;\n }\n }\n}\n", "import { AnimationFrameAction } from './AnimationFrameAction';\nimport { AnimationFrameScheduler } from './AnimationFrameScheduler';\n\n/**\n *\n * Animation Frame Scheduler\n *\n * Perform task when `window.requestAnimationFrame` would fire\n *\n * When `animationFrame` scheduler is used with delay, it will fall back to {@link asyncScheduler} scheduler\n * behaviour.\n *\n * Without delay, `animationFrame` scheduler can be used to create smooth browser animations.\n * It makes sure scheduled task will happen just before next browser content repaint,\n * thus performing animations as efficiently as possible.\n *\n * ## Example\n * Schedule div height animation\n * ```ts\n * // html:
\n * import { animationFrameScheduler } from 'rxjs';\n *\n * const div = document.querySelector('div');\n *\n * animationFrameScheduler.schedule(function(height) {\n * div.style.height = height + \"px\";\n *\n * this.schedule(height + 1); // `this` references currently executing Action,\n * // which we reschedule with new state\n * }, 0, 0);\n *\n * // You will see a div element growing in height\n * ```\n */\n\nexport const animationFrameScheduler = new AnimationFrameScheduler(AnimationFrameAction);\n\n/**\n * @deprecated Renamed to {@link animationFrameScheduler}. Will be removed in v8.\n */\nexport const animationFrame = animationFrameScheduler;\n", "import { Observable } from '../Observable';\nimport { SchedulerLike } from '../types';\n\n/**\n * A simple Observable that emits no items to the Observer and immediately\n * emits a complete notification.\n *\n * Just emits 'complete', and nothing else.\n *\n * ![](empty.png)\n *\n * A simple Observable that only emits the complete notification. It can be used\n * for composing with other Observables, such as in a {@link mergeMap}.\n *\n * ## Examples\n *\n * Log complete notification\n *\n * ```ts\n * import { EMPTY } from 'rxjs';\n *\n * EMPTY.subscribe({\n * next: () => console.log('Next'),\n * complete: () => console.log('Complete!')\n * });\n *\n * // Outputs\n * // Complete!\n * ```\n *\n * Emit the number 7, then complete\n *\n * ```ts\n * import { EMPTY, startWith } from 'rxjs';\n *\n * const result = EMPTY.pipe(startWith(7));\n * result.subscribe(x => console.log(x));\n *\n * // Outputs\n * // 7\n * ```\n *\n * Map and flatten only odd numbers to the sequence `'a'`, `'b'`, `'c'`\n *\n * ```ts\n * import { interval, mergeMap, of, EMPTY } from 'rxjs';\n *\n * const interval$ = interval(1000);\n * const result = interval$.pipe(\n * mergeMap(x => x % 2 === 1 ? of('a', 'b', 'c') : EMPTY),\n * );\n * result.subscribe(x => console.log(x));\n *\n * // Results in the following to the console:\n * // x is equal to the count on the interval, e.g. (0, 1, 2, 3, ...)\n * // x will occur every 1000ms\n * // if x % 2 is equal to 1, print a, b, c (each on its own)\n * // if x % 2 is not equal to 1, nothing will be output\n * ```\n *\n * @see {@link Observable}\n * @see {@link NEVER}\n * @see {@link of}\n * @see {@link throwError}\n */\nexport const EMPTY = new Observable((subscriber) => subscriber.complete());\n\n/**\n * @param scheduler A {@link SchedulerLike} to use for scheduling\n * the emission of the complete notification.\n * @deprecated Replaced with the {@link EMPTY} constant or {@link scheduled} (e.g. `scheduled([], scheduler)`). Will be removed in v8.\n */\nexport function empty(scheduler?: SchedulerLike) {\n return scheduler ? emptyScheduled(scheduler) : EMPTY;\n}\n\nfunction emptyScheduled(scheduler: SchedulerLike) {\n return new Observable((subscriber) => scheduler.schedule(() => subscriber.complete()));\n}\n", "import { SchedulerLike } from '../types';\nimport { isFunction } from './isFunction';\n\nexport function isScheduler(value: any): value is SchedulerLike {\n return value && isFunction(value.schedule);\n}\n", "import { SchedulerLike } from '../types';\nimport { isFunction } from './isFunction';\nimport { isScheduler } from './isScheduler';\n\nfunction last(arr: T[]): T | undefined {\n return arr[arr.length - 1];\n}\n\nexport function popResultSelector(args: any[]): ((...args: unknown[]) => unknown) | undefined {\n return isFunction(last(args)) ? args.pop() : undefined;\n}\n\nexport function popScheduler(args: any[]): SchedulerLike | undefined {\n return isScheduler(last(args)) ? args.pop() : undefined;\n}\n\nexport function popNumber(args: any[], defaultValue: number): number {\n return typeof last(args) === 'number' ? args.pop()! : defaultValue;\n}\n", "export const isArrayLike = ((x: any): x is ArrayLike => x && typeof x.length === 'number' && typeof x !== 'function');", "import { isFunction } from \"./isFunction\";\n\n/**\n * Tests to see if the object is \"thennable\".\n * @param value the object to test\n */\nexport function isPromise(value: any): value is PromiseLike {\n return isFunction(value?.then);\n}\n", "import { InteropObservable } from '../types';\nimport { observable as Symbol_observable } from '../symbol/observable';\nimport { isFunction } from './isFunction';\n\n/** Identifies an input as being Observable (but not necessary an Rx Observable) */\nexport function isInteropObservable(input: any): input is InteropObservable {\n return isFunction(input[Symbol_observable]);\n}\n", "import { isFunction } from './isFunction';\n\nexport function isAsyncIterable(obj: any): obj is AsyncIterable {\n return Symbol.asyncIterator && isFunction(obj?.[Symbol.asyncIterator]);\n}\n", "/**\n * Creates the TypeError to throw if an invalid object is passed to `from` or `scheduled`.\n * @param input The object that was passed.\n */\nexport function createInvalidObservableTypeError(input: any) {\n // TODO: We should create error codes that can be looked up, so this can be less verbose.\n return new TypeError(\n `You provided ${\n input !== null && typeof input === 'object' ? 'an invalid object' : `'${input}'`\n } where a stream was expected. You can provide an Observable, Promise, ReadableStream, Array, AsyncIterable, or Iterable.`\n );\n}\n", "export function getSymbolIterator(): symbol {\n if (typeof Symbol !== 'function' || !Symbol.iterator) {\n return '@@iterator' as any;\n }\n\n return Symbol.iterator;\n}\n\nexport const iterator = getSymbolIterator();\n", "import { iterator as Symbol_iterator } from '../symbol/iterator';\nimport { isFunction } from './isFunction';\n\n/** Identifies an input as being an Iterable */\nexport function isIterable(input: any): input is Iterable {\n return isFunction(input?.[Symbol_iterator]);\n}\n", "import { ReadableStreamLike } from '../types';\nimport { isFunction } from './isFunction';\n\nexport async function* readableStreamLikeToAsyncGenerator(readableStream: ReadableStreamLike): AsyncGenerator {\n const reader = readableStream.getReader();\n try {\n while (true) {\n const { value, done } = await reader.read();\n if (done) {\n return;\n }\n yield value!;\n }\n } finally {\n reader.releaseLock();\n }\n}\n\nexport function isReadableStreamLike(obj: any): obj is ReadableStreamLike {\n // We don't want to use instanceof checks because they would return\n // false for instances from another Realm, like an - -

General options

-
    -
  • no-dependencies (query parameter or header, default false). Can be used to prevent the auto dependencies resolution. To be used with caution.
    • -
  • listen-delete (query parameter or header, default true). Can be used prevent receive deletion events. To be used with caution.
    • -
  • with-inferences (query parameter or header, default false). Can be used to add inferences events (from rule engine) in the stream.
    • -
-

From and Recover

-

From and recover are 2 different options that need to be explains.

-
    -
  • from (query parameter) is always the parameter that describe the initial date/event_id you want to start from. Can also be setup with request header from or last-event-id
    • -
  • recover (query parameter) is an option that let you consume the initial event from the database and not from the stream. Can also be setup with request header recover or recover-date
    • -
-

This difference will be transparent for the consumer but very important to get old information as an initial snapshot. This also let you consume information that is no longer in the stream retention period.

-

The next diagram will help you to understand the concept:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/reference/taxonomy/index.html b/6.2.18/reference/taxonomy/index.html deleted file mode 100755 index 0d820aad..00000000 --- a/6.2.18/reference/taxonomy/index.html +++ /dev/null @@ -1,4306 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Taxonomy - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Taxonomy

-

In OpenCTI, taxonomies serve as structured classification systems that aid in organizing and categorizing intelligence data. This reference guide provides an exhaustive description of the platform's customizable fields within the taxonomies' framework. Users can modify, add, or delete values within the available vocabularies to tailor the classification system to their specific requirements.

-

For broader documentation on the taxonomies section, please consult the appropriate page.

-

Vocabularies

-

Default values are based on those defined in the STIX standard but can be tailored to better suit the organization's needs.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameUsed inDefault value
Account type vocabulary (account-type-ov)User accountfacebook, ldap, nis, openid, radius, skype, tacacs, twitter, unix, windows-domain, windows-local
Attack motivation vocabulary (attack-motivation-ov)Threat actor groupaccidental, coercion, dominance, ideology, notoriety, organizational-gain, personal-gain, personal-satisfaction, revenge, unpredictable
Attack resource level vocabulary (attack-resource-level-ov)Threat actor groupclub, contest, government, individual, organization, team
Case priority vocabulary (case_priority_ov)Incident responseP1, P2, P3, P4
Case severity vocabulary (case_severity_ov)Incident responsecritical, high, medium, low
Channel type vocabulary (channel_type_ov)ChannelFacebook, Twitter
Collection layers vocabulary (collection_layers_ov)Data sourcecloud-control-plane, container, host, network, OSINT
Event type vocabulary (event_type_ov)Eventconference, financial, holiday, international-summit, local-election, national-election, sport-competition
Eye color vocabulary (eye_color_ov)Threat actor individualblack, blue, brown, green, hazel, other
Gender vocabulary (gender_ov)Threat actor individualfemale, male, nonbinary, other
Grouping context vocabulary (grouping_context_ov)Groupingmalware-analysis, suspicious-activity, unspecified
Hair color vocabulary vocabulary (hair_color_ov)Threat actor individualbald, black, blond, blue, brown, gray, green, other, red
Implementation language vocabulary (implementation_language_ov)Malwareapplescript, bash, c, c++, c#, go, java, javascript, lua, objective-c, perl, php, powershell, python, ruby, scala, swift, typescript, visual-basic, x86-32, x86-64
Incident response type vocabulary (incident_response_type_ov)Incident responsedata-leak, ransomware
Incident severity vocabulary (incident_severity_ov)Incidentcritical, high, medium, low
Incident type vocabulary (incident_type_ov)Incidentalert, compromise, cybercrime, data-leak, information-system-disruption, phishing, reputation-damage, typosquatting
Indicator type vocabulary (indicator_type_ov)Indicatoranomalous-activity, anonymization, attribution, benign, compromised, malicious-activity, unknown
Infrastructure type vocabulary (infrastructure_type_ov)Infrastructureamplification, anonymization, botnet, command-and-control, control-system, exfiltration, firewall, hosting-malware, hosting-target-lists, phishing, reconnaissance, routers-switches, staging, unknown, workstation
Integrity level vocabulary (integrity_level_ov)Processhigh, medium, low, system
Malware capabilities vocabulary (malware_capabilities_ov)Malwareaccesses-remote-machines, anti-debugging, anti-disassembly, anti-emulation, anti-memory-forensics, anti-sandbox, anti-vm, captures-input-peripherals, captures-output-peripherals, captures-system-state-data, cleans-traces-of-infection, commits-fraud, communicates-with-c2, compromises-data-availability, compromises-data-integrity, compromises-system-availability, controls-local-machine, degrades-security-software, degrades-system-updates, determines-c2-server, emails-spam, escalates-privileges, evades-av, exfiltrates-data, fingerprints-host, hides-artifacts, hides-executing-code, infects-files, infects-remote-machines, installs-other-components, persists-after-system-reboot, prevents-artifact-access, prevents-artifact-deletion, probes-network-environment, self-modifies, steals-authentication-credentials, violates-system-operational-integrity
Malware result vocabulary (malware_result_ov)Malware analysisbenign, malicious, suspicious, unknown
Malware type vocabulary (malware_type_ov)Malwareadware, backdoor, bootkit, bot, ddos, downloader, dropper, exploit-kit, keylogger, ransomware, remote-access-trojan, resource-exploitation, rogue-security-software, rootkit, screen-capture, spyware, trojan, unknown, virus, webshell, wiper, worm
Marital status vocabulary (marital_status_ov)Threat actor individualannulled, divorced, domestic_partner, legally_separated, married, never_married, polygamous, separated, single, widowed
Note types vocabulary (note_types_ov)Noteanalysis, assessment, external, feedback, internal
Opinion vocabulary (opinion_ov)Opinionagree, disagree, neutral, strongly-agree, strongly-disagree
Pattern type vocabulary (pattern_type_ov)Indicatoreql, pcre, shodan, sigma, snort, spl, stix, suricata, tanium-signal, yara
Permissions vocabulary (permissions_ov)Attack patternAdministrator, root, User
Platforms vocabulary (platforms_ov)Data sourceandroid, Azure AD, Containers, Control Server, Data Historian, Engineering Workstation, Field Controller/RTU/PLC/IED, Google Workspace, Human-Machine Interface, IaaS, Input/Output Server, iOS, linux, macos, Office 365, PRE, SaaS, Safety Instrumented System/Protection Relay, windows
Processor architecture vocabulary (processor_architecture_ov)Malwarealpha, arm, ia-64, mips, powerpc, sparc, x86, x86-64
Reliability vocabulary (reliability_ov)Report, OrganizationA - Completely reliable, B - Usually reliable, C - Fairly reliable, D - Not usually reliable, E - Unreliable, F - Reliability cannot be judged
Report types vocabulary (report_types_ov)Reportinternal-report, threat-report
Request for information types vocabulary (request_for_information_types_ov)Request for informationnone
Request for takedown types vocabulary (request_for_takedown_types_ov)Request for takedownbrand-abuse, phishing
Service status vocabulary (service_status_ov)ProcessSERVICE_CONTINUE_PENDING, SERVICE_PAUSE_PENDING, SERVICE_PAUSED, SERVICE_RUNNING, SERVICE_START_PENDING, SERVICE_STOP_PENDING, SERVICE_STOPPED
Service type vocabulary (service_type_ov)ProcessSERVICE_FILE_SYSTEM_DRIVER, SERVICE_KERNEL_DRIVER, SERVICE_WIN32_OWN_PROCESS, SERVICE_WIN32_SHARE_PROCESS
Start type vocabulary (start_type_ov)ProcessSERVICE_AUTO_START, SERVICE_BOOT_START, SERVICE_DEMAND_START, SERVICE_DISABLED, SERVICE_SYSTEM_ALERT
Threat actor group role vocabulary (threat_actor_group_role_ov)Threat actor groupagent, director, independent, infrastructure-architect, infrastructure-operator, malware-author, sponsor
Threat actor group sophistication vocabulary (threat_actor_group_sophistication_ov)Threat actor groupadvanced, expert, innovator, intermediate, minimal, none, strategic
Threat actor group type vocabulary (threat_actor_group_type_ov)Threat actor groupactivist, competitor, crime-syndicate, criminal, hacker, insider-accidental, insider-disgruntled, nation-state, sensationalist, spy, terrorist, unknown
Threat actor individual role vocabulary (threat_actor_individual_role_ov)Threat actor individualagent, director, independent, infrastructure-architect, infrastructure-operator, malware-author, sponsor
Threat actor individual sophistication vocabulary (threat_actor_individual_sophistication_ov)Threat actor individualadvanced, expert, innovator, intermediate, minimal, none, strategic
Threat actor individual type vocabulary (threat_actor_individual_type_ov)Threat actor individualactivist, competitor, crime-syndicate, criminal, hacker, insider-accidental, insider-disgruntled, nation-state, sensationalist, spy, terrorist, unknown
Tool types vocabulary (tool_types_ov)Toolcredential-exploitation, denial-of-service, exploitation, information-gathering, network-capture, remote-access, unknown, vulnerability-scanning
-

Vocabularies list

-

Customization

-

Users can customize the taxonomies by modifying the available values or adding new ones. These modifications enable users to adapt the classification system to their specific intelligence requirements. Additionally, within each vocabulary list, users have the flexibility to customize the order of the dropdown menu associated with the taxonomy. This feature allows users to prioritize certain values or arrange them in a manner that aligns with their specific classification needs. Additionally, users can track the usage count for each vocabulary, providing insights into the frequency of usage and helping to identify the most relevant and impactful classifications. These customization options empower users to tailor the taxonomy system to their unique intelligence requirements, enhancing the efficiency and effectiveness of intelligence analysis within the OpenCTI platform.

-

Vocabularies customization

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/reference/usage-telemetry/index.html b/6.2.18/reference/usage-telemetry/index.html deleted file mode 100755 index 55a3f9c3..00000000 --- a/6.2.18/reference/usage-telemetry/index.html +++ /dev/null @@ -1,4113 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Usage telemetry - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Usage telemetry

-

The application collects statistical data related to its usage and performances.

-
-

Confidentiality

-

The OpenCTI platform does not collect any information related to threat intelligence knowledge which remains strictly confidential. Also, the collection is strictly anonymous and personally identifiable information is NOT collected (including IP addresses).

-
-

All data collected is anonymized and aggregated to protect the privacy of individual users, in compliance with all privacy regulations.

-

Purpose of the telemetry

-

The collected data is used for the following purposes:

-
    -
  • Improving the functionality and performance of the application.
    • -
  • Analyzing user behavior to enhance user experience.
    • -
  • Generating aggregated and anonymized statistics for internal and external reporting.
    • -
-

Important thing to know

-

The platform send the metrics to the hostname telemetry.filigran.io using the OTLP protocol (over HTTPS). The format of the data is OpenTelemetry JSON.

-

The metrics push is done every 6 hours if OpenCTI was able to connect to the hostname when the telemetry manager is started. Metrics are also written in specific logs files in order to be included in support package

-

Telemetry metrics

-

The application collects statistical data related to its usage. Here are an exhaustive list of the collected metrics:

-
    -
  • The current platform version
    • -
  • The platform unique identifier
    • -
  • The platform creation date
    • -
  • The number of active users
    • -
  • The number of total users
    • -
  • The number of nodes in the platform
    • -
  • Enterprise Edition status (activated or not)
    • -
  • The number of active connectors
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/search/search_index.json b/6.2.18/search/search_index.json deleted file mode 100755 index 896925a2..00000000 --- a/6.2.18/search/search_index.json +++ /dev/null @@ -1 +0,0 @@ -{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"OpenCTI Documentation Space","text":"

Welcome to the OpenCTI Documentation space. Here you will be able to find all documents, meeting notes and presentations about the platform.

Release notes

Please, be sure to also take a look at the OpenCTI releases notes, they may contain important information about releases and deployments.

"},{"location":"#introduction","title":"Introduction","text":"

OpenCTI is an open source platform allowing organizations to manage their cyber threat intelligence knowledge and observables. It has been created in order to structure, store, organize and visualize technical and non-technical information about cyber threats.

"},{"location":"#getting-started","title":"Getting started","text":"

  • Deployment & Setup

    Learn how to deploy and configure the platform as well as launch connectors to get the first data in OpenCTI.

    Deploy now

  • User Guide

    Understand how to use the platform, explore the knowledge, import and export information, create dashboard, etc.

    Explore

  • Administration

    Know how to administrate OpenCTI, create users and groups using RBAC / segregation, put retention policies and custom taxonomies.

    Customize

Need more help?

We are doing our best to keep this documentation complete, accurate and up to date.

If you still have questions or you find something which is not sufficiently explained, join the Filigran Community on Slack.

"},{"location":"#latest-blog-posts","title":"Latest blog posts","text":"

All tutorials are published directly on the Medium blog, this section provides a comprehensive list of the most important ones.

  • Introducing decay rules implementation for Indicators in OpenCTI Mar 25, 2024

    Cyber Threat Intelligence is made to be used. To be useful, it must be relevant and on time. It is why managing the lifecycle of Indicators of Compromise...

    Read

  • Introducing advanced filtering possibilities in OpenCTI Feb 5, 2024

    CTI databases are usually vast and made of complex, inter-dependent objects ingested from various sources. In this challenging context, cyber analysts need...

    Read

  • Breaking change: evolution of the way Connector, Streams and Feeds import data in OpenCTI Jan 29, 2024

    How Connectors, Feeds and Streams use Confidence level currently...

    Read

"},{"location":"#additional-resources","title":"Additional resources","text":"

Below, you will find external resources which may be useful along your OpenCTI journey.

OpenCTI Ecosystem List of available connectors and integrations to expand platform usage.

Training Courses Training courses for analysts and administrators in the Filigran training center.

Video materials Set of video illustrating the implementation of use cases and platform capabilities.

"},{"location":"administration/csv-mappers/","title":"CSV Mappers","text":"

In OpenCTI, CSV Mappers allow to parse CSV files in a STIX 2.1 Object. The mappers are created and configured by users with the Manage CSV mapper capability. Then, they are available to users who import CSV files, for instance inside a report or in the global import view.

"},{"location":"administration/csv-mappers/#principles","title":"Principles","text":"

The mapper contains representations of STIX 2.1 entities and relationships, in order for the parser to properly extract them. One mapper is dedicated to parsing a specific CSV file structure, and thus dedicated mappers should be created for every specific CSV structure you might need to ingest in the platform.

"},{"location":"administration/csv-mappers/#create-a-new-csv-mapper","title":"Create a new CSV Mapper","text":"

In menu Data, select the submenu Processing, and on the right menu select CSV Mappers. You are presented with a list of all the mappers set in the platform. Note that you can delete or update any mapper from the context menu via the burger button beside each mapper.

Click on the button + in the bottom-right corner to add a new Mapper.

Enter a name for your mapper and some basic information about your CSV files:

  • The line separator used (defaults to the standard comma character)
  • The presence of a header on the first line

Header management

The parser will not extract any information from the CSV header if any, it will just skip the first line during parsing.

Then, you need to create every representation, one per entity and relationship type represented in the CSV file. Click on the + button to add an empty representation in the list, and click on the chevron to expand the section and configure the representation.

Depending on the entity type, the form contains the fields that are either required (input outlined in red) or optional. For each field, set the corresponding columns mapping (the letter-based index of the column in the CSV table, as presented in common spreadsheet tools).

References to other entities should be picked from the list of all the other representations already defined earlier in the mapper.

You can do the same for all the relationships between entities that might be defined in this particular CSV file structure.

Fields might have options besides the mandatory column index, to help extract relevant data:

  • Date values are expected in ISO 8601 format, but you can set your own format to the time parser
  • Multiple values can be extracted by specifying the separator used inside the cell (e.g. + or |)

Or to set default values in case some data is missing in the imported file.

"},{"location":"administration/csv-mappers/#csv-mapper-validity","title":"CSV Mapper validity","text":"

The only parameter required to save a CSV Mapper is a name. The creation and refinement of its representations can be done iteratively.

Nonetheless, all CSV Mappers go through a quick validation that checks if all the representations have all their mandatory fields set. Only valid mappers can be run by the users on their CSV files.

Mapper validity is visible in the list of CSV Mappers as shown below.

"},{"location":"administration/csv-mappers/#test-your-csv-mapper","title":"Test your CSV mapper","text":"

In the creation or edition form, hit the button Test to open a dialog. Select a sample CSV file and hit the Test button.

The code block contains the raw result of the parsing attempt, in the form of a STIX 2.1 bundle in JSON format.

You can then check if the extracted values match the expected entities and relationships.

Partial test

The test conducted in this window relies only on the translation of CSV data according to the chosen representation in the mapper. It does not take into account checks for accurate entity formatting (e.g. IPv4) or specific entity configurations (e.g. mandatory \"description\" field on reports). Consequently, the entities visible in the test window may not be created during the actual import process.

Test with a small file

We strongly recommend limiting test files to 100 lines and 1MB. Otherwise, the browser may crash.

"},{"location":"administration/csv-mappers/#use-a-mapper-for-importing-a-csv-file","title":"Use a mapper for importing a CSV file","text":"

You can change the default configuration of the import csv connector in your configuration file.

\"import_csv_built_in_connector\": {\n  \"enabled\": true, \n  \"interval\": 10000, \n  \"validate_before_import\": false\n},\n

In Data import section, or Data tab of an entity, when you upload a CSV, you can select a mapper to apply to the file. The file will then be parsed following the representation rules set in the mapper.

By default, the imported elements will be added in a new Analyst Workbench where you will be able to check the result of the import.

"},{"location":"administration/csv-mappers/#default-values-for-attributes","title":"Default values for attributes","text":"

In the case of the CSV file misses some data, you can complete it with default values. To achieve this, you have two possibilities:

  • Set default values in the settings of the entities,
  • Set default values directly in the CSV mapper.
"},{"location":"administration/csv-mappers/#set-default-values-in-the-settings-of-the-entities","title":"Set default values in the settings of the entities","text":"

Default value mechanisms

Note that adding default values in settings have an impact at entity creation globally on the platform, not only on CSV mappers. If you want to apply those default values only at CSV mapper level, please use the second option.

In settings > Customization, you can select an entity type and then set default values for its attributes.

In the configuration of the entity, you have access to the entity's attributes that can be managed.

Click on the attribute to add a default value information.

Enter the default value in the input and save the update.

The value filled will be used in the case where the CSV file lacks data for this attribute.

"},{"location":"administration/csv-mappers/#set-specific-default-values-directly-in-the-csv-mapper","title":"Set specific default values directly in the CSV mapper","text":"

Information retained in case of default value

If you fill a default value in entity settings and the CSV mapper, the one from CSV mapper will be used.

In the mapper form, you will see next to the column index input a gear icon to add extra information for the attribute. If the attribute can have a customizable default value, then you will be able to set one here.

The example above shows the case of the attribute architecture implementation of a malware. You have some information here. First, it seems we have a default value already set in entity settings for this attribute with the value [powerpc, x86]. However, we want to override this value with another one for our case: [alpha].

"},{"location":"administration/csv-mappers/#specific-case-of-marking-definitions","title":"Specific case of marking definitions","text":"

For marking definitions, setting a default value is different from other attributes. We are not choosing a particular marking definition to use if none is specified in the CSV file. Instead, we will choose a default policy. Two option are available:

  • Use the default marking definitions of the user. In this case the default marking definitions of the connected user importing the CSV file will be used,
  • Let the user choose marking definitions. Here the user importing the CSV file will choose marking definitions (among the ones they can see) when selecting the CSV mapper.

"},{"location":"administration/csv-mappers/#additional-resources","title":"Additional resources","text":"
  • Usefulness: To additional content on entity customization, refers to the Customize entities page in the Administration section of the documentation.
"},{"location":"administration/decay-rules/","title":"Decay rules","text":"

Decay rules are used to update automatically indicators score in order to represent their lifecycle.

"},{"location":"administration/decay-rules/#configuration","title":"Configuration","text":"

Decay rules can be configured in the \"Settings > Customization > Decay rule\" menu.

There are built-in decay rules that can't be modified and are applied by default to indicators depending on their main observable type. Decay rules are applied from highest to lowest order (the lowest being 0).

You can create new decay rules with higher order to apply them along with (or instead of) the built-in rules.

When you create a decay rule, you can specify on which indicators' main observable types it will apply. If you don't enter any, it will apply to all indicators.

You can also add reaction points which represent the scores at which indicators are updated. For example, if you add one reaction point at 60 and another one at 40, indicators that have an initial score of 80 will be updated with a score of 60, then 40, depending on the decay curve.

The decay curve is based on two parameters:

  • the decay factor, which represents the speed at which the score falls, and
  • the lifetime, which represents the time (in days) during which the value will be lowered until it reaches 0.

Finally, the revoke score is the score at which the indicator can be revoked automatically.

Once you have created a new decay rule, you will be able to view its details, along with a life curve graph showing the score evolution over time.

You will also be able to edit your rule, change all its parameters and order, activate or deactivate it (only activated rules are applied), or delete it.

Indicator decay manager

Decay rules are only applied, and indicators score updated, if indicator decay manager is enabled (enabled by default).

Please read the dedicated page to have all information

"},{"location":"administration/enterprise/","title":"Enterprise edition","text":"

Filigran

Filigran is providing an Enterprise Edition of the platform, whether on-premise or in the SaaS.

"},{"location":"administration/enterprise/#what-is-opencti-ee","title":"What is OpenCTI EE?","text":"

OpenCTI Enterprise Edition is based on the open core concept. This means that the source code of OCTI EE remains open source and included in the main GitHub repository of the platform but is published under a specific license. As specified in the GitHub license file:

  • The OpenCTI Community Edition is licensed under the Apache License, Version 2.0 (the \u201cApache License\u201d).
  • The OpenCTI Enterprise Edition is licensed under the OpenCTI Enterprise Edition License (the \u201cEnterprise Edition Licensee\u201d).

The source files in this repository have a header indicating which license they are under. If no such header is provided, this means that the file belongs to the Community Edition under the Apache License, Version 2.0.

We wrote a complete article to explain the enterprise edition, feel free to read it to have more information

"},{"location":"administration/enterprise/#ee-activation","title":"EE Activation","text":"

Enterprise edition is easy to activate. You need to go the platform settings and click on the Activate button.

Then you will need to agree to the Filigran EULA.

As a reminder:

  • OpenCTI EE is free-to-use for development, testing and research purposes as well as for non-profit organizations.
  • OpenCTI EE is included for all Filigran SaaS customers without additional fee.
  • For all other usages, OpenCTI EE is reserved to organizations that have signed a Filigran Enterprise agreement.
"},{"location":"administration/enterprise/#available-features","title":"Available features","text":""},{"location":"administration/enterprise/#activity-monitoring","title":"Activity monitoring","text":"

Audit logs help you answer \"who did what, where, and when?\" within your data with the maximum level of transparency. Please read Activity monitoring page to get all information.

"},{"location":"administration/enterprise/#playbooks-and-automation","title":"Playbooks and automation","text":"

OpenCTI playbooks are flexible automation scenarios which can be fully customized and enabled by platform administrators to enrich, filter and modify the data created or updated in the platform. Please read Playbook automation page to get all information.

"},{"location":"administration/enterprise/#organizations-management-and-segregation","title":"Organizations management and segregation","text":"

Organizations segregation is a way to segregate your data considering the organization associated to the users. Useful when your platform aims to share data to multiple organizations that have access to the same OpenCTI platform. Please read Organizations RBAC to get more information.

"},{"location":"administration/enterprise/#full-text-indexing","title":"Full text indexing","text":"

Full text indexing grants improved searches across structured and unstructured data. OpenCTI classic searches are based on metadata fields (e.g. title, description, type) while advanced indexing capability enables searches to be extended to the document\u2019s contents. Please read File indexing to get all information.

"},{"location":"administration/enterprise/#more-to-come","title":"More to come","text":"

More features will be available in OpenCTI in the future. Features like:

  • Generative AI for correlation and content generation.
  • Supervised machine learning for natural language processing.
"},{"location":"administration/entities/","title":"Customize entities","text":""},{"location":"administration/entities/#introduction","title":"Introduction","text":"

A variety of entity customization options are available to optimize data representation, workflow management, and enhance overall user experience. Whether you're fine-tuning processing statuses, configuring entities' attributes, or hiding entities, OpenCTI's customization capabilities provide the flexibility you need to create a tailored environment for your threat intelligence and cybersecurity workflows.

The following chapter aims to provide readers with an understanding of the available customization options by entity type. Customize entities can be done in \"Settings > Customization\".

"},{"location":"administration/entities/#hidden-in-interface","title":"Hidden in interface","text":"

This configuration allows to hide a specific entity type throughout the entire platform. It provides a potent means to simplify the interface and tailor it to your domain expertise. For instance, if you have no interest in disinformation campaigns, you can conceal related entities such as Narratives and Channels from the menus.

You can specify which entities to hide on a platform-wide basis from \"Settings > Customization\" and from \"Settings > Parameters\", providing you with a list of hidden entities. Furthermore, you can designate hidden entities for specific Groups and Organizations from \"Settings > Security > Groups/Organizations\" by editing a Group/Organization.

An overview of hidden entity types is available in the \"Hidden entity types\" field in \"Settings > Parameters.\"

"},{"location":"administration/entities/#automatic-references-at-file-upload","title":"Automatic references at file upload","text":"

This configuration enables an entity to automatically construct an external reference from the uploaded file.

"},{"location":"administration/entities/#enforce-references","title":"Enforce references","text":"

This configuration enables the requirement of a reference message on an entity creation or modification. This option is helpful if you want to keep a strong consistency and traceability of your knowledge and is well suited for manual creation and update.

"},{"location":"administration/entities/#workflow","title":"Workflow","text":"

For now, OpenCTI has a simple workflow approach. They're represented by the \"Processing status\" field embedded in each object. By default, this field is disabled for most objects but can be activated through the platform settings:

  1. Navigate to \"Settings > Customization > Entity types > [Desired object type].\"
  2. Click on the small pink pen icon next to \"Workflow\" to access the object customization window.
  3. Add and configure the desired statuses, defining their order within the workflow.

In addition, the available statuses are defined by a collection of status templates visible in \"Settings > Taxonomies > Status templates\". This collection can be customized.

"},{"location":"administration/entities/#attributes","title":"Attributes","text":"

Each attribute in an Entity offers several customization options:

  • It can be set as mandatory if not already defined as such in the STIX standard.
  • A default value can be established to streamline entity creation through the creation forms.
  • Different thresholds and their corresponding labels for scalable attributes can be defined.

"},{"location":"administration/entities/#confidence-scale-configuration","title":"Confidence scale configuration","text":"

Confidence scale can be customized for each entity type by selecting another scale template or by editing directly the scale values. Once you have customized your scale, click on \"Update\" to save your configuration.

Max confidence level

The above scale also needs to take into account the confidence level per user. To understand the concept, please navigate to this page

"},{"location":"administration/entities/#overview-layout-customization","title":"Overview layout customization","text":"

At the platform level, the Overview layout tab of the containers can be rearranged to fit the users needs. The widgets can be reordered or extended to their full width.

To reset the layout to its default version, click the button next to the section title.

"},{"location":"administration/file-indexing/","title":"File indexing","text":"

Enterprise edition

Platform segregation by organization is available under the \"OpenCTI Enterprise Edition\" license. Please read the dedicated page to have all the information.

"},{"location":"administration/file-indexing/#files-search-requirements","title":"Files search requirements","text":"

In order to search in files, we need to extract and index files text content, which requires to have one of these database configurations :

  • Elasticsearch >= 8.4
  • Elasticsearch < 8.4 with ingest-attachment plugin
  • OpenSearch with ingest-attachment plugin
"},{"location":"administration/file-indexing/#file-indexing-configuration","title":"File indexing configuration","text":"

File indexing can be configured via the File indexing tab in the Settings menu.

The configuration and impact panel shows all file types that can be indexed, as well as the volume of storage used.

It is also possible to include or exclude files uploaded from the global Data import panel and that are not associated with a specific entity in the platform.

Finally, it is possible to set a maximum file size for indexing (5 Mb by default).

Currently supported content types : application/pdf, text/plain, text/csv, text/html, application/vnd.ms-excel, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet (excel sheets).

Once indexing has been launched by pressing the Start button, you can follow its progress.

You will also be able to Pause it and restart from the beginning by pressing Reset button which deletes all indexed files from the database.

If you change the configuration while file indexing is running, you might need to reset in order to include newly impacted files.

File indexing runs every 5 minutes to index last uploaded files.

"},{"location":"administration/introduction/","title":"Introduction","text":"

This guide aims to give you a full overview of the OpenCTI features and workflows. The platform can be used in various contexts to handle threats management use cases from a technical to a more strategic level.

"},{"location":"administration/introduction/#administrative-settings","title":"Administrative Settings","text":"

The OpenCTI Administrative settings console allows administrators to configure many options dynamically within the system. As an Administrator, you can access this settings console, by clicking the settings link.

The Settings Console allows for configuration of various aspects of the system.

"},{"location":"administration/introduction/#general-configuration","title":"General Configuration","text":"
  • Platform Title (Default: OpenCTI - Cyber Threat Intelligence Platform)
  • Platform Favicon
  • Platform General Sender email (Default: admin@opencti.io)
  • Platform Default Theme (Default: Dark)
  • Language (Default: Automatic Detection)
  • Hidden Entity Types (Default: None)
"},{"location":"administration/introduction/#authentication-strategies-display","title":"Authentication Strategies Display","text":"
  • This section will show configured and enabled/disabled strategies. The configuration is done in the config/default.json file or via ENV variables detected at launch.
"},{"location":"administration/introduction/#platform-messages","title":"Platform Messages","text":"
  • Platform Login Message (optional) - if configured this will be displayed on the login page. This is usually used to have a welcome type message for users before login.
  • Platform Consent Message (optional) - if configured this will be displayed on the login page. This is usually used to display some type of consent message for users to agree to before login. If enabled, a user must check the checkbox displayed to allow login.
  • Platform Consent Confirm Text (optional) - This is displayed next to the platform consent checkbox, if Platform Consent Message is configured. Users must agree to the checkbox before the login prompt will be displayed. This message can be configured, but by default reads: I have read and comply with the above statement
"},{"location":"administration/introduction/#dark-theme-color-scheme","title":"Dark Theme Color Scheme","text":"

Various aspects of the Dark Theme can be dynamically configured in this section.

"},{"location":"administration/introduction/#light-theme-color-scheme","title":"Light Theme Color Scheme","text":"

Various aspects of the Light Theme can be dynamically configured in this section.

"},{"location":"administration/introduction/#tools-configuration-display","title":"Tools Configuration Display","text":"

This section will give general status on the various tools and enabled components of the currently configured OpenCTI deployment.

"},{"location":"administration/merging/","title":"Merging","text":""},{"location":"administration/merging/#data-merging","title":"Data merging","text":"

Within the OpenCTI platform, the merge capability is present into the \"Data > Entities\" tab, and is fairly straightforward to use. To execute a merge, select the set of entities to be merged, then click on the Merge icon.

Merging limitation

It is not possible to merge entities of different types, nor is it possible to merge more than 4 entities at a time (it will have to be done in several stages).

Central to the merging process is the selection of a main entity. This primary entity becomes the anchor, retaining crucial attributes such as name and description. Other entities, while losing specific fields like descriptions, are aliased under the primary entity. This strategic decision preserves vital data while eliminating redundancy.

Once the choice has been made, simply validate to run the task in the background. Depending on the number of entity relationships, and the current workload on the platform, the merge may take more or less time. In the case of a healthy platform and around a hundred relationships per entity, merge is almost instantaneous.

"},{"location":"administration/merging/#data-preservation-and-relationship-continuity","title":"Data preservation and relationship continuity","text":"

A common concern when merging entities lies in the potential loss of information. In the context of OpenCTI, this worry is alleviated. Even if the merged entities were initially created by distinct sources, the platform ensures that data is not lost. Upon merging, the platform automatically generates relationships directly on the merged entity. This strategic approach ensures that all connections, regardless of their origin, are anchored to the consolidated entity. Post-merge, OpenCTI treats these once-separate entities as a singular, unified entity. Subsequent information from varied sources is channeled directly into the entity resulting from the merger. This unified entity becomes the focal point for all future relationships, ensuring the continuity of data and relationships without any loss or fragmentation.

"},{"location":"administration/merging/#important-considerations","title":"Important considerations","text":"
  • Irreversible process: It's essential to know that a merge operation is irreversible. Once completed, the merged entities cannot be reverted to their original state. Consequently, careful consideration and validation are crucial before initiating the merge process.
  • Loss of fields in aliased entities: Fields, such as descriptions, in aliased entities - entities that have not been chosen as the main - will be lost during the merge. Ensuring that essential information is captured in the primary entity is crucial to prevent data loss.
"},{"location":"administration/merging/#additional-resources","title":"Additional resources","text":"
  • Usefulness: To understand the benefits of entity merger, refer to the Merge objects page in the User Guide section of the documentation.
  • Deduplication mechanism: the platform is equipped with deduplication processes that automatically merge data at creation (either manually or by importing data from different sources) if it meets certain conditions.
"},{"location":"administration/notifier-samples/","title":"Notifier samples","text":""},{"location":"administration/notifier-samples/#configure-teams-webhook","title":"Configure Teams webhook","text":"

To configure a notifier for Teams, allowing to send notifications via Teams messages, we followed the guidelines outlined in the Microsoft documentation.

"},{"location":"administration/notifier-samples/#template-message-for-live-trigger","title":"Template message for live trigger","text":"

The Teams template message sent through webhook for a live notification is:

{\n        \"type\": \"message\",\n        \"attachments\": [\n            {\n                \"contentType\": \"application/vnd.microsoft.card.thumbnail\",\n                \"content\": {\n                    \"subtitle\": \"Operation : <%=content[0].events[0].operation%>\",\n                    \"text\": \"<%=(new Date(notification.created)).toLocaleString()%>\",\n                    \"title\": \"<%=content[0].events[0].message%>\",\n                    \"buttons\": [\n                        {\n                            \"type\": \"openUrl\",\n                            \"title\": \"See in OpenCTI\",\n                            \"value\": \"https://YOUR_OPENCTI_URL/dashboard/id/<%=content[0].events[0].instance_id%>\"\n                        }\n                    ]\n                }\n            }\n        ]\n    }\n
"},{"location":"administration/notifier-samples/#template-message-for-digest","title":"Template message for digest","text":"

The Teams template message sent through webhook for a digest notification is:

{\n    \"type\": \"message\",\n    \"attachments\": [\n        {\n            \"contentType\": \"application/vnd.microsoft.card.adaptive\",\n            \"content\": {\n                \"$schema\": \"http://adaptivecards.io/schemas/adaptive-card.json\",\n                \"type\": \"AdaptiveCard\",\n                \"version\": \"1.0\",\n                \"body\": [\n                    {\n                        \"type\": \"Container\",\n                        \"items\": [\n                            {\n                                \"type\": \"TextBlock\",\n                                \"text\": \"<%=notification.name%>\",\n                                \"weight\": \"bolder\",\n                                \"size\": \"extraLarge\"\n                            }, {\n                                \"type\": \"TextBlock\",\n                                \"text\": \"<%=(new Date(notification.created)).toLocaleString()%>\",\n                                \"size\": \"medium\"\n                            }\n                        ]\n                    },\n                    <% for(var i=0; i<content.length; i++) { %>\n                    {\n                        \"type\": \"Container\",\n                        \"items\": [<% for(var j=0; j<content[i].events.length; j++) { %>\n                            {\n                                \"type\" : \"TextBlock\",\n                                \"text\" : \"[<%=content[i].events[j].message%>](https://YOUR_OPENCTI_URL/dashboard/id/<%=content[i].events[j].instance_id%>)\"\n                            }<% if(j<(content[i].events.length - 1)) {%>,<% } %>\n                        <% } %>]\n           }<% if(i<(content.length - 1)) {%>,<% } %>\n                    <% } %>\n                ]\n            }\n        }\n    ],\n   \"dataString\": <%-JSON.stringify(notification)%>\n}\n
"},{"location":"administration/notifiers/","title":"Custom notifiers","text":"

Leveraging the platform's built-in connectors, users can create custom notifiers tailored to their unique needs. OpenCTI features three built-in connectors: a webhook connector, a simple mailer connector, and a platform mailer connector. These connectors operate based on registered schemas that describe their interaction methods.

"},{"location":"administration/notifiers/#built-in-notifier-connectors","title":"Built-In notifier connectors","text":""},{"location":"administration/notifiers/#platform-mailer","title":"Platform mailer","text":"

This notifier connector enables customization of notifications raised within the platform. It's simple to configure, requiring only:

  • Title: The title for the platform notification.
  • Template: Specifies the message template for the notification.
"},{"location":"administration/notifiers/#simple-mailer","title":"Simple mailer","text":"

This notifier connector offers a straightforward approach to email notifications with simplified configuration options. Users can set:

  • Title: The title for the email notification.
  • Header: Additional content to include at the beginning of the email.
  • Footer: Additional content to include at the end of the email.
  • Logo: The option to add a logo to the email.
  • Background Color: Customize the background color of the email.

"},{"location":"administration/notifiers/#webhook","title":"Webhook","text":"

This notifier connector enables users to send notifications to external applications or services through HTTP requests. Users can specify:

  • Verb: Specifies the HTTP method (GET, POST, PUT, DELETE).
  • URL: Defines the destination URL for the webhook.
  • Template: Specifies the message template for the notification.
  • Parameters and Headers: Customizable parameters and headers sent through the webhook request.

OpenCTI provides two notifier samples by default, designed to communicate with Microsoft Teams through a webhook. A documentation page providing details on these samples is available.

"},{"location":"administration/notifiers/#configuration-and-access","title":"Configuration and access","text":"

Custom notifiers are manageable in the \"Settings > Customization > Notifiers\" window and can be restricted through Role-Based Access Control (RBAC). Administrators can control access, limiting usage to specific Users, Groups, or Organizations.

For guidance on configuring notification triggers and exploring the usages of notifiers, refer to the dedicated documentation page.

"},{"location":"administration/ontologies/","title":"Taxonomies","text":"

Taxonomies in OpenCTI refer to the structured classification systems that help in organizing and categorizing cyber threat intelligence data. They play a crucial role in the platform by allowing analysts to systematically tag and retrieve information based on predefined categories and terms.

Along with the Customization page, these pages allow the administrator to customize the platform.

"},{"location":"administration/ontologies/#labels","title":"Labels","text":"

Labels in OpenCTI serve as a powerful tool for organizing, categorizing, and prioritizing data. Here\u2019s how they can be used effectively:

  1. Tagging and Categorization: Labels can be used to tag malware, incidents, or indicators (IOCs) with specific categories, making it easier to filter and search through large datasets.
  2. Prioritization: By labeling threats based on their severity or impact, security analysts can prioritize their response efforts accordingly.
  3. Correlation and Analysis: Labels help in correlating different pieces of intelligence. For example, if multiple indicators are tagged with the same label, it might indicate a larger campaign or a common adversary.
  4. Automation and Integration: Labels can trigger automated workflows (also called playbooks) within OpenCTI. For instance, a label might automatically initiate further investigation or escalate an incident.
  5. Reporting and Metrics: Labels facilitate the generation of reports and metrics, allowing organizations to track trends through dashboards, measure response effectiveness, and make data-driven decisions.
  6. Sharing and Collaboration: When sharing intelligence with other organizations or platforms, labels provide a common language that helps in understanding the context and relevance of the shared data.

Tip

In order to achieve effective data labeling methods, it is recommended to establish a clear and consistent criteria for your labeling and document them in a policy or guideline.

"},{"location":"administration/ontologies/#kill-chain-phases","title":"Kill chain phases","text":"

Kill chain phases are used in OpenCTI to structure and analyze the data related to cyber threats and attacks. They describe the stages of an attack from the perspective of the attacker and provide a framework for identifying, analysing and responding to threats.

OpenCTI supports the following kill chain models:

  • Lockheed Martin Cyber Kill Chain
  • MITRE ATT&CK Framework (Entreprise, PRE, Mobile and ICS)
  • DISARM framework

You can add, edit, or delete kill chain phases in the settings page, and assign them to indicators, attack patterns, incidents, or courses of action in the platform. You can also filter the data by kill chain phase, and view the kill chain phases in a timeline or as a matrix.

"},{"location":"administration/ontologies/#vocabularies","title":"Vocabularies","text":"

Open vocabularies are sets of terms and definitions that are agreed upon by the CTI community. They help to standardize the communication documentation of cyber threat information. This section allows you to customize a set of available fields by adding vocabulary. Almost all of the drop-down menus available in the entities can be modified from this panel.

Open vocabularies in OpenCTI are mainly based on the STIX standard.

"},{"location":"administration/ontologies/#status-templates","title":"Status templates","text":"

Status templates are predefined statuses that can be assigned to different entities in OpenCTI, such as reports, incidents, or cases (incident responses, requests for information and requests for takedown).

They help to track the progress of the analysis and response activities by defining statuses that are used in the workflows.

"},{"location":"administration/ontologies/#case-templates","title":"Case templates","text":"

Customizable case templates help to streamline the process of creating cases with predefined lists of tasks.

"},{"location":"administration/organization-segregation/","title":"Organization segregation","text":"

Enterprise edition

Platform segregation by organization is available under the \"OpenCTI Enterprise Edition\" license. Please read the dedicated page to have all the information.

"},{"location":"administration/organization-segregation/#organization-administration","title":"Organization administration","text":"

Platform administrators can promote members of an organization as \"Organization administrator\". This elevated role grants them the necessary capabilities to create, edit and delete users from the corresponding Organization. Additionally, administrators have the flexibility to define a list of groups that can be granted to newly created members by the organization administrators. This feature simplifies the process of granting appropriate access and privileges to individuals joining the organization.

The platform administrator can promote/demote an organization admin through its user edition form.

Organization admin rights

The \"Organization admin\" has restricted access to Settings. They can only manage the members of the organizations for which they have been promoted as \"admins\".

"},{"location":"administration/parameters/","title":"Parameters","text":""},{"location":"administration/parameters/#description","title":"Description","text":"

This part of the interface wil let you configure global platform settings, like title, favicon, etc.

It will also give you important information about the platform.

"},{"location":"administration/parameters/#the-configuration-section","title":"The \"Configuration\" section","text":"

This section allows the administrator to edit the following settings:

  • Platform title
  • Platform favicon URL
  • Sender email address: email address displayed as sender when sending notifications. The technical sender is defined in the SMTP configuration.
  • Theme
  • Language
  • Hidden entity types: allows you to customize which types of entities you want to see or hide in the platform. This can help you focus on the relevant information and avoid cluttering the platform with unnecessary data.
"},{"location":"administration/parameters/#opencti-platform","title":"OpenCTI Platform","text":"

This is where the Enterprise edition can be enabled.

This section gives important information about the platform like the used version, the edition, the architecture mode (can be Standalone or Cluster) and the number used nodes.

Through the \"Remove Filigran logos\" toggle, the administrator has the option to hide the Filigran logo on the login page and the sidebar.

"},{"location":"administration/parameters/#platform-announcement","title":"Platform Announcement","text":"

This section gives you the possibility to set and display Announcements in the platform. Those announcements will be visible to every user in the platform, on top of the interface.

They can be used to inform some of your users or all of important information, like a scheduled downtime, an incoming upgrade, or even to share important tips regarding the usage of the platform.

An Announcement can be accompanied by a \"Dismiss\u201d button. When clicked by a user, it makes the message disappear for this user.

This option can be deactivated to have a permanent announcement.

\u26a0\ufe0f Only one announcement is shown at a time, with priority given to dismissible ones. If there are no dismissible announcements, the most recent non-dismissible one is shown.

"},{"location":"administration/parameters/#third-party-analytics","title":"Third-party Analytics","text":"

Enterprise edition

Analytics is available under the \"OpenCTI Enterprise Edition\" license.

Please read the dedicated page to have more information

This is where you can configure analytics providers. At the moment only Google Analytics v4 is supported.

"},{"location":"administration/parameters/#theme-customization","title":"Theme customization","text":"

In this section, the administrator can customize the two OpenCTI themes

"},{"location":"administration/parameters/#tools","title":"Tools","text":"

This section informs the administrator of the statuses of the different managers used in the Platform. More information about the managers can be found here. It shows also the used versions of the search engine database, RabbitMQ and Redis.

In cluster mode, the fact that a manager appears as enabled means that it is active in at least one node.

"},{"location":"administration/policies/","title":"Policies","text":"

The Policies configuration window (in \"Settings > Security > Policies\") encompasses essential settings that govern the organizational sharing, authentication strategies, password policies, login messages, and banner appearance within the OpenCTI platform.

"},{"location":"administration/policies/#platform-main-organization","title":"Platform main organization","text":"

Allow to set a main organization for the entire platform. Users belonging to the main organization enjoy unrestricted access to all data stored in the platform. In contrast, users affiliated with other organizations will only have visibility into data explicitly shared with them.

Numerous repercussions linked to the activation of this feature

This feature has implications for the entire platform and must be fully understood before being used. For example, it's mandatory to have organizations set up for each user, otherwise they won't be able to log in. It is also advisable to include connector's users in the platform main organization to avoid import problems.

"},{"location":"administration/policies/#authentication-strategies","title":"Authentication strategies","text":"

The authentication strategies section provides insights into the configured authentication methods. Additionally, an \"Enforce Two-Factor Authentication\" button is available, allowing administrators to mandate 2FA activation for users, enhancing overall account security.

Please see the Authentication section for further details on available authentication strategies.

"},{"location":"administration/policies/#local-password-policies","title":"Local password policies","text":"

This section encompasses a comprehensive set of parameters defining the local password policy. Administrators can specify requirements such as minimum/maximum number of characters, symbols, digits, and more to ensure robust password security across the platform. Here are all the parameters available:

Parameter Description Number of chars must be greater than or equals to Define the minimum length required for passwords. Number of chars must be lower or equals to (0 equals no maximum) Set an upper limit for password length. Number of symbols must be greater or equals to Specify the minimum number of symbols required in a password. Number of digits must be greater or equals to Set the minimum number of numeric characters in a password. Number of words (split on hyphen, space) must be greater or equals to Enforce a minimum count of words in a password. Number of lowercase chars must be greater or equals to Specify the minimum number of lowercase characters. Number of uppercase chars must be greater or equals to Specify the minimum number of uppercase characters.

"},{"location":"administration/policies/#login-messages","title":"Login messages","text":"

Allow to define messages on the login page to customize and highlight your platform's security policy. Three distinct messages can be customized:

  • Platform login message: Appears above the login form to convey important information or announcements.
  • Platform consent message: A consent message that obscures the login form until users check the approval box, ensuring informed user consent.
  • Platform consent confirm text: A message accompanying the consent box, providing clarity on the consent confirmation process.

"},{"location":"administration/policies/#platform-banner-configuration","title":"Platform banner configuration","text":"

The platform banner configuration section allows administrators to display a custom banner message at the top and bottom of the screen. This feature enables customization for enhanced visual communication and branding within the OpenCTI platform. It can be used to add a disclaimer or system purpose.

This configuration has two parameters:

  • Platform banner level: Options defining the banner background color (Green, Red, or Yellow).
  • Platform banner text: Field referencing the message to be displayed within the banner.

"},{"location":"administration/reasoning/","title":"Rules engine","text":""},{"location":"administration/reasoning/#inference-rules","title":"Inference rules","text":"

The rules engine comprises a set of predefined rules (named inference rules) that govern how new relationships are inferred based on existing data. These rules are carefully crafted to ensure logical and accurate relationship creation. Here is the list of existing inference rules:

"},{"location":"administration/reasoning/#raise-incident-based-on-sighting","title":"Raise incident based on sighting","text":"Conditions Creations A non-revoked Indicator is sighted in an Entity Creation of an Incident linked to the sighted Indicator and the targeted Entity"},{"location":"administration/reasoning/#sightings-of-observables-via-observed-data","title":"Sightings of observables via observed data","text":"Conditions Creations An Indicator is based on an Observable contained in an Observed Data Creation of a sighting between the Indicator and the creating Identity of the Observed Data"},{"location":"administration/reasoning/#sightings-propagation-from-indicator","title":"Sightings propagation from indicator","text":"Conditions Creations An Indicator based on an Observable is sighted in an Entity The Observable is sighted in the Entity"},{"location":"administration/reasoning/#sightings-propagation-from-observable","title":"Sightings propagation from observable","text":"Conditions Creations An Indicator is based on an Observable sighted in an Entity The Indicator is sighted in the Entity"},{"location":"administration/reasoning/#relation-propagation-via-an-observable","title":"Relation propagation via an observable","text":"Conditions Creations An observable is related to two Entities Create a related to relationship between the two Entities"},{"location":"administration/reasoning/#attribution-propagation","title":"Attribution propagation","text":"Conditions Creations An Entity A is attributed to an Entity B and this Entity B is itself attributed to an Entity C The Entity A is attributed to Entity C"},{"location":"administration/reasoning/#belonging-propagation","title":"Belonging propagation","text":"Conditions Creations An Entity A is part of an Entity B and this Entity B is itself part of an Entity C The Entity A is part of Entity C"},{"location":"administration/reasoning/#location-propagation","title":"Location propagation","text":"Conditions Creations A Location A is located at a Location B and this Location B is itself located at a Location C The Location A is located at Location C"},{"location":"administration/reasoning/#organization-propagation-via-participation","title":"Organization propagation via participation","text":"Conditions Creations A User is affiliated with an Organization B, which is part of an Organization C The User is affiliated to the Organization C"},{"location":"administration/reasoning/#identities-propagation-in-reports","title":"Identities propagation in reports","text":"Conditions Creations A Report contains an Identity B and this Identity B is part of an Identity C The Report contains Identity C, as well as the Relationship between Identity B and Identity C"},{"location":"administration/reasoning/#locations-propagation-in-reports","title":"Locations propagation in reports","text":"Conditions Creations A Report contains a Location B and this Location B is located at a Location C The Report contains Location B, as well as the Relationship between Location B and Location C"},{"location":"administration/reasoning/#observables-propagation-in-reports","title":"Observables propagation in reports","text":"Conditions Creations A Report contains an Indicator and this Indicator is based on an Observable The Report contains the Observable, as well as the Relationship between the Indicator and the Observable"},{"location":"administration/reasoning/#usage-propagation-via-attribution","title":"Usage propagation via attribution","text":"Conditions Creations An Entity A, attributed to an Entity C, uses an Entity B The Entity C uses the Entity B"},{"location":"administration/reasoning/#inference-of-targeting-via-a-sighting","title":"Inference of targeting via a sighting","text":"Conditions Creations An Indicator, sighted at an Entity C, indicates an Entity B The Entity B targets the Entity C"},{"location":"administration/reasoning/#targeting-propagation-via-attribution","title":"Targeting propagation via attribution","text":"Conditions Creations An Entity A, attributed to an Entity C, targets an Entity B The Entity C targets the Entity B"},{"location":"administration/reasoning/#targeting-propagation-via-belonging","title":"Targeting propagation via belonging","text":"Conditions Creations An Entity A targets an Identity B, part of an Identity C The Entity A targets the Identity C"},{"location":"administration/reasoning/#targeting-propagation-via-location","title":"Targeting propagation via location","text":"Conditions Creations An Entity targets a Location B and this Location B is located at a Location C The Entity targets the Location C"},{"location":"administration/reasoning/#targeting-propagation-when-located","title":"Targeting propagation when located","text":"Conditions Creations An Entity A targets an Entity B and this target is located at Location D. The Entity A targets the Location D"},{"location":"administration/reasoning/#rule-execution","title":"Rule execution","text":""},{"location":"administration/reasoning/#rule-activation","title":"Rule activation","text":"

When a rule is activated, a background task is initiated. This task scans all platform data, identifying existing relationships that meet the conditions defined by the rule. Subsequently, it creates new objects (entities and/or relationships), expanding the network of insights within your threat intelligence environment. Then, activated rules operate continuously. Whenever a relationship is created or modified, and this change aligns with the conditions specified in an active rule, the reasoning mechanism is triggered. This ensures real-time relationship inference.

"},{"location":"administration/reasoning/#rule-deactivation","title":"Rule deactivation","text":"

Deactivating a rule leads to the deletion of all objects and relationships created by it. This cleanup process maintains the accuracy and reliability of your threat intelligence database.

"},{"location":"administration/reasoning/#access-restrictions-and-data-impact","title":"Access restrictions and data impact","text":"

Access to the rule engine panel is restricted to administrators only. Regular users do not have visibility into this section of the platform. Administrators possess the authority to activate or deactivate rules.

The rules engine empowers OpenCTI with the capability to automatically establish intricate relationships within your data. However, these rules can lead to a very large number of objects created. Even if the operation is reversible, an administrator should consider the impact of activating a rule.

"},{"location":"administration/reasoning/#additional-resources","title":"Additional resources","text":"
  • Usefulness: To understand the benefits and results of these rules, refer to the Inferences and reasoning page in the User Guide section of the documentation.
  • New inference rule: Given the potential impact of a rule on your data, users are not allowed to add new rules. However, users can submit rule suggestions via a GitHub issue for evaluation. These suggestions are carefully evaluated by our team, ensuring continuous improvement and innovation.
"},{"location":"administration/retentions/","title":"Retention policies","text":"

Retention rules serve the purpose of establishing data retention times, specifying when data should be automatically deleted from the platform. Users can define filters to target specific objects. Any object meeting these criteria that haven't been updated within the designated time frame will be permanently deleted.

Note that the data deleted by an active retention policy will not appear in the trash and thus cannot be restored.

"},{"location":"administration/retentions/#configuration","title":"Configuration","text":"

Retention rules can be configured in the \"Settings > Customization > Retention policies\" window. A set of parameters must be configured:

  • Maximum retention days: Set the maximum number of days an object can remain unchanged before being eligible for deletion.
  • Filters: Define filters based on specific criteria to select the types of objects subject to retention rules.

An object will be removed if it meets the specified filters and hasn't been updated for the duration set in the \"Maximum retention days\" field.

"},{"location":"administration/retentions/#verification-process","title":"Verification process","text":"

Before activating a retention rule, users have the option to verify its impact using the \"Verify\" button. This action provides insight into the number of objects that currently match the rule's criteria and would be deleted if the rule is activated.

Verify before activation

Always use the \"Verify\" feature to assess the potential impact of a retention rule before activating it. Once the rule is activated, data deletion will begin, and retrieval of the deleted data will not be possible.

Retention rules contribute to maintaining a streamlined and efficient data lifecycle within OpenCTI, ensuring that outdated or irrelevant information is systematically removed from the platform, thereby optimizing disk space usage.

"},{"location":"administration/segregation/","title":"Marking restriction","text":"

Data segregation in the context of Cyber Threat Intelligence refers to the practice of categorizing and separating different types of data or information related to cybersecurity threats based on specific criteria.

This separation helps organizations manage and analyze threat intelligence more effectively and securely and the goal of data segregation is to ensure that only those individuals who are authorized to view a particular set of data have access to that set of data.

Practically, \"Need-to-know basis\" and \"classification level\" are data segregation measures.

"},{"location":"administration/segregation/#description","title":"Description","text":"

Marking definitions are essential in the context of data segregation to ensure that data is appropriately categorized and protected based on its sensitivity or classification level. Marking definitions establish a standardized framework for classifying data.

Marking Definition objects are unique among STIX objects in the STIX 2.1 standard in that they cannot be versioned. This restriction is in place to prevent the possibility of indirect alterations to the markings associated with a STIX Object.

Multiple markings can be added to the same object. Certain categories of marking definitions or trust groups may enforce rules that specify which markings take precedence over others or how some markings can be added to complement existing ones.

In OpenCTI, data is segregated based on knowledge marking. The diagram provided below illustrates the manner in which OpenCTI establishes connections between pieces of information to authorize data access for a user:

"},{"location":"administration/segregation/#manage-markings","title":"Manage markings","text":""},{"location":"administration/segregation/#create-new-markings","title":"Create new markings","text":"

To create a marking, you must first possess the capability Manage marking definitions. For further information on user administration, please refer to the Users and Role Based Access Control page.

Once you have access to the settings, navigate to \"Settings > Security > Marking Definitions\" to create a new marking.

A marking consists of the following attributes:

  • Type: Specifies the marking group to which it belongs.
  • Definition: The name assigned to the marking.
  • Color: The color associated with the marking.
  • Order: Determines the hierarchical order among markings of the same type.

"},{"location":"administration/segregation/#allowed-marking","title":"Allowed marking","text":"

The configuration of authorized markings for a user is determined at the Group level. To access entities and relationships associated with specific markings, the user must belong to a group that has been granted access to those markings.

There are two ways in which markings can be accessed:

  • The user is a member of a group that has been granted access to the marking.
  • The user is a member of a group that has access to a marking of the same type, with an equal or higher hierarchical order.

Access to an object with several markings

Access to all markings attached to an object is required in order to access it (not only one).

Automatically grant access to the new marking

To allow a group to automatically access a newly created marking definition, you can check Automatically authorize this group to new marking definition.

"},{"location":"administration/segregation/#default-marking-definitions","title":"Default marking definitions","text":"

To apply a default marking when creating a new entity or relationship, you can choose which marking to add by default from the list of allowed markings. You can add only one marking per type, but you can have multiple types. This configuration is also done at the Group level.

Need a configuration change

Simply adding markings as default markings is insufficient to display the markings when creating an entity or relationship. You also need to enable default markings in the customization settings of an entity or relationship. For example, to enable default markings for a new report, navigate to \"Settings > Customization > Report > Markings\" and toggle the option to Activate/Desactivate default values.

"},{"location":"administration/segregation/#maximum-shareable-marking-definitions","title":"Maximum shareable marking definitions","text":"

This configuration allows to define, for each type of marking definitions, until which level we allow to share data externally (via Public dashboard or file export).

The marking definitions that can be shared by a group are the ones

  • that are allowed for this group
  • and whose order are inferior or equal to the order of the maximum shareable markings defined for each marking type.

Users with the Bypass capability can share all the markings.

By default, every marking of a given marking type is shareable.

For example in the capture below, for the type of marking TLP, only data with a marking definition that is allowed and has a level equal or below GREEN will be shareable. And no data with marking definition statement will be shared at all.

"},{"location":"administration/segregation/#management-of-multiple-markings","title":"Management of multiple markings","text":"

In scenarios where multiple markings of the same type but different orders are added, the platform will retain only the marking with the highest order for each type. This consolidation can occurs in various instances:

  • During entity creation, if multiple markings are selected.
  • During entity updates, whether manually or via a connector, if additional markings are introduced.
  • When multiple entities are merged, their respective markings will be amalgamated.

For example:

Create a new report and add markings PAP:AMBER,PAP:RED,TLP:AMBER+STRICT,TLP:CLEAR and a statement CC-BY-SA-4.0 DISARM Foundation

The final markings kept are: PAP:RED, TLP:AMBER+STRICT and CC-BY-SA-4.0 DISARM Foundation

"},{"location":"administration/segregation/#update-an-object-manually","title":"Update an object manually","text":"

When update an entity or a relationship:

  • add a marking with the same type and different orders, a pop-up will be displayed to confirm the choice,
  • add a marking with the same type and the same order, the marking will be added,
  • add a marking with different types, the marking will be added.

"},{"location":"administration/segregation/#import-data-from-a-connector","title":"Import data from a connector","text":"

As a result of this mechanism, when importing data from a connector, the connector is unable to downgrade a marking for an entity if a marking of the same type is already present on it.

"},{"location":"administration/segregation/#additional-information","title":"Additional information","text":"

The Traffic Light Protocol is implemented by default as marking definitions in OpenCTI. It allows you to segregate information by TLP levels in your platform and restrict access to marked data if users are not authorized to see the corresponding marking.

The Traffic Light Protocol (TLP) was designed by the Forum of Incident Response and Security Teams (FIRST) to provide a standardized method for classifying and handling sensitive information, based on four categories of sensitivity.

For more details, the diagram provided below illustrates how are categorized the marking definitions:

"},{"location":"administration/support-package/","title":"Support Package","text":"

Support packages are useful for troubleshooting issue that occurs on OpenCTI platform. Administrators can request to create and download a support package that contains recent platform error logs and usage statistics.

Support package content

Even if we do our best to prevent logging any data, the support package may contains some sensitive information that you may not want to share with everyone. Before creating a ticket with your support package takes some time to check if you can safely share the content depending of your security policy.

Support Package can be requested from \"Settings > Support\" menu.

"},{"location":"administration/support-package/#package-generation","title":"Package generation","text":"

On a click on \"Generate support package\", a support event is propagated to every platform instances to request needed information. Every instance that will receive this message will process the request and send the files to the platform. During this processing the interface will display the expected support package name in an IN PROGRESS state waiting for completion. After finishing the process the support package will move to the READY state and the buttons download and delete will be activated.

"},{"location":"administration/support-package/#package-download","title":"Package download","text":"

After file generation, using the download button will dynamically create a (zip) containing all instances logs and telemetry.

"},{"location":"administration/support-package/#partial-package","title":"Partial package","text":"

In case of platform instability, some logs might not be retrieved and the support package will be incomplete.

If some instances fail to send their data, you will be able to force download a partial zip only after 1 minute. In case of a support package taking more than 5 minutes, the status will be moved to \"timeout\".

"},{"location":"administration/users/","title":"Users and Role Based Access Control","text":""},{"location":"administration/users/#introduction","title":"Introduction","text":"

In OpenCTI, the RBAC system not only related to what users can do or cannot do in the platform (aka. Capabilities) but also to the system of data segregation. Also, platform behavior such as default home dashboards, default triggers and digests as well as default hidden menus or entities can be defined across groups and organizations.

"},{"location":"administration/users/#high-level-design","title":"High level design","text":""},{"location":"administration/users/#roles","title":"Roles","text":"

Roles are used in the platform to grant the given groups with some capabilities to define what users in those groups can do or cannot do.

"},{"location":"administration/users/#list-of-capabilities","title":"List of capabilities","text":"Capability Description Bypass all capabilities Just bypass everything including data segregation and enforcements. Access knowledge Access in read-only to all the knowledge in the platform. Access to collaborative creation Create notes and opinions (and modify its own) on entities and relations. Create / Update knowledge Create and update existing entities and relationships. Restrict organization access Share entities and relationships with other organizations. Delete knowledge Delete entities and relationships. Manage authorized members Restrict the access to an entity to a user, group or organization. Bypass enforced reference If external references enforced in a type of entity, be able to bypass the enforcement. Upload knowledge files Upload files in the Data and Content section of entities. Import knowledge Trigger the ingestion of an uploaded file. Download knowledge export Download the exports generated in the entities (in the Data section). Generate knowledge export Trigger the export of the knowledge of an entity. Ask for knowledge enrichment Trigger an enrichment for a given entity. Access dashboards Access to existing custom dashboards. Create / Update dashboards Create and update custom dashboards. Delete dashboards Delete existing custom dashboards. Manage public dashboards Manage public dashboards. Access investigations Access to existing investigations. Create / Update investigations Create and update investigations. Delete investigations Delete existing investigations. Access connectors Read information in the Data > Connectors section. Manage connector state Reset the connector state to restart ingestion from the beginning. Connectors API usage: register, ping, export push ... Connectors specific permissions for register, ping, push export files, etc. Access data sharing Access and consume data such as TAXII collections, CSV feeds and live streams. Manage data sharing Share data such as TAXII collections, CSV feeds and live streams or custom dashboards. Access ingestion Access (read only) remote OCTI streams, TAXII feeds, RSS feeds, CSV feeds. Manage ingestion Create, update, delete any remote OCTI streams, TAXII feeds, RSS feeds, CSV feeds. Manage CSV mappers Create, update and delete CSV mappers. Access to admin functionalities Parent capability allowing users to only view the settings. Access administration parameters Access and manage overall parameters of the platform in Settings > Parameters. Manage credentials Access and manage roles, groups, users, organizations and security policies. Manage marking definitions Update and delete marking definitions. Manage customization Customize entity types, rules, notifiers retention policies and decays rules. Manage taxonomies Manage labels, kill chain phases, vocabularies, status templates, cases templates. Access to security activity Access to activity log. Access to file indexing Manage file indexing. Access to support Generate and download support packages."},{"location":"administration/users/#manage-roles","title":"Manage roles","text":"

You can manage the roles in Settings > Security > Roles.

To create a role, just click on the + button:

Then you will be able to define the capabilities of the role:

"},{"location":"administration/users/#users","title":"Users","text":"

You can manage the users in Settings > Security > Users. If you are using Single-Sign-On (SSO), the users in OpenCTI are automatically created upon login.

To create a user, just click on the + button:

"},{"location":"administration/users/#manage-a-user","title":"Manage a user","text":"

When access to a user, it is possible to:

  • Visualize information including the token
  • Modify it, reset 2FA if necessary
  • Manage its sessions
  • Manage its triggers and digests
  • Visualize the history and operations
  • Manage its max confidence levels

From this view you can edit the user's information by clicking the \"Update\" button, which opens a panel with several tabs.

  • Overview tab: edit all basic information such as the name or language
  • Password tab: change the password for this user
  • Groups tab: select the groups this user belongs to
  • Organization Admin tab: see Organization administration
  • Confidences tab: manage the user's maximum confidence level and overrides per entity type

Mandatory max confidence level

A user without Max confidence level won't have the ability to create, delete or update any data in our platform. Please be sure that your users are always either assigned to group that have a confidence level defined or that have an override of this group confidence level.

"},{"location":"administration/users/#groups","title":"Groups","text":"

Groups are the main way to manage permissions and data segregation as well as platform customization for the given users part of this group. You can manage the groups in Settings > Security > Groups.

Here is the description of the group available parameters.

Parameter Description Auto new markings If a new marking definition is created, this group will automatically be granted to it. Default membership If a new user is created (manually or upon SSO), it will be added to this group. Roles Roles and capabilities granted to the users belonging to this group. Default dashboard Customize the home dashboard for the users belonging to this group. Default markings In Settings > Customization > Entity types, if a default marking definition is enabled, default markings of the group is used. Allowed markings Grant access to the group to the defined marking definitions, more details in data segregation. Max shareable markings Grant authorization to the group to share marking definitions. Triggers and digests Define defaults triggers and digests for the users belonging to this group. Max confidence level Define the maximum confidence level for the group: it will impact the capacity to update entities, the confidence level of a newly created entity by a user of the group.

Max confidence level when a user has multiple groups

A user with multiple groups will have the the highest confidence level of all its groups. For instance, if a user is part of group A (max confidence level = 100) and group B (max confidence level = 50), then the user max confidence level will be 100.

"},{"location":"administration/users/#manage-a-group","title":"Manage a group","text":"

When managing a group, you can define the members and all above configurations.

"},{"location":"administration/users/#organizations","title":"Organizations","text":"

Users can belong to organizations, which is an additional layer of data segregation and customization. To find out more about this part, please refer to the page on organization segregation.

"},{"location":"administration/users/#organization-administration","title":"Organization administration","text":"

Platform administrators can promote members of an organization as \"Organization administrator\". This elevated role grants them the necessary capabilities to create, edit and delete users from the corresponding Organization. Additionally, administrators have the flexibility to define a list of groups that can be granted to newly created members by the organization administrators. This feature simplifies the process of granting appropriate access and privileges to individuals joining the organization.

The platform administrator can promote/demote an organization admin through its user edition form.

Organization admin rights

The \"Organization admin\" has restricted access to Settings. They can only manage the members of the organizations for which they have been promoted as \"admins\".

"},{"location":"administration/audit/configuration/","title":"Configuration","text":"

Enterprise edition

Activity unified interface and logging are available under the \"OpenCTI Enterprise Edition\" license.

Please read the dedicated page to have all information

As explained in the overview page, all administration actions are listened by default. However, all knowledge are not listened by default due to performance impact on the platform.

For this reason you need to explicitly activate extended listening on user / group or organization.

Listening will start just after the configuration. Every past events will not be taken into account.

"},{"location":"administration/audit/events/","title":"Events","text":"

Enterprise edition

Activity unified interface and logging are available under the \"OpenCTI Enterprise Edition\" license.

Please read the dedicated page to have all information

"},{"location":"administration/audit/events/#description","title":"Description","text":"

OpenCTI activity capability is the way to unified whats really happen in the platform. In events section you will have access to the UI that will answer to \"who did what, where, and when?\" within your data with the maximum level of transparency.

"},{"location":"administration/audit/events/#include-knowledge","title":"Include knowledge","text":"

By default, the events screen only show you the administration actions done by the users.

If you want to see also the information about the knowledge, you can simply activate the filter in the bar to get the complete overview of all user actions.

Don't hesitate to read again the overview page to have a better understanding of the difference between Audit, Basic/Extended knowledge.

"},{"location":"administration/audit/overview/","title":"Overview","text":""},{"location":"administration/audit/overview/#overview","title":"Overview","text":"

Enterprise edition

Activity unified interface and logging are available under the \"OpenCTI Enterprise Edition\" license.

Please read the dedicated page to have all the information

OpenCTI activity capability is the way to unify what's really happening in the platform. With this feature you will be able to answer \"who did what, where, and when?\" within your data with the maximum level of transparency.

Enabling activity helps your security, auditing, and compliance entities monitor platform for possible vulnerabilities or external data misuse.

"},{"location":"administration/audit/overview/#categories","title":"Categories","text":"

The activity groups 3 different concepts that need to be explained.

"},{"location":"administration/audit/overview/#basic-knowledge","title":"Basic knowledge","text":"

The basic knowledge refers to all STIX data knowledge inside OpenCTI. Every create/update/delete action on that knowledge is accessible through the history. That basic activity is handled by the history manager and can also be found directly on each entity.

"},{"location":"administration/audit/overview/#extended-knowledge","title":"Extended knowledge","text":"

The extended knowledge refers to extra information data to track specific user activity. As this kind of tracking is expensive, the tracking will only be done for specific users/groups/organizations explicitly configured in the configuration window.

"},{"location":"administration/audit/overview/#audit-knowledge","title":"Audit knowledge","text":"

Audit is focusing on user administration or security actions. Audit will produce console/logs files along with user interface elements.

{\n  \"auth\": \"<User information>\",\n  \"category\": \"AUDIT\",\n  \"level\": \"<info | error>\",\n  \"message\": \"<human readable explanation>\",\n  \"resource\": {\n    \"type\": \"<authentication | mutation>\",\n    \"event_scope\": \"<depends on type>\",\n    \"event_access\": \"<administration>\",\n    \"data\": \"<contextual data linked to the event type>\",\n    \"version\": \"<version of audit log format>\"\n  },\n  \"timestamp\": \"<event date>\",\n  \"version\": \"<platform version>\"\n}\n
"},{"location":"administration/audit/overview/#architecture","title":"Architecture","text":"

OpenCTI uses different mechanisms to be able to publish actions (audit) or data modification (history)

"},{"location":"administration/audit/overview/#audit-knowledge_1","title":"Audit knowledge","text":"

Administration or security actions

With Enterprise edition activated, Administration and security actions are always written; you can't configure, exclude, or disable them

Supported

Not supported for now

Not applicable

"},{"location":"administration/audit/overview/#ingestion","title":"Ingestion","text":"Create Delete Edit Remote OCTI Streams"},{"location":"administration/audit/overview/#data-sharing","title":"Data sharing","text":"Create Delete Edit CSV Feeds TAXII Feeds Stream Feeds"},{"location":"administration/audit/overview/#connectors","title":"Connectors","text":"Create Delete Edit Connectors State reset Works"},{"location":"administration/audit/overview/#parameters","title":"Parameters","text":"Create Delete Edit Platform parameters"},{"location":"administration/audit/overview/#security","title":"Security","text":"Create Delete Edit Roles Groups Users Sessions Policies"},{"location":"administration/audit/overview/#customization","title":"Customization","text":"Create Delete Edit Entity types Rules engine Retention policies"},{"location":"administration/audit/overview/#taxonomies","title":"Taxonomies","text":"Create Delete Edit Status templates Case templates + tasks"},{"location":"administration/audit/overview/#accesses","title":"Accesses","text":"Listen Login (success or fail) Logout Unauthorized access"},{"location":"administration/audit/overview/#extended-knowledge_1","title":"Extended knowledge","text":"

Extended knowledge

Extented knowledge activity are written only if you activate the feature for a subset of users / groups or organizations

"},{"location":"administration/audit/overview/#data-management","title":"Data management","text":"

Some history actions are already included in the \"basic knowledge\". (basic marker)

Read Create Delete Edit Platform knowledge basic basic basic Background tasks knowledge Knowledge files basic basic Global data import files Analyst workbenches files Triggers Workspaces Investigations User profile"},{"location":"administration/audit/overview/#user-actions","title":"User actions","text":"Supported Ask for file import Ask for data enrichment Ask for export generation Execute global search"},{"location":"administration/audit/triggers/","title":"Activity triggers","text":"

Enterprise edition

Activity unified interface and logging are available under the \"OpenCTI Enterprise Edition\" license.

Please read the dedicated page to have all information

"},{"location":"administration/audit/triggers/#description","title":"Description","text":"

Having all the history in the user interface (events) is sometimes not enough to have a proactive monitoring. For this reason, you can configure some specific triggers to receive notifications on audit events. You can configure like personal triggers, lives one that will be sent directly or digest depending on your needs.

"},{"location":"administration/audit/triggers/#configuration","title":"Configuration","text":"

In this type of trigger, you will need to configure various options:

  • Notification target: user interface or email,
  • Recipients: the recipient of the notification,
  • Filters: a set of filters to get only events that really interest you.
"},{"location":"administration/audit/triggers/#event-structure","title":"Event structure","text":"

In order to correctly configure the filters, here's a definition of the event structure

  • Event type: authentication

    • Event scopes: login and logout

  • Event type: read

    • Event scopes: read and unauthorized

  • Event type: file

    • Event scopes: read, create and delete

  • Event type: mutation

    • Event scopes: unauthorized, update, create and delete

  • Event type: command

    • Event scopes: search, enrich, import and export
"},{"location":"deployment/authentication/","title":"Authentication","text":""},{"location":"deployment/authentication/#introduction","title":"Introduction","text":"

OpenCTI supports several authentication providers. If you configure multiple strategies, they will be tested in the order you declared them.

Activation

You need to configure/activate only the authentication strategy that you really want to propose to your users.

The product proposes two kinds of authentication strategies:

  • Form (asking user for a user/password),
  • Buttons (click with authentication on an external system).
"},{"location":"deployment/authentication/#supported-strategies","title":"Supported Strategies","text":"

Under the hood, we technically use the strategies provided by PassportJS. We integrate a subset of the strategies available with passport. If you need more, we can integrate other strategies.

"},{"location":"deployment/authentication/#local-users-form","title":"Local users (form)","text":"

This strategy uses the OpenCTI database as a user management.

OpenCTI use this strategy as the default, but it's not the one we recommend for security reasons.

\"local\": {\n    \"strategy\": \"LocalStrategy\",\n    \"config\": {\n        \"disabled\": false\n    }\n}\n

Production deployment

Please use the LDAP/Auth0/OpenID/SAML strategy for production deployment.

"},{"location":"deployment/authentication/#ldap-form","title":"LDAP (form)","text":"

This strategy can be used to authenticate your user with your company LDAP and is based on Passport - LDAPAuth.

\"ldap\": {\n    \"strategy\": \"LdapStrategy\",\n    \"config\": {\n        \"url\": \"ldaps://mydc.domain.com:686\",\n        \"bind_dn\": \"cn=Administrator,cn=Users,dc=mydomain,dc=com\",\n        \"bind_credentials\": \"MY_STRONG_PASSWORD\",\n        \"search_base\": \"cn=Users,dc=mydomain,dc=com\",\n        \"search_filter\": \"(cn={{username}})\",\n        \"mail_attribute\": \"mail\",\n        // \"account_attribute\": \"givenName\",\n        // \"firstname_attribute\": \"cn\",\n        // \"lastname_attribute\": \"cn\",\n        \"account_attrgroup_search_filteribute\": \"givenName\",\n        \"allow_self_signed\": true\n    }\n}\n

If you would like to use LDAP groups to automatically associate LDAP groups and OpenCTI groups/organizations:

\"ldap\": {\n    \"config\": {\n        ...\n        \"group_search_base\": \"cn=Groups,dc=mydomain,dc=com\",\n        \"group_search_filter\": \"(member={{dn}})\",\n        \"groups_management\": { // To map LDAP Groups to OpenCTI Groups\n            \"group_attribute\": \"cn\",\n            \"groups_mapping\": [\"LDAP_Group_1:OpenCTI_Group_1\", \"LDAP_Group_2:OpenCTI_Group_2\", ...]\n        },\n        \"organizations_management\": { // To map LDAP Groups to OpenCTI Organizations\n            \"organizations_path\": \"cn\",\n            \"organizations_mapping\": [\"LDAP_Group_1:OpenCTI_Organization_1\", \"LDAP_Group_2:OpenCTI_Organization_2\", ...]\n        }\n    }\n}\n
"},{"location":"deployment/authentication/#saml-button","title":"SAML (button)","text":"

This strategy can be used to authenticate your user with your company SAML and is based on Passport - SAML.

\"saml\": {\n    \"identifier\": \"saml\",\n    \"strategy\": \"SamlStrategy\",\n    \"config\": {\n        \"issuer\": \"mytestsaml\",\n        // \"account_attribute\": \"nameID\",\n        // \"firstname_attribute\": \"nameID\",\n        // \"lastname_attribute\": \"nameID\",\n        \"entry_point\": \"https://auth.mydomain.com/auth/realms/mydomain/protocol/saml\",\n        \"saml_callback_url\": \"http://localhost:4000/auth/saml/callback\",\n        // \"private_key\": \"MIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwg...\",\n        \"cert\": \"MIICmzCCAYMCBgF2Qt3X1zANBgkqhkiG9w0BAQsFADARMQ8w...\",\n        \"logout_remote\": false\n        \"want_assertions_signed\": true,\n        \"want_authn_response_signed\": true\n    }\n}\n

For the SAML strategy to work:

  • The cert parameter is mandatory (PEM format) because it is used to validate the SAML response.
  • The private_key (PEM format) is optional and is only required if you want to sign the SAML client request.

Certificates

Be careful to put the cert / private_key key in PEM format. Indeed, a lot of systems generally export the keys in X509 / PCKS12 formats and so you will need to convert them. Here is an example to extract PEM from PCKS12: 

openssl pkcs12 -in keystore.p12 -out newfile.pem -nodes\n

Starting from OpenCTI 6.2 when want_assertions_signed and want_authn_response_signed SAML parameter are not present in OpenCTI configuration, the default is set to \"true\" by the underlaying library (passport-saml) when previously it was false by default. If you have issues after upgrade, you can try with both of them set to false.

Here is an example of SAML configuration using environment variables:

- PROVIDERS__SAML__STRATEGY=SamlStrategy \n- \"PROVIDERS__SAML__CONFIG__LABEL=Login with SAML\"\n- PROVIDERS__SAML__CONFIG__ISSUER=mydomain\n- PROVIDERS__SAML__CONFIG__ENTRY_POINT=https://auth.mydomain.com/auth/realms/mydomain/protocol/saml\n- PROVIDERS__SAML__CONFIG__SAML_CALLBACK_URL=http://opencti.mydomain.com/auth/saml/callback\n- PROVIDERS__SAML__CONFIG__CERT=MIICmzCCAYMCBgF3Rt3X1zANBgkqhkiG9w0BAQsFADARMQ8w\n- PROVIDERS__SAML__CONFIG__LOGOUT_REMOTE=false\n- PROVIDERS__SAML__CONFIG__WANT_AUTHN_RESPONSE_SIGNED=true\n- PROVIDERS__SAML__CONFIG__WANT_ASSERTIONS_SIGNED=true\n

OpenCTI supports mapping SAML Roles/Groups on OpenCTI Groups. Here is an example:

\"saml\": {\n    \"config\": {\n        ...,\n        // Groups mapping\n        \"groups_management\": { // To map SAML Groups to OpenCTI Groups\n            \"group_attributes\": [\"Group\"],\n            \"groups_mapping\": [\"SAML_Group_1:OpenCTI_Group_1\", \"SAML_Group_2:OpenCTI_Group_2\", ...]\n        },\n        \"groups_management\": { // To map SAML Roles to OpenCTI Groups\n            \"group_attributes\": [\"Role\"],\n            \"groups_mapping\": [\"SAML_Role_1:OpenCTI_Group_1\", \"SAML_Role_2:OpenCTI_Group_2\", ...]\n        },\n        // Organizations mapping\n        \"organizations_management\": { // To map SAML Groups to OpenCTI Organizations\n            \"organizations_path\": [\"Group\"],\n            \"organizations_mapping\": [\"SAML_Group_1:OpenCTI_Organization_1\", \"SAML_Group_2:OpenCTI_Organization_2\", ...]\n        },\n        \"organizations_management\": { // To map SAML Roles to OpenCTI Organizations\n            \"organizations_path\": [\"Role\"],\n            \"organizations_mapping\": [\"SAML_Role_1:OpenCTI_Organization_1\", \"SAML_Role_2:OpenCTI_Organization_2\", ...]\n        }\n    }\n}\n

Here is an example of SAML Groups mapping configuration using environment variables:

- \"PROVIDERS__SAML__CONFIG__GROUPS_MANAGEMENT__GROUP_ATTRIBUTES=[\\\"Group\\\"]\"\n- \"PROVIDERS__SAML__CONFIG__GROUPS_MANAGEMENT__GROUPS_MAPPING=[\\\"SAML_Group_1:OpenCTI_Group_1\\\", \\\"SAML_Group_2:OpenCTI_Group_2\\\", ...]\"\n
"},{"location":"deployment/authentication/#auth0-button","title":"Auth0 (button)","text":"

This strategy allows to use Auth0 Service to handle the authentication and is based on Passport - Auth0.

\"authzero\": {\n    \"identifier\": \"auth0\",\n    \"strategy\": \"Auth0Strategy\",\n    \"config\": {\n        \"clientID\": \"XXXXXXXXXXXXXXXXXX\",\n        \"baseURL\": \"https://opencti.mydomain.com\",\n        \"clientSecret\": \"XXXXXXXXXXXXXXXXXX\",\n        \"callback_url\": \"https://opencti.mydomain.com/auth/auth0/callback\",\n        \"domain\": \"mycompany.eu.auth0.com\",\n        \"audience\": \"XXXXXXXXXXXXXXX\",\n        \"scope\": \"openid email profile XXXXXXXXXXXXXXX\",\n        \"logout_remote\": false\n    }\n}\n

Here is an example of Auth0 configuration using environment variables:

- PROVIDERS__AUTHZERO__STRATEGY=Auth0Strategy\n- PROVIDERS__AUTHZERO__CONFIG__CLIENT_ID=${AUTH0_CLIENT_ID}\n- PROVIDERS__AUTHZERO__CONFIG__BASEURL=${AUTH0_BASE_URL}\n- PROVIDERS__AUTHZERO__CONFIG__CLIENT_SECRET=${AUTH0_CLIENT_SECRET}\n- PROVIDERS__AUTHZERO__CONFIG__CALLBACK_URL=${AUTH0_CALLBACK_URL}\n- PROVIDERS__AUTHZERO__CONFIG__DOMAIN=${AUTH0_DOMAIN}\n- \"PROVIDERS__AUTHZERO__CONFIG__SCOPE=openid email profile\"\n- PROVIDERS__AUTHZERO__CONFIG__LOGOUT_REMOTE=false\n
"},{"location":"deployment/authentication/#openid-connect-button","title":"OpenID Connect (button)","text":"

This strategy allows to use the OpenID Connect Protocol to handle the authentication and is based on Node OpenID Client which is more powerful than the passport one.

\"oic\": {\n    \"identifier\": \"oic\",\n    \"strategy\": \"OpenIDConnectStrategy\",\n    \"config\": {\n        \"label\": \"Login with OpenID\",\n        \"issuer\": \"https://auth.mydomain.com/auth/realms/mydomain\",\n        \"client_id\": \"XXXXXXXXXXXXXXXXXX\",\n        \"client_secret\": \"XXXXXXXXXXXXXXXXXX\",\n        \"redirect_uris\": [\"https://opencti.mydomain.com/auth/oic/callback\"],\n        \"logout_remote\": false\n    }\n}\n

Here is an example of OpenID configuration using environment variables:

- PROVIDERS__OPENID__STRATEGY=OpenIDConnectStrategy \n- \"PROVIDERS__OPENID__CONFIG__LABEL=Login with OpenID\"\n- PROVIDERS__OPENID__CONFIG__ISSUER=https://auth.mydomain.com/auth/realms/xxxx\n- PROVIDERS__OPENID__CONFIG__CLIENT_ID=XXXXXXXXXXXXXXXXXX\n- PROVIDERS__OPENID__CONFIG__CLIENT_SECRET=XXXXXXXXXXXXXXXXXX\n- \"PROVIDERS__OPENID__CONFIG__REDIRECT_URIS=[\\\"https://opencti.mydomain.com/auth/oic/callback\\\"]\"\n- PROVIDERS__OPENID__CONFIG__LOGOUT_REMOTE=false\n

OpenCTI support mapping OpenID Claims on OpenCTI Groups (everything is tied to a group in the platform). Here is an example:

\"oic\": {\n    \"config\": {\n        ...,\n        // Groups mapping\n        \"groups_management\": { // To map OpenID Claims to OpenCTI Groups\n            \"groups_scope\": \"groups\",\n            \"groups_path\": [\"groups\", \"realm_access.groups\", \"resource_access.account.groups\"],\n            \"groups_mapping\": [\"OpenID_Group_1:OpenCTI_Group_1\", \"OpenID_Group_2:OpenCTI_Group_2\", ...]\n        },\n        // Organizations mapping  \n        \"organizations_management\": { // To map OpenID Claims to OpenCTI Organizations\n            \"organizations_scope\": \"groups\",\n            \"organizations_path\": [\"groups\", \"realm_access.groups\", \"resource_access.account.groups\"],\n            \"organizations_mapping\": [\"OpenID_Group_1:OpenCTI_Group_1\", \"OpenID_Group_2:OpenCTI_Group_2\", ...]\n        },\n    }\n}\n

Here is an example of OpenID Groups mapping configuration using environment variables:

- PROVIDERS__OPENID__CONFIG__GROUPS_MANAGEMENT__GROUPS_SCOPE=groups\n- \"PROVIDERS__OPENID__CONFIG__GROUPS_MANAGEMENT__GROUPS_PATH=[\\\"groups\\\", \\\"realm_access.groups\\\", \\\"resource_access.account.groups\\\"]\"\n- \"PROVIDERS__OPENID__CONFIG__GROUPS_MANAGEMENT__GROUPS_MAPPING=[\\\"OpenID_Group_1:OpenCTI_Group_1\\\", \\\"OpenID_Group_2:OpenCTI_Group_2\\\", ...]\"\n

By default, the claims are mapped based on the content of the JWT access_token. If you want to map claims which are in other JWT (such as id_token), you can define the following environment variables:

- PROVIDERS__OPENID__CONFIG__GROUPS_MANAGEMENT__TOKEN_REFERENCE=id_token\n- PROVIDERS__OPENID__CONFIG__ORGANISATIONS_MANAGEMENT__TOKEN_REFERENCE=id_token\n

Alternatively, you can request OpenCTI to use claims from the userinfo endpoint instead of a JWT. 

- PROVIDERS__OPENID__CONFIG__GROUPS_MANAGEMENT__READ_USERINFO=true\n- PROVIDERS__OPENID__CONFIG__ORGANISATIONS_MANAGEMENT__READ_USERINFO=true\n

"},{"location":"deployment/authentication/#facebook-button","title":"Facebook (button)","text":"

This strategy can authenticate your users with Facebook and is based on Passport - Facebook.

\"facebook\": {\n    \"identifier\": \"facebook\",\n    \"strategy\": \"FacebookStrategy\",\n    \"config\": {\n        \"client_id\": \"XXXXXXXXXXXXXXXXXX\",\n        \"client_secret\": \"XXXXXXXXXXXXXXXXXX\",\n        \"callback_url\": \"https://opencti.mydomain.com/auth/facebook/callback\",\n        \"logout_remote\": false\n    }\n}\n
"},{"location":"deployment/authentication/#google-button","title":"Google (button)","text":"

This strategy can authenticate your users with Google and is based on Passport - Google.

\"google\": {\n    \"identifier\": \"google\",\n    \"strategy\": \"GoogleStrategy\",\n    \"config\": {\n        \"client_id\": \"XXXXXXXXXXXXXXXXXX\",\n        \"client_secret\": \"XXXXXXXXXXXXXXXXXX\",\n        \"callback_url\": \"https://opencti.mydomain.com/auth/google/callback\",\n        \"logout_remote\": false\n    }\n}\n
"},{"location":"deployment/authentication/#github-button","title":"GitHub (button)","text":"

This strategy can authenticate your users with GitHub and is based on Passport - GitHub.

\"github\": {\n    \"identifier\": \"github\",\n    \"strategy\": \"GithubStrategy\",\n    \"config\": {\n        \"client_id\": \"XXXXXXXXXXXXXXXXXX\",\n        \"client_secret\": \"XXXXXXXXXXXXXXXXXX\",\n        \"callback_url\": \"https://opencti.mydomain.com/auth/github/callback\",\n        \"logout_remote\": false\n  }\n}\n
"},{"location":"deployment/authentication/#client-certificate-button","title":"Client certificate (button)","text":"

This strategy can authenticate a user based on SSL client certificates. For this, you need to configure OpenCTI to start in HTTPS, for example:

\"port\": 443,\n\"https_cert\": {\n    \"key\": \"/cert/server_key.pem\",\n    \"crt\": \"/cert/server_cert.pem\",\n    \"reject_unauthorized\": true\n}\n

And then add the ClientCertStrategy:

\"cert\": {\n    \"strategy\":\"ClientCertStrategy\",\n    \"config\": {\n        \"label\":\"CLIENT CERT\"\n    }\n}\n

Afterwards, when accessing for the first time OpenCTI, the browser will ask for the certificate you want to use.

"},{"location":"deployment/authentication/#proxy-headers-automatic","title":"Proxy headers (automatic)","text":"

This strategy can authenticate the users directly from trusted headers.

{\n  \"header\": {\n    \"strategy\": \"HeaderStrategy\",\n    \"config\": {\n      \"disabled\": false,\n      \"header_email\": \"auth_email_address\",\n      \"header_name\": \"auth_name\",\n      \"header_firstname\": \"auth_firstname\",\n      \"header_lastname\": \"auth_lastname\",\n      \"logout_uri\": \"https://www.filigran.io\",\n      \"groups_management\": {\n        \"groups_header\": \"auth_groups\",\n        \"groups_splitter\": \",\",\n        \"groups_mapping\": [\"admin:admin\", \"root:root\"]\n      },\n      \"organizations_management\": {\n        \"organizations_header\": \"auth_institution\",\n        \"organizations_splitter\": \",\",\n        \"organizations_mapping\": [\"test:test\"]\n      }\n    }\n  }\n}\n

If this mode is activated and the headers are available, the user will be automatically logged without any action or notice. The logout uri will remove the session and redirect to the configured uri. If not specified, the redirect will be done to the request referer and so the header authentication will be done again.

"},{"location":"deployment/authentication/#automatically-create-group-on-sso","title":"Automatically create group on SSO","text":"

The variable auto_create_group can be added in the options of some strategies (LDAP, SAML and OpenID). If this variable is true, the groups of a user that logins will automatically be created if they don\u2019t exist.

More precisely, if the user that tries to authenticate has groups that don\u2019t exist in OpenCTI but exist in the SSO configuration, there are two cases:

  • if auto_create_group= true in the SSO configuration: the groups are created at the platform initialization and the user will be mapped on them.
  • else: an error is raised.

Example

We assume that Group1 exists in the platform, and newGroup doesn\u2019t exist. The user that tries to log in has the group newGroup. If auto_create_group = true in the SSO configuration, the group named newGroup will be created at the platform initialization and the user will be mapped on it. If auto_create_group = false or is undefined, the user can\u2019t log in and an error is raised.

\"groups_management\": {\n  \"group_attribute\": \"cn\",\n  \"groups_mapping\": [\"SSO_GROUP_NAME1:group1\", \"SSO_GROUP_NAME_2:newGroup\", ...]\n},\n\"auto_create_group\": true\n
"},{"location":"deployment/authentication/#examples","title":"Examples","text":""},{"location":"deployment/authentication/#ldap-then-fallback-to-local","title":"LDAP then fallback to local","text":"

In this example the users have a login form and need to enter login and password. The authentication is done on LDAP first, then locally if user failed to authenticate and finally fail if none of them succeeded. Here is an example for the production.json file:

\"providers\": {\n    \"ldap\": {\n        \"strategy\": \"LdapStrategy\",\n        \"config\": {\n            \"url\": \"ldaps://mydc.mydomain.com:636\",\n            \"bind_dn\": \"cn=Administrator,cn=Users,dc=mydomain,dc=com\",\n            \"bind_credentials\": \"MY_STRONG_PASSWORD\",\n            \"search_base\": \"cn=Users,dc=mydomain,dc=com\",\n            \"search_filter\": \"(cn={{username}})\",\n            \"mail_attribute\": \"mail\",\n            \"account_attribute\": \"givenName\"\n        }\n    },\n    \"local\": {\n        \"strategy\": \"LocalStrategy\",\n        \"config\": {\n            \"disabled\": false\n        }\n    }\n}\n

If you use a container deployment, here is an example using environment variables:

- PROVIDERS__LDAP__STRATEGY=LdapStrategy\n- PROVIDERS__LDAP__CONFIG__URL=ldaps://mydc.mydomain.org:636\n- PROVIDERS__LDAP__CONFIG__BIND_DN=cn=Administrator,cn=Users,dc=mydomain,dc=com\n- PROVIDERS__LDAP__CONFIG__BIND_CREDENTIALS=XXXXXXXXXX\n- PROVIDERS__LDAP__CONFIG__SEARCH_BASE=cn=Users,dc=mydomain,dc=com\n- PROVIDERS__LDAP__CONFIG__SEARCH_FILTER=(cn={{username}})\n- PROVIDERS__LDAP__CONFIG__MAIL_ATTRIBUTE=mail\n- PROVIDERS__LDAP__CONFIG__ACCOUNT_ATTRIBUTE=givenName\n- PROVIDERS__LDAP__CONFIG__ALLOW_SELF_SIGNED=true\n- PROVIDERS__LOCAL__STRATEGY=LocalStrategy\n
"},{"location":"deployment/breaking-changes/","title":"Breaking changes and migrations","text":"

This section lists breaking changes introduced in OpenCTI, per version starting with the latest.

Please follow the migration guides if you need to upgrade your platform.

"},{"location":"deployment/breaking-changes/#opencti-62","title":"OpenCTI 6.2","text":""},{"location":"deployment/breaking-changes/#change-to-the-observable-promote","title":"Change to the observable \"promote\"","text":"

The API calls that promote an Observable to Indicator now return the created Indicator instead of the original Observable.

GraphQL API

  • Mutation StixCyberObservableEditMutations.promote is now deprecated
  • New Mutation StixCyberObservableEditMutations.promoteToIndicator introduced

Client-Python API

  • Client-python method client.stix_cyber_observable.promote_to_indicator is now deprecated
  • New Client-python method client.stix_cyber_observable.promote_to_indicator_v2 introduced

Discontinued Support

Please note that the deprecated methods will be permanently removed in OpenCTI 6.5.

"},{"location":"deployment/breaking-changes/#how-to-migrate","title":"How to migrate","text":"

If you are using custom scripts that make use of the deprecated API methods, please update these scripts.

The changes are straightforward: if you are using the return value of the method, you should now expect the new Indicator instead of the Observable being promoted; adapt your code accordingly.

"},{"location":"deployment/breaking-changes/#change-to-saml-authentication","title":"Change to SAML authentication","text":"

When want_assertions_signed and want_authn_response_signed SAML parameter are not present in OpenCTI configuration, the default is now set to true by the underlying library (passport-saml) when previously it was false by default.

"},{"location":"deployment/breaking-changes/#how-to-migrate_1","title":"How to migrate","text":"

If you have issues after upgrade, you can try with both parameters set to false.

"},{"location":"deployment/breaking-changes/#opencti-512","title":"OpenCTI 5.12","text":""},{"location":"deployment/breaking-changes/#major-changes-to-the-filtering-api","title":"Major changes to the filtering APi","text":"

OpenCTI 5.12 introduces a major rework of the filter engine with breaking changes to the model.

A dedicated blog post describes the reasons behind these changes.

"},{"location":"deployment/breaking-changes/#how-to-migrate_2","title":"How to migrate","text":"

Please read the dedicated migration guide.

"},{"location":"deployment/clustering/","title":"Clustering","text":""},{"location":"deployment/clustering/#introduction","title":"Introduction","text":"

The OpenCTI platform technological stack has been designed to be able to scale horizontally. All dependencies such as Elastic or Redis can be deployed in cluster mode and performances can be drastically increased by deploying multiple platform and worker instances.

"},{"location":"deployment/clustering/#high-level-architecture","title":"High level architecture","text":"

Here is the high level architecture for customers and Filigran cloud platform to ensure both high availability and throughput.

"},{"location":"deployment/clustering/#configuration","title":"Configuration","text":""},{"location":"deployment/clustering/#dependencies","title":"Dependencies","text":""},{"location":"deployment/clustering/#elasticsearch","title":"ElasticSearch","text":"

In the ElasticSearch configuration of OpenCTI, it is possible to declare all nodes.

- \"ELASTICSEARCH__URL=[\\\"https://user:pass@node1:9200\\\", \\\"https://user:pass@node2:9200\\\", ...]\"\n

Compatibility

OpenCTI is also compatible with OpenSearch and AWS / GCP / Azure native search services based on the ElasticSearch query language.

"},{"location":"deployment/clustering/#redis","title":"Redis","text":"

Redis should be turned to cluster mode:

- REDIS__MODE=cluster\n- \"REDIS__HOSTNAMES=[\\\"node1:6379\\\", \\\"node2:6379\\\", ...]\"\n

Compatibility

OpenCTI is also compatible with ElastiCache, MemoryStore and AWS / GCP / Azure native services based on the Redis protocol.

"},{"location":"deployment/clustering/#rabbitmq","title":"RabbitMQ","text":"

For the RabbitMQ cluster, you will need a TCP load balancer on top of the nodes since the configuration does not support multi-nodes for now:

- RABBITMQ__HOSTNAME=load-balancer-rabbitmq\n

Compatibility

OpenCTI is also compatible with Amazon MQ, CloudAMQP and AWS / GCP / Azure native services based on the AMQP protocol.

"},{"location":"deployment/clustering/#s3-bucket-minio","title":"S3 bucket / MinIO","text":"

MinIO is an open source server able to serve S3 buckets. It can be deployed in cluster mode and is compatible with several storage backend. OpenCTI is compatible with any tool following the S3 standard.

"},{"location":"deployment/clustering/#platform","title":"Platform","text":"

As showed on the schema, best practices for cluster mode and to avoid any congestion in the technological stack are:

  • Deploy platform(s) dedicated to end users and connectors registration
  • Deploy platform(s) dedicated to workers / ingestion process
    • We recommend 3 to 4 workers maximum by OpenCTI instance.
    • The ingestion platforms will never be accessed directly by end users.

When enabling clustering, the number of nodes is displayed in Settings > Parameters.

"},{"location":"deployment/clustering/#managers-and-schedulers","title":"Managers and schedulers","text":"

Also, since some managers like the rule engine, the task manager and the notification manager can take some resources in the OpenCTI NodeJS process, it is highly recommended to disable them in the frontend cluster. OpenCTI automatically handle the distribution and the launching of the engines across all nodes in the cluster except where they are explicitly disabled in the configuration.

"},{"location":"deployment/configuration/","title":"Configuration","text":"

The purpose of this section is to learn how to configure OpenCTI to have it tailored for your production and development needs. It is possible to check all default parameters implemented in the platform in the default.json file.

Here are the configuration keys, for both containers (environment variables) and manual deployment.

Parameters equivalence

The equivalent of a config variable in environment variables is the usage of a double underscores (__) for a level of config.

For example: 

\"providers\": {\n  \"ldap\": {\n    \"strategy\": \"LdapStrategy\"\n  }\n}\n

will become: 

PROVIDERS__LDAP__STRATEGY=LdapStrategy\n

If you need to put a list of elements for the key, it must have a special formatting. Here is an example for redirect URIs for OpenID config: 

\"PROVIDERS__OPENID__CONFIG__REDIRECT_URIS=[\\\"https://demo.opencti.io/auth/oic/callback\\\"]\"\n

"},{"location":"deployment/configuration/#platform","title":"Platform","text":""},{"location":"deployment/configuration/#api-frontend","title":"API & Frontend","text":""},{"location":"deployment/configuration/#basic-parameters","title":"Basic parameters","text":"Parameter Environment variable Default value Description app:port APP__PORT 4000 Listen port of the application app:base_path APP__BASE_PATH Specific URI (ie. /opencti) app:base_url APP__BASE_URL http://localhost:4000 Full URL of the platform (should include the base_path if any) app:request_timeout APP__REQUEST_TIMEOUT 1200000 Request timeout, in ms (default 20 minutes) app:session_timeout APP__SESSION_TIMEOUT 1200000 Session timeout, in ms (default 20 minutes) app:session_idle_timeout APP__SESSION_IDLE_TIMEOUT 0 Idle timeout (locking the screen), in ms (default 0 minute - disabled) app:session_cookie APP__SESSION_COOKIE false Use memory/session cookie instead of persistent one app:admin:email APP__ADMIN__EMAIL admin@opencti.io Default login email of the admin user app:admin:password APP__ADMIN__PASSWORD ChangeMe Default password of the admin user app:admin:token APP__ADMIN__TOKEN ChangeMe Default token (must be a valid UUIDv4) app:health_access_key APP__HEALTH_ACCESS_KEY ChangeMe Access key for the /health endpoint. Must be changed - will not respond to default value. Access with /health?health_access_key=ChangeMe"},{"location":"deployment/configuration/#network-and-security","title":"Network and security","text":"Parameter Environment variable Default value Description http_proxy HTTP_PROXY Proxy URL for HTTP connection (example: http://proxy:80080) https_proxy HTTPS_PROXY Proxy URL for HTTPS connection (example: http://proxy:80080) no_proxy NO_PROXY Comma separated list of hostnames for proxy exception (example: localhost,127.0.0.0/8,internal.opencti.io) app:https_cert:cookie_secure APP__HTTPS_CERT__COOKIE_SECURE false Set the flag \"secure\" for session cookies. app:https_cert:ca APP__HTTPS_CERT__CA Empty list [] Certificate authority paths or content, only if the client uses a self-signed certificate. app:https_cert:key APP__HTTPS_CERT__KEY Certificate key path or content app:https_cert:crt APP__HTTPS_CERT__CRT Certificate crt path or content app:https_cert:reject_unauthorized APP__HTTPS_CERT__REJECT_UNAUTHORIZED If not false, the server certificate is verified against the list of supplied CAs app:public_dashboard_authorized_domains APP__PUBLIC_DASHBOARD_AUTHORIZED_DOMAINS Empty string List of domain name that can display public dashboard in an embedded iframe. Empty string means none, '*' means all."},{"location":"deployment/configuration/#logging","title":"Logging","text":""},{"location":"deployment/configuration/#errors","title":"Errors","text":"Parameter Environment variable Default value Description app:app_logs:logs_level APP__APP_LOGS__LOGS_LEVEL info The application log level app:app_logs:logs_files APP__APP_LOGS__LOGS_FILES true If application logs is logged into files app:app_logs:logs_console APP__APP_LOGS__LOGS_CONSOLE true If application logs is logged to console (useful for containers) app:app_logs:logs_max_files APP__APP_LOGS__LOGS_MAX_FILES 7 Maximum number of daily files in logs app:app_logs:logs_directory APP__APP_LOGS__LOGS_DIRECTORY ./logs File logs directory"},{"location":"deployment/configuration/#audit","title":"Audit","text":"Parameter Environment variable Default value Description app:audit_logs:logs_files APP__AUDIT_LOGS__LOGS_FILES true If audit logs is logged into files app:audit_logs:logs_console APP__AUDIT_LOGS__LOGS_CONSOLE true If audit logs is logged to console (useful for containers) app:audit_logs:logs_max_files APP__AUDIT_LOGS__LOGS_MAX_FILES 7 Maximum number of daily files in logs app:audit_logs:logs_directory APP__AUDIT_LOGS__LOGS_DIRECTORY ./logs Audit logs directory"},{"location":"deployment/configuration/#telemetry","title":"Telemetry","text":"Parameter Environment variable Default value Description app:telemetry:metrics:enabled APP__TELEMETRY__METRICS__ENABLED false Enable the metrics collection. app:telemetry:metrics:exporter_otlp APP__TELEMETRY__METRICS__EXPORTER_OTLP Port to expose the OTLP endpoint. app:telemetry:metrics:exporter_prometheus APP__TELEMETRY__METRICS__EXPORTER_PROMETHEUS 14269 Port to expose the Prometheus endpoint."},{"location":"deployment/configuration/#maps-references","title":"Maps & references","text":"Parameter Environment variable Default value Description app:map_tile_server_dark APP__MAP_TILE_SERVER_DARK https://map.opencti.io/styles/filigran-dark2/{z}/{x}/{y}.png The address of the OpenStreetMap provider with dark theme style app:map_tile_server_light APP__MAP_TILE_SERVER_LIGHT https://map.opencti.io/styles/filigran-light2/{z}/{x}/{y}.png The address of the OpenStreetMap provider with light theme style app:reference_attachment APP__REFERENCE_ATTACHMENT false External reference mandatory attachment"},{"location":"deployment/configuration/#functional-customization","title":"Functional customization","text":"Parameter Environment variable Default value Description app:artifact_zip_password APP__ARTIFACT_ZIP_PASSWORD infected Artifact encrypted archive default password relations_deduplication:past_days RELATIONS_DEDUPLICATION__PAST_DAYS 30 De-duplicate relations based on start_time and stop_time - n days relations_deduplication:next_days RELATIONS_DEDUPLICATION__NEXT_DAYS 30 De-duplicate relations based on start_time and stop_time + n days relations_deduplication:created_by_based RELATIONS_DEDUPLICATION__CREATED_BY_BASED false Take into account the author to duplicate even if stat_time / stop_time are matching relations_deduplication:types_overrides:relationship_type:past_days RELATIONS_DEDUPLICATION__RELATIONSHIP_TYPE__PAST_DAYS Override the past days for a specific type of relationship (ex. targets) relations_deduplication:types_overrides:relationship_type:next_days RELATIONS_DEDUPLICATION__RELATIONSHIP_TYPE__NEXT_DAYS Override the next days for a specific type of relationship (ex. targets) relations_deduplication:types_overrides:relationship_type:created_by_based RELATIONS_DEDUPLICATION__RELATIONSHIP_TYPE__CREATED_BY_BASED Override the author duplication for a specific type of relationship (ex. targets)"},{"location":"deployment/configuration/#technical-customization","title":"Technical customization","text":"Parameter Environment variable Default value Description app:graphql:playground:enabled APP__GRAPHQL__PLAYGROUND__ENABLED true Enable the playground on /graphql app:graphql:playground:force_disabled_introspection APP__GRAPHQL__PLAYGROUND__FORCE_DISABLED_INTROSPECTION true Introspection is allowed to auth users but can be disabled in needed app:concurrency:retry_count APP__CONCURRENCY__RETRY_COUNT 200 Number of try to get the lock to work an element (create/update/merge, ...) app:concurrency:retry_delay APP__CONCURRENCY__RETRY_DELAY 100 Delay between 2 lock retry (in milliseconds) app:concurrency:retry_jitter APP__CONCURRENCY__RETRY_JITTER 50 Random jitter to prevent concurrent retry (in milliseconds) app:concurrency:max_ttl APP__CONCURRENCY__MAX_TTL 30000 Global maximum time for lock retry (in milliseconds)"},{"location":"deployment/configuration/#dependencies","title":"Dependencies","text":""},{"location":"deployment/configuration/#xtm-suite","title":"XTM Suite","text":"Parameter Environment variable Default value Description xtm:openbas_url XTM__OPENBAS_URL OpenBAS URL xtm:openbas_token XTM__OPENBAS_TOKEN OpenBAS token xtm:openbas_reject_unauthorized XTM__OPENBAS_REJECT_UNAUTHORIZED false Enable TLS certificate check xtm:openbas_disable_display XTM__OPENBAS_DISABLE_DISPLAY false Disable OpenBAS posture in the UI"},{"location":"deployment/configuration/#elasticsearch","title":"ElasticSearch","text":"Parameter Environment variable Default value Description elasticsearch:engine_selector ELASTICSEARCH__ENGINE_SELECTOR auto elk or opensearch, default is auto, please put elk if you use token auth. elasticsearch:engine_check ELASTICSEARCH__ENGINE_CHECK false Disable Search Engine compatibility matrix verification. Caution: OpenCTI was developed in compliance with the compatibility matrix. Setting the parameter to true may result in negative impacts. elasticsearch:url ELASTICSEARCH__URL http://localhost:9200 URL(s) of the ElasticSearch (supports http://user:pass@localhost:9200 and list of URLs) elasticsearch:username ELASTICSEARCH__USERNAME Username can be put in the URL or with this parameter elasticsearch:password ELASTICSEARCH__PASSWORD Password can be put in the URL or with this parameter elasticsearch:api_key ELASTICSEARCH__API_KEY API key for ElasticSearch token auth. Please set also engine_selector to elk elasticsearch:index_prefix ELASTICSEARCH__INDEX_PREFIX opencti Prefix for the indices elasticsearch:ssl:reject_unauthorized ELASTICSEARCH__SSL__REJECT_UNAUTHORIZED true Enable TLS certificate check elasticsearch:ssl:ca ELASTICSEARCH__SSL__CA Custom certificate path or content elasticsearch:search_wildcard_prefix ELASTICSEARCH__SEARCH_WILDCARD_PREFIX false Search includes words with automatic fuzzy comparison elasticsearch:search_fuzzy ELASTICSEARCH__SEARCH_FUZZY false Search will include words not starting with the search keyword"},{"location":"deployment/configuration/#redis","title":"Redis","text":"Parameter Environment variable Default value Description redis:mode REDIS__MODE single Connect to redis in \"single\", \"sentinel or \"cluster\" mode redis:namespace REDIS__NAMESPACE Namespace (to use as prefix) redis:hostname REDIS__HOSTNAME localhost Hostname of the Redis Server redis:hostnames REDIS__HOSTNAMES Hostnames definition for Redis cluster or sentinel mode: a list of host:port objects. redis:port REDIS__PORT 6379 Port of the Redis Server redis:sentinel_master_name REDIS__SENTINEL_MASTER_NAME Name of your Redis Sentinel Master (mandatory in sentinel mode) redis:use_ssl REDIS__USE_SSL false Is the Redis Server has TLS enabled redis:username REDIS__USERNAME Username of the Redis Server redis:password REDIS__PASSWORD Password of the Redis Server redis:database REDIS__DATABASE Database of the Redis Server (only work in single mode) redis:ca REDIS__CA [] List of path(s) of the CA certificate(s) redis:trimming REDIS__TRIMMING 2000000 Number of elements to maintain in the stream. (0 = unlimited)"},{"location":"deployment/configuration/#rabbitmq","title":"RabbitMQ","text":"Parameter Environment variable Default value Description rabbitmq:hostname RABBITMQ__HOSTNAME localhost 7 Hostname of the RabbitMQ server rabbitmq:port RABBITMQ__PORT 5672 Port of the RabbitMQ server rabbitmq:port_management RABBITMQ__PORT_MANAGEMENT 15672 Port of the RabbitMQ Management Plugin rabbitmq:username RABBITMQ__USERNAME guest RabbitMQ user rabbitmq:password RABBITMQ__PASSWORD guest RabbitMQ password rabbitmq:queue_type RABBITMQ__QUEUE_TYPE \"classic\" RabbitMQ Queue Type (\"classic\" or \"quorum\") - - - - rabbitmq:use_ssl RABBITMQ__USE_SSL false Use TLS connection rabbitmq:use_ssl_cert RABBITMQ__USE_SSL_CERT Path or cert content rabbitmq:use_ssl_key RABBITMQ__USE_SSL_KEY Path or key content rabbitmq:use_ssl_pfx RABBITMQ__USE_SSL_PFX Path or pfx content rabbitmq:use_ssl_ca RABBITMQ__USE_SSL_CA [] List of path(s) of the CA certificate(s) rabbitmq:use_ssl_passphrase RABBITMQ__SSL_PASSPHRASE Passphrase for the key certificate rabbitmq:use_ssl_reject_unauthorized RABBITMQ__SSL_REJECT_UNAUTHORIZED false Reject rabbit self signed certificate - - - - rabbitmq:management_ssl RABBITMQ__MANAGEMENT_SSL false Is the Management Plugin has TLS enabled rabbitmq:management_ssl_reject_unauthorized RABBITMQ__SSL_REJECT_UNAUTHORIZED true Reject management self signed certificate"},{"location":"deployment/configuration/#s3-bucket","title":"S3 Bucket","text":"Parameter Environment variable Default value Description minio:endpoint MINIO__ENDPOINT localhost Hostname of the S3 Service. Example if you use AWS Bucket S3: s3.us-east-1.amazonaws.com (if minio:bucket_region value is us-east-1). This parameter value can be omitted if you use Minio as an S3 Bucket Service. minio:port MINIO__PORT 9000 Port of the S3 Service. For AWS Bucket S3 over HTTPS, this value can be changed (usually 443). minio:use_ssl MINIO__USE_SSL false Indicates whether the S3 Service has TLS enabled. For AWS Bucket S3 over HTTPS, this value could be true. minio:access_key MINIO__ACCESS_KEY ChangeMe Access key for the S3 Service. minio:secret_key MINIO__SECRET_KEY ChangeMe Secret key for the S3 Service. minio:bucket_name MINIO__BUCKET_NAME opencti-bucket S3 bucket name. Useful to change if you use AWS. minio:bucket_region MINIO__BUCKET_REGION us-east-1 Region of the S3 bucket if you are using AWS. This parameter value can be omitted if you use Minio as an S3 Bucket Service. minio:use_aws_role MINIO__USE_AWS_ROLE false Indicates whether to use AWS role auto credentials. When this parameter is configured, the minio:access_key and minio:secret_key parameters are not necessary."},{"location":"deployment/configuration/#smtp-service","title":"SMTP Service","text":"Parameter Environment variable Default value Description smtp:hostname SMTP__HOSTNAME SMTP Server hostname smtp:port SMTP__PORT 465 SMTP Port (25 or 465 for TLS) smtp:use_ssl SMTP__USE_SSL false SMTP over TLS smtp:reject_unauthorized SMTP__REJECT_UNAUTHORIZED false Enable TLS certificate check smtp:username SMTP__USERNAME SMTP Username if authentication is needed smtp:password SMTP__PASSWORD SMTP Password if authentication is needed"},{"location":"deployment/configuration/#ai-service","title":"AI Service","text":"

AI deployment and cloud services

There are several possibilities for Enterprise Edition customers to use OpenCTI AI endpoints:

  • Use the Filigran AI Service leveraging our custom AI model using the token given by the support team.
  • Use OpenAI or MistralAI cloud endpoints using your own tokens.
  • Deploy or use local AI endpoints (Filigran can provide you with the custom model).
Parameter Environment variable Default value Description ai:enabled AI__ENABLED true Enable AI capabilities ai:type AI__TYPE mistralai AI type (mistralai or openai) ai:endpoint AI__ENDPOINT Endpoint URL (empty means default cloud service) ai:token AI__TOKEN Token for endpoint credentials ai:model AI__MODEL Model to be used for text generation (depending on type) ai:model_images AI__MODEL_IMAGES Model to be used for image generation (depending on type)"},{"location":"deployment/configuration/#using-a-credentials-provider","title":"Using a credentials provider","text":"

In some cases, it may not be possible to put directly dependencies credentials directly in environment variables or static configuration. The platform can then retrieve them from a credentials provider. Here is the list of supported providers:

Credentials provider Provider key CyberArk cyberark

For each dependency, special configuration keys are available to ensure the platform retrieves credentials during start process. Not all dependencies support this mechanism, here is the exhaustive list:

Dependency Prefix ElasticSearch elasticsearch S3 Storage minio Redis redis OpenID secrets oic"},{"location":"deployment/configuration/#common-configurations","title":"Common configurations","text":"Parameter Environment variable Default value Description {prefix}:credentials_provider:https_cert:reject_unauthorized {PREFIX}__CREDENTIALS_PROVIDER__HTTPS_CERT__REJECT_UNAUTHORIZED false Reject unauthorized TLS connection {prefix}:credentials_provider:https_cert:crt {PREFIX}__CREDENTIALS_PROVIDER__HTTPS_CERT__CRT Path to the HTTPS certificate {prefix}:credentials_provider:https_cert:key {PREFIX}__CREDENTIALS_PROVIDER__HTTPS_CERT__KEY Path to the HTTPS key {prefix}:credentials_provider:https_cert:ca {PREFIX}__CREDENTIALS_PROVIDER__HTTPS_CERT__CA Path to the HTTPS CA certificate"},{"location":"deployment/configuration/#cyberark","title":"CyberArk","text":"Parameter Environment variable Default value Description {prefix}:credentials_provider:cyberark:uri {PREFIX}__CREDENTIALS_PROVIDER__CYBERARK__URI The URL of the CyberArk endpoint for credentials retrieval (GET request) {prefix}:credentials_provider:cyberark:app_id {PREFIX}__CREDENTIALS_PROVIDER__CYBERARK__APP_ID The used application ID for the dependency within CyberArk {prefix}:credentials_provider:cyberark:safe {PREFIX}__CREDENTIALS_PROVIDER__CYBERARK__SAFE The used safe key for the dependency within CyberArk {prefix}:credentials_provider:cyberark:object {PREFIX}__CREDENTIALS_PROVIDER__CYBERARK__OBJECT The used object key for the dependency within CyberArk {prefix}:credentials_provider:cyberark:default_splitter {PREFIX}__CREDENTIALS_PROVIDER__CYBERARK__DEFAULT_SPLITTER : Default splitter of the credentials results, for \"username:password\", default is \":\" {prefix}:credentials_provider:cyberark:field_targets {PREFIX}__CREDENTIALS_PROVIDER__CYBERARK__FIELD_TARGETS [] Fields targets in the data content response after splitting

Here is an example for ElasticSearch:

Environment variables: 

- ELASTICSEARCH__CREDENTIALS_PROVIDER__CYBERARK__URI=http://my.cyberark.com/AIMWebService/api/Accounts\n- ELASTICSEARCH__CREDENTIALS_PROVIDER__CYBERARK__APP_ID=opencti-elastic\n- ELASTICSEARCH__CREDENTIALS_PROVIDER__CYBERARK__SAFE=mysafe-key\n- ELASTICSEARCH__CREDENTIALS_PROVIDER__CYBERARK__OBJECT=myobject-key\n- \"ELASTICSEARCH__CREDENTIALS_PROVIDER__CYBERARK__DEFAULT_SPLITTER=:\" # As default is already \":\", may not be necessary\n- \"ELASTICSEARCH__CREDENTIALS_PROVIDER__CYBERARK__FIELD_TARGETS=[\\\"username\\\",\\\"password\\\"]\"\n

JSON version: 

\"elasticsearch\": {\n    \"credentials_provider\": {\n        \"cyberark\": {\n            \"uri\": \"http://my.cyberark.com/AIMWebService/api/Accounts\",\n            \"app_id\": \"opencti-elastic\",\n            \"safe\": \"mysafe-key\",\n            \"object\": \"myobject-key\",\n            \"default_splitter\": \":\",\n            \"field_targets\": [\"username\", \"password\"]\n      }\n    }\n}\n

Another example for MinIo (S3) using certificate:

Environment variables: 

- MINIO__CREDENTIALS_PROVIDER__HTTPS_CERT__CRT=/cert_volume/mycert.crt\n- MINIO__CREDENTIALS_PROVIDER__HTTPS_CERT__KEY=/cert_volume/mycert.key\n- MINIO__CREDENTIALS_PROVIDER__HTTPS_CERT__CA=/cert_volume/ca.crt\n- MINIO__CREDENTIALS_PROVIDER__CYBERARK__URI=http://my.cyberark.com/AIMWebService/api/Accounts\n- MINIO__CREDENTIALS_PROVIDER__CYBERARK__APP_ID=opencti-s3\n- MINIO__CREDENTIALS_PROVIDER__CYBERARK__SAFE=mysafe-key\n- MINIO__CREDENTIALS_PROVIDER__CYBERARK__OBJECT=myobject-key\n- \"MINIO__CREDENTIALS_PROVIDER__CYBERARK__DEFAULT_SPLITTER=:\" # As default is already \":\", may not be necessary\n- \"MINIO__CREDENTIALS_PROVIDER__CYBERARK__FIELD_TARGETS=[\\\"access_key\\\",\\\"secret_key\\\"]\"\n

"},{"location":"deployment/configuration/#engines-schedules-and-managers","title":"Engines, Schedules and Managers","text":"Parameter Environment variable Default value Description rule_engine:enabled RULE_ENGINE__ENABLED true Enable/disable the rule engine rule_engine:lock_key RULE_ENGINE__LOCK_KEY rule_engine_lock Lock key of the engine in Redis - - - - history_manager:enabled HISTORY_MANAGER__ENABLED true Enable/disable the history manager history_manager:lock_key HISTORY_MANAGER__LOCK_KEY history_manager_lock Lock key for the manager in Redis - - - - task_scheduler:enabled TASK_SCHEDULER__ENABLED true Enable/disable the task scheduler task_scheduler:lock_key TASK_SCHEDULER__LOCK_KEY task_manager_lock Lock key for the scheduler in Redis task_scheduler:interval TASK_SCHEDULER__INTERVAL 10000 Interval to check new task to do (in ms) - - - - sync_manager:enabled SYNC_MANAGER__ENABLED true Enable/disable the sync manager sync_manager:lock_key SYNC_MANAGER__LOCK_KEY sync_manager_lock Lock key for the manager in Redis sync_manager:interval SYNC_MANAGER__INTERVAL 10000 Interval to check new sync feeds to consume (in ms) - - - - expiration_scheduler:enabled EXPIRATION_SCHEDULER__ENABLED true Enable/disable the scheduler expiration_scheduler:lock_key EXPIRATION_SCHEDULER__LOCK_KEY expired_manager_lock Lock key for the scheduler in Redis expiration_scheduler:interval EXPIRATION_SCHEDULER__INTERVAL 300000 Interval to check expired indicators (in ms) - - - - retention_manager:enabled RETENTION_MANAGER__ENABLED true Enable/disable the retention manager retention_manager:lock_key RETENTION_MANAGER__LOCK_KEY retention_manager_lock Lock key for the manager in Redis retention_manager:interval RETENTION_MANAGER__INTERVAL 60000 Interval to check items to be deleted (in ms) - - - - notification_manager:enabled NOTIFICATION_MANAGER__ENABLED true Enable/disable the notification manager notification_manager:lock_live_key NOTIFICATION_MANAGER__LOCK_LIVE_KEY notification_live_manager_lock Lock live key for the manager in Redis notification_manager:lock_digest_key NOTIFICATION_MANAGER__LOCK_DIGEST_KEY notification_digest_manager_lock Lock digest key for the manager in Redis notification_manager:interval NOTIFICATION_MANAGER__INTERVAL 10000 Interval to push notifications - - - - publisher_manager:enabled PUBLISHER_MANAGER__ENABLED true Enable/disable the publisher manager publisher_manager:lock_key PUBLISHER_MANAGER__LOCK_KEY publisher_manager_lock Lock key for the manager in Redis publisher_manager:interval PUBLISHER_MANAGER__INTERVAL 10000 Interval to send notifications / digests (in ms) - - - - ingestion_manager:enabled INGESTION_MANAGER__ENABLED true Enable/disable the ingestion manager ingestion_manager:lock_key INGESTION_MANAGER__LOCK_KEY ingestion_manager_lock Lock key for the manager in Redis ingestion_manager:interval INGESTION_MANAGER__INTERVAL 300000 Interval to check for new data in remote feeds - - - - playbook_manager:enabled PLAYBOOK_MANAGER__ENABLED true Enable/disable the playbook manager playbook_manager:lock_key PLAYBOOK_MANAGER__LOCK_KEY publisher_manager_lock Lock key for the manager in Redis playbook_manager:interval PLAYBOOK_MANAGER__INTERVAL 60000 Interval to check new playbooks - - - - activity_manager:enabled ACTIVITY_MANAGER__ENABLED true Enable/disable the activity manager activity_manager:lock_key ACTIVITY_MANAGER__LOCK_KEY activity_manager_lock Lock key for the manager in Redis - - - - connector_manager:enabled CONNECTOR_MANAGER__ENABLED true Enable/disable the connector manager connector_manager:lock_key CONNECTOR_MANAGER__LOCK_KEY connector_manager_lock Lock key for the manager in Redis connector_manager:works_day_range CONNECTOR_MANAGER__WORKS_DAY_RANGE 7 Days range before considering the works as too old connector_manager:interval CONNECTOR_MANAGER__INTERVAL 10000 Interval to check the state of the works - - - - import_csv_built_in_connector:enabled IMPORT_CSV_BUILT_IN_CONNECTOR__ENABLED true Enable/disable the csv import connector import_csv_built_in_connector:validate_before_import IMPORT_CSV_BUILT_IN_CONNECTOR__VALIDATE_BEFORE_IMPORT false Validates the bundle before importing - - - - file_index_manager:enabled FILE_INDEX_MANAGER__ENABLED true Enable/disable the file indexing manager file_index_manager:stream_lock_key FILE_INDEX_MANAGER__STREAM_LOCK file_index_manager_stream_lock Stream lock key for the manager in Redis file_index_manager:interval FILE_INDEX_MANAGER__INTERVAL 60000 Interval to check for new files - - - - indicator_decay_manager:enabled INDICATOR_DECAY_MANAGER__ENABLED true Enable/disable the indicator decay manager indicator_decay_manager:lock_key INDICATOR_DECAY_MANAGER__LOCK_KEY indicator_decay_manager_lock Lock key for the manager in Redis indicator_decay_manager:interval INDICATOR_DECAY_MANAGER__INTERVAL 60000 Interval to check for indicators to update indicator_decay_manager:batch_size INDICATOR_DECAY_MANAGER__BATCH_SIZE 10000 Number of indicators handled by the manager - - - - garbage_collection_manager:enabled GARBAGE_COLLECTION_MANAGER__ENABLED true Enable/disable the trash manager garbage_collection_manager:lock_key GARBAGE_COLLECTION_MANAGER__LOCK_KEY garbage_collection_manager_lock Lock key for the manager in Redis garbage_collection_manager:interval GARBAGE_COLLECTION_MANAGER__INTERVAL 60000 Interval to check for trash elements to delete garbage_collection_manager:batch_size GARBAGE_COLLECTION_MANAGER__BATCH_SIZE 10000 Number of trash elements to delete at once garbage_collection_manager:deleted_retention_days GARBAGE_COLLECTION_MANAGER__DELETED_RETENTION_DAYS 7 Days after which elements in trash are deleted - - - - telemetry_manager:lock_key TELEMETRY_MANAGER__LOCK_LOCK telemetry_manager_lock Lock key for the manager in Redis

Manager's duties

A description of each manager's duties is available on a dedicated page.

"},{"location":"deployment/configuration/#worker-and-connector","title":"Worker and connector","text":"

Can be configured manually using the configuration file config.yml or through environment variables.

Parameter Environment variable Default value Description opencti:url OPENCTI_URL The URL of the OpenCTI platform opencti:token OPENCTI_TOKEN A token of an administrator account with bypass capability - - - - mq:use_ssl / / Depending of the API configuration (fetch from API) mq:use_ssl_ca MQ_USE_SSL_CA Path or ca content mq:use_ssl_cert MQ_USE_SSL_CERT Path or cert content mq:use_ssl_key MQ_USE_SSL_KEY Path or key content mq:use_ssl_passphrase MQ_USE_SSL_PASSPHRASE Passphrase for the key certificate mq:use_ssl_reject_unauthorized MQ_USE_SSL_REJECT_UNAUTHORIZED false Reject rabbit self signed certificate"},{"location":"deployment/configuration/#worker-specific-configuration","title":"Worker specific configuration","text":""},{"location":"deployment/configuration/#logging_1","title":"Logging","text":"Parameter Environment variable Default value Description worker:log_level WORKER_LOG_LEVEL info The log level (error, warning, info or debug)"},{"location":"deployment/configuration/#telemetry_1","title":"Telemetry","text":"Parameter Environment variable Default value Description worker:telemetry_enabled WORKER_TELEMETRY_ENABLED false Enable the Prometheus endpoint worker:telemetry_prometheus_port WORKER_PROMETHEUS_TELEMETRY_PORT 14270 Port of the Prometheus endpoint worker:telemetry_prometheus_host WORKER_PROMETHEUS_TELEMETRY_HOST 0.0.0.0 Listen address of the Prometheus endpoint"},{"location":"deployment/configuration/#connector-specific-configuration","title":"Connector specific configuration","text":"

For specific connector configuration, you need to check each connector behavior.

"},{"location":"deployment/configuration/#elasticsearch_1","title":"ElasticSearch","text":"

If you want to adapt the memory consumption of ElasticSearch, you can use these options:

# Add the following environment variable:\n\"ES_JAVA_OPTS=-Xms8g -Xmx8g\"\n

This can be done in configuration file in the jvm.conf file.

"},{"location":"deployment/connectors/","title":"Connectors","text":""},{"location":"deployment/connectors/#introduction","title":"Introduction","text":"

Connectors list

You are looking for the available connectors? The list is in the OpenCTI Ecosystem.

Connectors are the cornerstone of the OpenCTI platform and allow organizations to easily ingest, enrich or export data. According to their functionality and use case, they are categorized in the following classes.

"},{"location":"deployment/connectors/#import","title":"Import","text":"

These connectors automatically retrieve information from an external organization, application, or service, and convert it to STIX 2.1 bundles. Then, they import it into OpenCTI using the workers.

"},{"location":"deployment/connectors/#enrichment","title":"Enrichment","text":"

When a new object is created in the platform or on the user request, it is possible to trigger the internal enrichment connector to lookup and/or search the object in external organizations, applications, or services. If the object is found, the connectors will generate a STIX 2.1 bundle which will increase the level of knowledge about the concerned object.

"},{"location":"deployment/connectors/#stream","title":"Stream","text":"

These connectors connect to a platform live stream and continuously do something with the received events. In most cases, they are used to consume OpenCTI data and insert them in third-party platforms such as SIEMs, XDRs, EDRs, etc. In some cases, stream connectors can also query the external system on a regular basis and act as import connector for instance to gather alerts and sightings related to CTI data and push them to OpenCTI (bi-directional).

"},{"location":"deployment/connectors/#import-files","title":"Import files","text":"

Information from an uploaded file can be extracted and ingested into OpenCTI. Examples are files attached to a report or a STIX 2.1 file.

"},{"location":"deployment/connectors/#export-files","title":"Export files","text":"

Information stored in OpenCTI can be extracted into different file formats like .csv or .json (STIX 2.1).

"},{"location":"deployment/connectors/#connector-configuration","title":"Connector configuration","text":""},{"location":"deployment/connectors/#connector-users-and-tokens","title":"Connector users and tokens","text":"

All connectors have to be able to access the OpenCTI API. To allow this connection, they have 2 mandatory configuration parameters, the OPENCTI_URL and the OPENCTI_TOKEN.

Connectors tokens

Be careful, we strongly recommend to use a dedicated token for each connector running in the platform. So you have to create a specific user for each of them.

Also, if all connectors users can run with a user belonging to the Connectors group (with the Connector role), the Internal Export Files should be run with a user who is Administrator (with bypass capability) because they impersonate the user requesting the export to avoid data leak.

Type Required role Used permissions EXTERNAL_IMPORT Connector Import data with the connector user. INTERNAL_ENRICHMENT Connector Enrich data with the connector user. INTERNAL_IMPORT_FILE Connector Import data with the connector user. INTERNAL_EXPORT_FILE Administrator Export data with the user who requested the export. STREAM Connector Consume the streams with the connector user."},{"location":"deployment/connectors/#parameters","title":"Parameters","text":"

In addition to these 2 parameters, connectors have other mandatory parameters that need to be set in order to get them work.

Here is an example of a connector docker-compose.yml file: 

- CONNECTOR_ID=ChangeMe\n- CONNECTOR_TYPE=EXTERNAL_IMPORT\n- CONNECTOR_NAME=MITRE ATT&CK\n- CONNECTOR_SCOPE=identity,attack-pattern,course-of-action,intrusion-set,malware,tool,report\n- CONNECTOR_LOG_LEVEL=info\n

Here is an example in a connector config.yml file:

connector:\n  id: 'ChangeMe'\n  type: 'EXTERNAL_IMPORT'\n  name: 'MITRE ATT&CK'\n  scope: 'identity,attack-pattern,course-of-action,intrusion-set,malware,tool,report'\n  log_level: 'info'\n
"},{"location":"deployment/connectors/#advanced-parameters","title":"Advanced parameters","text":"

By default, connectors are connecting to RabbitMQ.

You can also send the Bundle to API (stixBundlePush) that will push the bundle to the correct RabbitMQ queue.

connector:\n  queue_protocol: 'api' # use api to send bundle through API mutation, amqp (default) to send to rabbit\n

Limitation

Currently the connector can not send bundle larger the the configuration of the OpenCTI backend (default 50Mb)

The connection to RabbitMQ is done by using parameters and credentials directly given by the API during the connector registration process. In some cases, you may need to override them.

- MQ_HOST=rabbit.mydomain.com\n- MQ_PORT=5672\n- MQ_VHOST=/\n- MQ_USE_SSL=false\n- MQ_USER=guest\n- MQ_PASS=guest\n

Here is an example in a connector config.yml file:

mq:\n  host: 'rabbit.mydomain.com'\n  port: '5672'\n  use_ssl: false\n  user: 'guest'\n  pass: 'guest'\n
"},{"location":"deployment/connectors/#networking","title":"Networking","text":"

Be aware that all connectors are reaching RabbitMQ based the RabbitMQ configuration provided by the OpenCTI platform. The connector must be able to reach RabbitMQ on the specified hostname and port. If you have a specific Docker network configuration, please be sure to adapt your docker-compose.yml file in such way that the connector container gets attached to the OpenCTI Network, e.g.:

networks:\n  default:\n    external: true\n    name: opencti-docker_default\n

"},{"location":"deployment/connectors/#connector-token","title":"Connector token","text":""},{"location":"deployment/connectors/#create-the-user","title":"Create the user","text":"

As mentioned previously, it is strongly recommended to run each connector with its own user. The Internal Export File connectors should be launched with a user that belongs to a group which has an \u201cAdministrator\u201d role (with bypass all capabilities enabled).

By default, in platform, a group named \"Connectors\" already exists. So just create a new user with the name [C] Name of the connector in Settings > Security > Users.

"},{"location":"deployment/connectors/#put-the-user-in-the-group","title":"Put the user in the group","text":"

Just go to the user you have just created and add it to the Connectors group.

Then just get the token of the user displayed in the interface.

"},{"location":"deployment/connectors/#docker-activation","title":"Docker activation","text":"

You can either directly run the Docker image of connectors or add them to your current docker-compose.yml file.

"},{"location":"deployment/connectors/#add-a-connector-to-your-deployment","title":"Add a connector to your deployment","text":"

For instance, to enable the MISP connector, you can add a new service to your docker-compose.yml file:

  connector-misp:\n    image: opencti/connector-misp:latest\n    environment:\n      - OPENCTI_URL=http://localhost\n      - OPENCTI_TOKEN=ChangeMe\n      - CONNECTOR_ID=ChangeMe\n      - CONNECTOR_TYPE=EXTERNAL_IMPORT\n      - CONNECTOR_NAME=MISP\n      - CONNECTOR_SCOPE=misp\n      - CONNECTOR_LOG_LEVEL=info\n      - MISP_URL=http://localhost # Required\n      - MISP_KEY=ChangeMe # Required\n      - MISP_SSL_VERIFY=False # Required\n      - MISP_CREATE_REPORTS=True # Required, create report for MISP event\n      - MISP_REPORT_CLASS=MISP event # Optional, report_class if creating report for event\n      - MISP_IMPORT_FROM_DATE=2000-01-01 # Optional, import all event from this date\n      - MISP_IMPORT_TAGS=opencti:import,type:osint # Optional, list of tags used for import events\n      - MISP_INTERVAL=1 # Required, in minutes\n    restart: always\n
"},{"location":"deployment/connectors/#launch-a-standalone-connector","title":"Launch a standalone connector","text":"

To launch a standalone connector, you can use the docker-compose.yml file of the connector itself. Just download the latest release and start the connector:

$ wget https://github.com/OpenCTI-Platform/connectors/archive/{RELEASE_VERSION}.zip\n$ unzip {RELEASE_VERSION}.zip\n$ cd connectors-{RELEASE_VERSION}/misp/\n

Change the configuration in the docker-compose.yml according to the parameters of the platform and of the targeted service. Then launch the connector:

$ docker-compose up\n
"},{"location":"deployment/connectors/#manual-activation","title":"Manual activation","text":"

If you want to manually launch connector, you just have to install Python 3 and pip3 for dependencies:

$ apt install python3 python3-pip\n

Download the release of the connectors:

$ wget <https://github.com/OpenCTI-Platform/connectors/archive/{RELEASE_VERSION}.zip>\n$ unzip {RELEASE_VERSION}.zip\n$ cd connectors-{RELEASE_VERSION}/misp/src/\n

Install dependencies and initialize the configuration:

$ pip3 install -r requirements.txt\n$ cp config.yml.sample config.yml\n

Change the config.yml content according to the parameters of the platform and of the targeted service and launch the connector:

$ python3 misp.py\n
"},{"location":"deployment/connectors/#connectors-status","title":"Connectors status","text":"

The connector status can be displayed in the dedicated section of the platform available in Data > Ingestion > Connectors. You will be able to see the statistics of the RabbitMQ queue of the connector:

Problem

If you encounter problems deploying OpenCTI or connectors, you can consult the troubleshooting page.

"},{"location":"deployment/installation/","title":"Installation","text":"

All components of OpenCTI are shipped both as Docker images and manual installation packages.

Production deployment

For production deployment, we recommend to deploy all components in containers, including dependencies, using native cloud services or orchestration systems such as Kubernetes.

To have more details about deploying OpenCTI and its dependencies in cluster mode, please read the dedicated section.

  • Use Docker

    Deploy OpenCTI using Docker and the default docker-compose.yml provided in the docker.

    Setup

  • Manual installation

    Deploy dependencies and launch the platform manually using the packages released in the GitHub releases.

    Explore

"},{"location":"deployment/installation/#using-docker","title":"Using Docker","text":"

OpenCTI can be deployed using the docker-compose command.

Deploy FIPS 140-2 compliant components

We provide FIPS 140-2 compliant images. Please read the dedicated documentation to understand how to deploy OpenCTI in FIPS-compliant mode.

"},{"location":"deployment/installation/#pre-requisites","title":"Pre-requisites","text":"

Linux

sudo apt install docker-compose\n

Windows and MacOS

Just download the appropriate Docker for Desktop version for your operating system.

"},{"location":"deployment/installation/#clone-the-repository","title":"Clone the repository","text":"

Docker helpers are available in the Docker GitHub repository.

mkdir -p /path/to/your/app && cd /path/to/your/app\ngit clone https://github.com/OpenCTI-Platform/docker.git\ncd docker\n
"},{"location":"deployment/installation/#configure-the-environment","title":"Configure the environment","text":"

ElasticSearch / OpenSearch configuration

  • We strongly recommend that you add the following ElasticSearch / OpenSearch parameter:
thread_pool.search.queue_size=5000\n
  • Check the OpenCTI Integration User Permissions in OpenSearch/ElasticSearch for detailed information about the user permissions required for the OpenSearch/ElasticSearch integration.

Before running the docker-compose command, the docker-compose.yml file should be configured. By default, the docker-compose.yml file is using environment variables available in the file .env.sample.

You can either rename the file .env.sample as .env and enter the values or just directly edit the docker-compose.yml with the values for your environment.

Configuration static parameters

The complete list of available static parameters is available in the configuration section.

Here is an example to quickly generate the .env file under Linux, especially all the default UUIDv4:

sudo apt install -y jq\ncd ~/docker\n(cat << EOF\nOPENCTI_ADMIN_EMAIL=admin@opencti.io\nOPENCTI_ADMIN_PASSWORD=ChangeMePlease\nOPENCTI_ADMIN_TOKEN=$(cat /proc/sys/kernel/random/uuid)\nOPENCTI_BASE_URL=http://localhost:8080\nMINIO_ROOT_USER=$(cat /proc/sys/kernel/random/uuid)\nMINIO_ROOT_PASSWORD=$(cat /proc/sys/kernel/random/uuid)\nRABBITMQ_DEFAULT_USER=guest\nRABBITMQ_DEFAULT_PASS=guest\nELASTIC_MEMORY_SIZE=4G\nCONNECTOR_HISTORY_ID=$(cat /proc/sys/kernel/random/uuid)\nCONNECTOR_EXPORT_FILE_STIX_ID=$(cat /proc/sys/kernel/random/uuid)\nCONNECTOR_EXPORT_FILE_CSV_ID=$(cat /proc/sys/kernel/random/uuid)\nCONNECTOR_IMPORT_FILE_STIX_ID=$(cat /proc/sys/kernel/random/uuid)\nCONNECTOR_EXPORT_FILE_TXT_ID=$(cat /proc/sys/kernel/random/uuid)\nCONNECTOR_IMPORT_DOCUMENT_ID=$(cat /proc/sys/kernel/random/uuid)\nSMTP_HOSTNAME=localhost\nEOF\n) > .env\n

If your docker-compose deployment does not support .env files, just export all environment variables before launching the platform:

export $(cat .env | grep -v \"#\" | xargs)\n

As OpenCTI has a dependency on ElasticSearch, you have to set vm.max_map_count before running the containers, as mentioned in the ElasticSearch documentation.

sudo sysctl -w vm.max_map_count=1048575\n

To make this parameter persistent, add the following to the end of your /etc/sysctl.conf:

vm.max_map_count=1048575\n
"},{"location":"deployment/installation/#persist-data","title":"Persist data","text":"

The default for OpenCTI data is to be persistent.

In docker-compose.yml, you will find the list of necessary persistent volumes for the dependencies at the end:

volumes:\n  esdata:     # ElasticSearch data\n  s3data:     # S3 bucket data\n  redisdata:  # Redis data\n  amqpdata:   # RabbitMQ data\n
"},{"location":"deployment/installation/#run-opencti","title":"Run OpenCTI","text":""},{"location":"deployment/installation/#using-single-node-docker","title":"Using single node Docker","text":"

After changing your .env file run docker-compose in detached (-d) mode:

sudo systemctl start docker.service\n# Run docker-compose in detached\ndocker-compose up -d\n
"},{"location":"deployment/installation/#using-docker-swarm","title":"Using Docker swarm","text":"

In order to have the best experience with Docker, we recommend using the Docker stack feature. In this mode you will have the capacity to easily scale your deployment.

# If your virtual machine is not a part of a Swarm cluster, please use:\ndocker swarm init\n

Put your environment variables in /etc/environment:

# If you already exported your variables to .env from above:\nsudo cat .env >> /etc/environment\nsudo bash -c 'cat .env >> /etc/environment'\nsudo docker stack deploy --compose-file docker-compose.yml opencti\n

Installation done

You can now go to http://localhost:8080 and log in with the credentials configured in your environment variables.

"},{"location":"deployment/installation/#manual-installation","title":"Manual installation","text":""},{"location":"deployment/installation/#prerequisites","title":"Prerequisites","text":""},{"location":"deployment/installation/#installation-of-dependencies","title":"Installation of dependencies","text":"

You have to install all the needed dependencies for the main application and the workers. The example below is for Debian-based systems:

sudo apt-get update\nsudo apt-get install build-essential nodejs npm python3 python3-pip python3-dev\n
"},{"location":"deployment/installation/#download-the-application-files","title":"Download the application files","text":"

First, you have to download and extract the latest release file. Then select the version to install depending of your operating system:

For Linux:

  • If your OS supports libc (Ubuntu, Debian, ...) you have to install the opencti-release_{RELEASE_VERSION}.tar.gz version.
  • If your OS uses musl (Alpine, ...) you have to install the opencti-release-{RELEASE_VERSION}_musl.tar.gz version.

For Windows:

We don't provide any Windows release for now. However it is still possible to check the code out, manually install the dependencies and build the software.

mkdir /path/to/your/app && cd /path/to/your/app\nwget <https://github.com/OpenCTI-Platform/opencti/releases/download/{RELEASE_VERSION}/opencti-release-{RELEASE_VERSION}.tar.gz>\ntar xvfz opencti-release-{RELEASE_VERSION}.tar.gz\n
"},{"location":"deployment/installation/#install-the-main-platform","title":"Install the main platform","text":""},{"location":"deployment/installation/#configure-the-application","title":"Configure the application","text":"

The main application has just one JSON configuration file to change and a few Python modules to install

cd opencti\ncp config/default.json config/production.json\n

Change the config/production.json file according to your configuration of ElasticSearch, Redis, RabbitMQ and S3 bucket as well as default credentials (the ADMIN_TOKEN must be a valid UUID).

"},{"location":"deployment/installation/#install-the-python-modules","title":"Install the Python modules","text":"
cd src/python\npip3 install -r requirements.txt\ncd ../..\n
"},{"location":"deployment/installation/#start-the-application","title":"Start the application","text":"

The application is just a NodeJS process, the creation of the database schema and the migration will be done at starting.

Please verify that yarn version is greater than 4 and node version is greater or equals to v19. Please note that some Node.js version are outdated in linux package manager, you can download a recent one in https://nodejs.org/en/download or alternatively nvm can help to chose a recent version of Node.js https://github.com/nvm-sh/nvm

yarn --version\n#4.1.0\nnode --version\n#v20.11.1\n

Once Node.js is setup, you can build and run with (from inside opencti folder): 

yarn install\nyarn build\nyarn serv\n

The default username and password are those you have put in the config/production.json file.

"},{"location":"deployment/installation/#install-the-worker","title":"Install the worker","text":"

The OpenCTI worker is used to write the data coming from the RabbitMQ messages broker.

"},{"location":"deployment/installation/#configure-the-worker","title":"Configure the worker","text":"
cd worker\npip3 install -r requirements.txt\ncp config.yml.sample config.yml\n

Change the config.yml file according to your OpenCTI token.

"},{"location":"deployment/installation/#start-as-many-workers-as-you-need","title":"Start as many workers as you need","text":"
python3 worker.py &\npython3 worker.py &\n

Installation done

You can now go to http://localhost:4000 and log in with the credentials configured in your production.json file.

"},{"location":"deployment/installation/#community-contributions","title":"Community contributions","text":""},{"location":"deployment/installation/#terraform","title":"Terraform","text":"

  • Multi-clouds Terraform scripts

    This repository is here to provide you with a quick and easy way to deploy an OpenCTI instance in the cloud (AWS, Azure, or GCP).

    GitHub Respository

  • AWS Advanced Terraform scripts

    A Terraform deployment of OpenCTI designed to make use of native AWS Resources (where feasible). This includes AWS ECS Fargate, AWS OpenSearch, etc.

    GitHub Repository

"},{"location":"deployment/installation/#helm-charts","title":"Helm Charts","text":"

  • Kubernetes Helm Charts

    OpenCTI Helm Charts for Kubernetes with a global configuration file. More information how to deploy here on basic installation and examples.

    GitHub Repository

"},{"location":"deployment/installation/#deploy-behind-a-reverse-proxy","title":"Deploy behind a reverse proxy","text":"

If you want to use OpenCTI behind a reverse proxy with a context path, like https://domain.com/opencti, please change the base_path static parameter.

  • APP__BASE_PATH=/opencti

By default OpenCTI use websockets so don't forget to configure your proxy for this usage, an example with Nginx:

location / {\n    proxy_cache                 off;\n    proxy_buffering             off;\n    proxy_http_version          1.1;\n    proxy_set_header Upgrade    $http_upgrade;\n    proxy_set_header Connection \"upgrade\";\n    proxy_set_header Host       $host;\n    chunked_transfer_encoding   off;\n    proxy_pass                  http://YOUR_UPSTREAM_BACKEND;\n  }\n
"},{"location":"deployment/installation/#additional-memory-information","title":"Additional memory information","text":""},{"location":"deployment/installation/#platform","title":"Platform","text":"

OpenCTI platform is based on a NodeJS runtime, with a memory limit of 8GB by default. If you encounter OutOfMemory exceptions, this limit could be changed:

- NODE_OPTIONS=--max-old-space-size=8096\n
"},{"location":"deployment/installation/#workers-and-connectors","title":"Workers and connectors","text":"

OpenCTI workers and connectors are Python processes. If you want to limit the memory of the process, we recommend to directly use Docker to do that. You can find more information in the official Docker documentation.

"},{"location":"deployment/installation/#elasticsearch","title":"ElasticSearch","text":"

ElasticSearch is also a JAVA process. In order to setup the JAVA memory allocation, you can use the environment variable ES_JAVA_OPTS. You can find more information in the official ElasticSearch documentation.

"},{"location":"deployment/installation/#redis","title":"Redis","text":"

Redis has a very small footprint on keys but will consume memory for the stream. By default the size of the stream is limited to 2 millions which represents a memory footprint around 8 GB. You can find more information in the Redis docker hub.

"},{"location":"deployment/installation/#minio-s3-bucket","title":"MinIO / S3 Bucket","text":"

MinIO is a small process and does not require a high amount of memory. More information are available for Linux here on the Kernel tuning guide.

"},{"location":"deployment/installation/#rabbitmq","title":"RabbitMQ","text":"

The RabbitMQ memory configuration can be find in the RabbitMQ official documentation. RabbitMQ will consumed memory until a specific threshold, therefore it should be configure along with the Docker memory limitation.

"},{"location":"deployment/integrations/","title":"Integrations","text":""},{"location":"deployment/integrations/#introduction","title":"Introduction","text":"

OpenCTI supports multiple ways to integrate with other systems which do not have native connectors or plugins to the platform. Here are the technical features available to ease the connection and the integration of the platform with other applications.

Connectors list

If you are looking for the list of OpenCTI connectors or native integration, please check the OpenCTI Ecosystem.

"},{"location":"deployment/integrations/#native-feeds-and-streams","title":"Native feeds and streams","text":"

To ease integrations with other products, OpenCTI has built-in capabilities to deliver the data to third-parties.

"},{"location":"deployment/integrations/#csv-feeds","title":"CSV Feeds","text":"

It is possible to create as many CSV feeds as needed, based on filters and accessible in HTTP. CSV feeds are available in Data > Data sharing > CSV deeds.

When creating a CSV feed, you need to select one or multiple types of entities to make available. Then, you must assign a field (of an entity type) to each column in the CSV:

Details

For more information about CSV feeds, filters and configuration, please check the Native feeds page.

"},{"location":"deployment/integrations/#taxii-collections","title":"TAXII collections","text":"

Most of the modern cybersecurity systems such as SIEMs, EDRs, XDRs and even firewalls support the TAXII protocol which is basically a paginated HTTP STIX feed. OpenCTI implements a TAXII 2.1 server with the ability to create as many TAXII collections as needed in Data > Data sharing > TAXII Collections.

TAXII collections are a sub-selection of the knowledge available in the platform and rely on filters. For instance, it is possible to create TAXII collections for pieces of malware with a given label, for indicators with a score greater than n, etc.

"},{"location":"deployment/integrations/#live-streams","title":"Live Streams","text":"

After implementing CSV feeds and TAXII collections, we figured out that those 2 stateless APIs are definitely not enough when it comes to tackle advanced information sharing challenges such as:

  • Real time transmission of the information (i.e. avoid hundreds of systems to pull data every 5 minutes).
  • Dependencies resolution (i.e. an intrusion created by an organization but the organization is not in the TAXII collection).
  • Partial update for huge entities such as report (i.e. just having the update event).
  • Delete events when necessary (i.e. to handle indicators expiration in third party systems for instance).

That's why we've developed the live streams. They are available in Data > Data sharing > Live streams. As with TAXII collections, it is possible to create as many streams as needed using filters.

Streams implement the HTTP SSE (Server-sent events) protocol and give applications the possibility to consume a real time pure STIX 2.1 stream. Stream connectors in the OpenCTI Ecosystem are using live streams to consume data and do something such as create / update / delete information in SIEMs, XDRs, etc.

"},{"location":"deployment/integrations/#authentication","title":"Authentication","text":"

For all previously explained capabilities, as they are over the HTTP protocol, 3 authentication mechanisms are available to consume them.

  1. Using a bearer header with your OpenCTI API key

    Authorization: Bearer a17bc103-8420-4208-bd53-e1f80845d15f\n

    API Key

    Your API key can be found in your profile available clicking on the top right icon.

  2. Using basic authentication

    Username: Your platform username\nPassword: Your plafrom password\nAuthorization: Basic c2FtdWVsLmhhc3NpbmVBZmlsaWdyYW4uaW86TG91aXNlMTMwNCM=\n

  3. Using client certificate authentication

    To know how to configure the client certificate authentication, please consult the authentication configuration section.

"},{"location":"deployment/integrations/#api-and-libraries","title":"API and libraries","text":""},{"location":"deployment/integrations/#graphql-api","title":"GraphQL API","text":"

To allow analysts and developers to implement more custom or complex use cases, a full GraphQL API is available in the application on the /graphql endpoint.

The API can be queried using various GraphQL client such as Postman but you can leverage any HTTP client to forge GraphQL queries using POST methods.

"},{"location":"deployment/integrations/#authentication_1","title":"Authentication","text":"

The API authentication can be performed using the token of a user and a classic Authorization header:

Content-Type: application/json\nAuthorization: Bearer 6b6554c4-bb2c-4c80-9cd3-30288c8bf424\n
"},{"location":"deployment/integrations/#playground","title":"Playground","text":"

The playground is available on the /graphql endpoint. A link button is also available in the profile of your user.

All the schema documentation is directly available in the playground.

If you already logged to OpenCTI with the same browser you should be able to directly do some requests. If you are not authenticated or want to authenticate only through the playground you can use a header configuration using your profile token

Example of configuration (bottom left of the playground):

Additional GraphQL documentation

To find out more about GraphQL and the playground, you can find two additional documentation pages: the GraphQL API page and the GraphQL playground page.

"},{"location":"deployment/integrations/#python-library","title":"Python library","text":"

Since not everyone is familiar with GraphQL APIs, we've developed a Python library to ease the interaction with it. The library is pretty easy to use. To initiate the client:

# coding: utf-8\n\nfrom pycti import OpenCTIApiClient\n\n# Variables\napi_url = \"http://opencti:4000\"\napi_token = \"bfa014e0-e02e-4aa6-a42b-603b19dcf159\"\n\n# OpenCTI initialization\nopencti_api_client = OpenCTIApiClient(api_url, api_token)\n

Then just use the available helpers: 

# Search for malware with the keyword \"windows\"\nmalwares = opencti_api_client.malware.list(search=\"windows\")\n\n# Print\nprint(malwares)\n

Details

For more detailed information about the Python library, please read the dedicated section.

"},{"location":"deployment/managers/","title":"Platform managers","text":"

Platform managers are background components that perform various tasks to support some important functionalities in the platform.

Here is a list of all the managers on the platform:

"},{"location":"deployment/managers/#rules-engine","title":"Rules engine","text":"

Allows users to execute pre-defined actions based on the data and events in the platform.

These rules are accessible in Settings > Customization > Rules engine.

The rules engine is designed to help users automate and streamline their cyber threat intelligence processes.

More information can be found here.

"},{"location":"deployment/managers/#history-manager","title":"History manager","text":"

This manager keeps tracks of user/connector interactions on entities in the platform.

It is designed to help users audit and understand the evolution of their CTI data.

"},{"location":"deployment/managers/#activity-manager","title":"Activity manager","text":"

The activity manager in OpenCTI is a component that monitors and logs the user actions in the platform such as login, settings update, and user activities if configured (read, udpate, etc.).

More information can be found here.

"},{"location":"deployment/managers/#background-task-manager","title":"Background task manager","text":"

Is a component that handles the execution of tasks, such as importing data, exporting data and mass operations.

More information can be found here.

"},{"location":"deployment/managers/#expiration-scheduler","title":"Expiration scheduler","text":"

The expiration scheduler is responsible for monitoring expired elements in the platform. It cancels the access rights of expired user accounts and revokes expired indicators from the platform.

"},{"location":"deployment/managers/#synchronization-manager","title":"Synchronization manager","text":"

The synchronization manager enables the data sharing between multiple OpenCTI platforms. It allows the user to create and configure synchronizers which are processes that connect to the live streams of remote OpenCTI platforms and import the data into the local platform.

"},{"location":"deployment/managers/#retention-manager","title":"Retention manager","text":"

The retention manager is a component that allows the user to define rules to help delete data in OpenCTI that is no longer relevant or useful. This helps to optimize the performance and storage of the OpenCTI platform and ensures the quality and accuracy of the data.

More information can be found here.

"},{"location":"deployment/managers/#notification-manager","title":"Notification manager","text":"

The notification manager is a component that allows the user to customize and receive alerts about events/changes in the platform.

More information can be found here.

"},{"location":"deployment/managers/#ingestion-manager","title":"Ingestion manager","text":"

The ingestion manager in OpenCTI is a component that manages the ingestion of data from RSS, TAXII and CSV feeds.

More information can be found here.

"},{"location":"deployment/managers/#playbook-manager","title":"Playbook manager","text":"

The playbook manager handles the automation scenarios which can be fully customized and enabled by platform administrators to enrich, filter and modify the data created or updated in the platform.

Please read the Playbook automation page to get more information.

"},{"location":"deployment/managers/#file-index-manager","title":"File index manager","text":"

The file indexing manager extracts and indexes the text content of the files, and stores it in the database. It allows users to search for text content within files uploaded to the platform.

More information can be found here.

"},{"location":"deployment/managers/#indicator-decay-manager","title":"Indicator decay manager","text":"

The indicator decay manager allows to update indicators score automatically based on configured decay rules.

More information can be found here.

"},{"location":"deployment/managers/#trash-manager","title":"Trash manager","text":"

The trash manager is responsible to delete permanently elements stored in the trash after a specified period of time (7 days by default).

"},{"location":"deployment/managers/#filigran-telemetry-manager","title":"Filigran telemetry manager","text":"

The telemetry manager collects periodically statistical data about platform usage.

More information about data telemetry can be found here.

"},{"location":"deployment/map/","title":"Deploy on-premise map server with OpenCTI styles","text":""},{"location":"deployment/map/#introduction","title":"Introduction","text":"

The OpenStreetMap tiles for the planet will take 80GB. Here are the instructions to deploy a local OpenStreetMap server with the OpenCTI styles.

"},{"location":"deployment/map/#create-directory-for-the-data-and-upload-planet-data","title":"Create directory for the data and upload planet data","text":"

When you will launch the map server container, it will be necessary to mount a volume with the planet tiles data. Just create the directory for the data.

mkdir /var/YOUR_DATA_DIR\n

We have hosted the free-to-use planet tiles, just download the planet data from filigran.io.

wget https://filigran-marketplace-assets.s3.eu-west-3.amazonaws.com/maptiler-osm-2020-02-10-v3.11-planet.mbtiles\n

Put the file maptiler-osm-2020-12-14-v3.11-planet.mbtiles in the data directory:

cp maptiler-osm-2020-12-14-v3.11-planet.mbtiles /var/YOUR_DATA_DIR/\n
"},{"location":"deployment/map/#start-docker","title":"Start Docker","text":"

Replace the port 80 by the port you would like to expose. Inside the Docker, the map server listen on the port 80.

docker run -d --restart always -v /var/YOUR_DATA_DIR:/data -p 80:80 klokantech/openmaptiles-server:latest \n
"},{"location":"deployment/map/#configure","title":"Configure","text":"

Download on your computer the OpenCTI JSON styles (you will have to upload it through the web UI later).

  • OpenCTI Map Dark mode style (filigran-dark2.json)
  • OpenCTI Map Light mode style (filigran-light2.json)

Now, you can access to the map server, you should see the following page:

On the next page, you should see the existing data:

On the next page, click on \"Advanced Options\":

Upload the filigran-dark2.json and filigran-light2.json files:

Save and run the server with default parameters:

"},{"location":"deployment/map/#opencti-parameters","title":"OpenCTI Parameters","text":"

Once the server is running, you should see the list of available styles:

Click on \"Viewer\", and take the URL:

\ud83d\udc49 http:/YOUR_URL/styles/{ID}/....

In the OpenCTI configuration, just put:

Parameter Environment variable Value Description app:map_tile_server_dark APP__MAP_TILE_SERVER_DARK http://{YOUR_MAP_SERVER}/styles/{ID_DARK}/{z}/{x}/{y}.png The address of the OpenStreetMap provider with dark theme style app:map_tile_server_light APP__MAP_TILE_SERVER_LIGHT http://{YOUR_MAP_SERVER}/styles/{ID_LIGHT}/{z}/{x}/{y}.png The address of the OpenStreetMap provider with light theme style

You're good to go!

"},{"location":"deployment/overview/","title":"Overview","text":"

Before starting the installation, let's discover how OpenCTI is working, which dependencies are needed and what are the minimal requirements to deploy it in production.

"},{"location":"deployment/overview/#architecture","title":"Architecture","text":"

The OpenCTI platform relies on several external databases and services in order to work.

"},{"location":"deployment/overview/#platform","title":"Platform","text":"

The platform is the central part of the OpenCTI technological stack. It allows users to access to the user interface but also provides the GraphQL API used by connectors and workers to insert data. In the context of a production deployment, you may need to scale horizontally and launch multiple platforms behind a load balancer connected to the same databases (ElasticSearch, Redis, S3, RabbitMQ).

"},{"location":"deployment/overview/#workers","title":"Workers","text":"

The workers are standalone Python processes consuming messages from the RabbitMQ broker in order to do asynchronous write queries. You can launch as many workers as you need to increase the write performances. At some point, the write performances will be limited by the throughput of the ElasticSearch database cluster.

Number of workers

If you need to increase performances, it is better to launch more platforms to handle worker queries. The recommended setup is to have at least one platform for 3 workers (ie. 9 workers distributed over 3 platforms).

"},{"location":"deployment/overview/#connectors","title":"Connectors","text":"

The connectors are third-party pieces of software (Python processes) that can play five different roles on the platform:

Type Description Examples EXTERNAL_IMPORT Pull data from remote sources, convert it to STIX2 and insert it on the OpenCTI platform. MITRE Datasets, MISP, CVE, AlienVault, Mandiant, etc. INTERNAL_ENRICHMENT Listen for new OpenCTI entities or users requests, pull data from remote sources to enrich. Shodan, DomainTools, IpInfo, etc. INTERNAL_IMPORT_FILE Extract data from files uploaded on OpenCTI through the UI or the API. STIX 2.1, PDF, Text, HTML, etc. INTERNAL_EXPORT_FILE Generate export from OpenCTI data, based on a single object or a list. STIX 2.1, CSV, PDF, etc. STREAM Consume a platform data stream and do something with events. Splunk, Elastic Security, Q-Radar, etc.

List of connectors

You can find all currently available connectors in the OpenCTI Ecosystem.

"},{"location":"deployment/overview/#infrastructure-requirements","title":"Infrastructure requirements","text":""},{"location":"deployment/overview/#dependencies","title":"Dependencies","text":"Component Version CPU RAM Disk type Disk space ElasticSearch / OpenSearch >= 8.0 / >= 2.9 2 cores \u2265 8GB SSD \u2265 16GB Redis >= 7.1 1 core \u2265 1GB SSD \u2265 16GB RabbitMQ >= 3.11 1 core \u2265 512MB Standard \u2265 2GB S3 / MinIO >= RELEASE.2023-02 1 core \u2265 128MB SSD \u2265 16GB"},{"location":"deployment/overview/#platform_1","title":"Platform","text":"Component CPU RAM Disk type Disk space OpenCTI Core 2 cores \u2265 8GB None (stateless) - Worker(s) 1 core \u2265 128MB None (stateless) - Connector(s) 1 core \u2265 128MB None (stateless) -

Clustering

To have more details about deploying OpenCTI and its dependencies in cluster mode, please read the dedicated section.

"},{"location":"deployment/resources/","title":"Other resources","text":""},{"location":"deployment/resources/#introduction","title":"Introduction","text":"

OpenCTI is an open and modular platform. A lot of connectors, plugins and clients are created by Filigran and by the community. You can find here other resources available to complete your OpenCTI journey.

"},{"location":"deployment/resources/#videos-training","title":"Videos & training","text":"

  • YouTube channel

    Watch demonstration videos, use case explanations, customers and community testimonies, and past webinars.

    Watch

  • Training courses

    Empower your journey with OpenCTI training courses for both analyst and administrators, and get your certificate.

    Learn

"},{"location":"deployment/resources/#articles-news","title":"Articles & news","text":"

  • Blog articles

    Read posts written by both Filigran teams and community members about OpenCTI features and use cases.

    Read

  • Newsletters

    Subscribe to Filigran newsletters to get informed about the latest evolutions of our product ecosystems.

    Subscribe

"},{"location":"deployment/resources/#analysis","title":"Analysis","text":"

  • Verticalized threat landscapes

    Access to monthly sectorial analysis from our experts team based on knowledge and data collected by our partners.

    Consult

  • Case studies

    Explore the Filigran case studies about stories and usages of the platform among our communities and customers.

    Download

"},{"location":"deployment/rollover/","title":"Indices and rollover policies","text":""},{"location":"deployment/rollover/#introduction","title":"Introduction","text":"

ElasticSearch and OpenSearch both support rollover on indices. OpenCTI has been designed to be able to use aliases for indices and so supports index lifecycle policies very well. Thus, by default OpenCTI initializes indices with a suffix of -00001 and uses wildcards to query indices. When rollover policies are implemented (default starting OCTI 5.9.X if you initialized your platform at this version), indices are splitted to keep a reasonable volume of data in shards.

"},{"location":"deployment/rollover/#opencti-integration-user-permissions-in-opensearchelasticsearch","title":"OpenCTI Integration User Permissions in OpenSearch/ElasticSearch","text":"

  • Index Permissions

    • Patterns: opencti* (Dependent on the parameter elasticsearch:index_prefix value)
    • Permissions: indices_all

  • Cluster Permissions

    • cluster_composite_ops_ro
    • cluster_manage_index_templates
    • cluster:admin/ingest/pipeline/put
    • cluster:admin/opendistro/ism/policy/write
    • cluster:monitor/health
    • cluster:monitor/main
    • cluster:monitor/state
    • indices:admin/index_template/put
    • indices:data/read/scroll/clear
    • indices:data/read/scroll
    • indices:data/write/bulk

About indices:* in Cluster Permissions

It is crucial to include indices:* permissions in Cluster Permissions for the proper functioning of the OpenCTI integration. Removing these, even if already present in Index Permissions, may result in startup issues for the OpenCTI Platform.

"},{"location":"deployment/rollover/#elasticsearch-configuration","title":"ElasticSearch configuration","text":""},{"location":"deployment/rollover/#indices","title":"Indices","text":"

By default, a rollover policy is applied on all indices used by OpenCTI.

  • opencti_deleted_objects
  • opencti_files
  • opencti_history
  • opencti_inferred_entities
  • opencti_inferred_relationships
  • opencti_internal_objects
  • opencti_internal_relationships
  • opencti_stix_core_relationships
  • opencti_stix_cyber_observable_relationships
  • opencti_stix_cyber_observables
  • opencti_stix_domain_objects
  • opencti_stix_meta_objects
  • opencti_stix_meta_relationships
  • opencti_stix_sighting_relationships

For your information, the indices which can grow rapidly are:

  • Index opencti_stix_meta_relationships: it contains all the nested relationships between objects and labels / marking definitions / external references / authors, etc.
  • Index opencti_history: it contains the history log of all objects in the platform.
  • Index opencti_stix_cyber_observables: it contains all observables stored in the platform.
  • Index opencti_stix_core_relationships: it contains all main STIX relationships stored in the platform.
"},{"location":"deployment/rollover/#default-implemented-lifecycle-policy","title":"Default implemented lifecycle policy","text":"

Here is the recommended policy (for 1 shard per index) (initialized starting 5.9.X):

  • Maximum primary shard size: 50 GB
  • Maximum documents: 75,000,000
"},{"location":"deployment/rollover/#adapt-platform-initialized-before-the-6-version","title":"Adapt platform initialized before the 6+ version","text":"

Procedure information

If your platform has been initialized before 5.9.0, your platform will be not configured to automatically managed the indices

Unfortunately, to be able to implement rollover policies on ElasticSearch / OpenSearch indices, it will be needed to: - Upgrade your platform to the latest version - Check that policy and templates are available after the migration - split all the shards > 50Gb in new indices using ElasticSearch capabilities. - Reconfigure the writing alias to the latest index and ensure that the policy is running correctly.

If you need any help for this migration, please join the slack community.

"},{"location":"deployment/troubleshooting/","title":"Troubleshooting","text":"

This page aims to explain the typical errors you can have with your OpenCTI platform.

"},{"location":"deployment/troubleshooting/#finding-the-relevant-logs","title":"Finding the relevant logs","text":"

It is highly recommended to monitor the error logs of the platforms, workers and connectors. All the components have log outputs in an understandable JSON format. If necessary, it is always possible to increase the log level. In production, it is recommended to have the log level set to error.

"},{"location":"deployment/troubleshooting/#platform","title":"Platform","text":"

Here are some useful parameters for platform logging:

- APP__APP_LOGS__LOGS_LEVEL=[error|warning|info|debug]\n- APP__APP_LOGS__LOGS_CONSOLE=true # Output in the container console\n
"},{"location":"deployment/troubleshooting/#connectors","title":"Connectors","text":"

All connectors support the same set of parameters to manage the log level and outputs:

- OPENCTI_JSON_LOGGING=true # Enable / disable JSON logging\n- CONNECTOR_LOG_LEVEL=info=[error|warning|info|debug]\n
"},{"location":"deployment/troubleshooting/#workers","title":"Workers","text":"

The workers can have more or less verbose outputs:

- OPENCTI_JSON_LOGGING=true # Enable / disable JSON logging\n- WORKER_LOG_LEVEL=[error|warning|info|debug]\n
"},{"location":"deployment/troubleshooting/#elasticsearch-opensearch-data","title":"ElasticSearch / OpenSearch data","text":"

Kibana / OpenSearch dashboard

In case you need to troubleshoot the OpenCTI knowledge data, we recommend to install Kibana or OpenSearch dashboard.

"},{"location":"deployment/troubleshooting/#common-errors","title":"Common errors","text":""},{"location":"deployment/troubleshooting/#ingestion-technical-errors","title":"Ingestion technical errors","text":"

Missing reference to handle creation

After 5 retries, if an element required to create another element is missing, the platform raises an exception. It usually comes from a connector that generates inconsistent STIX 2.1 bundles.

Cant upsert entity. Too many entities resolved

OpenCTI received an entity which is matching too many other entities in the platform. In this condition we cannot take a decision. We need to dig into the data bundle to identify why it matches too much entities and fix the data in the bundle / or the platform according to what you expect.

Execution timeout, too many concurrent call on the same entities

The platform supports multi workers and multiple parallel creation but different parameters can lead to some locking timeout in the execution.

  • Throughput capacity of your ElasticSearch
  • Number of workers started at the same time
  • Dependencies between data
  • Merging capacity of OpenCTI

If you have this kind of error, limit the number of workers deployed. Try to find the right balance of the number of workers, connectors and elasticsearch sizing.

"},{"location":"deployment/troubleshooting/#ingestion-functional-errors","title":"Ingestion functional errors","text":"

Indicator of type yara is not correctly formatted

OpenCTI check the validity of the indicator rule.

Observable of type IPv4-Addr is not correctly formatted

OpenCTI check the validity of the observable value.

"},{"location":"deployment/troubleshooting/#dependencies-errors","title":"Dependencies errors","text":"

TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark...

Disk full, no space left on the device for ElasticSearch.

"},{"location":"deployment/upgrade/","title":"Upgrade","text":"

Depending on your installation mode, upgrade path may change.

Migrations

The platform is taking care of all necessary underlying migrations in the databases if any. You can upgrade OpenCTI from any version to the latest one, including skipping multiple major releases.

"},{"location":"deployment/upgrade/#using-docker","title":"Using Docker","text":"

Before applying this procedure, please update your docker-compose.yml file with the new version number of container images.

"},{"location":"deployment/upgrade/#for-single-node-docker","title":"For single node Docker","text":"
$ sudo docker-compose stop\n$ sudo docker-compose pull\n$ sudo docker-compose up -d\n
"},{"location":"deployment/upgrade/#for-docker-swarm","title":"For Docker swarm","text":"

For each of services, you have to run the following command:

$ sudo docker service update --force service_name\n
"},{"location":"deployment/upgrade/#manual-installation","title":"Manual installation","text":"

When upgrading the platform, you have to replace all files and restart the platform, the database migrations will be done automatically:

$ yarn serv\n
"},{"location":"development/api-usage/","title":"GraphQL playground","text":"

The GraphQL playground is an integrated development environment (IDE) provided by OpenCTI for exploring and testing GraphQL APIs. It offers a user-friendly interface that allows developers to interactively query the GraphQL schema, experiment with different queries, and visualize the responses.

"},{"location":"development/api-usage/#key-features","title":"Key features","text":""},{"location":"development/api-usage/#interactive-querying","title":"Interactive querying","text":"

The Playground provides a text editor where developers can write GraphQL queries, mutations, and subscriptions. As you type, the Playground offers syntax highlighting, autocompletion, and error checking to aid in query composition.

"},{"location":"development/api-usage/#documentation","title":"Documentation","text":"

Developers can access comprehensive documentation for the GraphQL schema directly within the Playground. This documentation includes descriptions of all available types, fields, and directives, making it easy to understand the data model and construct queries.

"},{"location":"development/api-usage/#query-history","title":"Query history","text":"

The playground keeps track of previously executed queries, allowing developers to revisit and reuse queries from previous sessions. This feature streamlines the development process by eliminating the need to retype complex queries.

"},{"location":"development/api-usage/#response-visualization","title":"Response visualization","text":"

Upon executing a query, the playground displays the response data in a structured and readable format. JSON responses are presented in a collapsible tree view, making it easy to navigate nested data structures and inspect individual fields.

"},{"location":"development/api-usage/#schema-exploration","title":"Schema exploration","text":"

Developers can explore the GraphQL schema using the built-in schema viewer. This feature provides a graphical representation of the schema, showing types, fields, and their relationships. Developers can explore the schema and understand its structure.

"},{"location":"development/api-usage/#getting-started","title":"Getting started","text":"

To access the GraphQL playground, navigate to the GraphQL endpoint of your OpenCTI instance: https://[your-opencti-instance]/graphql. Then, follow these steps to utilize the playground:

  1. Query editor: Write GraphQL queries, mutations, and subscriptions in the text editor. Use syntax highlighting and autocompletion to speed up query composition.
  2. Documentation explorer: Access documentation for the GraphQL schema by clicking on the \"Docs\" tab on the right. Browse types, fields, and descriptions to understand the available data and query syntax.
  3. Query history: View and execute previously executed queries from the \"History\" tab on the top. Reuse queries and experiment with variations without retyping.
  4. Response pane: Visualize query responses in the response pane. Expand and collapse sections to navigate complex data structures and inspect individual fields.
  5. Schema viewer: Explore the GraphQL schema interactively using the \"Schema\" tab on the right. Navigate types, fields, and relationships to understand the data model and plan queries.
"},{"location":"development/api-usage/#external-resources","title":"External Resources","text":"

For a more in-depth understanding of GraphQL and its usage, consider exploring the following external resources:

  • GraphQL Official Documentation
  • GraphQL query documentation
  • How to GraphQL
"},{"location":"development/connectors/","title":"Connector development","text":""},{"location":"development/connectors/#introduction","title":"Introduction","text":"

A connector in OpenCTI is a service that runs next to the platform and can be implemented in almost any programming language that has STIX2 support. Connectors are used to extend the functionality of OpenCTI and allow operators to shift some of the processing workload to external services. To use the conveniently provided OpenCTI connector SDK you need to use Python3 at the moment.

We choose to have a very decentralized approach on connectors, in order to bring a maximum freedom to developers and vendors. So a connector on OpenCTI can be defined by a standalone Python 3 process that pushes an understandable format of data to an ingestion queue of messages.

Each connector must implement a long-running process that can be launched just by executing the main Python file. The only mandatory dependency is the OpenCTIConnectorHelper class that enables the connector to send data to OpenCTI.

"},{"location":"development/connectors/#getting-started","title":"Getting started","text":"

In the beginning first think about your use-case to choose an appropriate connector type - what do want to achieve with your connector? The following table gives you an overview of the current connector types and some typical use-cases:

Connector types

Type Typical use cases Example connector EXTERNAL_IMPORT Integrate external TI provider, Integrate external TI platform AlienVault INTERNAL_ANALYSIS Map unstructured data from files or entity fields to existing entities Import document INTERNAL_ENRICHMENT Enhance existing data with additional knowledge AbuseIP INTERNAL_IMPORT_FILE (Bulk) import knowledge from files Import document INTERNAL_EXPORT_FILE (Bulk) export knowledge to files STIX 2.1, CSV. STREAM Integrate external TI provider, Integrate external TI platform Elastic Security

After you've selected your connector type make yourself familiar with STIX2 and the supported relationships in OpenCTI. Having some knowledge about the internal data models with help you a lot with the implementation of your idea.

"},{"location":"development/connectors/#preparation","title":"Preparation","text":""},{"location":"development/connectors/#environment-setup","title":"Environment Setup","text":"

To develop and test your connector, you need a running OpenCTI instance with the frontend and the messaging broker accessible. If you don't plan on developing anything for the OpenCTI platform or the frontend, the easiest setup for the connector development is using the docker setup, For more details see here.

"},{"location":"development/connectors/#coding-setup","title":"Coding Setup","text":"

To give you an easy starting point we prepared an example connector in the public repository you can use as template to bootstrap your development.

Some prerequisites we recommend to follow this tutorial:

  • Code editor with good Python3 support (e.g. Visual Studio Code with the Python extension pack)
  • Python3 + setuptools is installed and configured
  • Command shell (either Linux/Mac terminal or WSL on Windows)

In the terminal check out the connectors repository and copy the template connector to $myconnector (replace it with your name throughout the following text examples).

$ pip3 install black flake8 pycti\n# Fork the current repository, then clone your fork\n$ git clone https://github.com/YOUR-USERNAME/connectors.git\n$ cd connectors\n$ git remote add upstream https://github.com/OpenCTI-Platform/connectors.git\n# Create a branch for your feature/fix\n$ git checkout -b [branch-name]\n# Copy the appropriate template directory for the connector type\n$ cp -r templates/$connector_type $connector_type/$myconnector\n$ cd $connector_type/$myconnector\n$ ls -R\nDockerfile              docker-compose.yml      requirements.txt\nREADME.md               entrypoint.sh           src\n\n./src:\nlib     main.py\n\n./src/lib:\n$connector_type.py\n
"},{"location":"development/connectors/#changing-the-template","title":"Changing the template","text":"

There are a few files in the template we need to change for our connector to be unique. You can check for all places you need to change you connector name with the following command (the output will look similar):

$ grep -Ri template .\n\nREADME.md:# OpenCTI Template Connector\nREADME.md:| `connector_type`                     | `CONNECTOR_TYPE`                    | Yes          | Must be `Template_Type` (this is the connector type).                                                                                                      |\nREADME.md:| `connector_name`                     | `CONNECTOR_NAME`                    | Yes          | Option `Template`                                                                                                                                          |\nREADME.md:| `connector_scope`                    | `CONNECTOR_SCOPE`                   | Yes          | Supported scope: Template Scope (MIME Type or Stix Object)                                                                                                 |\nREADME.md:| `template_attribute`                 | `TEMPLATE_ATTRIBUTE`                | Yes          | Additional setting for the connector itself                                                                                                                |\ndocker-compose.yml:  connector-template:\ndocker-compose.yml:    image: opencti/connector-template:4.5.5\ndocker-compose.yml:      - CONNECTOR_TYPE=Template_Type\ndocker-compose.yml:      - CONNECTOR_NAME=Template\ndocker-compose.yml:      - CONNECTOR_SCOPE=Template_Scope # MIME type or Stix Object\nentrypoint.sh:cd /opt/opencti-connector-template\nDockerfile:COPY src /opt/opencti-template\nDockerfile:    cd /opt/opencti-connector-template && \\\nsrc/main.py:class Template:\nsrc/main.py:            \"TEMPLATE_ATTRIBUTE\", [\"template\", \"attribute\"], config, True\nsrc/main.py:        connectorTemplate = Template()\nsrc/main.py:        connectorTemplate.run()\nsrc/config.yml.sample:  type: 'Template_Type'\nsrc/config.yml.sample:  name: 'Template'\nsrc/config.yml.sample:  scope: 'Template_Scope' # MIME type or SCO\n

Required changes:

  • Change Template or templatementions to your connector name e.g. ImportCsv or importcsv
  • Change TEMPLATE mentions to your connector name e.g. IMPORTCSV
  • Change Template_Scope mentions to the required scope of your connector. For processing imported files, that can be the Mime type e.g. application/pdf or for enriching existing information in OpenCTI, define the STIX object's name e.g. Report. Multiple scopes can be separated by a simple ,
  • Change Template_Type to the connector type you wish to develop. The OpenCTI types are defined hereafter:
    • EXTERNAL_IMPORT
    • INTERNAL_ANALYSIS
    • INTERNAL_ENRICHMENT
    • INTERNAL_EXPORT_FILE
    • INTERNAL_IMPORT_FILE
    • STREAM
"},{"location":"development/connectors/#development","title":"Development","text":""},{"location":"development/connectors/#initialize-the-opencti-connector-helper","title":"Initialize the OpenCTI connector helper","text":"

After getting the configuration parameters of your connector, you have to initialize the OpenCTI connector helper by using the pycti Python library. This is shown in the following example:

class TemplateConnector:\n    def __init__(self):\n                # Instantiate the connector helper from config\n        config_file_path = os.path.dirname(os.path.abspath(__file__)) + \"/config.yml\"\n        config = (\n            yaml.load(open(config_file_path), Loader=yaml.SafeLoader)\n            if os.path.isfile(config_file_path)\n            else {}\n        )\n        self.helper = OpenCTIConnectorHelper(config)\n                self.custom_attribute = get_config_variable(\n            \"TEMPLATE_ATTRIBUTE\", [\"template\", \"attribute\"], config\n        )\n

Since there are some basic differences in the tasks of the different connector classes, the structure is also a bit class dependent. While the external-import and the stream connector run independently in a regular interval or constantly, the other 3 connector classes only run when being requested by the OpenCTI platform.

The self-triggered connectors run independently, but the OpenCTI need to define a callback function, which can be executed for the connector to start its work. This is done via self.helper.listen(self._process_message). In the appended examples, the difference of the setup can be seen.

Self-triggered Connectors

  • external-import
  • stream

OpenCTI triggered

  • internal-analysis
  • internal-enrichment
  • internal-import
  • internal-export
from pycti import OpenCTIConnectorHelper, get_config_variable\n\nclass TemplateConnector:\n    def __init__(self) -> None:\n                # Initialization procedures\n                [...]\n        self.template_interval = get_config_variable(\n            \"TEMPLATE_INTERVAL\", [\"template\", \"interval\"], config, True\n        )\n\n    def get_interval(self) -> int:\n        return int(self.template_interval) * 60 * 60 * 24\n\n    def run(self) -> None:\n                # Main procedure\n\nif __name__ == \"__main__\":\n    try:\n        template_connector = TemplateConnector()\n        template_connector.run()\n    except Exception as e:\n        print(e)\n        time.sleep(10)\n        exit(0)\n
from pycti import OpenCTIConnectorHelper, get_config_variable\n\nclass TemplateConnector:\n    def __init__(self) -> None:\n                # Initialization procedures\n                [...]\n\n    def _process_message(self, data: dict) -> str:\n                # Main procedure                \n\n    # Start the main loop\n    def start(self) -> None:\n        self.helper.listen(self._process_message)\n\nif __name__ == \"__main__\":\n    try:\n        template_connector = TemplateConnector()\n        template_connector.start()\n    except Exception as e:\n        print(e)\n        time.sleep(10)\n        exit(0)\n
"},{"location":"development/connectors/#write-and-read-operations","title":"Write and Read Operations","text":"

When using the OpenCTIConnectorHelper class, there are two way for reading from or writing data to the OpenCTI platform.

  1. via the OpenCTI API interface via self.helper.api
  2. via the OpenCTI worker via self.send_stix2_bundle
"},{"location":"development/connectors/#sending-data-to-the-opencti-platform","title":"Sending data to the OpenCTI platform","text":"

The recommended way for creating or updating data in the OpenCTI platform is via the OpenCTI worker. This enables the connector to just send and forget about thousands of entities at once to without having to think about the ingestion order, performance or error handling.

\u26a0\ufe0f **Please DO NOT use the api interface to create new objects in connectors.**

The OpenCTI connector helper method send_stix2_bundle must be used to send data to OpenCTI. The send_stix2_bundle function takes 2 arguments.

  1. A serialized STIX2 bundle as a string (mandatory)
  2. A list of entities types that should be ingested (optional)

Here is an example using the STIX2 Python library:

from stix2 import Bundle, AttackPattern\n\n[...]\n\nattack_pattern = AttackPattern(name='Evil Pattern')\n\nbundle_objects = []\nbundle_objects.append(attack_pattern)\n\nbundle = Bundle(objects=bundle_objects).serialize()\nbundles_sent = self.opencti_connector_helper.send_stix2_bundle(bundle)\n
"},{"location":"development/connectors/#reading-from-the-opencti-platform","title":"Reading from the OpenCTI platform","text":"

Read queries to the OpenCTI platform can be achieved using the API and the STIX IDs can be attached to reports to create the relationship between those two entities.

entity = self.helper.api.vulnerability.read(\n    filters={\"key\": \"name\", \"values\": [\"T1234\"]}\n)\n

If you want to add the found entity via objects_refs to another SDO, simply add a list of stix_ids to the SDO. Here's an example using the entity from the code snippet above:

from stix2 import Report\n\n[...]\n\nreport = Report(\n    id=report[\"standard_id\"],\n  object_refs=[entity[\"standard_id\"]],\n)\n
"},{"location":"development/connectors/#logging","title":"Logging","text":"

When something crashes for a user, you as a developer want to know as much as possible about this incident to easily improve your code and remove this issue. To do so, it is very helpful if your connector documents what it does. Use info messages for big changes like the beginning or the finishing of an operation, but to facilitate your bug removal attempts, implement debug messages for minor operation changes to document different steps in your code.

When encountering a crash, the connector's user can easily restart the troubling connector with the debug logging activated.

  • CONNECTOR_LOG_LEVEL=debug

Using those additional log messages, the bug report is more enriched with information about the possible cause of the problem. Here's an example of how the logging should be implemented:

        def run(self) -> None:\n                self.helper.log_info('Template connector starts')\n                results = self._ask_for_news()\n                [...]\n\n        def _ask_for_news() -> None:\n                overall = []\n                for i in range(0, 10):\n                        self.log_debug(f\"Asking about news with count '{i}'\")\n                        # Do something\n                        self.log_debug(f\"Resut: '{result}'\")\n                        overall.append(result)\n                return overall\n

Please make sure that the debug messages rich of useful information, but that they are not redundant and that the user is not drowned by unnecessary information.

"},{"location":"development/connectors/#additional-implementations","title":"Additional implementations","text":"

If you are still unsure about how to implement certain things in your connector, we advise you to have a look at the code of other connectors of the same type. Maybe they are already using an approach which is suitable for addressing to your problem.

"},{"location":"development/connectors/#opencti-triggered-connector-special-cases","title":"OpenCTI triggered Connector - Special cases","text":""},{"location":"development/connectors/#data-layout-of-dictionary-from-callback-function","title":"Data Layout of Dictionary from Callback function","text":"

OpenCTI sends the connector a few instructions via the data dictionary in the callback function. Depending on the connector type, the data dictionary content is a bit different. Here are a few examples for each connector type.

Internal Analysis Connector

{\n   \"entity_id\": \"<stixCoreObjectId>\", // StixID of the object wanting to be analyzed\n   \"entity_type\": \"<stixCoreObjectEntityType>\",\n   \"content_type\": \"FIELDS\", // Analysis can be run on FIELDS or FILE\n   \"content_source\": \"content_mapping\", \n   \"content_fields\": [\"description\",\"content\"],\n   \"analysis_name\": \"<analysisName>\", // Analysis expected file name\n}\n

Internal Import Connector

{ \n  \"file_id\": \"<fileId>\",\n  \"file_mime\": \"application/pdf\", \n  \"file_fetch\": \"storage/get/<file_id>\", // Path to get the file\n  \"entity_id\": \"report--82843863-6301-59da-b783-fe98249b464e\", // Context of the upload\n}\n

Internal Enrichment Connector

{ \n  \"entity_id\": \"<stixCoreObjectId>\" // StixID of the object wanting to be enriched\n}\n

Internal Export Connector

{ \n  \"export_scope\": \"single\", // 'single' or 'list'\n  \"export_type\": \"simple\", // 'simple' or 'full'\n  \"file_name\": \"<fileName>\", // Export expected file name\n  \"max_marking\": \"<maxMarkingId>\", // Max marking id\n  \"entity_type\": \"AttackPattern\", // Exported entity type\n  // ONLY for single entity export\n  \"entity_id\": \"<entity.id>\", // Exported element\n  // ONLY for list entity export\n  \"list_params\": \"[<parameters>]\" // Parameters for finding entities\n}\n
"},{"location":"development/connectors/#self-triggered-connector-special-cases","title":"Self triggered Connector - Special cases","text":""},{"location":"development/connectors/#initiating-a-work-before-pushing-data","title":"Initiating a 'Work' before pushing data","text":"

For self-triggered connectors, OpenCTI has to be told about new jobs to process and to import. This is done by registering a so called work before sending the stix bundle and signalling the end of a work. Here an example:

By implementing the work registration, they will show up as shown in this screenshot for the MITRE ATT&CK connector:

def run() -> None:\n        # Anounce upcoming work\n        timestamp = int(time.time())\n        now = datetime.utcfromtimestamp(timestamp)\n    friendly_name = \"Template run @ \" + now.strftime(\"%Y-%m-%d %H:%M:%S\")\n    work_id = self.helper.api.work.initiate_work(\n                self.helper.connect_id, friendly_name\n        )\n\n        [...]\n        # Send Stix bundle\n        self.helper.send_stix2_bundle(\n                bundle,\n                entities_types=self.helper.connect_scope,\n                update=True,\n                work_id=work_id,\n        )\n        # Finish the work\n        self.helper.log_info(\n            f\"Connector successfully run, storing last_run as {str(timestamp)}\"\n    )              \n        message = \"Last_run stored, next run in: {str(round(self.get_interval() / 60 / 60 / 24, 2))} days\"\n        self.helper.api.work.to_processed(work_id, message)\n
"},{"location":"development/connectors/#interval-handling","title":"Interval handling","text":"

The connector is also responsible for making sure that it runs in certain intervals. In most cases, the intervals are definable in the connector config and then only need to be set and updated during the runtime.

class TemplateConnector:\n    def __init__(self) -> None:\n                # Initialization procedures\n                [...]\n        self.template_interval = get_config_variable(\n            \"TEMPLATE_INTERVAL\", [\"template\", \"interval\"], config, True\n        )\n\n    def get_interval(self) -> int:\n        return int(self.template_interval) * 60 * 60 * 24\n\n        def run(self) -> None:\n        self.helper.log_info(\"Fetching knowledge...\")\n        while True:\n            try:\n                # Get the current timestamp and check\n                timestamp = int(time.time())\n                current_state = self.helper.get_state()\n                if current_state is not None and \"last_run\" in current_state:\n                    last_run = current_state[\"last_run\"]\n                    self.helper.log_info(\n                        \"Connector last run: \"\n                        + datetime.utcfromtimestamp(last_run).strftime(\n                            \"%Y-%m-%d %H:%M:%S\"\n                        )\n                    )\n                else:\n                    last_run = None\n                    self.helper.log_info(\"Connector has never run\")\n                # If the last_run is more than interval-1 day\n                if last_run is None or (\n                    (timestamp - last_run)\n                    > ((int(self.template_interval) - 1) * 60 * 60 * 24)\n                ):\n                    timestamp = int(time.time())\n                    now = datetime.utcfromtimestamp(timestamp)\n                    friendly_name = \"Connector run @ \" + now.strftime(\"%Y-%m-%d %H:%M:%S\")\n\n                                        ###\n                                        # RUN CODE HERE     \n                                        ###\n\n                    # Store the current timestamp as a last run\n                    self.helper.log_info(\n                        \"Connector successfully run, storing last_run as \"\n                        + str(timestamp)\n                    )\n                    self.helper.set_state({\"last_run\": timestamp})\n                    message = (\n                        \"Last_run stored, next run in: \"\n                        + str(round(self.get_interval() / 60 / 60 / 24, 2))\n                        + \" days\"\n                    )\n                    self.helper.api.work.to_processed(work_id, message)\n                    self.helper.log_info(message)\n                    time.sleep(60)\n                else:\n                    new_interval = self.get_interval() - (timestamp - last_run)\n                    self.helper.log_info(\n                        \"Connector will not run, next run in: \"\n                        + str(round(new_interval / 60 / 60 / 24, 2))\n                        + \" days\"\n                    )\n                    time.sleep(60)\n
"},{"location":"development/connectors/#running-the-connector","title":"Running the connector","text":"

For development purposes, it is easier to simply run the python script locally until everything works as it should.

$ virtualenv env\n$ source ./env/bin/activate\n$ pip3 install -r requirements\n$ cp config.yml.sample config.yml\n# Define the opencti url and token, as well as the connector's id\n$ vim config.yml\n$ python3 main.py\nINFO:root:Listing Threat-Actors with filters null.\nINFO:root:Connector registered with ID: a2de809c-fbb9-491d-90c0-96c7d1766000\nINFO:root:Starting ping alive thread\n...\n
"},{"location":"development/connectors/#final-testing","title":"Final Testing","text":"

Before submitting a Pull Request, please test your code for different use cases and scenarios. We don't have an automatic testing suite for the connectors yet, thus we highly depend on developers thinking about creative scenarios their code could encounter.

"},{"location":"development/connectors/#prepare-for-release","title":"Prepare for release","text":"

If you plan to provide your connector to be used by the community (\u2764\ufe0f) your code should pass the following (minimum) criteria.

# Linting with flake8 contains no errors or warnings\n$ flake8 --ignore=E,W\n# Verify formatting with black\n$ black .\nAll done! \u2728 \ud83c\udf70 \u2728\n1 file left unchanged.\n# Verify import sorting\n$ isort --profile black .\nFixing /path/to/connector/file.py\n# Push you feature/fix on Github\n$ git add [file(s)]\n$ git commit -m \"[connector_name] descriptive message\"\n$ git push origin [branch-name]\n# Open a pull request with the title \"[connector_name] message\"\n

If you have any trouble with this just reach out to the OpenCTI core team. We are happy to assist with this.

"},{"location":"development/environment_ubuntu/","title":"Prerequisites Ubuntu","text":"

Development stack require some base software that need to be installed.

"},{"location":"development/environment_ubuntu/#docker-or-podman","title":"Docker or podman","text":"

Platform dependencies in development are deployed through container management, so you need to install a container stack.

We currently support docker and podman.

$ sudo apt-get install docker docker-compose curl\n
sudo apt-get -y install podman\n

As OpenCTI has a dependency to ElasticSearch, you have to set the vm.max_map_count before running the containers, as mentioned in the ElasticSearch documentation.

$ sudo sysctl -w vm.max_map_count=262144\n
"},{"location":"development/environment_ubuntu/#nodejs-and-yarn","title":"NodeJS and yarn","text":"

The platform is developed on nodejs technology, so you need to install node and the yarn package manager.

$ sudo apt-get install nodejs\n$ sudo curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -\n$ sudo echo \"deb https://dl.yarnpkg.com/debian/ stable main\" | sudo tee /etc/apt/sources.list.d/yarn.list\n$ sudo apt-get update && sudo apt-get install yarn\n
"},{"location":"development/environment_ubuntu/#python-runtime","title":"Python runtime","text":"

For worker and connectors, a python runtime is needed.

$ sudo apt-get install python3 python3-pip\n
"},{"location":"development/environment_ubuntu/#git-and-dev-tool","title":"Git and dev tool","text":"
  • Install Git from apt
$ sudo apt-get install git-all\n
  • Install your preferred IDE
    • Intellij community edition - https://www.jetbrains.com/idea/download/
    • VSCode - https://code.visualstudio.com/
"},{"location":"development/environment_windows/","title":"Prerequisites Windows","text":"

Development stack require some base software that need to be installed.

"},{"location":"development/environment_windows/#docker-or-podman","title":"Docker or podman","text":"

Platform dependencies in development are deployed through container management, so you need to install a container stack.

We currently support docker and postman.

Docker Desktop from - https://docs.docker.com/desktop/install/windows-install/

  • Install new version of - https://docs.microsoft.com/windows/wsl/wsl2-kernel. This will require a reboot.
  • Shell out to CMD as Administrator and run the following powershell command:

wsl --set-default-version 2

  • Reboot computer and continue to next step
  • Load Docker Application
  • NOTE DOCKER LICENSE - You are agreeing to the licence for Non-commercial Open Source Project use. OpenCTI is Open Source and the version you would be possibly contributing to enhancing is the unpaid non-commercial/non-enterprise version. If you intention is different - please consult with your organization's legal/licensing department.
  • Leave Docker Desktop running
"},{"location":"development/environment_windows/#nodejs-and-yarn","title":"NodeJS and yarn","text":"

The platform is developed on nodejs technology, so you need to install node and the yarn package manager.

  • Install NodeJS from - https://nodejs.org/download/release/v16.20.0/node-v16.20.0-x64.msi
  • Select the option for installing Chocolatey on the Tools for Native Modules screen
    • Will do this install for you automatically - https://chocolatey.org/packages/visualstudio2019-workload-vctools
    • Includes Python 3.11.4

  • Shell out to CMD prompt as Administrator and install/run:

    • pip3 install pywin32

  • Configure Yarn (https://yarnpkg.com/getting-started/install)

  • Open CMD as Administrator and run the following command:
    • corepack enable
"},{"location":"development/environment_windows/#python-runtime","title":"Python runtime","text":"

For worker and connectors, a python runtime is needed. Even if you already have a python runtime installed through node installation, on windows some nodejs package will be recompiled with python and C++ runtime.

For this reason Visual Studio Build Tools is required.

  • Install Visual Studio Build Tools from - https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=BuildTools
  • Check off Desktop Development with C++
  • Run install
"},{"location":"development/environment_windows/#git-and-dev-tool","title":"Git and dev tool","text":"
  • Download GIT for Windows (64-bit Setup)- https://git-scm.com/download/win

  • Just use defaults on each screen

  • Install your preferred IDE

  • Intellij community edition - https://www.jetbrains.com/idea/download/
  • VSCode - https://code.visualstudio.com/docs/?dv=win64
"},{"location":"development/platform/","title":"Platform development","text":""},{"location":"development/platform/#introduction","title":"Introduction","text":"

This summary should give you a detailed setup description for initiating the OpenCTI setup environment necessary for developing on the OpenCTI platform, a client library or the connectors. This page document how to set up an \"All-in-One\" development environment for OpenCTI. The devenv will contain data of 3 different repositories:

  • Platform: https://github.com/OpenCTI-Platform/opencti
  • Connectors: https://github.com/OpenCTI-Platform/connectors
  • Client python: https://github.com/OpenCTI-Platform/client-python
"},{"location":"development/platform/#platform","title":"Platform","text":"

Contains the platform OpenCTI project code base:

  • docker-compose (docker or podman) ~/opencti/opencti-platform/opencti-dev
  • Web frontend (nodejs / react) ~/opencti/opencti-platform/opencti-graphql
  • Backend (nodejs) ~/opencti/opencti-platform/opencti-frontend
  • Worker (nodejs / python) ~/opencti/opencti-worker
"},{"location":"development/platform/#connectors","title":"Connectors","text":"

Contains a lot of developed connectors, as a source of inspiration for your new connector.

"},{"location":"development/platform/#client-python","title":"Client python","text":"

Contains the source code of the python library used in worker or connectors.

"},{"location":"development/platform/#prerequisites","title":"Prerequisites","text":"

Some tools are needed before starting to develop. Please check Ubuntu prerequisites or Windows prerequisites

"},{"location":"development/platform/#clone-the-projects","title":"Clone the projects","text":"

Fork and clone the git repositories

  • https://github.com/OpenCTI-Platform/opencti/ - frontend / backend
  • https://github.com/OpenCTI-Platform/connectors - connectors
  • https://github.com/OpenCTI-Platform/docker - docker stack
  • https://github.com/OpenCTI-Platform/client-python/ - python client
"},{"location":"development/platform/#dependencies-containers","title":"Dependencies containers","text":"

In development dependencies are deployed trough containers. A development compose file is available in ~/opencti/opencti-platform/opencti-dev

cd ~/docker\n#Start the stack in background\ndocker-compose -f ./docker-compose-dev.yml up -d\n

You now have all the dependencies of OpenCTI running and waiting for product to run.

"},{"location":"development/platform/#backend-api","title":"Backend / API","text":""},{"location":"development/platform/#python-virtual-env","title":"Python virtual env","text":"

The GraphQL API is developed in JS and with some python code. As it's an \"all-in-one\" installation, the python environment will be installed in a virtual environment.

cd ~/opencti/opencti-platform/opencti-graphql\npython3 -m venv .venv --prompt \"graphql\"\nsource .venv/bin/activate\npip install --upgrade pip wheel setuptools\nyarn install\nyarn install:python \ndeactivate\n
"},{"location":"development/platform/#development-configuration","title":"Development configuration","text":"

The API can be specifically configured with files depending on the starting profile. By default, the default.json file is used and will be correctly configured for local usage except for admin password.

So you need to create a development profile file. You can duplicate the default file and adapt if you need. 

cd ~/opencti/opencti-platform/opencti-graphql/config\ncp default.json development.json\n

At minimum adapt the admin part for the password and token. 

    \"admin\": {\n      \"email\": \"admin@opencti.io\",\n      \"password\": \"MyNewPassord\",\n      \"token\": \"UUID generated with https://www.uuidgenerator.net\"\n    }\n

"},{"location":"development/platform/#install-start","title":"Install / start","text":"

Before starting the backend you need to install the nodejs modules

cd ~/opencti/opencti-platform/opencti-graphql\nyarn install\n

Then you can simply start the backend API with the yarn start command

cd ~/opencti/opencti-platform/opencti-graphql\nyarn start\n

The platform will start logging some interesting information

{\"category\":\"APP\",\"level\":\"info\",\"message\":\"[OPENCTI] Starting platform\",\"timestamp\":\"2023-07-02T16:37:10.984Z\",\"version\":\"5.8.7\"}\n{\"category\":\"APP\",\"level\":\"info\",\"message\":\"[OPENCTI] Checking dependencies statuses\",\"timestamp\":\"2023-07-02T16:37:10.987Z\",\"version\":\"5.8.7\"}\n{\"category\":\"APP\",\"level\":\"info\",\"message\":\"[SEARCH] Elasticsearch (8.5.2) client selected / runtime sorting enabled\",\"timestamp\":\"2023-07-02T16:37:11.014Z\",\"version\":\"5.8.7\"}\n{\"category\":\"APP\",\"level\":\"info\",\"message\":\"[CHECK] Search engine is alive\",\"timestamp\":\"2023-07-02T16:37:11.015Z\",\"version\":\"5.8.7\"}\n...\n{\"category\":\"APP\",\"level\":\"info\",\"message\":\"[INIT] Platform initialization done\",\"timestamp\":\"2023-07-02T16:37:11.622Z\",\"version\":\"5.8.7\"}\n{\"category\":\"APP\",\"level\":\"info\",\"message\":\"[OPENCTI] API ready on port 4000\",\"timestamp\":\"2023-07-02T16:37:12.382Z\",\"version\":\"5.8.7\"}\n

If you want to start on another profile you can use the -e parameter. For example here to use the profile.json configuration file.

yarn start -e profile\n
"},{"location":"development/platform/#code-check","title":"Code check","text":"

Before pushing your code you need to validate the syntax and ensure the testing will be validated.

"},{"location":"development/platform/#for-validation","title":"For validation","text":"

yarn lint

yarn check-ts

"},{"location":"development/platform/#for-testing","title":"For testing","text":"

For starting the test you will need to create a test.json configuration file. You can use the same dependencies by only adapting all prefix for all dependencies.

Tests are using dedicated indices in the Elastic database (prefixed with test-* or the prefix that you have set up in test.json).

The following command will run the complete test suite using vitest, which might take more than 30 minutes. It starts by cleaning up the test database and seeding a minimal dataset. The file vitest.config.test.ts can be edited to run only a specific file pattern.

yarn test:dev

We also provide utility scripts to ease the development of new tests, especially integration tests that rely on the sample data loaded after executing 00-inject/loader-test.ts.

To solely initialize the test database with this sample dataset run:

yarn test:dev:init

And then, execute the following command to run the pattern specified in the file vitest.config.test.ts, or add a file name to the command line to run only this test file.

yarn test:dev:resume

This last command will NOT cleanup & initialize the test database and thus will be quicker to execute.

"},{"location":"development/platform/#frontend","title":"Frontend","text":""},{"location":"development/platform/#install-start_1","title":"Install / start","text":"

Before starting the backend you need to install the nodejs modules

cd ~/opencti/opencti-platform/opencti-front\nyarn install\n

Then you can simply start the frontend with the yarn start command

cd ~/opencti/opencti-platform/opencti-front\nyarn start\n

The frontend will start with some interesting information

[INFO] [default] compiling...\n[INFO] [default] compiled documents: 1592 reader, 1072 normalization, 1596 operation text\n[INFO] Compilation completed.\n[INFO] Done.\n[HPM] Proxy created: /stream  -> http://localhost:4000\n[HPM] Proxy created: /storage  -> http://localhost:4000\n[HPM] Proxy created: /taxii2  -> http://localhost:4000\n[HPM] Proxy created: /feeds  -> http://localhost:4000\n[HPM] Proxy created: /graphql  -> http://localhost:4000\n[HPM] Proxy created: /auth/**  -> http://localhost:4000\n[HPM] Proxy created: /static/flags/**  -> http://localhost:4000\n

The web UI should be accessible on http://127.0.0.1:3000

"},{"location":"development/platform/#code-check_1","title":"Code check","text":"

Before pushing your code you need to validate the syntax and ensure the testing will be validated.

"},{"location":"development/platform/#for-validation_1","title":"For validation","text":"

yarn lint

yarn check-ts

"},{"location":"development/platform/#for-testing_1","title":"For testing","text":"

yarn test

"},{"location":"development/platform/#worker","title":"Worker","text":"

Running a worker is required when you want to develop on the ingestion or import/export connectors.

"},{"location":"development/platform/#python-virtual-env_1","title":"Python virtual env","text":"
cd ~/opencti/opencti-worker/src\npython3 -m venv .venv --prompt \"worker\"\nsource .venv/bin/activate\npip3 install --upgrade pip wheel setuptools\npip3 install -r requirements.txt\ndeactivate\n
"},{"location":"development/platform/#install-start_2","title":"Install / start","text":"
cd ~/opencti/opencti-worker/src\nsource .venv/bin/activate\npython worker.py\n
"},{"location":"development/platform/#connectors_1","title":"Connectors","text":"

For connectors development, please take a look to Connectors development dedicated page.

"},{"location":"development/platform/#production-build","title":"Production build","text":"

Based on development source you can build the package for production. This package will be minified and optimized with esbuild.

$ cd opencti-frontend\n$ yarn build\n$ cd ../opencti-graphql\n$ yarn build\n

After the build you can start the production build with yarn serv. This build will use the production.json configuration file.

$ cd ../opencti-graphql\n$ yarn serv\n
"},{"location":"development/platform/#continuous-integration-and-features-cross-repository","title":"Continuous Integration and features cross repository","text":"

When a feature requires changes in two or more repositories in opencti, connectors and client-python; then some specific convention must be used to have the continuous integration build them all together.

"},{"location":"development/platform/#naming-convention-of-branch","title":"Naming convention of branch","text":"

The Pull Request on opencti repository should be (issue or bug)/number + optional, example: issue/7062-contributing

The pull request on connector or client-python should refer to the opencti one by starting with \"opencti/\" and then the same name. Example: opencti/issue/7062-contributing

Note that if there are several matches, the first one is taken. So for example having issue/7062-contributing and issue/7062 that are both marked as \"multi-repository\" is not a good idea.

"},{"location":"development/platform/#labels","title":"Labels","text":"

All Pull Requests involved must have the label multi-repository added in GitHub.

"},{"location":"development/python/","title":"Python library","text":"

The PyCTI library is the official Python client for OpenCTI. It is made to help developers interact with the openCTI plaform.

"},{"location":"development/python/#installation","title":"Installation","text":"

To install the latest Python client library, please use pip:

$ pip3 install pycti\n
"},{"location":"development/python/#using-the-helper-functions","title":"Using the helper functions","text":"

The main class OpenCTIApiClient contains all what you need to interact with the platform, you just have to initialize it.

The following example shows how you create an indicator in OpenCTI using the python library with TLP marking and OpenCTI compatible date format.

from dateutil.parser import parse\nfrom pycti import OpenCTIApiClient\nfrom stix2 import TLP_GREEN\n\n# OpenCTI API client initialization\nopencti_api_client = OpenCTIApiClient(\"https://myopencti.server\", \"mysupersecrettoken\")\n\n# Define an OpenCTI compatible date\ndate = parse(\"2019-12-01\").strftime(\"%Y-%m-%dT%H:%M:%SZ\")\n\n# Get the OpenCTI marking for stix2 TLP_GREEN\nTLP_GREEN_CTI = opencti_api_client.marking_definition.read(id=TLP_GREEN[\"id\"])\n\n# Use the client to create an indicator in OpenCTI\nindicator = opencti_api_client.indicator.create(\n    name=\"C2 server of the new campaign\",\n    description=\"This is the C2 server of the campaign\",\n    pattern_type=\"stix\",\n    pattern=\"[domain-name:value = 'www.5z8.info']\",\n    x_opencti_main_observable_type=\"IPv4-Addr\",\n    valid_from=date,\n    update=True,\n    markingDefinitions=[TLP_GREEN_CTI[\"id\"]],\n)\n
"},{"location":"development/python/#examples","title":"Examples","text":"

A suite of illustrative examples is available in the PyCTI GitHub repository to aid in better understanding.

"},{"location":"reference/api/","title":"GraphQL API","text":"

OpenCTI provides a comprehensive API based on GraphQL, allowing users to perform various actions programmatically. The API enables users to interact with OpenCTI's functionality and data, offering a powerful tool for automation, integration, and customization. All actions that can be performed through the platform's graphical interface are also achievable via the API.

"},{"location":"reference/api/#authentication","title":"Authentication","text":"

Access to the OpenCTI API requires authentication using standard authentication mechanisms. Access rights to data via the API will be determined by the access privileges of the user associated with the API key. For authentication, users need to include the following headers in their API requests:

Content-Type: application/json\nAuthorization: Bearer [API key]\n
"},{"location":"reference/api/#documentation","title":"Documentation","text":"

The OpenCTI API consists of various endpoints corresponding to different functionalities and operations within the platform. These endpoints allow users to perform actions such as querying data, creating or updating entities, and more. Users can refer to the Understand GraphQL section to understand how it works.

Documentation for the OpenCTI API, including schema definitions, the list of filters available and queryable fields, is available through the OpenCTI platform. It can be found on the GraphQL playground. However, query examples and mutation examples are not yet available. In the meantime, users can explore the available endpoints and their functionality by inspecting network traffic in the browser's developer tools or by examining the source code of the Python client.

"},{"location":"reference/api/#understand-graphql","title":"Understand GraphQL","text":"

GraphQL is a powerful query language for APIs that enables clients to request exactly the data they need. Unlike traditional REST APIs, which expose fixed endpoints and return predefined data structures, GraphQL APIs allow clients to specify the shape and structure of the data they require.

"},{"location":"reference/api/#core-concepts","title":"Core concepts","text":""},{"location":"reference/api/#schema-definition-language-sdl","title":"Schema Definition Language (SDL)","text":"

GraphQL APIs are defined by a schema, which describes the types of data that can be queried and the relationships between them. The schema is written using the Schema Definition Language (SDL), which defines types, fields, and their relationships.

"},{"location":"reference/api/#query-language","title":"Query language","text":"

GraphQL uses a query language to request data from the server. Clients can specify exactly which fields they need and how they are related, enabling precise data retrieval without over-fetching or under-fetching.

Example:

query IntrusionSets {\n    intrusionSets (\n        filters:\n        {\n            mode: and,\n            filters: [\n                {\n                    key: \"name\",\n                    values: [\"Ajax Security Team\"],\n                    operator: eq,\n                    mode: or,\n                }\n            ],\n            filterGroups: [],\n        }\n    )\n    {\n        edges{\n            node{\n                id\n                name\n                description\n                externalReferences{\n                    edges{\n                        node{\n                            url\n                            source_name\n                        }\n                    }\n                }\n            }\n        }\n    }\n}\n
"},{"location":"reference/api/#resolvers","title":"Resolvers","text":"

Resolvers are functions responsible for fetching the requested data. Each field in the GraphQL schema corresponds to a resolver function, which determines how to retrieve the data from the underlying data sources.

"},{"location":"reference/api/#how-it-works","title":"How it Works","text":"
  1. Schema definition: The API provider defines a GraphQL schema using SDL, specifying the types and fields available for querying.
  2. Query execution: Clients send GraphQL queries to the server, specifying the data they need. The server processes the query, resolves each field, and constructs a response object with the requested data.
  3. Validation and execution: The server validates the query against the schema to ensure it is syntactically and semantically correct. If validation passes, the server executes the query, invoking the appropriate resolver functions to fetch the requested data.
  4. Data retrieval: Resolvers fetch data from the relevant data sources, such as databases, APIs, or other services. They transform the raw data into the shape specified in the query and return it to the client.
  5. Response formation: Once all resolvers have completed, the server assembles the response object containing the requested data and sends it back to the client.
"},{"location":"reference/api/#external-resources","title":"External Resources","text":"

For a more in-depth understanding of GraphQL and its usage, consider exploring the following external resources:

  • GraphQL Official Documentation
  • GraphQL query documentation
  • How to GraphQL
"},{"location":"reference/data-intelligence/","title":"Data intelligence","text":"

As a cyber threat intelligence platform, OpenCTI offers functionalities that enable users to move quickly from raw data to operational intelligence by building up high-quality, structured information.

To do so, the platform provides a number of essential capabilities, such as automated data deduplication, merging of similar entities while preserving relationship integrity, the ability to modulate the confidence levels on your intelligence, and the presence of inference rules to automate the creation of logical relationships among your data.

The purpose of this page is to list the features of the platform that contribute to the intelligibility and quality of intelligence.

"},{"location":"reference/data-intelligence/#deduplication","title":"Deduplication","text":"

The first essential data intelligence mechanism in OpenCTI is the deduplication of information and relations.

This advanced functionality not only enables you to check whether a piece of data, information or a relationship is not a duplicate of an existing element, but will also, under certain conditions, enrich the element already present.

If the new duplicated entity has new content, the pre-existing entity can be enriched with the new information from the duplicate.

It works as follows (see details in the dedicated page):

  • For entities: based on the entity's properties based on a specific ID generated by the \"ID Contributing Properties\" platform (properties listed on the dedicated page).
  • For relationships: based on type, source, target, start time, and stop time.
  • For observables: a specific ID is also generated by the platform, this time based on the specifications of the STIX model.

The ability to update and enrich is determined by the confidence level and quality level of the entities and relationships (see diagram on page deduplication).

"},{"location":"reference/data-intelligence/#merging","title":"Merging","text":"

OpenCTI's merging function is one of the platform's crucial data intelligence elements.

From the Data > Entities tab, this feature lets you merge up to 4 entities of the same type. A parent entity is selected and assigned up to three child entities.

The benefit of this feature is to centralize a number of similar elements from different sources without losing data or degrading the quality of the information. During merging, the platform will create relationships to anchor all the data to the consolidated entity.

This enrichment function consolidates the data and avoids duplication, but above all initiates a structured intelligence process while preserving the integrity of pre-existing relationships as presented here.

"},{"location":"reference/data-intelligence/#confidence-level-and-data-segregation","title":"Confidence level and data segregation","text":"

Another key element of OpenCTI's data intelligence is its ability to apply confidence levels and to segregate the data present in the platform.

The confidence level is directly linked to users and Role Based Access Control. It is applied to a user directly or indirectly via the confidence level of the group to which the user belongs. This element is fundamental as it defines the levels of data manipulation to which the user (real or connector) is entitled.

The correct application of confidence levels is all the more important as it will determine the confidence level of the data manipulated by a user. It is therefore a decisive mechanism, since it underpins the confidence you have in the content of your instance.

While it is important to apply a level of trust to your users or groups, it is also important to define a way of categorizing and protecting your data.

Data segregation makes it possible to apply marking definitions and therefore establish a standardized framework for classifying data.

These marking definitions, like the classic Traffic Light Protocols (TLP) implemented by default in the platform, will determine whether a user can access a specific data set. The marking will be applied at the group level to which the user belongs, which will determine the data to which the user has access and therefore the data that the user can potentially handle.

"},{"location":"reference/data-intelligence/#inference-rules","title":"Inference rules","text":"

In OpenCTI, data intelligence is not just about the ability to segregate, qualify or enrich data. OpenCTI's inference rules enable you to mobilize the data on your platform effectively and operationally.

These predefined rules enable the user to speed up cyber threat management. For example, inferences can be used to automatically identify incidents based on a sighting, to create sightings on observables based on new observed data, to propagate relationships based on an observable, etc.

In all, the platform includes some twenty high-performance inference rules that considerably speed up the analysis and response to threats (see the full list here).

These rules are based on a logical interpretation of the data, resulting in a pre-analysis of the information by creating relationships that will enrich the intelligence in the platform. There are three main benefits: efficiency, completeness and accuracy. These user benefits can be found here.

Note: If these rules are present in the platform, they are not activated by default.

Once activated, they scan all the data in your platform in the background to identify all the existing relationships that meet the conditions of the rules. Then, the rules operate continuously to create relationships. If you deactivate a rule, all the objects and relationships it has created will be deleted.

These actions can only be carried out by an administrator of the instance.

"},{"location":"reference/data-model/","title":"Data model","text":"

Under construction

This page will be automatically generated to reference the platform's data model. We are doing our best to implement this automatic generation as quickly as possible.

"},{"location":"reference/filters-migration/","title":"Filters format migration for OpenCTI 5.12","text":"

The version 5.12 of OpenCTI introduces breaking changes to the filters format used in the API. This documentation describes how you can migrate your scripts or programs that call the OpenCTI API, when updating from a version of OpenCTI inferior to 5.12.

"},{"location":"reference/filters-migration/#why-this-migration","title":"Why this migration?","text":"

Before OpenCTI 5.12, it was not possible to construct complex filters combinations: we couldn't embed filters within filters, used different boolean modes (and/or), filter on all available attributes or relations for a given entity type, or even test for empty fields of any sort.

Legacy of years of development, the former format and filtering mechanics were not adapted for such task, and a profound refactoring was necessary to make it happen.

Here are the main pain points we identified beforehand:

  • The filters frontend and backend formats were very different, requiring careful conversions.
  • The filter were static lists of keys, depending on each given entity type and maintained by hands.
  • The operator (eq, not_eq, etc.) was inside the key (e.g. entity_type_not_eq), limiting operator combination and requiring error-prone parsing.
  • The frontend format imposed a unique form of combination (and between filters, or between values inside each filter, and nothing else possible).
  • The flat list structure made impossible filter imbrication by nature.
  • Filters and query options were mixed in GQL queries for the same purpose (for instance, option types analog to a filter on key entity_type).
// filter formats in OpenCTI < 5.12\n\ntype Filter = {\n    key: string, // a key in the list of the available filter keys for given the entity type\n    values: string[],\n    operator: string,\n    filterMode: 'and' | 'or',\n}\n\n// \"give me Reports labelled with labelX or labelY\"\nconst filters = [\n  { \n    \"key\": \"entity_type\",\n    \"values\": [\"Report\"],\n    \"operator\": \"eq\",\n    \"filterMode\": \"or\"\n  },\n  { \n    \"key\": \"labelledBy\",\n    \"values\": [\"<id-for-labelX>\", \"<id-for-labelY>\"],\n    \"operator\": \"eq\",\n    \"filterMode\": \"or\"\n  },\n]\n

The new format brings a lot of short-term benefits and is compatible with our long-term vision of the filtering capabilities in OpenCTI. We chose a simple recursive structure that allow complex combination of any sort with respect to basic boolean logic.

The list of operator is fixed and can be extended during future developments.

// filter formats in OpenCTI >= 5.12\n\ntype FilterGroup = {\n  mode: 'and' | 'or'\n  filters: Filter[]\n  filterGroups: FilterGroup[] // recursive definition\n}\n\ntype Filter  = {\n  key: string[]\n  values: string[]\n  operator: 'eq' | 'not_eq' | 'gt' // ... and more\n  mode: 'and' | 'or',\n}\n\n// \"give me Reports and RFIs, not marked TLP:RED with labelX or no label\"\nconst filters = {\n  mode: 'and',\n  filters: [\n    { key: 'entity_type', values: ['Report', 'Case-Rfi'], operator: 'eq', mode: 'or', },\n    { key: 'objectMarking', values: ['<id-for-TLP:RED>'], operator: 'not_eq', mode: 'or', },\n  ],\n  filterGroups: [{\n    mode: 'or',\n    filters: [\n      { key: 'objectLabel', values: [\"<id-for-labelX>\"], operator: 'eq', mode: 'or', },\n      { key: 'objectLabel', values: [], operator: 'nil', mode: 'or', },\n    ],\n    filterGroups: [],\n  }],\n};\n

Because changing filters format impacts almost everything in the platform, we decided to do a complete refactoring once and for all. We want this migration process to be clear and easy.

"},{"location":"reference/filters-migration/#what-has-been-changed","title":"What has been changed","text":"

The new filter implementation bring major changes in the way filters are processed and executed.

  • We change the filters formats (see FilterGroup type above):

    • In the frontend, an operator and a mode are stored for each key.
    • The new format enables filters imbrication thanks to the new attribute 'filterGroups'.
    • The keys are of type string (no more static list of enums).
    • The 'values' attribute can no longer contain null values (use the nil operator instead).

  • We also renamed some filter keys, to be consistent with the entities schema definitions.

  • We implemented the handling of the different operators and modes in the backend.
  • We introduced new void operators (nil / not_nil) to test the presence or absence of value in any field.
"},{"location":"reference/filters-migration/#how-to-migrate-your-own-filters","title":"How to migrate your own filters","text":"

We wrote a migration script to convert all stored filters created prior to version 5.12. These filters will thus be migrated automatically when starting your updated platform.

However, you might have your own connectors, queries, or python scripts that use the graphql API or the python client. If this is the case, you must change the filter format if you want to run the code against OpenCTI >= 5.12.

"},{"location":"reference/filters-migration/#filter-conversion","title":"Filter conversion","text":"

To convert filters prior to version 5.12 in the new format:

  1. update the key field if it has been changed in 5.12 (see the conversion table below),
  2. rename the field filterMode in mode
  3. if values contains null, see below for conversion.

Now you can build your new FilterGroup object with:

  • mode: 'and'
  • filters = array of converted filters (following previous steps),
  • filterGroups: []
const oldFilter = {\n    key: 'old_key',\n    values: ['value1', 'value2'],\n    operator: 'XX',\n    filterMode: 'XX',\n}\n\nconst convertedFilter = {\n    key: 'converted_key_if_necessary',\n    values: ['value1', 'value2'],\n    operator: 'XX',\n    mode: 'XX',\n}\n\nconst newFilters = {\n    mode: 'and',\n    filters: [convertedFilter1, convertedFilter2...], // array with all converted filters\n    filterGroups: [],\n}\n

If values contains a null value, you need to convert the filter by using the new nil / not_nil operators. Here's the procedure:

  1. Extract one filter dedicated to null

    • if operator was 'eq', switch to operator: 'nil' / if operator was not_eq, switch to operator = 'not_nil'
    • values = []

  2. Extract another filter for all the other values.

// \"Must have a label that is not Label1 or Label2\"\nconst oldFilter = {\n    key: 'labelledBy',\n    values: [null, 'id-for-Label1', 'id-for-Label2'],\n    operator: 'not_eq',\n    filterMode: 'and',\n}\n\nconst newFilters = {\n    mode: 'and',\n    filters: [\n      {\n        key: 'objectLabel',\n        values: ['id-label-1', 'id-for-Label2'],\n        operator: 'not_eq',\n        mode: 'and',\n      },\n      {\n        key: 'objectLabel',\n        values: [],\n        operator: 'not_nil',\n        mode: 'and',\n      },\n    ],\n    filterGroups: [],\n}\n

Switch to nested filter to preserve logic

To preserve the logic of your old filter you might need to compose nested filter groups. This could happen for instance when using eq operator with null values for one filter, combined in and mode with other filters.

"},{"location":"reference/filters-migration/#filter-keys-conversion-table","title":"Filter keys conversion table","text":"

Make sure you address all the filter keys that require conversion, following the map below:

// array of [oldKey, newKey] for the renamed keys\nconst keyConversion = [\n    ['labelledBy', 'objectLabel'],\n    ['markedBy', 'objectMarking'],\n    ['objectContains', 'objects'],\n    ['killChainPhase', 'killChainPhases'],\n    ['assigneeTo', 'objectAssignee'],\n    ['participant', 'objectParticipant'],\n    ['creator', 'creator_id'],\n    ['hasExternalReference', 'externalReferences'],\n    ['hashes_MD5', 'hashes.MD5'],\n    ['hashes_SHA1', 'hashes.SHA-1'],\n    ['hashes_SHA256', 'hashes.SHA-256'],\n    ['hashes_SHA512', 'hashes.SHA-512']\n]\n
"},{"location":"reference/filters-migration/#examples","title":"Examples","text":""},{"location":"reference/filters-migration/#simple-example","title":"Simple example","text":"

Let's start with a simple case:

All Reports with label \"label1\" or \"label2\"

(entity_type = Report) AND (label = label1 OR label2)

const oldBackendFilter = [\n  {\n    key: 'entity_type',\n    values: ['Report'],\n    operator: 'eq',\n    filterMode: 'or',\n  },\n  {\n   key: 'labelledBy',\n    values: [label1_id, label2_id],\n    operator: 'eq',\n    filterMode: 'or',\n  },\n];\n\nconst newFilters = {\n  mode: 'and',\n  filters: [\n    {\n      key: 'entity_type',\n      values: ['Report'],\n      operator: 'eq',\n      mode: 'or',\n    },\n    {\n      key: 'objectLabel',\n      values: [label1_id, label2_id],\n      operator: 'eq',\n      mode: 'or',\n    }\n  ],\n  filterGroups: [],\n};\n
"},{"location":"reference/filters-migration/#complex-example","title":"Complex example","text":"

Now let's see a more complex case involving filter group nesting:

\"All Reports that have either the label \"label1\" or \"label2\", or no label at all\"

(entity_type = Report) AND (label = \"No label\" OR label1 OR label2)

const oldBackendFilter = [\n    {\n      key: 'labelledBy',\n      values: [label1_id, label2_id, null],\n      operator: 'eq',\n      filterMode: 'or',\n    },\n    {\n      key: 'entity_type',\n      values: ['Report'],\n      operator: 'eq',\n      filterMode: 'or',\n    },\n];\n\nconst newFilters = {\n    mode: 'and',\n    filters: [\n      {\n        key: 'entity_type',\n        values: ['Report'],\n        operator: 'eq',\n        mode: 'or',\n      },\n    ],\n    // the combination mode/operator in this case requires nested filter groups\n    filterGroups: [\n      {\n        mode: 'or',\n        filters: [\n          {\n            key: 'objectLabel',\n            values: [label1_id, label2_id],\n            operator: 'eq',\n            mode: 'or',\n          },\n          {\n            key: 'objectLabel',\n            operator: 'nil',\n            values: [], // empty, does not matter\n            mode: 'or', // and/or, does not matter \n          },\n        ],\n        filterGroups: [],\n      }\n    ],\n};\n
"},{"location":"reference/filters-migration/#residual-dynamic-filters","title":"Residual dynamic filters","text":"

Dynamic filters are not stored in the database, they enable to filter view in the UI, e.g. filters in entities list, investigations, knowledge graphs. They are saved as URL parameters, and can be saved in local storage.

These filters are not migrated automatically and are lost when moving to 5.12. This concerns the filters saved for each view, that are restored when coming back to the same view. You will need to reconstruct the filters by hand in the UI; these new filters will be properly saved and restored afterward.

Also, when going to an url with filters in the old format, OpenCTI will display a warning and remove the filter parameters. Only URLs built by OpenCTI 5.12 are compatible with it, so you will need to reconstruct the filters by hand and save / share your updated links.

"},{"location":"reference/filters/","title":"Filter knowledge","text":"

In OpenCTI, you can filter data to target or view entities that have particular attributes.

"},{"location":"reference/filters/#filters-usages","title":"Filters usages","text":"

There are two types of filters that are used in many locations in the platform:

  • in entities lists: to display only the entities matching the filters. If an export or a background task is generated, only the filtered data will be taken into account,
  • in investigations and knowledge graphs: to display only the entities matching the filters,
  • in dashboards: to create widget with only the entities matching the filters,
  • in feeds, TAXII collections, triggers, streams, playbooks, background tasks: to process only the data or events matching the filters.
"},{"location":"reference/filters/#dynamic-filters","title":"Dynamic filters","text":"

Dynamic filters are not stored in the database, they enable to filter view in the UI, e.g. filters in entities list, investigations, knowledge graphs.

However, they are still persistent in the platform frontend side. The filters used in a view are saved as URL parameters, so you can save and share links of these filtered views.

Also, your web browser saves in local storage the filters that you are setting in various places of the platform, allowing to retrieve them when you come back to the same view. You can then keep working from where you left of.

"},{"location":"reference/filters/#stored-filters","title":"Stored filters","text":"

Stored filters are attributes of an entity, and are therefore stored in the database. They are stored as an attribute in the object itself, e.g. filters in dashboards, feeds, TAXII collections, triggers, streams, playbooks.

"},{"location":"reference/filters/#create-a-filter","title":"Create a filter","text":"

To create a filter, add every key you need using the 'Add filter' select box. It will give you the possible attributes on which you can filter in the current view.

A grey box appears and allows to select:

  1. the operator to use, and
  2. the values to compare (if the operator is not \"empty\" or \"not_empty\").

You can add as many filters as you want, even use the same key twice with different operators and values.

The boolean modes (and/or) are either global (between every attribute filters) or local (between values inside a filter). Both can be switched with a single click, changing the logic of your filtering.

"},{"location":"reference/filters/#filters-format","title":"Filters format","text":"

Since OpenCTI 5.12, the OpenCTI platform uses a new filter format called FilterGroup. The FilterGroup model enables to do complex filters imbrication with different boolean operators, which extends greatly the filtering capabilities in every part of the platform.

"},{"location":"reference/filters/#structure","title":"Structure","text":"

The new format used internally by OpenCTI and exposed through its API, can be described as below:

// filter formats in OpenCTI >= 5.12\n\ntype FilterGroup = {\n  mode: 'and' | 'or'\n  filters: Filter[]\n  filterGroups: FilterGroup[] // recursive definition\n}\n\ntype Filter  = {\n  key: string[] // or single string (input coercion)\n  values: string[]\n  operator: 'eq' | 'not_eq' | 'gt' // ... and more\n  mode: 'and' | 'or',\n}\n
"},{"location":"reference/filters/#properties","title":"Properties","text":"

In a given filter group, the mode (and or or) represents the boolean operation between the different filters and filterGroups arrays. The filters and filterGroups arrays are composed of objects of type Filter and FilterGroup.

The Filter has 4 properties:

  • a key, representing the kind of data we want to target (example: objectLabel to filter on labels or createdBy to filter on the author),
  • an array of values, representing the values we want to compare to,
  • an operator representing the operation we want to apply between the key and the values,
  • a mode (and or or) to apply between the values if there are several ones.
"},{"location":"reference/filters/#operators","title":"Operators","text":"

The available operators are:

Value Meaning Additional information eq equal not_eq different gt greater than against textual values, the alphabetical ordering is used gte greater than or equal against textual values, the alphabetical ordering is used lt lower than against textual values, the alphabetical ordering is used lte lower than or equal against textual values, the alphabetical ordering is used nil empty / no value nil do not require anything inside values not_nil non-empty / any value not_nil do not require anything inside values

In addition, there are operators:

  • starts_with / not_starts_with / ends_with / not_ends_with / contains / not contains, available for searching in short string fields (name, value, title, etc.),
  • search, available in short string and text fields.

There is a small difference between search and contains. search finds any occurrence of specified words, regardless of order, while \"contains\" specifically looks for the exact sequence of words you provide.

Always use single-key filters

Multi-key filters are not supported across the platform and are reserved to specific, internal cases.

"},{"location":"reference/filters/#examples","title":"Examples","text":"

entity_type = 'Report'

filters = {\n    mode: 'and',\n    filters: [{\n        key: 'entity_type',\n        values: ['Report'],\n        operator: 'eq',\n        mode: 'or', // useless here because values contains only one value\n    }],\n    filterGroups: [],\n};\n

(entity_type = 'Report') AND (label = 'label1' OR 'label2')

filters = {\n    mode: 'and',\n    filters: [\n        {\n            key: 'entity_type',\n            values: ['Report'],\n            operator: 'eq',\n            mode: 'or',\n        },\n        {\n            key: 'objectLabel',\n            values: ['label1', 'label2'],\n            operator: 'eq',\n            mode: 'or',\n        }\n    ],\n    filterGroups: [],\n};\n

(entity_type = 'Report') AND (confidence > 50 OR marking is empty)

filters = {\n    mode: 'and',\n    filters: [\n        {\n            key: 'entity_type',\n            values: ['Report'],\n            operator: 'eq',\n            mode: 'or',\n        }\n    ],\n    filterGroups: [\n        {\n            mode: 'or',\n            filters: [\n                {\n                    key: 'confidence',\n                    values: ['50'],\n                    operator: 'gt',\n                    mode: 'or',\n                },\n                {\n                    key: 'objectMarking',\n                    values: [],\n                    operator: 'nil',\n                    mode: 'or',\n                },\n            ],\n            filterGroups: [],\n        }\n    ],\n};\n
"},{"location":"reference/filters/#keys","title":"Keys","text":""},{"location":"reference/filters/#filter-keys-validation","title":"Filter keys validation","text":"

Only a specific set of key can be used in the filters.

Automatic key checking prevents typing error when constructing filters via the API. If a user write an unhandled key (object-label instead of objectLabel for instance), the API will return an error instead of an empty list. Doing so, we make sure the platform do not provide misleading results.

"},{"location":"reference/filters/#regular-filter-keys","title":"Regular filter keys","text":"

For an extensive list of available filter keys, refer to the attributes and relations schema definitions.

Here are some of the most useful keys as example. NB: X refers here to the filtered entities.

  • objectLabel: label applied on X,
  • objectMarking: marking applied on X,
  • createdBy: author of X,
  • creator_id: technical creator of X,
  • created_at: date of creation of X in the platform,
  • confidence: confidence of X,
  • entity_type: entity type of X ('Report', 'Stix-Cyber-Observable', ...),
"},{"location":"reference/filters/#special-filter-keys","title":"Special filter keys","text":"

Some keys do not exist in the schema definition, but are allowed in addition. They describe a special behavior.

It is the case for:

  • sightedBy: entities to which X is linked via a STIX sighting relationship,
  • workflow_id: status id of the entities, or status template id of the status of the entities,
  • representative: entities whose representative (name for reports, value for some observables, composition of the source and target names for a relationship...) matches the filter,
  • connectedToId: the listened instances for an instance trigger.

For some keys, negative equality filtering is not supported yet (not_eq operator). For instance, it is the case for:

  • fromId
  • fromTypes
  • toId
  • toTypes

The regardingOf filter key has a special format and enables to target the entities having a relationship of a certain type with certain entities. Here is an example of filter to fetch the entities related to the entity X:

filters = {\n  mode: 'and',\n  filters: [\n    {\n      key: 'regardingOf',\n      values: [\n        { key: 'id', values: ['id-of-X'] },\n        { key: 'relationship_type', values: ['related-to'] },\n      ],\n    },\n  ],\n  filterGroups: [],\n};\n
"},{"location":"reference/filters/#limited-support-in-stream-events-filtering","title":"Limited support in stream events filtering","text":"

Filters that are run against the event stream are not using the complete schema definition in terms of filtering keys.

This concerns:

  • Live streams,
  • CSV feeds,
  • TAXII collection,
  • Triggers,
  • Playbooks.

For filters used in this context, only some keys are supported for the moment:

  • confidence
  • objectAssignee
  • createdBy
  • creator
  • x_opencti_detection
  • indicator_types
  • objectLabel
  • x_opencti_main_observable_type
  • objectMarking
  • objects
  • pattern_type
  • priority
  • revoked
  • severity
  • x_opencti_score
  • entity_type
  • x_opencti_workflow_id
  • connectedToId (for the instance triggers)
  • fromId (the instance in the \"from\" of a relationship)
  • fromTypes (the entity type in the \"from\" of a relationship)
  • toId (the instance in the \"to\" of a relationship)
  • toTypes (the entity type in the \"to\" of a relationship)
"},{"location":"reference/fips/","title":"SSL FIPS 140-2 deployment","text":""},{"location":"reference/fips/#introduction","title":"Introduction","text":"

For organizations that need to deploy OpenCTI in a SSL FIPS 140-2 compliant environment, we provide FIPS compliant OpenCTI images for all components of the platform. Please note that you will also need to deploy dependencies (ElasticSearch / OpenSearch, Redis, etc.) with FIPS 140-2 SSL to have the full compliant OpenCTI technological stack.

OpenCTI SSL FIPS 140-2 compliant builds

The OpenCTI platform, workers and connectors SSL FIPS 140-2 compliant images are based on packaged Alpine Linux with OpenSSL 3 and FIPS mode enabled maintened by the Filigran engineering team.

"},{"location":"reference/fips/#dependencies","title":"Dependencies","text":""},{"location":"reference/fips/#aws-native-services-in-fedramp-compliant-environment","title":"AWS Native Services in FedRAMP compliant environment","text":"

It is important to remind that OpenCTI is fully compatible with AWS native services and all dependencies are available in both FedRAMP Moderate (East / West) and FedRAMP High (GovCloud) scopes.

  • Amazon OpenSearch Service (OpenSearch)
  • Amazon ElastiCache (Redis)
  • Amazon MQ (RabbitMQ)
  • Amazon Simple Storage Service (S3 bucket)
"},{"location":"reference/fips/#elasticsearch-opensearch","title":"ElasticSearch / OpenSearch","text":"

ElasticSearch is known to be compatible with FIPS 140-2 SSL using the proper JVM. There is a comprehensive guide in the Elastic documentation.

Alternatively, please note that Elastic is also providing an ElasticSearch FedRAMP authorized cloud offering.

"},{"location":"reference/fips/#redis","title":"Redis","text":"

Redis does not provide FIPS 140-2 SSL compliant Docker images but supports very well custom tls-ciphersuites that can be configured to use the system FIPS 140-2 OpenSSL library.

Alternatively, you can use a Stunnel TLS endpoint to ensure encrypted communication between OpenCTI and Redis. There are a few examples available, here or here.

"},{"location":"reference/fips/#rabbitmq","title":"RabbitMQ","text":"

RabbitMQ does not provide FIPS 140-2 SSL compliant Docker images but, as Redis, supports custom cipher suites. Also, it is confirmed since RabbitMQ version 3.12.5, the associated Erlang build (> 26.1), supports FIPS mode on OpenSSL 3.

Alternatively, you can use a Stunnel TLS endpoint to ensure encrypted communication between OpenCTI and RabbitMQ.

"},{"location":"reference/fips/#s3-bucket-minio","title":"S3 Bucket / MinIO","text":"

If you cannot use an S3 endpoint already deployed in your FIPS 140-2 SSL compliant environment, MinIO provides FIPS 140-2 SSL compliant Docker images which then are very easy to deploy within your environment.

"},{"location":"reference/fips/#opencti-stack","title":"OpenCTI stack","text":""},{"location":"reference/fips/#platform","title":"Platform","text":"

For the platform, we provide FIPS 140-2 SSL compliant Docker images. Just use the appropriate tag to ensure you are deploying the FIPS compliant version and follow the standard Docker deployment procedure.

"},{"location":"reference/fips/#worker","title":"Worker","text":"

For the worker, we provide FIPS 140-2 SSL compliant Docker images. Just use the appropriate tag to ensure you are deploying the FIPS compliant version and follow the standard Docker deployment procedure.

"},{"location":"reference/fips/#connectors","title":"Connectors","text":"

All connectors have FIPS 140-2 SSL compliant Docker images. For each connector you need to deploy, please use the tag {version}-fips instead of {version} and follow the standard deployment procedure. An example is available on Docker Hub.

"},{"location":"reference/streaming/","title":"Data Streaming","text":""},{"location":"reference/streaming/#presentation","title":"Presentation","text":"

In order to provide a real time way to consume STIX CTI information, OpenCTI provides data events in a stream that can be consumed to react on creation, update, deletion and merge. This way of getting information out of OpenCTI is highly efficient and already use by some connectors.

"},{"location":"reference/streaming/#technology","title":"Technology","text":""},{"location":"reference/streaming/#redis-stream","title":"Redis stream","text":"

OpenCTI is currently using REDIS Stream as the technical layer. Each time something is modified in the OpenCTI database, a specific event is added in the stream.

"},{"location":"reference/streaming/#sse-protocol","title":"SSE protocol","text":"

In order to provide a really easy consuming protocol we decide to provide a SSE (https://fr.wikipedia.org/wiki/Server-sent_events) HTTP URL linked to the standard login system of OpenCTI. Any user with the correct access rights can open and access http://opencti_instance/stream, and open an SSE connection to start receiving live events. You can of course consume directly the stream in Redis, but you will have to manage access and rights directly.

"},{"location":"reference/streaming/#events-format","title":"Events format","text":"
id: {Event stream id} -> Like 1620249512318-0\nevent: {Event type} -> create / update / delete\ndata: { -> The complete event data\n    version -> The version number of the event\n    type -> The inner type of the event\n    scope -> The scope of the event [internal or external]\n    data: {STIX data} -> The STIX representation of the data.\n    message -> A simple string to easy understand the event\n    origin: {Data Origin} -> Complex object with different information about the origin of the event\n    context: {Event context} -> Complex object with meta information depending of the event type\n}\n

It can be used to consume the stream from this specific point.

"},{"location":"reference/streaming/#stix-data","title":"STIX data","text":"

The current stix data representation is based on the STIX 2.1 format using extension mechanism. Please take a look to the STIX documentation for more information.

"},{"location":"reference/streaming/#create","title":"Create","text":"

It's simply the data created in STIX format.

"},{"location":"reference/streaming/#delete","title":"Delete","text":"

It's simply the data in STIX format just before his deletion. You will also find the automated deletions in context due to automatic dependency management.

{\n  \"context\": {\n      \"deletions\": [{STIX data}]\n  }\n}\n
"},{"location":"reference/streaming/#update","title":"Update","text":"

This event type publish the complete STIX data information along with patches information. Thanks to the patches, it's possible to rebuild the previous version and easily understand what happens in the update.

Patch and reverse_patch follow the official jsonpatch specification. You can find more information on the jsonpatch page

{\n  \"context\": {\n      \"patch\": [/* patch operation object */],\n      \"reverse_patch\": [/* patch operation object */]\n  }\n}\n
"},{"location":"reference/streaming/#merge","title":"Merge","text":"

Merge is a combination of an update of the merge targets and deletions of the sources. In this event you will find the same patch and reverse_patch as an update and the list of elements merged into the target in the \"sources\" attribute.

{\n  \"context\": {\n      \"patch\": [/* patch operation object */],\n      \"reverse_patch\": [/* patch operation object */],\n      \"sources\": [{STIX data}]\n  }\n}\n
"},{"location":"reference/streaming/#stream-types","title":"Stream types","text":"

In OpenCTI we propose 2 types of streams.

"},{"location":"reference/streaming/#base-stream","title":"Base stream","text":"

The stream hosted in /stream url contains all the raw events of the platform, always filtered by the user rights (marking based). It's a technical stream a bit complex to used but very useful for internal processing or some specific connectors like backup/restore.

This stream is live by default but if, you want to catchup, you can simply add the from parameter to your query. This parameter accept a timestamp in millisecond and also an event id, e.g. http://localhost/stream?from=1620249512599

Stream size?

The raw stream is really important in the platform and needs te be sized according to the period of retention you want to ensure. More retention you will have, more security about reprocessing the past information you will get. We usually recommand 1 month of retention, that usually match 2 000 000 of events. This limit can be configured with redis:trimming option, please check deployment configuration page.

"},{"location":"reference/streaming/#live-stream","title":"Live stream","text":"

This stream aims to simplify your usage of the stream through the connectors, providing a way to create stream with specific filters through the UI. After creating this stream, is simply accessible from /stream/{STREAM_ID}.

It's very useful for various cases of data externalization, synchronization, like SPLUNK, TANIUM...

This stream provides different interesting mechanics:

  • Stream the initial list of instances matching your filters when connecting based on main database if you use the recover parameter
  • Auto dependencies resolution to guarantee the consistency of the information distributed
  • Automatic events translation depending on the element segregation

If you want to dig in about the internal behavior you can check this complete diagram:

"},{"location":"reference/streaming/#general-options","title":"General options","text":"
  • no-dependencies (query parameter or header, default false). Can be used to prevent the auto dependencies resolution. To be used with caution.
  • listen-delete (query parameter or header, default true). Can be used prevent receive deletion events. To be used with caution.
  • with-inferences (query parameter or header, default false). Can be used to add inferences events (from rule engine) in the stream.
"},{"location":"reference/streaming/#from-and-recover","title":"From and Recover","text":"

From and recover are 2 different options that need to be explains.

  • from (query parameter) is always the parameter that describe the initial date/event_id you want to start from. Can also be setup with request header from or last-event-id
  • recover (query parameter) is an option that let you consume the initial event from the database and not from the stream. Can also be setup with request header recover or recover-date

This difference will be transparent for the consumer but very important to get old information as an initial snapshot. This also let you consume information that is no longer in the stream retention period.

The next diagram will help you to understand the concept:

"},{"location":"reference/taxonomy/","title":"Taxonomy","text":"

In OpenCTI, taxonomies serve as structured classification systems that aid in organizing and categorizing intelligence data. This reference guide provides an exhaustive description of the platform's customizable fields within the taxonomies' framework. Users can modify, add, or delete values within the available vocabularies to tailor the classification system to their specific requirements.

For broader documentation on the taxonomies section, please consult the appropriate page.

"},{"location":"reference/taxonomy/#vocabularies","title":"Vocabularies","text":"

Default values are based on those defined in the STIX standard but can be tailored to better suit the organization's needs.

Name Used in Default value Account type vocabulary (account-type-ov) User account facebook, ldap, nis, openid, radius, skype, tacacs, twitter, unix, windows-domain, windows-local Attack motivation vocabulary (attack-motivation-ov) Threat actor group accidental, coercion, dominance, ideology, notoriety, organizational-gain, personal-gain, personal-satisfaction, revenge, unpredictable Attack resource level vocabulary (attack-resource-level-ov) Threat actor group club, contest, government, individual, organization, team Case priority vocabulary (case_priority_ov) Incident response P1, P2, P3, P4 Case severity vocabulary (case_severity_ov) Incident response critical, high, medium, low Channel type vocabulary (channel_type_ov) Channel Facebook, Twitter Collection layers vocabulary (collection_layers_ov) Data source cloud-control-plane, container, host, network, OSINT Event type vocabulary (event_type_ov) Event conference, financial, holiday, international-summit, local-election, national-election, sport-competition Eye color vocabulary (eye_color_ov) Threat actor individual black, blue, brown, green, hazel, other Gender vocabulary (gender_ov) Threat actor individual female, male, nonbinary, other Grouping context vocabulary (grouping_context_ov) Grouping malware-analysis, suspicious-activity, unspecified Hair color vocabulary vocabulary (hair_color_ov) Threat actor individual bald, black, blond, blue, brown, gray, green, other, red Implementation language vocabulary (implementation_language_ov) Malware applescript, bash, c, c++, c#, go, java, javascript, lua, objective-c, perl, php, powershell, python, ruby, scala, swift, typescript, visual-basic, x86-32, x86-64 Incident response type vocabulary (incident_response_type_ov) Incident response data-leak, ransomware Incident severity vocabulary (incident_severity_ov) Incident critical, high, medium, low Incident type vocabulary (incident_type_ov) Incident alert, compromise, cybercrime, data-leak, information-system-disruption, phishing, reputation-damage, typosquatting Indicator type vocabulary (indicator_type_ov) Indicator anomalous-activity, anonymization, attribution, benign, compromised, malicious-activity, unknown Infrastructure type vocabulary (infrastructure_type_ov) Infrastructure amplification, anonymization, botnet, command-and-control, control-system, exfiltration, firewall, hosting-malware, hosting-target-lists, phishing, reconnaissance, routers-switches, staging, unknown, workstation Integrity level vocabulary (integrity_level_ov) Process high, medium, low, system Malware capabilities vocabulary (malware_capabilities_ov) Malware accesses-remote-machines, anti-debugging, anti-disassembly, anti-emulation, anti-memory-forensics, anti-sandbox, anti-vm, captures-input-peripherals, captures-output-peripherals, captures-system-state-data, cleans-traces-of-infection, commits-fraud, communicates-with-c2, compromises-data-availability, compromises-data-integrity, compromises-system-availability, controls-local-machine, degrades-security-software, degrades-system-updates, determines-c2-server, emails-spam, escalates-privileges, evades-av, exfiltrates-data, fingerprints-host, hides-artifacts, hides-executing-code, infects-files, infects-remote-machines, installs-other-components, persists-after-system-reboot, prevents-artifact-access, prevents-artifact-deletion, probes-network-environment, self-modifies, steals-authentication-credentials, violates-system-operational-integrity Malware result vocabulary (malware_result_ov) Malware analysis benign, malicious, suspicious, unknown Malware type vocabulary (malware_type_ov) Malware adware, backdoor, bootkit, bot, ddos, downloader, dropper, exploit-kit, keylogger, ransomware, remote-access-trojan, resource-exploitation, rogue-security-software, rootkit, screen-capture, spyware, trojan, unknown, virus, webshell, wiper, worm Marital status vocabulary (marital_status_ov) Threat actor individual annulled, divorced, domestic_partner, legally_separated, married, never_married, polygamous, separated, single, widowed Note types vocabulary (note_types_ov) Note analysis, assessment, external, feedback, internal Opinion vocabulary (opinion_ov) Opinion agree, disagree, neutral, strongly-agree, strongly-disagree Pattern type vocabulary (pattern_type_ov) Indicator eql, pcre, shodan, sigma, snort, spl, stix, suricata, tanium-signal, yara Permissions vocabulary (permissions_ov) Attack pattern Administrator, root, User Platforms vocabulary (platforms_ov) Data source android, Azure AD, Containers, Control Server, Data Historian, Engineering Workstation, Field Controller/RTU/PLC/IED, Google Workspace, Human-Machine Interface, IaaS, Input/Output Server, iOS, linux, macos, Office 365, PRE, SaaS, Safety Instrumented System/Protection Relay, windows Processor architecture vocabulary (processor_architecture_ov) Malware alpha, arm, ia-64, mips, powerpc, sparc, x86, x86-64 Reliability vocabulary (reliability_ov) Report, Organization A - Completely reliable, B - Usually reliable, C - Fairly reliable, D - Not usually reliable, E - Unreliable, F - Reliability cannot be judged Report types vocabulary (report_types_ov) Report internal-report, threat-report Request for information types vocabulary (request_for_information_types_ov) Request for information none Request for takedown types vocabulary (request_for_takedown_types_ov) Request for takedown brand-abuse, phishing Service status vocabulary (service_status_ov) Process SERVICE_CONTINUE_PENDING, SERVICE_PAUSE_PENDING, SERVICE_PAUSED, SERVICE_RUNNING, SERVICE_START_PENDING, SERVICE_STOP_PENDING, SERVICE_STOPPED Service type vocabulary (service_type_ov) Process SERVICE_FILE_SYSTEM_DRIVER, SERVICE_KERNEL_DRIVER, SERVICE_WIN32_OWN_PROCESS, SERVICE_WIN32_SHARE_PROCESS Start type vocabulary (start_type_ov) Process SERVICE_AUTO_START, SERVICE_BOOT_START, SERVICE_DEMAND_START, SERVICE_DISABLED, SERVICE_SYSTEM_ALERT Threat actor group role vocabulary (threat_actor_group_role_ov) Threat actor group agent, director, independent, infrastructure-architect, infrastructure-operator, malware-author, sponsor Threat actor group sophistication vocabulary (threat_actor_group_sophistication_ov) Threat actor group advanced, expert, innovator, intermediate, minimal, none, strategic Threat actor group type vocabulary (threat_actor_group_type_ov) Threat actor group activist, competitor, crime-syndicate, criminal, hacker, insider-accidental, insider-disgruntled, nation-state, sensationalist, spy, terrorist, unknown Threat actor individual role vocabulary (threat_actor_individual_role_ov) Threat actor individual agent, director, independent, infrastructure-architect, infrastructure-operator, malware-author, sponsor Threat actor individual sophistication vocabulary (threat_actor_individual_sophistication_ov) Threat actor individual advanced, expert, innovator, intermediate, minimal, none, strategic Threat actor individual type vocabulary (threat_actor_individual_type_ov) Threat actor individual activist, competitor, crime-syndicate, criminal, hacker, insider-accidental, insider-disgruntled, nation-state, sensationalist, spy, terrorist, unknown Tool types vocabulary (tool_types_ov) Tool credential-exploitation, denial-of-service, exploitation, information-gathering, network-capture, remote-access, unknown, vulnerability-scanning

"},{"location":"reference/taxonomy/#customization","title":"Customization","text":"

Users can customize the taxonomies by modifying the available values or adding new ones. These modifications enable users to adapt the classification system to their specific intelligence requirements. Additionally, within each vocabulary list, users have the flexibility to customize the order of the dropdown menu associated with the taxonomy. This feature allows users to prioritize certain values or arrange them in a manner that aligns with their specific classification needs. Additionally, users can track the usage count for each vocabulary, providing insights into the frequency of usage and helping to identify the most relevant and impactful classifications. These customization options empower users to tailor the taxonomy system to their unique intelligence requirements, enhancing the efficiency and effectiveness of intelligence analysis within the OpenCTI platform.

"},{"location":"reference/usage-telemetry/","title":"Usage telemetry","text":"

The application collects statistical data related to its usage and performances.

Confidentiality

The OpenCTI platform does not collect any information related to threat intelligence knowledge which remains strictly confidential. Also, the collection is strictly anonymous and personally identifiable information is NOT collected (including IP addresses).

All data collected is anonymized and aggregated to protect the privacy of individual users, in compliance with all privacy regulations.

"},{"location":"reference/usage-telemetry/#purpose-of-the-telemetry","title":"Purpose of the telemetry","text":"

The collected data is used for the following purposes:

  • Improving the functionality and performance of the application.
  • Analyzing user behavior to enhance user experience.
  • Generating aggregated and anonymized statistics for internal and external reporting.
"},{"location":"reference/usage-telemetry/#important-thing-to-know","title":"Important thing to know","text":"

The platform send the metrics to the hostname telemetry.filigran.io using the OTLP protocol (over HTTPS). The format of the data is OpenTelemetry JSON.

The metrics push is done every 6 hours if OpenCTI was able to connect to the hostname when the telemetry manager is started. Metrics are also written in specific logs files in order to be included in support package

"},{"location":"reference/usage-telemetry/#telemetry-metrics","title":"Telemetry metrics","text":"

The application collects statistical data related to its usage. Here are an exhaustive list of the collected metrics:

  • The current platform version
  • The platform unique identifier
  • The platform creation date
  • The number of active users
  • The number of total users
  • The number of nodes in the platform
  • Enterprise Edition status (activated or not)
  • The number of active connectors
"},{"location":"usage/ask-ai/","title":"Ask AI","text":"

Enterprise edition

Ask AI is available under the \"OpenCTI Enterprise Edition\" license.

Please read the dedicated page to have all information

"},{"location":"usage/ask-ai/#prerequisites-for-using-ask-ai","title":"Prerequisites for using Ask AI","text":"

There are several possibilities for Enterprise Edition customers to use OpenCTI AI endpoints:

  • Use the Filigran AI Service leveraging our custom AI model using the token given by the support team.
  • Use OpenAI or MistralAI cloud endpoints using your own tokens.
  • Deploy or use local AI endpoints (Filigran can provide you with the custom model).

Please read the configuration documentation

Beta Feature

Ask AI is a beta feature as we are currently fine-tuning our models. Consider checking important information.

"},{"location":"usage/ask-ai/#how-it-works","title":"How it works","text":"

Even if in the future, we would like to leverage AI to do RAG, for the moment we are mostly using AI to analyze and produce texts or images, based on data directly sent into the prompt.

This means that if you are using Filigran AI endpoint or a local one, your data is never used to re-train or adapt the model and everything relies on a pre-trained and fixed model. When using the Ask AI button in the platform, a prompt is generated with the proper instruction to generate the expected result and use it in the context of the button (in forms, rich text editor etc.).

"},{"location":"usage/ask-ai/#filigran-custom-model","title":"Filigran custom model","text":"

We are hosting a scalable AI endpoint for all SaaS or On-Prem enterprise edition customers, this endpoint is based on MistralAI with a model that will be adapted over time to be more effective when processing threat intelligence related contents.

The model, which is still in beta version, will be adapted in the upcoming months to reach maturity at the end of 2024. It can be shared with on-prem enterprise edition customers under NDA.

"},{"location":"usage/ask-ai/#functionalities-of-ask-ai","title":"Functionalities of Ask AI","text":"

Ask AI is represented by a dedicated icon wherever on of its functionalities is available to use.

"},{"location":"usage/ask-ai/#assistance-for-writing-meaningful-content","title":"Assistance for writing meaningful content","text":"

Ask AI can assist you for writing better textual content, for example better title, name, description and detailed content of Objects.

  • Fix spelling & grammar: try to improve the text from a formulation and grammar perspective.
  • Make it shorter/longer: try to shorten or lengthen the text.
  • Change tone: try to change the tone of the text. You can select if you want the text to be written for Strategic (Management, decision makers), Tactical (for team leaders) or Operational (for technical CTI analysts) audiences.
  • Summarize: try to summarize the text in bullet points.
  • Explain: try to explain the context of the subject's text based on what is available to the LLM.
"},{"location":"usage/ask-ai/#assistance-for-importing-data-from-documents","title":"Assistance for importing data from documents","text":"

Fom the Content tab of a Container (Reports, Groupings and Cases), Ask AI can also assist you for importing data contained in uploaded documents into OpenCTI for further exploitation.

  • Generate report document: Generate a text report based on the knowledge graph (entities and relationships) of this container.
  • Summarize associated files: Generate a summary of the selected files (or all files associated to this container).
  • Try to convert the selected files (or all files associated to this container) in a STIX 2.1 bundle you will then be able to use at your convenience (for example importing it into the platform).

A short video on the FiligranHQ YouTube channel presents tha capabilities of AskAI: https://www.youtube.com/watch?v=lsP3VVsk5ds.

"},{"location":"usage/ask-ai/#improving-generated-elements-of-ask-ai","title":"Improving generated elements of Ask AI","text":"

Be aware that the text quality is highly dependent on the capabilities of the associated LLM.

That is why every generated text by Ask AI is provided in a dedicated panel, allowing you to verify and rectify any error the LLM could have made.

"},{"location":"usage/automation/","title":"Playbooks Automation","text":"

Enterprise edition

Playbooks automation is available under the \"OpenCTI Enterprise Edition\" license. Please read the dedicated page to have all information.

OpenCTI playbooks are flexible automation scenarios which can be fully customized and enabled by platform administrators to enrich, filter and modify the data created or updated in the platform.

Playbook automation is accessible in the user interface under Data > Processing > Automation.

Right needed

You need the \"Manage credentials\" capability to use the Playbooks automation, because you will be able to manipulate data simple users cannot access.

You will then be able to:

  • add labels depending on enrichment results to be used in threat intelligence-driven detection feeds,
  • create reports and cases based on various criteria,
  • trigger enrichments or webhooks in given conditions,
  • modify attributes such as first_seen and last_seen based on other pieces of knowledge,
  • etc.
"},{"location":"usage/automation/#playbook-philosophy","title":"Playbook philosophy","text":"

Consider Playbook as a STIX 2.1 bundle pipeline.

Initiating with a component listening to a data stream, each subsequent component in the playbook processes a received STIX bundle. These components have the ability to modify the bundle and subsequently transmit the altered result to connected components.

In this paradigm, components can send out the STIX 2.1 bundle to multiple components, enabling the development of multiple branches within your playbook.

A well-designed playbook end with a component executing an action based on the processed information. For instance, this may involve writing the STIX 2.1 bundle in a data stream.

Validate ingestion

The STIX bundle processed by the playbook won't be written in the platform without specifying it using the appropriate component, i.e. \"Send for ingestion\".

"},{"location":"usage/automation/#create-a-playbook","title":"Create a Playbook","text":"

It is possible to create as many playbooks as needed which are running independently. You can give a name and description to each playbook.

The first step to define in the playbook is the \u201ctriggering event\u201d, which can be any knowledge event (create, update or delete) with customizable filters. To do so, click on the grey rectangle in the center of the workspace and choose the component to \"listen knowledge events\". Configure it with adequate filters. You can use same filters as in other part of the platform.

Then you have flexible choices for the next steps to:

  • filter the initial knowledge,
  • enrich data using external sources and internal rules,
  • modify entities and relationships by applying patches,
  • write the data, send notifications,
  • etc.

Do not forget to start your Playbook when ready, with the Start option of the burger button placed near the name of your Playbook.

By clicking the burger button of a component, you can replace it by another one.

By clicking on the arrow icon in the bottom right corner of a component, you can develop a new branch at the same level.

By clicking the \"+\" button on a link between components, you can insert a component between the two.

"},{"location":"usage/automation/#components-of-playbooks","title":"Components of playbooks","text":""},{"location":"usage/automation/#log-data-in-standard-output","title":"Log data in standard output","text":"

Will write the received STIX 2.1 bundle in platform logs with configurable log level and then send out the STIX 2.1 bundle unmodified.

"},{"location":"usage/automation/#send-for-ingestion","title":"Send for ingestion","text":"

Will pass the STIX 2.1 bundle to be written in the data stream. This component has no output and should end a branch of your playbook.

"},{"location":"usage/automation/#filter-knowledge","title":"Filter Knowledge","text":"

Will allow you to define filter and apply it to the received STIX 2.1 bundle. The component has 2 output, one for data matching the filter and one for the remainder.

By default, filtering is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all elements in the bundle (elements that might result from enrichment for example).

"},{"location":"usage/automation/#enrich-through-connector","title":"Enrich through connector","text":"

Will send the received STIX 2.1 bundle to the stated enrichment connector and send out the modified bundle. Entities that are passed to this stage must be compatible with the enrichment connector being used, as otherwise the playbook may stop at this stage. The Reduce Knowledge component can be used to filter out incompatible entities from being passed to this stage.

"},{"location":"usage/automation/#manipulate-knowledge","title":"Manipulate knowledge","text":"

Will add, replace or remove compatible attribute of the entities contains in the received STIX 2.1 bundle and send out the modified bundle.

By default, modification is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all elements in the bundle (elements that might result from enrichment for example).

"},{"location":"usage/automation/#container-wrapper","title":"Container wrapper","text":"

Will modify the received STIX 2.1 bundle to include the entities into an container of the type you configured. By default, wrapping is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all elements in the bundle (elements that might result from enrichment for example).

"},{"location":"usage/automation/#share-with-organizations","title":"Share with organizations","text":"

Will share every entity in the received STIX 2.1 bundle with Organizations you configured. Your platform needs to have declared a platform main organization in Settings/Parameters.

"},{"location":"usage/automation/#apply-predefined-rule","title":"Apply predefined rule","text":"

Will apply a complex automation built-in rule. This kind of rule might impact performance. Current rules are:

  • First/Last seen computing extension from report publication date: will populate first seen and last seen date of entities contained in the report based on its publication date,
  • Resolve indicators based on observables (add in bundle): will retrieve all indicators linked to the bundle's observables from the database,
  • Resolve observables an indicator is based on (add in bundle): retrieve all observables linked to the bundle's indicator from the database,
  • Resolve container references (add in bundle): will add to the bundle all the relationships and entities the container contains (if the entity having triggered the playbook is not a container, the output of this component will be empty),
  • Resolve neighbors relations and entities (add in bundle): will add to the bundle all relations of the entity having triggered the playbook, as well as all entities at the end of these relations, i.e. the \"first neighbors\" (if the entity is a container, the output of this component will be empty).
"},{"location":"usage/automation/#send-to-notifier","title":"Send to notifier","text":"

Will generate a Notification each time a STIX 2.1 bundle is received.

"},{"location":"usage/automation/#promote-observable-to-indicator","title":"Promote observable to indicator","text":"

Will generate indicator based on observables contained in the received STIX 2.1 bundle.

By default, it is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all observables in the bundle (e.g. observables that might result from predefined rule).

You can also add all indicators and relationships generated by this component in the entity having triggered the playbook, if this entity is a container.

"},{"location":"usage/automation/#extract-observables-from-indicator","title":"Extract observables from indicator","text":"

Will extract observables based on indicators contained in the received STIX 2.1 bundle.

By default, it is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all indicators in the bundle (e.g. indicators that might result from enrichment.

You can also add all observables and relationships generated by this component in the entity having triggered the playbook, if this entity is a container.

"},{"location":"usage/automation/#reduce-knowledge","title":"Reduce Knowledge","text":"

Will filter out any entities in the current stage that do not match the filter conditions in the stage. If the original triggering entity is a container, such as a report or case, then the container itself cannot be filtered out, and will be passed to subsequent stages.

"},{"location":"usage/automation/#monitor-playbook-activity","title":"Monitor playbook activity","text":"

At the top right of the interface, you can access execution trace of your playbook and consult the raw data after every step of your playbook execution.

"},{"location":"usage/background-tasks/","title":"Background tasks","text":"

Three types of tasks are done in the background:

  • rule tasks,
  • knowledge tasks,
  • user tasks.

Rule tasks can be seen and activated in Settings > Customization > Rules engine. Knowledge and user tasks can be seen and managed in Data > Background Tasks. The scope of each task is indicated.

"},{"location":"usage/background-tasks/#rule-tasks","title":"Rule tasks","text":"

If a rule task is enabled, it leads to the scan of the whole platform data and the creation of entities or relationships in case a configuration corresponds to the tasks rules. The created data are called 'inferred data'. Each time an event occurs in the platform, the rule engine checks if inferred data should be updated/created/deleted.

"},{"location":"usage/background-tasks/#knowledge-tasks","title":"Knowledge tasks","text":"

Knowledge tasks are background tasks updating or deleting entities and correspond to mass operations on these data. To create one, select entities via the checkboxes in an entity list, and choose the action to perform via the toolbar.

"},{"location":"usage/background-tasks/#rights","title":"Rights","text":"
  • To create a knowledge task, the user should have the capability to Update Knowledge (or the capability to delete knowledge if the task action is a deletion).
  • To see a knowledge task in the Background task section, the user should be the creator of the task, or have the KNOWLEDGE capability.
  • To delete a knowledge task from the Background task section, the user should be the creator of the task, or have the KNOWLEDGE_UPDATE capability.
"},{"location":"usage/background-tasks/#user-tasks","title":"User tasks","text":"

User tasks are background tasks updating or deleting notifications. It can be done from the Notification section, by selecting several notifications via the checkboxes, and choosing an action via the toolbar.

"},{"location":"usage/background-tasks/#rights_1","title":"Rights","text":"
  • A user can create a user task on its own notifications only.
  • To see or delete a user task, the user should be the creator of the task or have the SET_ACCESS capability.
"},{"location":"usage/case-management/","title":"Case management","text":""},{"location":"usage/case-management/#why-case-management","title":"Why Case management?","text":"

Compiling CTI data in one place, deduplicate and correlate to transform it into Intelligence is very important. But ultimately, you need to act based on this Intelligence. Some situations will need to be taken care of, like cybersecurity incidents, requests for information or requests for takedown. Some actions will then need to be traced, to be coordinated and oversaw. Some actions will include feedback and content delivery.

OpenCTI includes Cases to allow organizations to manage situations and organize their team's work. Better, by doing Case management in OpenCTI, you handle your cases with all the context and Intelligence you need, at hand.

"},{"location":"usage/case-management/#how-to-manage-your-case-in-opencti","title":"How to manage your Case in OpenCTI?","text":"

Multiple situations can be modelize in OpenCTI as a Case, either an Incident Response, a Request for Takedown or a Request for Information.

All Cases can contain any entities and relationships you need to represent the Intelligence context related to the situation. At the beginning of your case, you may find yourself with only some Observables sighted in a system. At the end, you may have Indicators, Threat Actor, impacted systems, attack patterns. All representing your findings, ready to be presented and exported as graph, pdf report, timeline, etc.

Some Cases may need some collaborative work and specific Tasks to be performed by people that have relevant skillsets. OpenCTI allows you to associate Tasks in your Cases and assign them to users in the platform. As some type of situation may need the same tasks to be done, it is also possible to pre-define lists of tasks to be applied on your case. You can define these lists by accessing the Settings/Taxonomies/Case templates panel. Then you just need to add it from the overview of your desire Case.

Tip: A user can have a custom dashboard showing him all the tasks that have been assigned to him.

As with other objects in OpenCTI, you can also leverage the Notes to add some investigation and analysis related comments, helping you shaping up the content of your case with unstructured data and trace all the work that have been done.

You can also use Opinions to collect how the Case has been handled, helping you to build Lessons Learned.

To trace the evolution of your Case and define specific resolution worflows, you can use the Status (that can be define in Settings/Taxonomies/Status templates).

At the end of your Case, you will certainly want to report on what has been done. OpenCTI allows you to export the content of the Case in a simple but customizable PDF (currently in refactor). But of course, your company has its own documents' templates, right? With OpenCTI, you will be able to include some nice graphics in it. For example, a Matrix view of the attacker attack pattern or even a graph display of how things are connected.

Also, we are currently working a more meaningfull Timeline view that will be possible to export too.

"},{"location":"usage/case-management/#use-case-example-a-suspicious-observable-is-sighted-by-a-defense-system-is-it-important","title":"Use case example: A suspicious observable is sighted by a defense system. Is it important?","text":"
  • Daily, your SIEM and EDR are fed Indicators of Compromise from your OpenCTI instance.
  • Today, your SIEM has sighted the domain name \"bad.com\" matching one of them. Its alert has been transfered to OpenCTI and has created a Sighting relationship between your System \"SIEM permiter A\" and the Observable \"bad.com\".
  • You are alerted immediatly, because you have activated the inference rule creating a corresponding Incident in this situation, and you have created an alert based on new Incident that sends you email notification and Teams message (webhook).
  • In OpenCTI, you can clearly see the link between the alerting System, the sighted Observable and the corresponding Indicator. Better, you can also see all the context of the Indicator. It is linked to a notorious and recent phishing campaign targeting your activity sector. \"bad.com\" is clearly something to investigate ASAP.
  • You quickly select all the context you have found, and add it to a new Incident responsecase. You position the priority to High, regarding the context, and the severity to Low, as you don't know yet if someone really interacted with \"bad.com\".
  • You also assign the case to one of your colleagues, on duty for investigative work. To guide him, you also create a Task in your case for verifying if an actual interaction happened with \"bad.com\".
"},{"location":"usage/containers/","title":"Containers","text":""},{"location":"usage/containers/#stix-standard","title":"STIX standard","text":""},{"location":"usage/containers/#definition","title":"Definition","text":"

In the STIX 2.1 standard, some STIX Domain Objects (SDO) can be considered as \"container of knowledge\", using the object_refs attribute to refer multiple other objects as nested references. In object_refs, it is possible to refer to entities and relationships.

"},{"location":"usage/containers/#example","title":"Example","text":"
{\n   \"type\": \"report\",\n   \"spec_version\": \"2.1\",\n   \"id\": \"report--84e4d88f-44ea-4bcd-bbf3-b2c1c320bcb3\",\n   \"created_by_ref\": \"identity--a463ffb3-1bd9-4d94-b02d-74e4f1658283\",\n   \"created\": \"2015-12-21T19:59:11.000Z\",\n   \"modified\": \"2015-12-21T19:59:11.000Z\",\n   \"name\": \"The Black Vine Cyberespionage Group\",\n   \"description\": \"A simple report with an indicator and campaign\",\n   \"published\": \"2016-01-20T17:00:00.000Z\",\n   \"report_types\": [\"campaign\"],\n   \"object_refs\": [\n      \"indicator--26ffb872-1dd9-446e-b6f5-d58527e5b5d2\",\n      \"campaign--83422c77-904c-4dc1-aff5-5c38f3a2c55c\",\n      \"relationship--f82356ae-fe6c-437c-9c24-6b64314ae68a\"\n   ]\n}\n

In the previous example, we have a nested reference to 3 other objects:

\"object_refs\": [\n   \"indicator--26ffb872-1dd9-446e-b6f5-d58527e5b5d2\",\n   \"campaign--83422c77-904c-4dc1-aff5-5c38f3a2c55c\",\n   \"relationship--f82356ae-fe6c-437c-9c24-6b64314ae68a\"\n]\n
"},{"location":"usage/containers/#implementation","title":"Implementation","text":""},{"location":"usage/containers/#types-of-container","title":"Types of container","text":"

In OpenCTI, containers are displayed differently than other entities, because they contain pieces of knowledge. Here is the list of containers in the platform:

Type of entity STIX standard Description Report Native Reports are collections of threat intelligence focused on one or more topics, such as a description of a threat actor, malware, or attack technique, including context and related details. Grouping Native A Grouping object explicitly asserts that the referenced STIX Objects have a shared context, unlike a STIX Bundle (which explicitly conveys no context). Observed Data Native Observed Data conveys information about cyber security related entities such as files, systems, and networks using the STIX Cyber-observable Objects (SCOs). Note Native A Note is intended to convey informative text to provide further context and/or to provide additional analysis not contained in the STIX Objects. Opinion Native An Opinion is an assessment of the correctness of the information in a STIX Object produced by a different entity. Case Extension A case whether an Incident Response, a Request for Information or a Request for Takedown is used to convey an epic with a set of tasks. Task Extension A task, generally used in the context of a case, is intended to convey information about something that must be done in a limited timeframe."},{"location":"usage/containers/#containers-behavior","title":"Containers behavior","text":"

In the platform, it is always possible to visualize the list of entities and/or observables referenced in a container (Container > Entities or Observables) but also to add / remove entities from the container.

As containers can also contain relationships, which are generally linked to the other entities in the container, it is also possible to visualize the container as a graph (Container > Knowledge)

"},{"location":"usage/containers/#containers-of-an-entity-or-a-relationship","title":"Containers of an entity or a relationship","text":"

On the entity or the relationship side, you can always find all containers where the object is contained using the top menu Analysis:

In all containers list, you can also filter containers based on one or multiple contained object(s):

"},{"location":"usage/dashboards-share/","title":"Share custom dashboards","text":"

OpenCTI provides a simple way to share a visualisation of a custom dashboard to anyone, even for people that are outside of the platform. We call those visualisations: public dashboards.

Public dashboards are a snapshot of a custom dashboard at a specific moment of time. By this way you can share a version of a custom dashboard, then modify your custom dashboard without worrying about the impact on public dashboards you have created.

On the contrary, if you want that your public dashboard is updated with the last version of the associated custom dashboard, you can do it with few clicks by recreating a public dashboard using the same name of the one to update.

To be able to share custom dashboards you need to have the Manage data sharing & ingestion capability.

"},{"location":"usage/dashboards-share/#create-a-public-dashboard","title":"Create a public dashboard","text":"

On the top-right of your custom dashboard page you will find a button that will open a panel to manage the public dashboards associated to this custom dashboard.

In this panel you will find two parts: - At the top you have a form allowing you to create public dashboards, - And below, the list of the public dashboards you have created.

"},{"location":"usage/dashboards-share/#form-to-create-a-new-public-dashboard","title":"Form to create a new public dashboard","text":"

First you need to specify a name for your public dashboard. This name will be displayed on the dashboard page. The name is also used to generate an ID for your public dashboard that will be used in the URL to access the dashboard.

The ID is generated as follow: replace all spaces with symbol - and remove special characters. This ID also needs to be unique in the platform as it is used in the URL to access the dashboard.

Then you can choose if the public dashboard is enabled or not. A disabled dashboard means that you cannot access the public dashboard through the custom URL. But you can still manage it from this panel.

Finally you choose the max level of marking definitions for the data to be displayed in the public dashboard. For example if you choose TLP:AMBER then the data fetched by the widgets inside the public dashboard will be at maximum AMBER, you won't retrieved data with RED marking definition.

Also note that the list of marking definitions you can see is based on your current marking access on the platform and the maximum sharable marking definitions defined in your groups.

Define maximum shareable markings in groups

As a platform administrator, you can define, for each group and for each type of marking definition, Maximum marking definitions shareable to be shared through Public Dashboard, regardless of the definition set by users in their public dashboard.

"},{"location":"usage/dashboards-share/#list-of-the-public-dashboards","title":"List of the public dashboards","text":"

When you have created a public dashboard, it will appear in the list below the form.

In this list each item represents a public dashboard you have created. For each you can see its name, path of the URL, max marking definitions, the date of creation, the status to know if the dashboard is enabled or not and some actions.

The possible actions are: copy the link of the public dashboard, disable or enable the dashboard and delete the dashboard.

To share a public dashboard just copy the link and give the URL to the person you want to share with. The dashboard will be visible even if the person is not connected to OpenCTI.

"},{"location":"usage/dashboards/","title":"Custom dashboards","text":"

OpenCTI provides an adaptable and entirely customizable dashboard functionality. The flexibility of OpenCTI's dashboard ensures a tailored and insightful visualization of data, fostering a comprehensive understanding of the platform's knowledge, relationships, and activities.

"},{"location":"usage/dashboards/#dashboard-overview","title":"Dashboard overview","text":"

You have the flexibility to tailor the arrangement of widgets on your dashboard, optimizing organization and workflow efficiency. Widgets can be intuitively placed to highlight key information. Additionally, you can resize widgets from the bottom right corner based on the importance of the information, enabling adaptation to specific analytical needs. This technical flexibility ensures a fluid, visually optimized user experience.

Moreover, the top banner of the dashboard offers a convenient feature to configure the timeframe for displayed data. This can be accomplished through the selection of a relative time period, such as \"Last 7 days\", or by specifying fixed \"Start\" and \"End\" dates, allowing users to precisely control the temporal scope of the displayed information.

"},{"location":"usage/dashboards/#access-control","title":"Access control","text":"

In OpenCTI, the power to create custom dashboards comes with a flexible access control system, allowing users to tailor visibility and rights according to their collaborative needs.

When a user crafts a personalized dashboard, by default, it remains visible only to the dashboard creator. At this stage, the creator holds administrative access rights. However, they can extend access and rights to others using the \"Manage access\" button, denoted by a locker icon, located at the top right of the dashboard page.

Levels of access:

  • View: Access to view the dashboard.
  • Edit: View + Permission to modify and update the dashboard and its widgets.
  • Manage: Edit + Ability to delete the dashboard and to control user access and rights.

It's crucial to emphasize that at least one user must retain admin access to ensure ongoing management capabilities for the dashboard.

Knowledge access restriction

The platform's data access restrictions also apply to dashboards. The data displayed in the widgets is subject to the user's access rights within the platform. Therefore, an admin user will not see the same results in the widgets as a user with limited access, such as viewing only TLP:CLEAR data (assuming the platform contains data beyond TLP:CLEAR).

"},{"location":"usage/dashboards/#share-dashboard-and-widget-configurations","title":"Share dashboard and widget configurations","text":"

OpenCTI provides functionality for exporting, importing and duplicating dashboard and widget configurations, facilitating the seamless transfer of customized dashboard setups between instances or users.

"},{"location":"usage/dashboards/#export","title":"Export","text":"

Dashboards can be exported from either the custom dashboards list or the dashboard view.

To export a dashboard configuration from the custom dashboards list:

  1. Click on the burger menu button at the end of the dashboard line.
  2. Select Export.

To export a widget, the same mechanism is used, but from the burger menu button in the upper right-hand corner of the widget.

To export a dashboard configuration from the dashboard view:

  1. Navigate to the desired dashboard.
  2. Click on the Export button (file with an arrow pointing to the top right corner) located in the top-right corner of the dashboard.

"},{"location":"usage/dashboards/#configuration-file","title":"Configuration file","text":"

The dashboard configuration will be saved as a JSON file, with the title formatted as [YYYYMMDD]_octi_dashboard_[dashboard title]. The expected configuration file content is as follows:

{\n  \"openCTI_version\": \"5.12.0\",\n  \"type\": \"dashboard\",\n  \"configuration\": {\n    \"name\": \"My dashboard title\",\n    \"manifest\": \"eyJ3aWRn(...)uZmlnIjp7fX0=\"\n  }\n}\n

The widget configuration will be saved as a JSON file, with the title formatted as [YYYYMMDD]_octi_widget_[widget view]. The expected configuration file content is as follows:

{\n  \"openCTI_version\": \"5.12.0\",\n  \"type\": \"widget\",\n  \"configuration\": \"eyJ0eXB(...)iOmZhbHNlfX0=\"\n}\n

Source platform-related filters

When exporting a dashboard or widget configuration, all filters will be exported as is. Filters on objects that do not exist in the receiving platform will need manual deletion after import. Filters to be deleted can be identified by their \"delete\" barred value.

"},{"location":"usage/dashboards/#import","title":"Import","text":"

Dashboards can be imported from the custom dashboards list:

  1. Hover over the Add button (+) in the right bottom corner.
  2. Click on the Import dashboard button (cloud with an upward arrow).
  3. Select your file.

To import a widget, the same mechanism is used, but from a dashboard view.

Configuration compatibility

Only JSON files with the required properties will be accepted, including \"openCTI_version: [5.12.0 and above]\", \"type: [dashboard|widget]\", and a \"configuration\". This applies to both dashboards and widgets configurations.

"},{"location":"usage/dashboards/#duplicate","title":"Duplicate","text":"

Dashboards can be duplicated from either the custom dashboards list or the dashboard view.

To duplicate a dashboard from the custom dashboards list:

  1. Click on the burger menu button at the end of the dashboard line.
  2. Select Duplicate.

To duplicate a widget, the same mechanism is used, but from the burger menu button in the upper right-hand corner of the widget.

To duplicate a dashboard from the dashboard view:

  1. Navigate to the desired dashboard.
  2. Click on the Duplicate the dashboard button (two stacked sheets) located in the top-right corner of the dashboard.

Upon successful duplication, a confirmation message is displayed for a short duration, accompanied by a link for easy access to the new dashboard view. Nevertheless, the new dashboard can still be found in the dashboards list.

Dashboard access

The user importing or duplicating a dashboard becomes the only one with access to it. Then, access can be managed as usual.

"},{"location":"usage/data-model/","title":"Data model","text":""},{"location":"usage/data-model/#introduction","title":"Introduction","text":"

The OpenCTI core design relies on the concept of a knowledge graph, where you have two different kinds of object:

  1. Nodes are used to describe entities, which have some properties or attributes.
  2. Edges are used to describe relationships, which are created between two entity nodes and have some properties or attributes.

Example

An example would be that the entity APT28 has a relationship uses to the malware entity Drovorub.

"},{"location":"usage/data-model/#standard","title":"Standard","text":""},{"location":"usage/data-model/#the-stix-model","title":"The STIX model","text":"

To enable a unified approach in the description of threat intelligence knowledge as well as importing and exporting data, the OpenCTI data model is based on the STIX 2.1 standard. Thus we highly recommend to take a look to the STIX Introductory Walkthrough and to the different kinds of STIX relationships to get a better understanding of how OpenCTI works.

Some more important STIX naming shortcuts are:

  • STIX Domain Objects (SDO): Attack Patterns, Malware, Threat Actors, etc.
  • STIX Cyber Observable (SCO): IP Addresses, domain names, hashes, etc.
  • STIX Relationship Object (SRO): Relationships, Sightings

"},{"location":"usage/data-model/#extensions","title":"Extensions","text":"

In some cases, the model has been extended to be able to:

  • Support more types of SCOs to modelize information systems such as cryptocurrency wallets, user agents, etc.
  • Support more types of SDOs to modelize disinformation and cybercrime such as channels, events, narrative, etc.
  • Support more types of SROs to extend the new SDOs such asamplifies, publishes, etc.
"},{"location":"usage/data-model/#implementation-in-the-platform","title":"Implementation in the platform","text":""},{"location":"usage/data-model/#diagram-of-types","title":"Diagram of types","text":"

You can find below the digram of all types of entities and relationships available in OpenCTI.

"},{"location":"usage/data-model/#attributes-and-properties","title":"Attributes and properties","text":"

To get a comprehensive list of available properties for a given type of entity or relationship, you can use the GraphQL playground schema available in your \"Profile > Playground\". Then you can click on schema. You can for instance search for the keyword IntrusionSet:

"},{"location":"usage/dates/","title":"Meaning of dates","text":"

In OpenCTI, entities can contain various dates, each representing different types of information. The available dates vary depending on the entity types.

"},{"location":"usage/dates/#dates","title":"Dates","text":"

In OpenCTI, dates play a crucial role in understanding the context and history of entities. Here's a breakdown of the different dates you might encounter in the platform:

  • \u201cPlatform creation date\u201d: This date signifies the moment the entity was created within OpenCTI. On the API side, this timestamp corresponds to the created_at field. It reflects the initiation of the entity within the OpenCTI environment.
  • \u201cOriginal creation date\u201d: This date reflects the original creation date of the data on the source's side. It becomes relevant if the source provides this information and if the connector responsible for importing the data takes it into account. In cases where the source date is unavailable or not considered, this date defaults to the import date (i.e. the \u201cPlatform creation date\u201d). On the API side, this timestamp corresponds to the created field.
  • \u201cModification date\u201d: This date captures the most recent modification made to the entity, whether a connector automatically modifies it or a user manually edits the entity. On the API side, this timestamp corresponds to the updated_at field. It serves as a reference point for tracking the latest changes made to the entity.
  • Date not shown on GUI: There is an additional date which is not visible on the entity in the GUI. This date is the modified field on the API. This date reflects the original update date of the data on the source's side. The difference between modified and updated_at is identical to the difference between created and created_at.

Understanding these dates is pivotal for contextualizing the information within OpenCTI, ensuring a comprehensive view of entity history and evolution.

"},{"location":"usage/dates/#date-types","title":"Date types","text":""},{"location":"usage/dates/#technical-dates","title":"Technical dates","text":"

The technical dates refer to the dates directly associated to data management within the platform. The API fields corresponding to technical dates are:

  • created_at: Indicates the date and time when the entity was created in the platform.
  • updated_at: Represents the date and time of the most recent update to the entity in the platform.
"},{"location":"usage/dates/#functional-dates","title":"Functional dates","text":"

The functional dates are the dates functionally significant, often indicating specific events or milestones. The API fields corresponding to functional dates are:

  • created: Denotes the date and time when the entity was created on the source's side.
  • modified: Represents the date and time of the most recent modification to the entity on the source's side.
  • start_time: Indicates the start date and time associated with a relationship.
  • stop_time: Indicates the stop date and time associated with a relationship.
  • first_seen: Represents the initial date and time when the entity/activity was observed.
  • last_seen: Represents the most recent date and time when the entity/activity was observed.
"},{"location":"usage/deduplication/","title":"Deduplication","text":"

One of the core concept of the OpenCTI knowledge graph is all underlying mechanisms implemented to accurately de-duplicate and consolidate (aka. upserting) information about entities and relationships.

"},{"location":"usage/deduplication/#creation-behavior","title":"Creation behavior","text":"

When an object is created in the platform, whether manually by a user or automatically by the connectors / workers chain, the platform checks if something already exist based on some properties of the object. If the object already exists, it will return the existing object and, in some cases, update it as well.

Technically, OpenCTI generates deterministic IDs based on the listed properties below to prevent duplicate (aka \"ID Contributing Properties\"). Also, it is important to note that there is a special link between name and aliases leading to not have entities with overlapping aliases or an alias already used in the name of another entity.

"},{"location":"usage/deduplication/#entities","title":"Entities","text":"Type Attributes Area (name OR x_opencti_alias) AND x_opencti_location_type Attack Pattern (name OR alias) AND optional x_mitre_id Campaign name OR alias Channel name OR alias City (name OR x_opencti_alias) AND x_opencti_location_type Country (name OR x_opencti_alias) AND x_opencti_location_type Course Of Action (name OR alias) AND optional x_mitre_id Data Component name OR alias Data Source name OR alias Event name OR alias Feedback Case name AND created (date) Grouping name AND context Incident name OR alias Incident Response Case name OR alias Indicator pattern OR alias Individual (name OR x_opencti_alias) and identity_class Infrastructure name OR alias Intrusion Set name OR alias Language name OR alias Malware name OR alias Malware Analysis name OR alias Narrative name OR alias Note None Observed Data name OR alias Opinion None Organization (name OR x_opencti_alias) and identity_class Position (name OR x_opencti_alias) AND x_opencti_location_type Region name OR alias Report name AND published (date) RFI Case name AND created (date) RFT Case name AND created (date) Sector (name OR alias) and identity_class Task None Threat Actor name OR alias Tool name OR alias Vulnerability name OR alias

Names and aliases management

The name and aliases of an entity define a set of unique values, so it's not possible to have the name equal to an alias and vice versa.

"},{"location":"usage/deduplication/#relationships","title":"Relationships","text":"

The deduplication process of relationships is based on the following criterias:

  • Type
  • Source
  • Target
  • Start time between -30 days / + 30 days
  • Stop time between -30 days / + 30 days
"},{"location":"usage/deduplication/#observables","title":"Observables","text":"

For STIX Cyber Observables, OpenCTI also generate deterministic IDs based on the STIX specification using the \"ID Contributing Properties\" defined for each type of observable.

"},{"location":"usage/deduplication/#update-behavior","title":"Update behavior","text":"

In cases where an entity already exists in the platform, incoming creations can trigger updates to the existing entity's attributes. This logic has been implemented to converge the knowledge base towards the highest confidence and quality levels for both entities and relationships.

To understand in details how the deduplication mechanism works in context of the maximum confidence level, you can navigate through this diagram (section deduplication):

"},{"location":"usage/delete-restore/","title":"Delete and restore knowledge","text":"

Knowledge can be deleted from OpenCTI either in an overview of an object or using background tasks. When an object is deleted, all its relationships and references to other objects are also deleted.

The deletion event is written to the stream, to trigger automated playbooks or synchronize another platform.

Since OpenCTI 6.1, a record of the deleted objects is kept for a given period of a time, allowing to restore them on demand. This does not impact the stream events or other side effect of the deletion: the object is still deleted.

"},{"location":"usage/delete-restore/#trash","title":"Trash","text":"

A view called \"Trash\" displays all \"delete\" operations, entities and relationships alike.

A delete operation contains not only the entity or relationship that has been deleted, but also all the relationships and references from (to) this main object to (from) other elements in the platform.

You can sort, filter or search this table using the usual UI controls. You are limited to the type of object, their representation (most of the time, the name of the object), the user who deleted the object, the date and time of deletion and the marking of the object.

Note that the delete operations (i.e. the entries in this table view) inherit the marking of the main entity that was deleted, and thus follow the same access restriction as the object that was deleted.

You can individually restore or permanently delete an object from the trash view using the burger menu at the end of the line.

Alternatively, you can use the checkboxes at the start of the line to select a subset of deleted objects, and trigger a background task to restore or permanently delete them by batch.

"},{"location":"usage/delete-restore/#restore","title":"Restore","text":"

Restoring an element creates it again in the platform with the same information it had before its deletion. It also restores all the relationships from or to this object, that have been also deleted during the deletion operation. If the object had attached files (uploaded or exported), they are also restored.

"},{"location":"usage/delete-restore/#permanent-delete","title":"Permanent delete","text":"

From the Trash panel, it is also possible to delete permanently the object, its relationships, and attached files.

"},{"location":"usage/delete-restore/#trash-retention","title":"Trash retention","text":"

Deleted objects are kept in trash during a fixed period of time (7 days by default), then they are permanently deleted by the trash manager.

"},{"location":"usage/delete-restore/#limitations","title":"Limitations","text":"

When it comes to restoring a deleted object from the trash, the current implementation shows several limitations. First and foremost, if an object in the trash has lost a relationship dependency (i.e. the other side of a relationship from or to this object is no longer in live database), you will not be able to restore the object.

In such case, if the missing dependency is in the trash too, you can manually restore this dependency first and then retry.

If the missing dependency has been permanently deleted, the object cannot be recovered.

In other words: * no partial restore: the object and all its relationships must be restored in one pass * no \"cascading\" restore: restoring one object does not restore automatically all linked objects in the trash

"},{"location":"usage/enrichment/","title":"Enrichment connectors","text":"

Enriching the data within the OpenCTI platform is made seamlessly through the integration of enrichment connectors. These connectors facilitate the retrieval of additional data from external sources or portals.

"},{"location":"usage/enrichment/#automatic-enrichment","title":"Automatic enrichment","text":"

Enrichment can be conducted automatically in two distinct modes:

  • Upon data arrival: Configuring the connector to run automatically when data arrives in OpenCTI ensures a real-time enrichment process, supplementing the platform's data. However, it's advisable to avoid automatic enrichment for quota-based connectors to paid sources to prevent quickly depleting all quotas. Additionally, this automatic enrichment contributes to increased data volume. On a large scale, with hundreds of thousands of objects, the disk space occupied by this data can be substantial, and it should be considered, especially if disk space is a concern. The automatic execution is configured at the connector level using the \"auto: true|false\" parameter.
  • Targeted enrichment via playbooks: Enrichment can also be performed in a more targeted manner using playbooks. This approach allows for a customized enrichment strategy, focusing on specific objects and optimizing the relevance of the retrieved data.
"},{"location":"usage/enrichment/#manual-enrichment","title":"Manual enrichment","text":"

Manually initiating the enrichment process is straightforward. Simply locate the button with the cloud icon at the top right of an entity.

Clicking on this icon unveils a side panel displaying a list of available connectors that can be activated for the given object. If no connectors appear in the panel, it indicates that no enrichment connectors are available for the specific type of object in focus.

Activation of an enrichment connector triggers a contact with the designated remote source, importing a set of data into OpenCTI to enrich the selected object. Each enrichment connector operates uniquely, focusing on a specific set of object types it can enrich and a distinct set of data it imports. Depending on the connectors, they may, establish relationships, add external references, or complete object information, thereby contributing to the comprehensiveness of information within the platform.

The list of available connectors can be found in our connectors catalog. In addition, further documentation on connectors is available on the dedicated documentation page.

Impact of the max confidence level

The maximum confidence level per user can have an impact on enrichment connectors, not being able to update data in the platform. To understand the concept and the potential issues you could face, please navigate to this page to understand.

"},{"location":"usage/exploring-analysis/","title":"Analyses","text":"

When you click on \"Analyses\" in the left-side bar, you see all the \"Analyses\" tabs, visible on the top bar on the left. By default, the user directly access the \"Reports\" tab, but can navigate to the other tabs as well.

From the Analyses section, users can access the following tabs:

  • Reports: See Reports as a sort of containers to detail and structure what is contained on a specific report, either from a source or write by yourself. Think of it as an Intelligence Production in OpenCTI.
  • Groupings: Groupings are containers, like Reports, but do not represent an Intelligence Production. They regroup Objects sharing an explicit context. For example, a Grouping might represent a set of data that, in time, given sufficient analysis, would mature to convey an incident or threat report as Report container.
  • Malware Analyses: As define by STIX 2.1 standard, Malware Analyses captures the metadata and results of a particular static or dynamic analysis performed on a malware instance or family.
  • Notes: Through this tab, you can find all the Notes that have been written in the platform, for example to add some analyst's unstructured knowledge about an Object.
  • External references: Intelligence is never created from nothing. External references give user a way to link sources or reference documents to any Object in the platform.

"},{"location":"usage/exploring-analysis/#reports","title":"Reports","text":""},{"location":"usage/exploring-analysis/#general-presentation","title":"General presentation","text":"

Reports are one of the central component of the platform. It is from a Report that knowledge is extracted and integrated in the platform for further navigation, analyses and exports. Always tying the information back to a report allows for the user to be able to identify the source of any piece of information in the platform at all time.

In the MITRE STIX 2.1 documentation, a Report is defined as such :

Reports are collections of threat intelligence focused on one or more topics, such as a description of a threat actor, malware, or attack technique, including context and related details. They are used to group related threat intelligence together so that it can be published as a comprehensive cyber threat story.

As a result, a Report object in OpenCTI is a set of attributes and metadata defining and describing a document outside the platform, which can be a threat intelligence report from a security reseearch team, a blog post, a press article a video, a conference extract, a MISP event, or any type of document and source.

When clicking on the Reports tab at the top left, you see the list of all the Reports you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of reports.

"},{"location":"usage/exploring-analysis/#visualizing-knowledge-within-a-report","title":"Visualizing Knowledge within a Report","text":"

When clicking on a Report, you land on the Overview tab. For a Report, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge contained in the report, accessible through different views (See below for a dive-in). As described here.
  • Content: a tab to provide access to content mapping, suggested mapping and allows to preview, manage and write the deliverables associated with the Report. For example, an analytical report to share with other teams, a markdown file to feed a collaborative wiki, etc. As described here.
  • Entities: A table containing all SDO (Stix Domain Objects) contained in the Report, with search and filters available. It also displays if the SDO has been added directly or through inferences with the reasoning engine
  • Observables: A table containing all SCO (Stix Cyber Observable) contained in the Report, with search and filters available. It also displays if the SCO has been added directly or through inferences with the reasoning engine
  • Data: as described here.

Exploring and modifying the structured Knowledge contained in a Report can be done through different lenses.

"},{"location":"usage/exploring-analysis/#graph-view","title":"Graph View","text":"

In Graph view, STIX SDO are displayed as graph nodes and relationships as graph links. Nodes are colored depending of their type. Direct relationship are displayed as plain link and inferred relationships in dotted link. At the top right, you will find a serie of icons. From there you can change the current type of view. Here you can also perform global action on the Knowledge of the Report. Let's highlight 2 of them: - Suggestions: This tool suggests you some logical relationships to add between your contained Object to give more consistency to your Knowledge. - Share with an Organization: if you have designated a main Organization in the platform settings, you can here share your Report and its content with users of an other Organization. At the bottom, you have many option to manipulate the graph: - Multiple option for shaping the graph and applying forces to the nodes and links - Multiple selection options - Multiple filters, including a time range selector allowing you to see the evolution of the Knowledge within the Report. - Multiple creation and edition tools to modify the Knowledge contained in the Report.

"},{"location":"usage/exploring-analysis/#timeline-view","title":"Timeline view","text":"

This view allows you to see the structured Knowledge chronologically. This view is really useful when the report describes an attack or a campaign that lasted some time, and the analyst payed attention to the dates. The view can be filtered and displayed relationships too.

"},{"location":"usage/exploring-analysis/#correlation-view","title":"Correlation view","text":"

The correlation view is a great way to visualize and find other Reports related to your current subject of interest. This graph displays all Report related to the important nodes contained in your current Report, for example Objects like Malware or Intrusion sets.

"},{"location":"usage/exploring-analysis/#matrix-view","title":"Matrix view","text":"

If your Report describes let's say an attack, a campaign, or an understanding of an Intrusion set, it should contains multiple attack patterns Objects to structure the Knowledge about the TTPs of the Threat Actor. Those attack patterns can be displayed as highlighted matrices, by default the MITRE ATT&CK Enterprise matrix. As some matrices can be huge, it can be also filtered to only display attack patterns describes in the Report.

"},{"location":"usage/exploring-analysis/#groupings","title":"Groupings","text":"

Groupings are an alternative to Report for grouping Objects sharing a context without describing an Intelligence Production.

In the MITRE STIX 2.1 documentation, a Grouping is defined as such :

A Grouping object explicitly asserts that the referenced STIX Objects have a shared context, unlike a STIX Bundle (which explicitly conveys no context). A Grouping object should not be confused with an intelligence product, which should be conveyed via a STIX Report. A STIX Grouping object might represent a set of data that, in time, given sufficient analysis, would mature to convey an incident or threat report as a STIX Report object. For example, a Grouping could be used to characterize an ongoing investigation into a security event or incident. A Grouping object could also be used to assert that the referenced STIX Objects are related to an ongoing analysis process, such as when a threat analyst is collaborating with others in their trust community to examine a series of Campaigns and Indicators.

When clicking on the Groupings tab at the top of the interface, you see the list of all the Groupings you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of the groupings.

Clicking on a Grouping, you land on its Overview tab. For a Groupings, the following tabs are accessible: - Overview: as described here. - Knowledge: a complex tab that regroups all the structured Knowledge contained in the groupings, as for a Report, except for the Timeline view. As described here. - Content: a tab to provide access to content mapping, suggested mapping and allows to preview, manage and write the deliverables associated with the Grouping. For example, an analytical report to share with other teams, a markdown file to feed a collaborative wiki, etc. As described here. - Entities: A table containing all SDO (Stix Domain Objects) contained in the Grouping, with search and filters available. It also display if the SDO has been added directly or through inferences with the reasonging engine - Observables: A table containing all SCO (Stix Cyber Observable) contained in the Grouping, with search and filters available. It also display if the SDO has been added directly or through inferences with the reasonging engine - Data: as described here.

"},{"location":"usage/exploring-analysis/#malware-analyses","title":"Malware Analyses","text":"

Malware analyses are an important part of the Cyber Threat Intelligence, allowing an precise understanding of what and how a malware really do on the host but also how and from where it receives its command and communicates its results.

In OpenCTI, Malware Analyses can be created from enrichment connectors that will take an Observable as input and perform a scan on a online service platform to bring back results. As such, Malware Analyses can be done on File, Domain and URL.

In the MITRE STIX 2.1 documentation, a Malware Analyses is defined as such :

Malware Analyses captures the metadata and results of a particular static or dynamic analysis performed on a malware instance or family.

When clicking on the Malware Analyses tab at the top of the interface, you see the list of all the Malware Analyses you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of the Malware Analyses.

Clicking on a Malware Analyses, you land on its Overview tab. The following tabs are accessible: - Overview: This view contains some additions from the common Overview here. You will find here details about how the analysis have been performed, what is the global result regarding the malicioussness of the analysed artifact and all the Observables that have been found during the analysis. - Knowledge: If you Malware analysis is linked to other Objects that are not part of the analysis result, they will be displayed here. As described here. - Content: This specific tab allows to previzualize, manage and write deliverable associated with the Malware Analyses. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here. - Data: as described here. - History: as described here.

"},{"location":"usage/exploring-analysis/#notes","title":"Notes","text":"

Not every Knowledge can be structured. For allowing any users to share their insights about a specific Knowledge, they can create a Note for every Object and relationship in OpenCTI they can access to. All the Notes are listed within the Analyses menu for allowing global review of this unstructured addition to the global Knowledge.

In the MITRE STIX 2.1 documentation, a Note is defined as such :

A Note is intended to convey informative text to provide further context and/or to provide additional analysis not contained in the STIX Objects, Marking Definition objects, or Language Content objects which the Note relates to. Notes can be created by anyone (not just the original object creator).

Clicking on a Note, you land on its Overview tab. The following tabs are accessible: - Overview: as described here. - Data: as described here. - History: as described here.

"},{"location":"usage/exploring-analysis/#external-references","title":"External references","text":"

Intelligence is never created from nothing. External references give user a way to link sources or reference documents to any Object in the platform. All external references are listed within the Analyses menu for accessing directly sources of the structured Knowledge.

In the MITRE STIX 2.1 documentation, a External references is defined as such :

External references are used to describe pointers to information represented outside of STIX. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.

Clicking on an External reference, you land on its Overview tab. The following tabs are accessible: - Overview: as described here.

"},{"location":"usage/exploring-arsenal/","title":"Arsenal","text":"

When you click on \"Arsenal\" in the left-side bar, you access all the \"Arsenal\" tabs, visible on the top bar on the left. By default, the user directly access the \"Malware\" tab, but can navigate to the other tabs as well.

From the Arsenal section, users can access the following tabs:

  • Malware: Malware represents any piece of code specifically designed to damage, disrupt, or gain unauthorized access to computer systems, networks, or user data.
  • Channels: Channels, in the context of cybersecurity, refer to places or means through which actors disseminate information. This category is used in particular in the context of FIMI (Foreign Information Manipulation Interference).
  • Tools: Tools represent legitimate, installed software or hardware applications on an operating system that can be misused by attackers for malicious purposes. (e.g. LOLBAS).
  • Vulnerabilities: Vulnerabilities are weaknesses or that can be exploited by attackers to compromise the security, integrity, or availability of a computer system or network.
"},{"location":"usage/exploring-arsenal/#malware","title":"Malware","text":""},{"location":"usage/exploring-arsenal/#general-presentation","title":"General presentation","text":"

Malware encompasses a broad category of malicious pieces of code built, deployed, and operated by intrusion set. Malware can take many forms, including viruses, worms, Trojans, ransomware, spyware, and more. These entities are created by individuals or groups, including state-nations, state-sponsored groups, corporations, or hacktivist collectives.

Use the Malware SDO to model and track these threats comprehensively, facilitating in-depth analysis, response, and correlation with other security data.

When clicking on the Malware tab on the top left, you see the list of all the Malware you have access to, in respect with your allowed marking definitions. These malware are displayed as Cards where you can find a summary of the important Knowledge associated with each of them: description, aliases, related intrusion sets, countries and sectors they target, and labels. You can then search and filter on some common and specific attributes of Malware.

At the top right of each Card, you can click the star icon to put it as favorite. It will pin the card on top of the list. You will also be able to display all your favorite easily in your Custom Dashboards.

"},{"location":"usage/exploring-arsenal/#visualizing-knowledge-associated-with-a-malware","title":"Visualizing Knowledge associated with a Malware","text":"

When clicking on an Malware card you land on its Overview tab. For a Malware, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Malware. Different thematic views are proposed to easily see the victimology, the threat actors and intrusion sets using the Malware, etc. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Malware. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-arsenal/#channels","title":"Channels","text":""},{"location":"usage/exploring-arsenal/#general-presentation_1","title":"General presentation","text":"

Channels - such as forums, websites and social media platforms (e.g. Twitter, Telegram) - are mediums for disseminating news, knowledge, and messages to a broad audience. While they offer benefits like open communication and outreach, they can also be leveraged for nefarious purposes, such as spreading misinformation, coordinating cyberattacks, or promoting illegal activities.

Monitoring and managing content within Channels aids in analyzing threats, activities, and indicators associated with various threat actors, campaigns, and intrusion sets.

When clicking on the Channels tab at the top left, you see the list of all the Channels you have access to, in respect with your allowed marking definitions. These channels are displayed in a list where you can find certain fields characterizing the entity: type of channel, labels, and dates. You can then search and filter on some common and specific attributes of Channels.

"},{"location":"usage/exploring-arsenal/#visualizing-knowledge-associated-with-a-channel","title":"Visualizing Knowledge associated with a Channel","text":"

When clicking on a Channel in the list, you land on its Overview tab. For a Channel, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Channel. Different thematic views are proposed to easily see the victimology, the threat actors and intrusion sets using the Malware, etc. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Channel. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-arsenal/#tools","title":"Tools","text":""},{"location":"usage/exploring-arsenal/#general-presentation_2","title":"General presentation","text":"

Tools refers to legitimate, pre-installed software applications, command-line utilities, or scripts that are present on a compromised system. These objects enable you to model and monitor the activities of these tools, which can be misused by attackers.

When clicking on the Tools tab at the top left, you see the list of all the Tools you have access to, in respect with your allowed marking definitions. These tools are displayed in a list where you can find certain fields characterizing the entity: labels and dates. You can then search and filter on some common and specific attributes of Tools.

"},{"location":"usage/exploring-arsenal/#visualizing-knowledge-associated-with-an-observed-data","title":"Visualizing Knowledge associated with an Observed Data","text":"

When clicking on a Tool in the list, you land on its Overview tab. For a Tool, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Tool. Different thematic views are proposed to easily see the threat actors, the intrusion sets and the malware using the Tool. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Tool. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-arsenal/#vulnerabilities","title":"Vulnerabilities","text":""},{"location":"usage/exploring-arsenal/#general-presentation_3","title":"General presentation","text":"

Vulnerabilities represent weaknesses or flaws in software, hardware, configurations, or systems that can be exploited by malicious actors. This object assists in managing and tracking the organization's security posture by identifying areas that require attention and remediation, while also providing insights into associated intrusion sets, malware and campaigns where relevant.

When clicking on the Vulnerabilities tab at the top left, you see the list of all the Vulnerabilities you have access to, in respect with your allowed marking definitions. These vulnerabilities are displayed in a list where you can find certain fields characterizing the entity: CVSS3 severity, labels, dates and creators (in the platform). You can then search and filter on some common and specific attributes of Vulnerabilities.

"},{"location":"usage/exploring-arsenal/#visualizing-knowledge-associated-with-an-observed-data_1","title":"Visualizing Knowledge associated with an Observed Data","text":"

When clicking on a Vulnerabilities in the list, you land on its Overview tab. For a Vulnerability, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Vulnerability. Different thematic views are proposed to easily see the threat actors, the intrusion sets and the malware exploiting the Vulnerability. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Vulnerability. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-cases/","title":"Cases","text":"

When you click on \"Cases\" in the left-side bar, you access all the \"Cases\" tabs, visible on the top bar on the left. By default, the user directly access the \"Incident Responses\" tab, but can navigate to the other tabs as well.

As Analyses, Cases can contain other objects. This way, by adding context and results of your investigations in the case, you will be able to get an up-to-date overview of the ongoing situation, and later produce more easily an incident report.

From the Cases section, users can access the following tabs:

  • Incident Responses: This type of Cases is dedicated to the management of incidents. An Incident Response case does not represent an incident, but all the context and actions that will encompass the response to a specific incident.
  • Request for Information: CTI teams are often asked to provide extensive information and analysis on a specific subject, be it related to an ongoing incident or a particular trending threat. Request for Information cases allow you to store context and actions relative to this type of request and its response.
  • Request for Takedown: When an organization is targeted by an attack campaign, a typical response action can be to request the Takedown of elements of the attack infrastructure, for example a domain name impersonating the organization to phish its employees, or an email address used to deliver phishing content. As Takedown needs in most case to reach out to external providers and be effective quickly, it often needs specific workflows. Request for Takedown cases give you a dedicated space to manage these specific actions.
  • Tasks: In every case, you need tasks to be performed in order to solve it. The Tasks tab allows you to review all created tasks to quickly see past due date, or quickly see every task assigned to a specific user.
  • Feedbacks: If you use your platform to interact with other teams and provide them CTI Knowledge, some users may want to give you feedback about it. Those feedbacks can easily be considered as another type of case to solve, as it will often refer to Knowledge inconsistency or gaps.

"},{"location":"usage/exploring-cases/#incident-response-request-for-information-request-for-takedown","title":"Incident Response, Request for Information & Request for Takedown","text":""},{"location":"usage/exploring-cases/#general-presentation","title":"General presentation","text":"

Incident responses, Request for Information & Request for Takedown cases are an important part of the case management system in OpenCTI. Here, you can organize the work of your team to respond to cybersecurity situations. You can also give context to the team and other users on the platform about the situation and actions (to be) taken.

To manage the situation, you can issue Tasks and assign them to users in the platform, by directly creating a Task or by applying a Case template that will append a list of predefined tasks.

To bring context, you can use your Case as a container (like Reports or Groupings), allowing you to add any Knowledge from your platform in it. You can also use this possibility to trace your investigation, your Case playing the role of an Incident report. You will find more information about case management here.

Incident Response, Request for Information & Request for Takedown are not STIX 2.1 Objects.

When clicking on the Incident Response, Request for Information & Request for Takedown tabs at the top, you see the list of all the Cases you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes.

"},{"location":"usage/exploring-cases/#visualizing-knowledge-within-an-incident-response-request-for-information-request-for-takedown","title":"Visualizing Knowledge within an Incident Response, Request for Information & Request for Takedown","text":"

When clicking on an Incident Response, Request for Information or Request for Takedown, you land on the Overview tab. The following tabs are accessible:

  • Overview: Overview of Cases are slightly different from the usual (described here). Cases' Overview displays also the list of the tasks associated with the case. It also let you highlight Incident, Report or Sighting at the origin of the case. If other cases contains some Observables with your Case, they will be displayed as Related Cases in the Overview.
  • Knowledge: a complex tab that regroups all the structured Knowledge contained in the Case, accessible through different views (See below for a dive-in). As described here.
  • Content: a tab to provide access to content mapping, suggested mapping and allows to preview, manage and write the deliverables associated with the Case. For example, an analytical report to share with other teams, a markdown file to feed a collaborative wiki, etc. As described here.
  • Entities: A table containing all SDO (Stix Domain Objects) contained in the Case, with search and filters available. It also displays if the SDO has been added directly or through inferences with the reasoning engine
  • Observables: A table containing all SCO (Stix Cyber Observable) contained in the Case, with search and filters available. It also displays if the SDO has been added directly or through inferences with the reasoning engine
  • Data: as described here.

Exploring and modifying the structured Knowledge contained in a Case can be done through different lenses.

"},{"location":"usage/exploring-cases/#graph-view","title":"Graph View","text":"

In Graph view, STIX SDO are displayed as graph nodes and relationships as graph links. Nodes are colored depending on their type. Direct relationship are displayed as plain link and inferred relationships in dotted link. At the top right, you will find a series of icons. From there you can change the current type of view. Here you can also perform global action on the Knowledge of the Case. Let's highlight 2 of them:

  • Suggestions: This tool suggests you some logical relationships to add between your contained Object to give more consistency to your Knowledge.
  • Share with an Organization: if you have designated a main Organization in the platform settings, you can here share your Case and its content with users of another Organization. At the bottom, you have many option to manipulate the graph:
  • Multiple option for shaping the graph and applying forces to the nodes and links
  • Multiple selection options
  • Multiple filters, including a time range selector allowing you to see the evolution of the Knowledge within the Case.
  • Multiple creation and edition tools to modify the Knowledge contained in the Case.
"},{"location":"usage/exploring-cases/#timeline-view","title":"Timeline view","text":"

This view allows you to see the structured Knowledge chronologically. This view is particularly useful in the context of a Case, allowing you to see the chain of events, either from the attack perspectives, the defense perspectives or both. The view can be filtered and displayed relationships too.

"},{"location":"usage/exploring-cases/#matrix-view","title":"Matrix view","text":"

If your Case contains attack patterns, you will be able to visualize them in a Matrix view.

"},{"location":"usage/exploring-cases/#tasks","title":"Tasks","text":"

Tasks are actions to be performed in the context of a Case (Incident Response, Request for Information, Request for Takedown). Usually, a task is assigned to a user, but important tasks may involve more participants.

When clicking on the Tasks tab at the top of the interface, you see the list of all the Tasks you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of the tasks.

Clicking on a Task, you land on its Overview tab. For a Tasks, the following tabs are accessible:

  • Overview: as described here.
  • Content: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-cases/#feedbacks","title":"Feedbacks","text":"

When a user fill a feedback form from its Profile/Feedback menu, it will then be accessible here.

This feature gives the opportunity to engage with other users of your platform and to respond directly to their concern about it or the Knowledge, without the need of third party software.

Clicking on a Feedback, you land on its Overview tab. For a Feedback, the following tabs are accessible:

  • Overview: as described here.
  • Content: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-entities/","title":"Entities","text":"

OpenCTI's Entities objects provides a comprehensive framework for modeling various targets and attack victims within your threat intelligence data. With five distinct Entity object types, you can represent sectors, events, organizations, systems, and individuals. This robust classification empowers you to contextualize threats effectively, enhancing the depth and precision of your analysis.

When you click on \"Entities\" in the left-side bar, you access all the \"Entities\" tabs, visible on the top bar on the left. By default, the user directly access the \"Sectors\" tab, but can navigate to the other tabs as well.

From the Entities section, users can access the following tabs:

  • Sectors: areas of activity.
  • Events: event in the real world.
  • Organizations: groups with specific aims such as companies and government entities.
  • Systems: technologies such as platforms and software.
  • Individuals: real persons.
"},{"location":"usage/exploring-entities/#sectors","title":"Sectors","text":""},{"location":"usage/exploring-entities/#general-presentation","title":"General presentation","text":"

Sectors represent specific domains of activity, defining areas such as energy, government, health, finance, and more. Utilize sectors to categorize targeted industries or sectors of interest, providing valuable context for threat intelligence analysis within distinct areas of the economy.

When clicking on the Sectors tab at the top left, you see the list of all the Sectors you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-entities/#visualizing-knowledge-associated-with-a-sector","title":"Visualizing Knowledge associated with a Sector","text":"

When clicking on a Sector in the list, you land on its Overview tab. For a Sector, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Sector. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Sector. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Sector. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in the Sector.
  • Data: as described here.
  • History: as described here.

"},{"location":"usage/exploring-entities/#events","title":"Events","text":""},{"location":"usage/exploring-entities/#general-presentation_1","title":"General presentation","text":"

Events encompass occurrences like international sports events, summits (e.g., G20), trials, conferences, or any significant happening in the real world. By modeling events, you can analyze threats associated with specific occurrences, allowing for targeted investigations surrounding high-profile incidents.

When clicking on the Events tab at the top left, you see the list of all the Events you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-entities/#visualizing-knowledge-associated-with-an-event","title":"Visualizing Knowledge associated with an Event","text":"

When clicking on an Event in the list, you land on its Overview tab. For an Event, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Event. Different thematic views are proposed to easily see the related entities, the threats, the locations, etc. linked to the Event. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Event. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted during an attack against the Event.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-entities/#organizations","title":"Organizations","text":""},{"location":"usage/exploring-entities/#general-presentation_2","title":"General presentation","text":"

Organizations include diverse entities such as companies, government bodies, associations, non-profits, and other groups with specific aims. Modeling organizations enables you to understand the threat landscape concerning various entities, facilitating investigations into cyber-espionage, data breaches, or other malicious activities targeting specific groups.

When clicking on the Organizations tab at the top left, you see the list of all the Organizations you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-entities/#visualizing-knowledge-associated-with-an-organization","title":"Visualizing Knowledge associated with an Organization","text":"

When clicking on an Organization in the list, you land on its Overview tab. For an Organization, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Organization. Different thematic views are proposed to easily see the related entities, the threats, the locations, etc. linked to the Organization. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Organization. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in the Organization.
  • Data: as described here.
  • History: as described here.

Furthermore, an Organization can be observed from an \"Author\" perspective. It is possible to change this viewpoint to the right of the entity name, using the \"Display as\" drop-down menu (see screenshot below). This different perspective is accessible in the Overview, Knowledge and Analyses tabs. When switched to \"Author\" mode, the observed data pertains to the entity's description as an author within the platform:

  • Overview: The \"Latest created relationships\" and \"Latest containers about the object\" panels are replaced by the \"Latest containers authored by this entity\" panel.
  • Knowledge: A tab that presents an overview of the data authored by the Organization (i.e. counters and a graph).
  • Analyses: The list of all Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) for which the Organization is the author.

"},{"location":"usage/exploring-entities/#systems","title":"Systems","text":""},{"location":"usage/exploring-entities/#general-presentation_3","title":"General presentation","text":"

Systems represent software applications, platforms, frameworks, or specific tools like WordPress, VirtualBox, Firefox, Python, etc. Modeling systems allows you to focus on threats related to specific software or technology, aiding in vulnerability assessments, patch management, and securing critical applications.

When clicking on the Systems tab at the top left, you see the list of all the Systems you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-entities/#visualizing-knowledge-associated-with-a-system","title":"Visualizing Knowledge associated with a System","text":"

When clicking on a System in the list, you land on its Overview tab. For a System, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the System. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the System. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the System. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in the System.
  • Data: as described here.
  • History: as described here.

Furthermore, a System can be observed from an \"Author\" perspective. It is possible to change this viewpoint to the right of the entity name, using the \"Display as\" drop-down menu (see screenshot below). This different perspective is accessible in the Overview, Knowledge and Analyses tabs. When switched to \"Author\" mode, the observed data pertains to the entity's description as an author within the platform:

  • Overview: The \"Latest created relationships\" and \"Latest containers about the object\" panels are replaced by the \"Latest containers authored by this entity\" panel.
  • Knowledge: A tab that presents an overview of the data authored by the System (i.e. counters and a graph).
  • Analyses: The list of all Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) for which the System is the author.
"},{"location":"usage/exploring-entities/#individuals","title":"Individuals","text":""},{"location":"usage/exploring-entities/#general-presentation_4","title":"General presentation","text":"

Individuals represent specific persons relevant to your threat intelligence analysis. This category includes targeted individuals, or influential figures in various fields. Modeling individuals enables you to analyze threats related to specific people, enhancing investigations into cyber-stalking, impersonation, or other targeted attacks.

When clicking on the Individuals tab at the top left, you see the list of all the Individuals you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-entities/#visualizing-knowledge-associated-with-an-individual","title":"Visualizing Knowledge associated with an Individual","text":"

When clicking on an Individual in the list, you land on its Overview tab. For an Individual, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Individual. Different thematic views are proposed to easily see the related entities, the threats, the locations, etc. linked to the Individual. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Individual. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in the Individual.
  • Data: as described here.
  • History: as described here.

Furthermore, an Individual can be observed from an \"Author\" perspective. It is possible to change this viewpoint to the right of the entity name, using the \"Display as\" drop-down menu (see screenshot below). This different perspective is accessible in the Overview, Knowledge and Analyses tabs. When switched to \"Author\" mode, the observed data pertains to the entity's description as an author within the platform:

  • Overview: The \"Latest created relationships\" and \"Latest containers about the object\" panels are replaced by the \"Latest containers authored by this entity\" panel.
  • Knowledge: A tab that presents an overview of the data authored by the Individual (i.e. counters and a graph).
  • Analyses: The list of all Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) for which the Individual is the author.
"},{"location":"usage/exploring-events/","title":"Events","text":"

When you click on \"Events\" in the left-side bar, you access all the \"Events\" tabs, visible on the top bar on the left. By default, the user directly access the \"Incidents\" tab, but can navigate to the other tabs as well.

From the Events section, users can access the following tabs:

  • Incidents: In OpenCTI, Incidents correspond to a negative event happening on an information system. This can include a cyberattack (intrusion, phishing, etc.), a consolidated security alert generated by a SIEM or EDR that need to be qualified, and so on. It can also refer to an information warfare attack in the context of countering disinformation.
  • Sightings: Sightings correspond to the event in which an Observable (IP, domain name, certificate, etc.) is detected by or within an information system, an individual or an organization. Most often, this corresponds to a security event transmitted by a SIEM or an EDR.
  • Observed Data: Observed Data has been added in OpenCTI by compliance with the STIX 2.1 standard. You can see it has a pseudo-container that contains Observables, like a line of firewall log for example. Currently, it is rarely used.
"},{"location":"usage/exploring-events/#incidents","title":"Incidents","text":""},{"location":"usage/exploring-events/#general-presentation","title":"General presentation","text":"

Incidents usually represents negative events impacting resources you want to protect, but local definitions can vary a lot, from a simple security events send by a SIEM to a massive scale supply chain attack impacting a whole activity sector.

In the MITRE STIX 2.1, the Incident SDO has not yet been finalized and is the object of important work as part of a forthcoming STIX Extension.

When clicking on the Incidents tab at the top left, you see the list of all the Incidents you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-events/#visualizing-knowledge-associated-with-an-incident","title":"Visualizing Knowledge associated with an Incident","text":"

When clicking on an Incident in the list, you land on its Overview tab. For an Incident, the following tabs are accessible:

  • Overview: as described here, with the particularity to display two distribution graphs of its related Entities (STIX SDO) and Observable (STIX SCO).
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Incident. Different thematic views are proposed to easily see the victimology, arsenal, techniques and so on used in the context of the Incident. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Incident. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.

"},{"location":"usage/exploring-events/#sightings","title":"Sightings","text":""},{"location":"usage/exploring-events/#general-presentation_1","title":"General presentation","text":"

The Sightings correspond to events in which an Observable (IP, domain name, url, etc.) is detected by or within an information system, an individual or an organization. Most often, this corresponds to a security event transmitted by a SIEM or EDR.

In OpenCTI, as we are in a cybersecurity context, Sightings are associated with Indicators of Compromise (IoC) and the notion of \"True positive\" and \"False positive\".

It is important to note that Sightings are a type of relationship (not a STIX SDO or STIX SCO), between an Observable and an Entities or Locations.

When clicking on the Sightings tab at the top left, you see the list of all the Sightings you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-events/#visualizing-knowledge-associated-with-a-sighting","title":"Visualizing Knowledge associated with a Sighting","text":"

When clicking on a Sighting in the list, you land on its Overview tab. As other relationships in the platform, Sighting's overview displays common related metadata, containers, external references, notes and entities linked by the relationship.

In addition, this overview displays: - Qualification : if the Sighting is a True Positive or a False Positive - Count : number of times the event has been seen

"},{"location":"usage/exploring-events/#observed-data","title":"Observed Data","text":""},{"location":"usage/exploring-events/#general-presentation_2","title":"General presentation","text":"

Observed Data correspond to an extract from a log that contains Observables.

In the MITRE STIX 2.1, the Observed Data SDO is defined as such:

Observed Data conveys information about cybersecurity related entities such as files, systems, and networks using the STIX Cyber-observable Objects (SCOs). For example, Observed Data can capture information about an IP address, a network connection, a file, or a registry key. Observed Data is not an intelligence assertion, it is simply the raw information without any context for what it means.

When clicking on the Observed Data tab at the top left, you see the list of all the Observed Data you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-events/#visualizing-knowledge-associated-with-an-observed-data","title":"Visualizing Knowledge associated with an Observed Data","text":"

When clicking on an Observed Data in the list, you land on its Overview tab. The following tabs are accessible:

  • Overview: as described here, with the particularity to display a distribution graphs of its related Observables (STIX SCO).
  • Entities : a sortable and filterable list of all Entities (SDO)
  • Observables: a sortable and filterable list of all Observables (SCO) in relation with the Observed Data
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-locations/","title":"Location","text":"

OpenCTI's Locations objects provides a comprehensive framework for representing various geographic entities within your threat intelligence data. With five distinct Location object types, you can precisely define regions, countries, areas, cities, and specific positions. This robust classification empowers you to contextualize threats geographically, enhancing the depth and accuracy of your analysis.

When you click on \"Locations\" in the left-side bar, you access all the \"Locations\" tabs, visible on the top bar on the left. By default, the user directly access the \"Regions\" tab, but can navigate to the other tabs as well.

From the Locations section, users can access the following tabs:

  • Regions: very large geographical territories, such as a continent.
  • Countries: the world's countries.
  • Areas: more or less extensive geographical areas and often not having a very defined limit
  • Cities: the world's cities.
  • Positions: very precise positions on the globe.
"},{"location":"usage/exploring-locations/#regions","title":"Regions","text":""},{"location":"usage/exploring-locations/#general-presentation","title":"General presentation","text":"

Regions encapsulate broader geographical territories, often representing continents or significant parts of continents. Examples include EMEA (Europe, Middle East, and Africa), Asia, Western Europe, and North America. Utilize regions to categorize large geopolitical areas and gain macro-level insights into threat patterns.

When clicking on the Regions tab at the top left, you see the list of all the Regions you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-locations/#visualizing-knowledge-associated-with-a-region","title":"Visualizing Knowledge associated with a Region","text":"

When clicking on a Region in the list, you land on its Overview tab. For a Region, the following tabs are accessible:

  • Overview: as described here, with the particularity of not having a Details section but a map locating the Region.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Region. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Region. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Location. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in a Region.
  • Data: as described here.
  • History: as described here.

"},{"location":"usage/exploring-locations/#countries","title":"Countries","text":""},{"location":"usage/exploring-locations/#general-presentation_1","title":"General presentation","text":"

Countries represent individual nations across the world. With this object type, you can specify detailed information about a particular country, enabling precise localization of threat intelligence data. Countries are fundamental entities in geopolitical analysis, offering a focused view of activities within national borders.

When clicking on the Countries tab at the top left, you see the list of all the Countries you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-locations/#visualizing-knowledge-associated-with-a-country","title":"Visualizing Knowledge associated with a Country","text":"

When clicking on a Country in the list, you land on its Overview tab. For a Country, the following tabs are accessible:

  • Overview: as described here, with the particularity of not having a Details section but a map locating the Country.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Country. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Country. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Country. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in a Country.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-locations/#areas","title":"Areas","text":""},{"location":"usage/exploring-locations/#general-presentation_2","title":"General presentation","text":"

Areas define specific geographical regions of interest, such as the Persian Gulf, the Balkans, or the Caucasus. Use areas to identify unique zones with distinct geopolitical, cultural, or strategic significance. This object type facilitates nuanced analysis of threats within defined geographic contexts.

When clicking on the Areas tab at the top left, you see the list of all the Areas you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-locations/#visualizing-knowledge-associated-with-an-area","title":"Visualizing Knowledge associated with an Area","text":"

When clicking on an Area in the list, you land on its Overview tab. For an Area, the following tabs are accessible:

  • Overview: as described here, with the particularity of not having a Details section but a map locating the Area.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Area. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Area. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Area. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in an Area.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-locations/#cities","title":"Cities","text":""},{"location":"usage/exploring-locations/#general-presentation_3","title":"General presentation","text":"

Cities provide granular information about urban centers worldwide. From major metropolises to smaller towns, cities are crucial in understanding localized threat activities. With this object type, you can pinpoint threats at the urban level, aiding in tactical threat assessments and response planning.

When clicking on the Cities tab at the top left, you see the list of all the Cities you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-locations/#visualizing-knowledge-associated-with-a-city","title":"Visualizing Knowledge associated with a City","text":"

When clicking on a City in the list, you land on its Overview tab. For a City, the following tabs are accessible:

  • Overview: as described here, with the particularity of not having a Details section but a map locating the City.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the City. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the City. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the City. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in a City.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-locations/#positions","title":"Positions","text":""},{"location":"usage/exploring-locations/#general-presentation_4","title":"General presentation","text":"

Positions represent highly precise geographical points, such as monuments, buildings, or specific event locations. This object type allows you to define exact coordinates, enabling accurate mapping of events or incidents. Positions enhance the granularity of your threat intelligence data, facilitating precise geospatial analysis.

When clicking on the Positions tab at the top left, you see the list of all the Positions you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-locations/#visualizing-knowledge-associated-with-a-position","title":"Visualizing Knowledge associated with a Position","text":"

When clicking on a Position in the list, you land on its Overview tab. For a Position, the following tabs are accessible:

  • Overview: as described here, with the particularity to display a map locating the Position.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Position. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Position. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Position. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted at a Position.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-observations/","title":"Observations","text":"

When you click on \"Observations\" in the left-side bar, you access all the \"Observations\" tabs, visible on the top bar on the left. By default, the user directly access the \"Observables\" tab, but can navigate to the other tabs as well.

From the Observations section, users can access the following tabs:

  • Observables: An Observable represents an immutable object. Observables can encompass a wide range of entities such as IPv4 addresses, domain names, email addresses, and more.
  • Artefacts: In OpenCTI, the Artefacts is a particular Observable. It may contain a file, such as a malware sample.
  • Indicators: An Indicator is a detection object. It is defined by a search pattern, which could be expressed in various formats such as STIX, Sigma, YARA, among others.
  • Infrastructures: An Infrastructure describes any systems, software services and any associated physical or virtual resources intended to support some purpose (e.g. C2 servers used as part of an attack, devices or servers that are part of defense, database servers targeted by an attack, etc.).
"},{"location":"usage/exploring-observations/#observables","title":"Observables","text":""},{"location":"usage/exploring-observations/#general-presentation","title":"General presentation","text":"

An Observable is a distinct entity from the Indicator within OpenCTI and represents an immutable object. Observables can encompass a wide range of entities such as IPv4 addresses, domain names, email addresses, and more. Importantly, Observables don't inherently imply malicious intent, they can include items like legitimate IP addresses or domains associated with an organization. Additionally, they serve as raw data points without the additional detection context found in Indicators.

When clicking on the Observables tab at the top left, you see the list of all the Observables you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-observations/#visualizing-knowledge-associated-with-an-observable","title":"Visualizing Knowledge associated with an Observable","text":"

When clicking on an Observable in the list, you land on its Overview tab. For an Observable, the following tabs are accessible:

  • Overview: as described here, with the particularity to display Indicators composed with the Observable.
  • Knowledge: a tab listing all its relationships and nested objects.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Observation. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which the Observable (IP, domain name, url, etc.) has been sighted.
  • Data: as described here.
  • History: as described here.

"},{"location":"usage/exploring-observations/#artefacts","title":"Artefacts","text":""},{"location":"usage/exploring-observations/#general-presentation_1","title":"General presentation","text":"

An Artefact is a particular Observable. It may contain a file, such as a malware sample. Files can be uploaded or downloaded in encrypted archives, providing an additional layer of security against potential manipulation of malicious payloads.

When clicking on the Artefacts tab at the top left, you see the list of all the Artefacts you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-observations/#visualizing-knowledge-associated-with-an-artefact","title":"Visualizing Knowledge associated with an Artefact","text":"

When clicking on an Artefact in the list, you land on its Overview tab. For an Artefact, the following tabs are accessible:

  • Overview: as described here, with the particularity to be able to download the attached file.
  • Knowledge: a tab listing all its relationships and nested objects.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Artefact. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which the Artefact has been sighted.
  • Data: as described here.
  • History: as described here.

"},{"location":"usage/exploring-observations/#indicators","title":"Indicators","text":""},{"location":"usage/exploring-observations/#general-presentation_2","title":"General presentation","text":"

An Indicator is a detection object. It is defined by a search pattern, which could be expressed in various formats such as STIX, Sigma, YARA, among others. This pattern serves as a key to identify potential threats within the data. Furthermore, an Indicator includes additional information that enriches its detection context. This information encompasses:

  • Validity dates: Indicators are accompanied by a time frame, specifying the duration of their relevance, and modeled by the Valid from and Valid until dates.
  • Actionable fields: Linked to the validity dates, the Revoked and Detection fields can be used to sort Indicators for detection purposes.
  • Kill chain phase: They indicate the phase within the cyber kill chain where they are applicable, offering insights into the progression of a potential threat.
  • Types: Indicators are categorized based on their nature, aiding in classification and analysis.

When clicking on the Indicators tab at the top left, you see the list of all the Indicators you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-observations/#visualizing-knowledge-associated-with-an-indicator","title":"Visualizing Knowledge associated with an Indicator","text":"

When clicking on an Indicator in the list, you land on its Overview tab. For an Indicator, the following tabs are accessible:

  • Overview: as described here, with the particularity to display the Observables on which it is based.
  • Knowledge: a tab listing all its relationships.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Indicator. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Sightings: a table containing all Sightings relationships corresponding to events in which the Indicator has been sighted.
  • Data: as described here.
  • History: as described here.

"},{"location":"usage/exploring-observations/#infrastructures","title":"Infrastructures","text":""},{"location":"usage/exploring-observations/#general-presentation_3","title":"General presentation","text":"

An Infrastructure refers to a set of resources, tools, systems, or services employed by a threat to conduct their activities. It represents the underlying framework or support system that facilitates malicious operations, such as the command and control (C2) servers in an attack. Notably, like Observables, an Infrastructure doesn't inherently imply malicious intent. It can also represent legitimate resources affiliated with an organization (e.g. devices or servers that are part of defense, database servers targeted by an attack, etc.).

When clicking on the Infrastructures tab at the top left, you see the list of all the Infrastructures you have access to, in respect with your allowed marking definitions.

"},{"location":"usage/exploring-observations/#visualizing-knowledge-associated-with-an-infrastructure","title":"Visualizing Knowledge associated with an Infrastructure","text":"

When clicking on an Infrastructure in the list, you land on its Overview tab. For an Infrastructure, the following tabs are accessible:

  • Overview: as described here, with the particularity to display distribution graphs of its related Observable (STIX SCO).
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Infrastructure. Different thematic views are proposed to easily see the threats, the arsenal, the observations, etc. linked to the Infrastructure. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Infrastructure. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-techniques/","title":"Techniques","text":"

When you click on \"Techniques\" in the left-side bar, you access all the \"Techniques\" tabs, visible on the top bar on the left. By default, the user directly access the \"Attack pattern\" tab, but can navigate to the other tabs as well.

From the Techniques section, users can access the following tabs:

  • Attack pattern: attacks pattern used by the threat actors to perform their attacks. By default, OpenCTI is provisionned with attack patterns from MITRE ATT&CK matrices (for CTI) and DISARM matrix (for FIMI).
  • Narratives: In OpenCTI, narratives used by threat actors can be represented and linked to other Objects. Narratives are mainly used in the context of disinformation campaigns where it is important to trace which narratives have been and are still used by threat actors.
  • Courses of action: A Course of Action is an action taken either to prevent an attack or to respond to an attack that is in progress. It may describe technical, automatable responses (applying patches, reconfiguring firewalls) but can also describe higher level actions like employee training or policy changes. For example, a course of action to mitigate a vulnerability could describe applying the patch that fixes it.
  • Data sources: Data sources represent the various subjects/topics of information that can be collected by sensors/logs. Data sources also include data components,
  • Data components: Data components identify specific properties/values of a data source relevant to detecting a given ATT&CK technique or sub-technique.
"},{"location":"usage/exploring-techniques/#attack-pattern","title":"Attack pattern","text":""},{"location":"usage/exploring-techniques/#general-presentation","title":"General presentation","text":"

Attacks pattern used by the threat actors to perform their attacks. By default, OpenCTI is provisionned with attack patterns from MITRE ATT&CK matrices and CAPEC (for CTI) and DISARM matrix (for FIMI).

In the MITRE STIX 2.1 documentation, an Attack pattern is defined as such :

Attack Patterns are a type of TTP that describe ways that adversaries attempt to compromise targets. Attack Patterns are used to help categorize attacks, generalize specific attacks to the patterns that they follow, and provide detailed information about how attacks are performed. An example of an attack pattern is \"spear phishing\": a common type of attack where an attacker sends a carefully crafted e-mail message to a party with the intent of getting them to click a link or open an attachment to deliver malware. Attack Patterns can also be more specific; spear phishing as practiced by a particular threat actor (e.g., they might generally say that the target won a contest) can also be an Attack Pattern.

When clicking on the Attack pattern tab at the top left, you access the list of all the attack pattern you have access too, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of attack patterns.

"},{"location":"usage/exploring-techniques/#visualizing-knowledge-associated-with-an-attack-pattern","title":"Visualizing Knowledge associated with an Attack pattern","text":"

When clicking on an Attack pattern, you land on its Overview tab. For an Attack pattern, the following tabs are accessible:

  • Overview: Overview of Attack pattern is a bit different as the usual described here. The \"Details\" box is more structured and contains information about:

  • parent or subtechniques (as in the MITRE ATT&CK matrices),

  • related kill chain phases
  • Platform on which the Attack pattern is usable,
  • permission required to apply it
  • Related detection technique
  • Courses of action to mitigate the Attack pattern
  • Data components in which find data to detect the usage of the Attack pattern
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Attack pattern. Different thematic views are proposed to easily see Threat Actors and Intrusion Sets using this techniques, linked incidents, etc.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Attack pattern. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-techniques/#narratives","title":"Narratives","text":""},{"location":"usage/exploring-techniques/#general-presentation_1","title":"General presentation","text":"

In OpenCTI, narratives used by threat actors can be represented and linked to other Objects. Narratives are mainly used in the context of disinformation campaigns where it is important to trace which narratives have been and are still used by threat actors.

An example of Narrative can be \"The country A is weak and corrupted\" or \"The ongoing operation aims to free people\".

Narrative can be a mean in the context of a more broad attack or the goal of the operation, a vision to impose.

When clicking on the Narrative tab at the top left, you access the list of all the Narratives you have access too, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of narratives.

"},{"location":"usage/exploring-techniques/#visualizing-knowledge-associated-with-a-narrative","title":"Visualizing Knowledge associated with a Narrative","text":"

When clicking on a Narrative, you land on its Overview tab. For a Narrative, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Narratives. Different thematic views are proposed to easily see the Threat actors and Intrusion Set using the Narrative, etc.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the technique. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-techniques/#courses-of-action","title":"Courses of action","text":""},{"location":"usage/exploring-techniques/#general-presentation_2","title":"General presentation","text":"

In the MITRE STIX 2.1 documentation, an Course of action is defined as such :

A Course of Action is an action taken either to prevent an attack or to respond to an attack that is in progress. It may describe technical, automatable responses (applying patches, reconfiguring firewalls) but can also describe higher level actions like employee training or policy changes. For example, a course of action to mitigate a vulnerability could describe applying the patch that fixes it.

When clicking on the Courses of action tab at the top left, you access the list of all the Courses of action you have access too, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of course of action.

"},{"location":"usage/exploring-techniques/#visualizing-knowledge-associated-with-a-course-of-action","title":"Visualizing Knowledge associated with a Course of action","text":"

When clicking on a Course of Action, you land on its Overview tab. For a Course of action, the following tabs are accessible:

  • Overview: Overview of Course of action is a bit different as the usual described here. In \"Details\" box, mitigated attack pattern are listed.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Narratives. Different thematic views are proposed to easily see the Threat actors and Intrusion Set using the Narrative, etc.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Course of action. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-techniques/#data-sources-data-components","title":"Data sources & Data components","text":""},{"location":"usage/exploring-techniques/#general-presentation_3","title":"General presentation","text":"

In the MITRE ATT&CK documentation, Data sources are defined as such :

Data sources represent the various subjects/topics of information that can be collected by sensors/logs. Data sources also include data components, which identify specific properties/values of a data source relevant to detecting a given ATT&CK technique or sub-technique.

"},{"location":"usage/exploring-techniques/#visualizing-knowledge-associated-with-a-data-source-or-a-data-components","title":"Visualizing Knowledge associated with a Data source or a Data components","text":"

When clicking on a Data source or a Data component, you land on its Overview tab. For a Course of action, the following tabs are accessible:

  • Overview: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-threats/","title":"Threats","text":"

When you click on \"Threats\" in the left-side bar, you access all the \"Threats\" tabs, visible on the top bar on the left. By default, the user directly access the \"Threat Actor (Group)\" tab, but can navigate to the other tabs as well.

From the Threats section, users can access the following tabs:

  • Threat actors (Group): Threat actor (Group) represents a physical group of attackers operating an Intrusion set, using malware and attack infrastructure, etc.
  • Threat actors (Indvidual): Threat actor (Individual) represents a real attacker that can be described by physical and personal attributes and motivations. Threat actor (Individual) operates Intrusion set, uses malware and infrastructure, etc.
  • Intrusion sets: Intrusion set is an important concept in Cyber Threat Intelligence field. It is a consistent set of technical and non-technical elements corresponding of what, how and why a Threat actor acts. it is particularly useful for associating multiple attacks and malicious actions to a defined Threat, even without sufficient information regarding who did them. Often, with you understanding of the threat growing, you will link an Intrusion set to a Threat actor (either a Group or an Individual).
  • Campaigns: Campaign represents a series of attacks taking place in a certain period of time and/or targeting a consistent subset of Organization/Individual.
"},{"location":"usage/exploring-threats/#threat-actors-group-and-individual","title":"Threat actors (Group and Individual)","text":""},{"location":"usage/exploring-threats/#general-presentation","title":"General presentation","text":"

Threat actors are the humans who are building, deploying and operating intrusion sets. A threat actor can be an single individual or a group of attackers (who may be composed of individuals). A group of attackers may be a state-nation, a state-sponsored group, a corporation, a group of hacktivists, etc.

Beware, groups of attackers might be modelled as \"Intrusion sets\" in feeds, as there is sometimes a misunderstanding in the industry between group of people and the technical/operational intrusion set they operate.

When clicking on the Threat actor (Group or Individual) tabs at the top left, you see the list of all the groups of Threat actors or Individual Threat actors you have access to, in respect with your allowed marking definitions. These groups or individual are displayed as Cards where you can find a summary of the important Knowledge associated with each of them: description, aliases, malware they used, countries and industries they target, labels. You can then search and filter on some common and specific attributes of Threat actors.

At the top right of each Card, you can click the star icon to put it as favorite. It will pin the card on top of the list. You will also be able to display all your favorite easily in your Custom Dashboards.

"},{"location":"usage/exploring-threats/#demographic-and-biographic-information","title":"Demographic and Biographic Information","text":"

Individual Threat actors have unique properties to represent demographic and biographic information. Currently tracked demographics include their countries of residence, citizenships, date of birth, gender, and more.

Biographic information includes their eye and hair color, as well as known heights and weights.

An Individual Threat actor can also be tracked as employed by an Organization or a Threat Actor group. This relationship can be set under the knowledge tab.

"},{"location":"usage/exploring-threats/#visualizing-knowledge-associated-with-a-threat-actor","title":"Visualizing Knowledge associated with a Threat actor","text":"

When clicking on a Threat actor Card, you land on its Overview tab. For a Threat actor, the following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Threat actor. Different thematic views are proposed to easily see the victimology, arsenal and techniques used by the Threat actor, etc. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Threat actor. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-threats/#intrusion-sets","title":"Intrusion Sets","text":"

An intrusion set is a consistent group of technical elements such as \"tactics, technics and procedures\" (TTP), tools, malware and infrastructure used by a threat actor against one or a number of victims who are usually sharing some characteristics (field of activity, country or region) to reach a similar goal whoever the victim is. The intrusion set may be deployed once or several times and may evolve with time. Several intrusion sets may be linked to one threat actor. All the entities described below may be linked to one intrusion set. There are many debates in the Threat Intelligence community on how to define an intrusion set and how to distinguish several intrusion sets with regards to:

  • their differences
  • their evolutions
  • the possible reuse
  • \"false flag\" type of attacks

As OpenCTI is very customizable, each organization or individual may use these categories as they wish. Instead, it is also possible to use the import feed for the choice of categories.

When clicking on the Intrusion set tab on the top left, you see the list of all the Intrusion sets you have access to, in respect with your allowed marking definitions. These intrusion sets are displayed as Cards where you can find a summary of the important Knowledge associated with each of them: description, aliases, malware they used, countries and industries they target, labels. You can then search and filter on some common and specific attributes of Intrusion set.

At the top right of each Card, you can click the star icon to put it as favorite. It will pin the card on top of the list. You will also be able to display all your favorite easily in your Custom Dashboards.

"},{"location":"usage/exploring-threats/#visualizing-knowledge-associated-with-an-intrusion-set","title":"Visualizing Knowledge associated with an Intrusion set","text":"

When clicking on an Intrusion set Card, you land on its Overview tab. The following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Intrusion Set. Different thematic views are proposed to easily see the victimology, arsenal and techniques used by the Intrusion Set, etc. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Intrusion set. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/exploring-threats/#campaigns","title":"Campaigns","text":"

A campaign can be defined as \"a series of malicious activities or attacks (sometimes called a \"wave of attacks\") taking place within a limited period of time, against a defined group of victims, associated to a similar intrusion set and characterized by the use of one or several identical malware towards the various victims and common TTPs\". However, a campaign is an investigation element and may not be widely recognized. Thus, a provider might define a series of attacks as a campaign and another as an intrusion set. Campaigns can be attributed to an Intrusion set.

When clicking on the Campaign tab on the top left, you see the list of all the Campaigns you have access to, in respect with your allowed marking definitions. These campaigns are displayed as Cards where you can find a summary of the important Knowledge associated with each of them: description, aliases, malware used, countries and industries they target, labels. You can then search and filter on some common and specific attributes of Campaigns.

At the top right of each Card, you can click the star icon to put it as favorite. It will pin the card on top of the list. You will also be able to display all your favorite easily in your Custom Dashboards.

"},{"location":"usage/exploring-threats/#visualizing-knowledge-associated-with-a-campaign","title":"Visualizing Knowledge associated with a Campaign","text":"

When clicking on an Campaign Card, you land on its Overview tab. The following tabs are accessible:

  • Overview: as described here.
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Campaign. Different thematic views are proposed to easily see the victimology, arsenal and techniques used in the context of the Campaign. As described here.
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Campaign. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
  • Analyses: as described here.
  • Data: as described here.
  • History: as described here.
"},{"location":"usage/export/","title":"Manual export","text":""},{"location":"usage/export/#introduction","title":"Introduction","text":"

With the OpenCTI platform, you can manually export your intelligence content in the following formats:

  • JSON,
  • CSV,
  • PDF,
  • TXT.

"},{"location":"usage/export/#export-in-structured-or-document-format","title":"Export in structured or document format","text":""},{"location":"usage/export/#generate-an-export","title":"Generate an export","text":"

To export one or more entities you have two possibilities. First you can click on the button \"Open export panel\". The list of pre-existing exports will open, and in the bottom right-hand corner you can configure and generate a new export.

This opens the export settings panel, where you can customize your export according to four fields:

  • desired export format (text/csv, application/pdf, application/vnd.oasis.stix+json, text/plain)
  • export type (simple or full),
  • the max marking definition levels of the elements to be included in the export (a TLP level, for instance). The list of the available max markings is limited by the user allowed markings and its maximum shareable markings (more details about maximum shareable marking definitions in data segregation). For a marking definition type to be taken into account here, a marking definition from this type must be provided. For example, if you select TLP:GREEN for this field, AMBER and RED elements will be excluded but it will not take into account any PAP markings unless one is elected too.
  • the file marking definition levels of the export (a TLP level, for instance). This marking on the file itself will then restrain the access to it in accordance with users' marking definition levels. For example, if a file has the marking TLP:RED and INTERNAL, a user will need to have these marking to see and access the file in the platform.```

The second way is to click directly on the \"Generate an Export\" button to export the content of an entity in the desired format. The same settings panel will open.

Both ways add your export in the Exported files list in the Data tab.

"},{"location":"usage/export/#export-possibilities","title":"Export possibilities","text":"

All entities in your instance can be exported either directly via Generate Export or indirectly via Export List in .json and .csv formats.

"},{"location":"usage/export/#export-a-list-of-entities","title":"Export a list of entities","text":"

You have the option to export either a single element, such as a report, or a collection of elements, such as multiple reports. These exports may contain not only the entity itself but also related elements, depending on the type of export you select: \"simple\" or \"full\". See the Export types (simple and full) section.

You can also choose to export a list of entities within a container. To do so, go to the container's entities tab. For example, for a report, if you only want to retrieve entity type attack pattern and indicators to design a detection strategy, go to the entities tab and select specific elements for export.

"},{"location":"usage/export/#export-types-simple-and-full","title":"Export types (simple and full)","text":"

When you wish to export only the content of a specific entity such as a report, you can choose a \"simple\" export type.

If you also wish to export associated content, you can choose a \"full\" export. With this type of export, the entity will be exported along with all entities directly associated with the central one (first neighbors).

"},{"location":"usage/export/#exports-list-panel","title":"Exports list panel","text":"

Once an export has been created, you can find it in the export list panel. Simply click on a particular export to download it.

You can also generate a new export directly from the Exports list, as explained in the Generate an export section.

"},{"location":"usage/feeds/","title":"Native feeds","text":"

OpenCTI provides versatile mechanisms for sharing data through its built-in feeds, including Live streams, TAXII collections, and CSV feeds.

"},{"location":"usage/feeds/#feed-configuration","title":"Feed configuration","text":"

Feeds are configured in the \"Data > Data sharing\" window. Configuration for all feed types is uniform and relies on the following parameters:

  • Filter setup: The feed can have specific filters to publish only a subset of the platform overall knowledge. Any data that meets the criteria established by the user's feed filters will be shared (e.g. specific types of entities, labels, marking definitions, etc.).
  • Access control: A feed can be either public, i.e. accessible without authentication, or restricted. By default, it's accessible to any user with the \"Access data sharing\" capability, but it's possible to increase restrictions by limiting access to a specific user, group, or organization.

By carefully configuring filters and access controls, you can tailor the behavior of Live streams, TAXII collections, and CSV feeds to align with your specific data-sharing needs.

"},{"location":"usage/feeds/#live-streams","title":"Live streams","text":""},{"location":"usage/feeds/#introduction","title":"Introduction","text":"

Live streams, an exclusive OpenCTI feature, increase the capacity for real-time data sharing by serving STIX 2.1 bundles as TAXII collections with advanced capabilities. What distinguishes them is their dynamic nature, which includes the creation, updating, and deletion of data. Unlike TAXII, Live streams comprehensively resolve relationships and dependencies, ensuring a more nuanced and interconnected exchange of information. This is particularly beneficial in scenarios where sharing involves entities with complex relationships, providing a richer context for the shared data.

In scenarios involving data sharing between two OpenCTI platforms, Live streams emerge as the preferred mechanism. These streams operate like TAXII collections but are notably enhanced, supporting:

  • create, update and delete events depending on the parameters,
  • caching already created entities in the last 5 minutes,
  • resolving relationships and dependencies even out of the filters,
  • can be public (without authentication).

Resolve relationships and dependencies

Dependencies and relationships of entities shared via Live streams, as determined by specified filters, are automatically shared even beyond the confines of these filters. This means that interconnected data, which may not directly meet the filter criteria, is still included in the Live stream. However, OpenCTI data segregation mechanisms are still applied. They allow restricting access to shared data based on factors such as markings or organization. It's imperative to carefully configure and manage these access controls to ensure that no confidential data is shared.

"},{"location":"usage/feeds/#illustrative-scenario","title":"Illustrative scenario","text":"

To better understand how live streams are working, let's take a few examples, from simple to complex.

Given a live stream with filters Entity type: Indicator AND Label: detection. Let's see what happens with an indicator with:

  • Marking definition: TLP:GREEN
  • Author Crowdstrike
  • Relation indicates to the malware Emotet
Action Result in stream (with Avoid dependencies resolution=true) Result in stream (with Avoid dependencies resolution=false) 1. Create an indicator Nothing Nothing 2. Add the label detection Create TLP:GREEN, create CrowdStrike, create the indicator Create TLP:GREEN, create CrowdStrike, create the malware Emotet, create the indicator, create the relationship indicates 3. Remove the label detection Delete the indicator Delete the indicator and the relationship 4. Add the label detection Create the indicator Create the indicator, create the relationship indicates 5. Delete the indicator Delete the indicator Delete the indicator and the relationship

Details on how to consume these Live streams can be found on the dedicated page.

"},{"location":"usage/feeds/#taxii-collections","title":"TAXII Collections","text":"

OpenCTI has an embedded TAXII API endpoint which provides valid STIX 2.1 bundles. If you wish to know more about the TAXII standard, please read the official introduction.

In OpenCTI you can create as many TAXII 2.1 collections as needed.

After creating a new collection, every system with a proper access token can consume the collection using different kinds of authentication (basic, bearer, etc.).

As when using the GraphQL API, TAXII 2.1 collections have a classic pagination system that should be handled by the consumer. Also, it's important to understand that element dependencies (nested IDs) inside the collection are not always contained/resolved in the bundle, so consistency needs to be handled at the client level.

"},{"location":"usage/feeds/#csv-feeds","title":"CSV feeds","text":"

The CSV feed facilitates the automatic generation of a CSV file, accessible via a URL. The CSV file is regenerated and updated at user-defined intervals, providing flexibility. The entries in the file correspond to the information that matches the filters applied and that were created or modified in the platform during the time interval (between the last generation of the CSV and the new one).

CSV size limit

The CSV file generated has a limit of 5 000 entries. If more than 5 000 entities are retrieved by the platform, only the most recent 5 000 will be shared in the file.

"},{"location":"usage/getting-started/","title":"Getting started","text":"

This guide aims to give you a full overview of the OpenCTI features and workflows. The platform can be used in various contexts to handle threats management use cases from a technical to a more strategic level. OpenCTI has been designed as a knowledge graph, taking inputs (threat intelligence feeds, sightings & alerts, vulnerabilities, assets, artifacts, etc.) and generating outputs based on built-in capabilities and / or connectors.

Here are some examples of use cases:

  • Cyber Threat Intelligence knowledge base
  • Detection as code feeds for XDR, EDR, SIEMs, firewalls, proxies, etc.
  • Incident response artifacts & cases management
  • Vulnerabilities management
  • Reporting, alerting and dashboarding on a subset of data

"},{"location":"usage/getting-started/#welcome-dashboard","title":"Welcome dashboard","text":"

The welcome page gives any visitor on the OpenCTI platform an overview of what's happening on the platform. It can be replaced by a custom dashboard, created by a user (or the default dashboard set up in a role, a group or an organization).

"},{"location":"usage/getting-started/#indicators-in-the-dashboard","title":"Indicators in the dashboard","text":""},{"location":"usage/getting-started/#numbers","title":"Numbers","text":"Component Description Intrusion sets Number of intrusion sets . Malware Number of malware. Reports Number of reports. Indicators Number of indicators."},{"location":"usage/getting-started/#charts-lists","title":"Charts & lists","text":"Component Description Most active threats (3 last months) Top active threats (threat actor, intrusion set and campaign) during the last 3 months. Most targeted victims (3 last months) Intensity of the targeting tied to the number of relations targets for a given entities (organization, sector, location, etc.) during the last 3 months. Relationships created Volume of relationships created over the past 12 months. Most active malware (3 last months) Top active malware during the last 3 months. Most active vulnerabilities (3 last months) List of the vulnerabilities with the greatest number of relations over the last 3 months. Targeted countries (3 last months) Intensity of the targeting tied to the number of relations targets for a given country over the past 3 months. Latest reports Last reports ingested in the platform. Most active labels (3 last months) Top labels given to entities during the last 3 months.

Explore the platform

To start exploring the platform and understand how information is structured, we recommend starting with the overview documentation page.

"},{"location":"usage/import-automated/","title":"Automated import","text":"

Automated imports in OpenCTI streamline the process of data ingestion, allowing users to effortlessly bring in valuable intelligence from diverse sources. This page focuses on the automated methods of importing data, which serve as bridges between OpenCTI and diverse external systems, formatting it into a STIX bundle, and importing it into the OpenCTI platform.

"},{"location":"usage/import-automated/#connectors","title":"Connectors","text":"

Connectors in OpenCTI serve as dynamic gateways, facilitating the import of data from a wide array of sources and systems. Every connector is designed to handle specific data types and structures of the source, allowing OpenCTI to efficiently ingest the data.

"},{"location":"usage/import-automated/#connector-behaviors","title":"Connector behaviors","text":"

The behavior of each connector is defined by its development, determining the types of data it imports and its configuration options. This flexibility allows users to customize the import process to their specific needs, ensuring a seamless and personalized data integration experience.

The level of configuration granularity regarding the imported data type varies with each connector. Nevertheless, connectors empower users to specify the date from which they wish to fetch data. This capability is particularly useful during the initial activation of a connector, enabling the retrieval of historical data. Following this, the connector operates in real-time, continuously importing new data from the source.

"},{"location":"usage/import-automated/#reset-connector-state","title":"Reset connector state","text":"

Resetting the connector state enables you to restart the ingestion process from the very beginning. Additionally, resetting the connector state will purge the RabbitMQ queue for this specific connector.

However, this action requires the \"Manage connector state\" capability (more details about capabilities: List of capabilities). Without this specific capability, you will not be able to reset the connector state.

When the action is performed, a message is displayed confirming the reset and inform you about the number of messages that will be purged

Purging a message queue is necessary to remove any accumulated messages that may be outdated or redundant. It helps to avoid reprocessing messages that have already been ingested.

By purging the queue, you ensure that the connector starts with a clean slate, processing only the new data.

"},{"location":"usage/import-automated/#connector-ecosystem","title":"Connector Ecosystem","text":"

OpenCTI's connector ecosystem covers a broad spectrum of sources, enhancing the platform's capability to integrate data from various contexts, from threat intelligence providers to specialized databases. The list of available connectors can be found in our connectors catalog. Connectors are categorized into three types: import connectors (the focus here), enrichment connectors, and stream consumers. Further documentation on connectors is available on the dedicated documentation page.

In summary, automated imports through connectors empower OpenCTI users with a scalable, efficient, and customizable mechanism for data ingestion, ensuring that the platform remains enriched with the latest and most relevant intelligence.

"},{"location":"usage/import-automated/#native-automated-import","title":"Native automated import","text":"

In OpenCTI, the \"Data > Ingestion\" section provides users with built-in functions for automated data import. These functions are designed for specific purposes and can be configured to seamlessly ingest data into the platform. Here, we'll explore the configuration process for the four built-in functions: Live Streams, TAXII Feeds, RSS Feeds, and CSV Feeds.

"},{"location":"usage/import-automated/#live-streams","title":"Live streams","text":"

Live Streams enable users to consume data from another OpenCTI platform, fostering collaborative intelligence sharing. Here's a step-by-step guide to configure Live streams synchroniser:

  1. Remote OpenCTI URL: Provide the URL of the remote OpenCTI platform (e.g., https://[domain]; don't include the path).
  2. Remote OpenCTI token: Provide the user token. An administrator from the remote platform must supply this token, and the associated user must have the \"Access data sharing\" privilege.
  3. After filling in the URL and user token, validate the configuration.
  4. Once validated, select a live stream to which you have access.

Additional configuration options:

  • User responsible for data creation: Define the user responsible for creating data received from this stream. Best practice is to dedicate one user per source for organizational clarity. Please see the section \"Best practices\" below for more information.
  • Starting synchronization: Specify the date of the oldest data to retrieve. Leave the field empty to import everything.
  • Take deletions into account: Enable this option to delete data from your platform if it was deleted on the providing stream. (Note: Data won't be deleted if another source has imported it previously.)
  • Verify SSL certificate: Check the validity of the certificate of the domain hosting the remote platform.
  • Avoid dependencies resolution: Import only entities without their relationships. For instance, if the stream shares malware, all the malware's relationships will be retrieved by default. This option enables you to choose not to recover them.
  • Use perfect synchronization: This option is specifically for synchronizing two platforms. If an imported entity already exists on the platform, the one from the stream will overwrite it.

"},{"location":"usage/import-automated/#taxii-feeds","title":"TAXII feeds","text":"

TAXII Feeds in OpenCTI provide a robust mechanism for ingesting TAXII collections from TAXII servers or other OpenCTI instances. Configuring TAXII ingester involves specifying essential details to seamlessly integrate threat intelligence data. Here's a step-by-step guide to configure TAXII ingesters:

  1. TAXII server URL: Provide the root API URL of the TAXII server. For collections from another OpenCTI instance, the URL is in the form https://[domain]/taxii2/root.
  2. TAXII collection: Enter the ID of the TAXII collection to be ingested. For collections from another OpenCTI instance, the ID follows the format 426e3acb-db50-4118-be7e-648fab67c16c.
  3. Authentication type (if necessary): Enter the authentication type. For non-public collections from another OpenCTI instance, the authentication type is \"Bearer token.\" Enter the token of a user with access to the collection (similar to the point 2 of the Live streams configuration above).

TAXII root API URL

Many ISAC TAXII configuration instructions will provide the URL for the collection or discovery service. In these cases, remove the last path segment from the TAXII Server URL in order to use it in OpenCTI. eg. use https://[domain]/tipapi/tip21, and not https://[domain]/tipapi/tip21/collections.

Additional configuration options:

  • User responsible for data creation: Define the user responsible for creating data received from this TAXII feed. Best practice is to dedicate one user per source for organizational clarity. Please see the section \"Best practices\" below for more information.
  • Import from date: Specify the date of the oldest data to retrieve. Leave the field empty to import everything.

"},{"location":"usage/import-automated/#rss-feeds","title":"RSS feeds","text":"

RSS Feeds functionality enables users to seamlessly ingest items in report form from specified RSS feeds. Configuring RSS Feeds involves providing essential details and selecting preferences to tailor the import process. Here's a step-by-step guide to configure RSS ingesters:

  1. RSS Feed URL: Provide the URL of the RSS feed from which items will be imported.

Additional configuration options:

  • User responsible for data creation: Define the user responsible for creating data received from this RSS feed. Best practice is to dedicate one user per source for organizational clarity. Please see the section \"Best practices\" below for more information.
  • Import from date: Specify the date of the oldest data to retrieve. Leave the field empty to import everything.
  • Default report types: Indicate the report type to be applied to the imported report.
  • Default author: Indicate the default author to be applied to the imported report. Please see the section \"Best practices\" below for more information.
  • Default marking definitions: Indicate the default markings to be applied to the imported reports.

"},{"location":"usage/import-automated/#csv-feeds","title":"CSV feeds","text":"

CSV feed ingester enables users to import CSV files exposed on URLs. Here's a step-by-step guide to configure TAXII ingesters:

  1. CSV URL: Provide the URL of the CSV file exposed from which items will be imported.
  2. CSV Mappers: Choose the CSV mapper to be used to import the data.
  3. Authentication type (if necessary): Enter the authentication type.

CSV mapper

CSV feed functionality is based on CSV mappers. It is necessary to create the appropriate CSV mapper to import the data contained in the file. See the page dedicated to the CSV mapper.

Additional configuration options:

  • User responsible for data creation: Define the user responsible for creating data received from this CSV feed. Best practice is to dedicate one user per source for organizational clarity. Please see the section \"Best practices\" below for more information.
  • Import from date: Specify the date of the oldest data to retrieve. Leave the field empty to import everything.

in CSV Mappers, if you created a representative for Marking definition, you could have chosen between 2 options:

  • let the user choose marking definitions
  • Use default marking definitions of the user

This configuration applies when using a CSV Mapper for a CSV Ingester. If you select a CSV Mapper containing the option \"Use default marking definitions of the user\", the default marking definitions of the user you chose to be responsible for the data creation will be applied to all data imported. If you select a CSV Mapper containing the option \"let the user choose marking definitions\", you will be presented with the list of all the marking definitions of the user you chose to be responsible for the data creation (and not yours!)

To finalize the creation, click on \"Verify\" to run a check on the submitted URL with the selected CSV mapper. A valid URL-CSV mapper combination results in the identification of up to 50 entities.

To start your new ingester, click on \"Start\", in the burger menu.

CSV feed ingestion is made possible thanks to the connector \"ImportCSV\". So you can track the progress in \"Data > Ingestion > Connectors\". On a regular basis, the ingestion is updated when new data is added to the CSV feed.

"},{"location":"usage/import-automated/#best-practices-for-feed-import","title":"Best practices for feed import","text":"

Ensuring a secure and well-organized environment is paramount in OpenCTI. Here are two recommended best practices to enhance security, traceability, and overall organizational clarity:

  1. Create a dedicated user for each source: Generate a user specifically for feed import, following the convention [F] Source name for clear identification. Assign the user to the \"Connectors\" group to streamline user management and permission related to data creation. Please see here for more information on this good practice.
  2. Establish a dedicated Organization for the source: Create an organization named after the data source for clear identification. Assign the newly created organization to the \"Default author\" field in feed import configuration if available.

By adhering to these best practices, you ensure independence in managing rights for each import source through dedicated user and organization structures. In addition, you enable clear traceability to the entity's creator, facilitating source evaluation, dashboard creation, data filtering and other administrative tasks.

"},{"location":"usage/import-automated/#automated-import-behaviors","title":"Automated import behaviors","text":"

An ingestion manager runs periodically in background, and for each running feeds: - fetches new data from the source. When data is paginated, fetches the next page - compose a stix bundle for data and send it in queue to be processed by workers

!!! Note on timeline of data ingestion from Taxii feed, CSV feed, and RSS feed.

Depending on workers load, the data can take some time between the fetch from source and visibility in the platform.\n

Periodicity interval is configured with the manager with ingestion_manager:interval.

"},{"location":"usage/import-automated/#digest","title":"Digest","text":"

Users can streamline the data ingestion process using various automated import capabilities. Each method proves beneficial in specific circumstances.

  • Connectors act as bridges to retrieve data from diverse sources and format it for seamless ingestion into OpenCTI.
  • Live Streams enable collaborative intelligence sharing across OpenCTI instances, fostering real-time updates and efficient data synchronization.
  • TAXII Feeds provide a standardized mechanism for ingesting threat intelligence data from TAXII servers or other OpenCTI instances.
  • RSS Feeds facilitate the import of items in report form from specified RSS feeds, offering a straightforward way to stay updated on relevant intelligence.

By leveraging these automated import functionalities, OpenCTI users can build a comprehensive, up-to-date threat intelligence database. The platform's adaptability and user-friendly configuration options ensure that intelligence workflows remain agile, scalable, and tailored to the unique needs of each organization.

"},{"location":"usage/import-files/","title":"Import from files","text":""},{"location":"usage/import-files/#import-mechanisms","title":"Import mechanisms","text":"

The platform provides a seamless process for automatically parsing data from various file formats. This capability is facilitated by two distinct mechanisms.

File import connectors: Currently, there are two connectors designed for importing files and automatically identifying entities.

  • ImportFileStix: Designed to handle STIX-structured files (json or xml format).
  • ImportDocument: Versatile connector supporting an array of file formats, including pdf, text, html, and markdown.

CSV mappers: The CSV mapper is a tailored functionality to facilitate the import of data stored in CSV files. For more in-depth information on using CSV mappers, refer to the CSV Mappers documentation page.

"},{"location":"usage/import-files/#usage","title":"Usage","text":""},{"location":"usage/import-files/#locations","title":"Locations","text":"

Both mechanisms can be employed wherever file uploads are possible. This includes the \"Data\" tabs of all entities and the dedicated panel named \"Data import and analyst workbenches\" located in the top right-hand corner (database logo with a small gear). Importing files from these two locations is not entirely equal; refer to the \"Relationship handling from entity's Data tab\" section below for details on this matter.

"},{"location":"usage/import-files/#entity-identification-process","title":"Entity identification process","text":"

For ImportDocument connector, the identification process involves searching for existing entities in the platform and scanning the document for relevant information. In additions, the connector use regular expressions (regex) to detect IP addresses and domains within the document.

As for the ImportFileStix connector and the CSV mappers, there is no identification mechanism. The imported data will be, respectively, the data defined in the STIX bundle or according to the configuration of the CSV mapper used.

"},{"location":"usage/import-files/#workflow-overview","title":"Workflow overview","text":"
  1. Upload file: Navigate to the desired location, such as the \"Data\" tabs of an entity or the \"Data import and analyst workbenches\" panel. Then, upload the file containing the relevant data by clicking on the small cloud with the arrow inside next to \"Uploaded files\".
  2. Entity identification: For a CSV file, select the connector and CSV mapper to be used by clicking on the icon with an upward arrow in a circle. If it's not a CSV file, the connector will launch automatically. Then, the file import connectors or CSV mappers will identify entities within the uploaded document.
  3. Workbench review and validation: Entities identified by connectors are not immediately integrated into the platform's knowledge base. Instead, they are thoughtfully placed in a workbench, awaiting review and validation by an analyst. Workbenches function as draft spaces, ensuring that no data is officially entered into the platform until the workbench has undergone the necessary validation process. For more information on workbenches, refer to the Analyst workbench documentation page.

Review workbenches

Import connectors may introduce errors in identifying object types or add \"unknown\" entities. Workbenches were established with the intent of reviewing the output of connectors before validation. Therefore, it is crucial to be vigilant when examining the workbench to prevent the import of incorrect data into the platform.

"},{"location":"usage/import-files/#additional-information","title":"Additional information","text":""},{"location":"usage/import-files/#no-workbench-for-csv-mapper","title":"No workbench for CSV mapper","text":"

It's essential to note that CSV mappers operate differently from other import mechanisms. Unlike connectors, CSV mappers do not generate workbenches. Instead, the data identified by CSV mappers is imported directly into the platform without an intermediary workbench stage.

"},{"location":"usage/import-files/#relationship-handling-from-entitys-data-tab","title":"Relationship handling from entity's \"Data\" tab","text":"

When importing a document directly from an entity's \"Data\" tab, there can be an automatic addition of relationships between the objects identified by connectors and the entity in focus. The process differs depending on the type of entity in which the import occurs:

  • If the entity is a container (e.g., Report, Grouping, and Cases), the identified objects in the imported file will be linked to the entity (upon workbench validation). In the context of a container, the object is said to be \"contained\".
  • For entities that are not containers, a distinct behavior unfolds. In this scenario, the identified objects are not linked to the entity, except for Observables. Related to relationships between the Observables and the entity are automatically added to the workbench and created after validation of this one.
"},{"location":"usage/import-files/#file-import-in-content-tab","title":"File import in Content tab","text":"

Expanding the scope of file imports, users can seamlessly add files in the Content tab of Analyses or Cases. In this scenario, the file is directly added as an attachment without utilizing an import mechanism.

"},{"location":"usage/import-files/#user-capability-requirement","title":"User capability requirement","text":"

In order to initiate file imports, users must possess the requisite capability: \"Upload knowledge files.\" This capability ensures that only authorized users can contribute and manage knowledge files within the OpenCTI platform, maintaining a controlled and secure environment for data uploads.

Deprecation warning

Using the ImportDocument connector to parse CSV file is now disallowed as it produces inconsistent results. Please configure and use CSV mappers dedicated to your specific CSV content for a reliable parsing. CSV mappers can be created and configured in the administration interface.

"},{"location":"usage/indicators-lifecycle/","title":"Indicators Lifecycle Management","text":""},{"location":"usage/indicators-lifecycle/#introduction","title":"Introduction","text":"

OpenCTI enforces strict rules to determine the period during which an indicator is effective for usage. This period is defined by the valid_from and valid_until dates. All along its lifecycle, the indicator score will decrease according to configured decay rules. After the indicator expires, the object is marked as revoked and the detection field is automatically set to false. Here, we outline how these dates are calculated within the OpenCTI platform and how the score is updated with decay rules.

"},{"location":"usage/indicators-lifecycle/#setting-validity-dates","title":"Setting validity dates","text":""},{"location":"usage/indicators-lifecycle/#data-source-provided-the-dates","title":"Data source provided the dates","text":"

If a data source provides valid_from and valid_until dates when creating an indicator on the platform, these dates are used without modification. But, if the creation is performed from the UI and the indicator is elligible to be manages by a decay rule, the platform will change this valid_until with the one calculated by the Decay rule.

"},{"location":"usage/indicators-lifecycle/#fallback-rules-for-unspecified-dates","title":"Fallback rules for unspecified dates","text":"

If a data source does not provide validity dates, OpenCTI applies the decay rule matching the indicator to determine these dates. The valid_until date is computed based on the revoke score of the decay rule : it is set at the exact time at which the indicator will reach the revoke score. Past valid_until date, the indicator is marked as revoked.

"},{"location":"usage/indicators-lifecycle/#score-decay","title":"Score decay","text":"

Indicators have an initial score at creation, either provided by data source, or 50 by default. Over time, this score is going to decrease according to the configured decay rules. Score is updated at each reaction point defined for the decay rule matching the indicator at creation.

"},{"location":"usage/indicators-lifecycle/#example","title":"Example","text":"

This URL indicator has matched the Built-in IP and URL decay rule. Its initial score at creation is 100.

Right next to the indicator score, there is a button Lifecycle which enables to open a dialog to see the details of the indicator's lifecyle.

"},{"location":"usage/indicators-lifecycle/#conclusion","title":"Conclusion","text":"

Understanding how OpenCTI calculates validity periods and scores is essential for effective threat intelligence analysis. These rules ensure that your indicators are accurate and up-to-date, providing a reliable foundation for threat intelligence data.

"},{"location":"usage/inferences/","title":"Inferences and reasoning","text":""},{"location":"usage/inferences/#overview","title":"Overview","text":"

OpenCTI\u2019s inferences and reasoning capability is a robust engine that automates the process of relationship creation within your threat intelligence data. This capability, situated at the core of OpenCTI, allows logical rules to be applied to existing relationships, resulting in the automatic generation of new, pertinent connections.

"},{"location":"usage/inferences/#understanding-inferences-and-reasoning","title":"Understanding inferences and reasoning","text":"

Inferences and reasoning serve as OpenCTI\u2019s intelligent engine. It interprets your data logically. By activating specific predefined rules (of which there are around twenty), OpenCTI can deduce new relationships from the existing ones. For instance, if there's a connection indicating an Intrusion Set targets a specific country, and another relationship stating that this country is part of a larger region, OpenCTI can automatically infer that the Intrusion Set also targets the broader region.

"},{"location":"usage/inferences/#key-benefits","title":"Key benefits","text":"
  • Efficiency: Reduces manual workload by automating relationship creation, saving valuable analyst time.
  • Completeness: Fills relationship gaps, ensuring a comprehensive and interconnected threat intelligence database.
  • Accuracy: Minimizes manual input errors by deriving relationships from predefined, accurate logic.
"},{"location":"usage/inferences/#how-it-operates","title":"How it operates","text":"

When you activate an inference rule, OpenCTI continuously analyzes your existing relationships and applies the defined logical rules. These rules are logical statements that define conditions for new relationships. When the set of conditions is met, the OpenCTI creates the corresponding relationship automatically.

For example, if you activate a rule as follows:

IF [Entity A targets Identity B] AND [Identity B is part of Identity C] THEN [Entity A targets Identity C]

OpenCTI will apply this rule to existing data. If it finds an Intrusion Set (\"Entity A\") targeting a specific country (\"Identity B\") and that country is part of a larger region (\"Identity C\"), the platform will automatically establish a relationship between the Intrusion Set and the region.

"},{"location":"usage/inferences/#identifying-inferred-relationships","title":"Identifying inferred relationships","text":"

In the knowledge graphs: Inferred relationships are represented by dotted lines of a different color, distinguishing them from non-inferred relations.

In the lists: In a relationship list, a magic wand icon at the end of the line indicates relationship created by inference.

"},{"location":"usage/inferences/#additional-resources","title":"Additional resources","text":"
  • Administration: To find out about existing inference rules and enable/disable them, refer to the Rules engine page in the Administration section of the documentation.
  • Playbooks: OpenCTI playbooks are highly customizable automation scenarios. This seamless integration allows for further automation, making your threat intelligence processes even more efficient and tailored to your specific needs. More information in our blog post.
"},{"location":"usage/manual-creation/","title":"Manual creations","text":"

Manual data creation in OpenCTI is an intuitive process that occurs throughout the platform. This page provides guidance on two key aspects of manual creation: Entity creation and Relationship creation.

"},{"location":"usage/manual-creation/#entity-creation","title":"Entity creation","text":"

To create an entity:

  1. Navigate to the relevant section: Be on the section of the platform related to the object type you want to create.
  2. Click on the \"+\" icon: Locate the \"+\" icon located at the bottom right of the window.
  3. Fill in entity-specific fields: A form on the right side of the window will appear, allowing to fill in specific fields of the entity. Certain fields are inherently obligatory, and administrators have the option to designate additional mandatory fields (See here for more information).
  4. Click on \"Create\": Once you've filled in the desired fields, click on \"create\" to initiate the entity creation process.

"},{"location":"usage/manual-creation/#relationship-creation","title":"Relationship creation","text":"

Before delving into the creation of relationships between objects in OpenCTI, it's crucial to grasp some foundational concepts. Here are key points to understand:

  • On several aspects, including relationships, two categories of objects must be differentiated: containers (e.g., Reports, Groupings, and Cases) and others. Containers aren't related to but contains objects.
  • Relationships, like all other entities, are objects. They possess fields, can be linked, and share characteristics identical to other entities.
  • Relationships are inherently directional, comprising a \"from\" entity and a \"to\" entity. Understanding this directionality is essential for accurate relationship creation.
  • OpenCTI supports various relationship types, and their usage depends on the entity types being linked. For example, a \"target\" relationship might link malware to an organization, while linking malware to an intrusion set might involve a different relationship type.

Now, let\u2019s explore the process of creating relationships. To do this, we will differentiate the case of containers from the others.

"},{"location":"usage/manual-creation/#for-container","title":"For container","text":"

When it comes to creating relationships within containers in OpenCTI, the process is straightforward. Follow these steps to attach objects to a container:

  1. Navigate to the container: Go to the specific container to which you want to attach an object. This could be a Report, Grouping, or Cases.
  2. Access the \"Entities\" tab: Within the container, locate and access the \"Entities\" tab.
  3. Click on the \"+\" icon: Find the \"+\" icon located at the bottom right of the window.
  4. Search for entities: A side window will appear. Search for the entities you want to add to the container.
  5. Add entities to the container: Click on the desired entities. They will be added directly to the container.
"},{"location":"usage/manual-creation/#for-other","title":"For other","text":"

When creating relationships not involving a container, the creation method is distinct. Follow these steps to create relationships between entities:

  1. Navigate to one of the entities: Go to one of the entities you wish to link. Please be aware that the entity from which you create the relationship will be designated as the \"from\" entity for that relationship. So the decision of which entity to choose for creating the relationship should be considered, as it will impact the outcome.
  2. Access the \"Knowledge\" tab: Within the entity, go to the \"Knowledge\" tab.
  3. Select the relevant categories: In the right banner, navigate to the categories that correspond to the object to be linked. The available categories depend on the type of entity you are currently on. For example, if you are on malware and want to link to a sector, choose \"victimology.\"
  4. Click on the \"+\" icon: Find the \"+\" icon located at the bottom right of the window.
  5. Search for entities: A side window will appear. Search for the entities you want to link.
  6. Add entities and click on \"Continue\": Click on the entities you wish to link. Multiple entities can be selected. Then click on \"Continue\" at the bottom right.
  7. Fill in the relationship form: As relationships are objects, a creation form similar to creating an entity will appear.
  8. Click on \"Create\": Once you've filled in the desired fields, click on \"create\" to initiate the relationship creation process.

"},{"location":"usage/manual-creation/#additional-methods","title":"Additional methods","text":"

While the aforementioned methods are primary for creating entities and relationships, OpenCTI offers versatility, allowing users to create objects in various locations within the platform. Here's a non-exhaustive list of additional places that facilitate on-the-fly creation:

  • Creating entities during relationship creation: During the \"Search for entities\" phase (see above) of the relationship creation process, click on the \"+\" icon to create a new entity directly.
  • Knowledge graph: Within the knowledge graph - found in the knowledge tab of the containers or in the investigation functionality - users can seamlessly create entities or relationships.
  • Inside a workbench: The workbench serves as another interactive space where users can create entities and relationships efficiently.

These supplementary methods offer users flexibility and convenience, allowing them to adapt their workflow to various contexts within the OpenCTI platform. As users explore the platform, they will naturally discover additional means of creating entities and relationships.

Max confidence level

When creating knowledge in the platform, the maximum confidence level of the users is used. Please navigate to this page to understand this concept and the impact it can have on the knowledge creation.

"},{"location":"usage/merging/","title":"Merge objects","text":""},{"location":"usage/merging/#introduction","title":"Introduction","text":"

OpenCTI\u2019s merge capability stands as a pivotal tool for optimizing threat intelligence data, allowing to consolidate multiple entities of the same type. This mechanism serves as a powerful cleanup tool, harmonizing the platform and unifying scattered information. In this section, we explore the significance of this feature, the process of merging entities, and the strategic considerations involved.

"},{"location":"usage/merging/#data-streamlining","title":"Data streamlining","text":"

In the ever-expanding landscape of threat intelligence and the multitude of names chosen by different data sources, data cleanliness is essential. Duplicates and fragmented information hinder efficient analysis. The merge capability is a strategic solution for amalgamating related entities into a cohesive unit. Central to the merging process is the selection of a main entity. This primary entity becomes the anchor, retaining crucial attributes such as name and description. Other entities, while losing specific fields like descriptions, are aliased under the primary entity. This strategic decision preserves vital data while eliminating redundancy.

"},{"location":"usage/merging/#preserving-entity-relationships","title":"Preserving entity relationships","text":"

One of the key feature of the merge capability is its ability to preserve relationships. While merging entities, their interconnected relationships are not lost. Instead, they seamlessly integrate into the new, merged entity. This ensures that the intricate web of relationships within the data remains intact, fostering a comprehensive understanding of the threat landscape.

"},{"location":"usage/merging/#conclusion","title":"Conclusion","text":"

OpenCTI\u2019s merge capability helps improve the quality of threat intelligence data. By consolidating entities and centralizing relationships, OpenCTI empowers analysts to focus on insights and strategies, unburdened by data silos or fragmentation. However, exercising caution and foresight in the merging process is essential, ensuring a robust and streamlined knowledge basis.

"},{"location":"usage/merging/#additional-resources","title":"Additional resources","text":"
  • Administration: To understand how to merge entities and the consideration to take into account, refer to the Merging page in the Administration section of the documentation.
  • Deduplication mechanism: the platform is equipped with deduplication processes that automatically merge data at creation (either manually or by importing data from different sources) if it meets certain conditions.
"},{"location":"usage/nested/","title":"Nested references and objects","text":""},{"location":"usage/nested/#stix-standard","title":"STIX standard","text":""},{"location":"usage/nested/#definition","title":"Definition","text":"

In the STIX 2.1 standard, objects can:

  1. Refer to other objects in directly in their attributes, by referencing one or multiple IDs.
  2. Have other objects directly embedded in the entity.
"},{"location":"usage/nested/#example","title":"Example","text":"
{\n   \"type\": \"intrusion-set\",\n   \"spec_version\": \"2.1\",\n   \"id\": \"intrusion-set--4e78f46f-a023-4e5f-bc24-71b3ca22ec29\",\n   \"created_by_ref\": \"identity--f431f809-377b-45e0-aa1c-6a4751cae5ff\", // nested reference to an identity\n   \"object_marking_refs\": [\"marking-definition--34098fce-860f-48ae-8e50-ebd3cc5e41da\"], // nested reference to multiple marking defintions\n   \"external_references\": [\n      {\n         \"source_name\": \"veris\",\n         \"external_id\": \"0001AA7F-C601-424A-B2B8-BE6C9F5164E7\",\n         \"url\": \"https://github.com/vz-risk/VCDB/blob/125307638178efddd3ecfe2c267ea434667a4eea/data/json/validated/0001AA7F-C601-424A-B2B8-BE6C9F5164E7.json\",    \n      }\n   ],\n   \"created\": \"2016-04-06T20:03:48.000Z\",\n   \"modified\": \"2016-04-06T20:03:48.000Z\",\n   \"name\": \"Bobcat Breakin\",\n   \"description\": \"Incidents usually feature a shared TTP of a bobcat being released within the building containing network access...\",\n   \"aliases\": [\"Zookeeper\"],\n   \"goals\": [\"acquisition-theft\", \"harassment\", \"damage\"]\n}\n

In the previous example, we have 2 nested references to other objects in:

\"created_by_ref\": \"identity--f431f809-377b-45e0-aa1c-6a4751cae5ff\", // nested reference to an identity\n\"object_marking_refs\": [\"marking-definition--34098fce-860f-48ae-8e50-ebd3cc5e41da\"], // nested reference to multiple marking defintions\n

But we also have a nested object within the entity (an External Reference):

\"external_references\": [\n   {\n      \"source_name\": \"veris\",\n      \"external_id\": \"0001AA7F-C601-424A-B2B8-BE6C9F5164E7\",\n      \"url\": \"https://github.com/vz-risk/VCDB/blob/125307638178efddd3ecfe2c267ea434667a4eea/data/json/validated/0001AA7F-C601-424A-B2B8-BE6C9F5164E7.json\",    \n   }\n]\n
"},{"location":"usage/nested/#implementation","title":"Implementation","text":""},{"location":"usage/nested/#modelization","title":"Modelization","text":"

In OpenCTI, all nested references and objects are modelized as relationships, to be able to pivot more easily on labels, external references, kill chain phases, marking definitions, etc.

"},{"location":"usage/nested/#import-export","title":"Import & export","text":"

When importing and exporting data to/from OpenCTI, the translation between nested references and objects to full-fledged nodes and edges is automated and therefore transparent for the users. Here is an example with the object in the graph above:

{\n   \"id\": \"file--b6be3f04-e50f-5220-af3a-86c2ca66b719\",\n   \"spec_version\": \"2.1\",\n   \"x_opencti_description\": \"...\",\n   \"x_opencti_score\": 50,\n   \"hashes\": {\n       \"MD5\": \"b502233b34256285140676109dcadde7\"\n   },\n   \"labels\": [\n       \"cookiecutter\",\n       \"clouddata-networks-1\"\n   ],\n   \"external_references\": [\n       {\n           \"source_name\": \"Sekoia.io\",\n           \"url\": \"https://app.sekoia.io/intelligence/objects/indicator--3e6d61b4-d5f0-48e0-b934-fdbe0d87ab0c\"\n       }\n   ],\n   \"x_opencti_id\": \"8a3d108f-908c-4833-8ff4-4d6fc996ce39\",\n   \"type\": \"file\",\n   \"created_by_ref\": \"identity--b5b8f9fc-d8bf-5f85-974e-66a7d6f8d4cb\",\n   \"object_marking_refs\": [\n       \"marking-definition--613f2e26-407d-48c7-9eca-b8e91df99dc9\"\n   ]\n}\n
"},{"location":"usage/notifications/","title":"Notifications and alerting","text":"

In the evolving landscape of cybersecurity, timely awareness is crucial. OpenCTI empowers users to stay informed and act swiftly through its robust notifications and alerting system. This feature allows users to create personalized triggers that actively monitor the platform for specific events and notify them promptly when these conditions are met.

From individual users tailoring their alert preferences to administrators orchestrating collaborative triggers for Groups or Organizations, OpenCTI's notification system is a versatile tool for keeping cybersecurity stakeholders in the loop.

The main menu \"Notifications and triggers\" for creating and managing notifications is located in the top right-hand corner with the bell icon.

"},{"location":"usage/notifications/#triggers","title":"Triggers","text":"

In OpenCTI, triggers serve as personalized mechanisms for users to stay informed about specific events that align with their cybersecurity priorities. Users can create and manage triggers to tailor their notification experience. Each trigger operates by actively listening to events based on predefined filters and event types, promptly notifying users via chosen notifiers when conditions are met.

"},{"location":"usage/notifications/#trigger-management","title":"Trigger management","text":"

Individual user triggers: Each user possesses the autonomy to craft their own triggers, finely tuned to their unique preferences and responsibilities. By setting up personalized filters and selecting preferred notifiers, users ensure that they receive timely and relevant notifications aligned with their specific focus areas.

Administrative control: Platform administrators have the capability to create and manage triggers for Users, Groups and Organizations. This provides centralized control and the ability to configure triggers that address collective cybersecurity objectives. Users within the designated Group or Organization will benefit from triggers with read-only access rights. These triggers are to be created directly on the User|Group|Organization with whom to share them in \"Settings > Security > Users|Groups|Organizations\".

"},{"location":"usage/notifications/#trigger-filters","title":"Trigger filters","text":"

Leveraging the filters, users can meticulously define the criteria that activate their triggers. This level of granularity ensures that triggers are accurate, responding precisely to events that matter most. Users can tailor filters to consider various parameters such as object types, markings, sources, or other contextual details. They can also allow notifications for the assignment of a Task, a Case, etc.

Beyond filters, a trigger can be configured to respond to three event types: creation, modification, and deletion.

"},{"location":"usage/notifications/#instance-triggers","title":"Instance triggers","text":"

Instance triggers offer a targeted approach to live monitoring by allowing users to set up triggers specific to one or several entities. These triggers, when activated, keep a vigilant eye on a predefined set of events related to the selected entities, ensuring that you stay instantly informed about crucial changes.

"},{"location":"usage/notifications/#creating-instance-triggers","title":"Creating instance triggers","text":"

Method 1: Using the general trigger creation form

  1. Go on the \"Notifications and triggers\" window.
  2. Navigate to the \"Triggers and digests\" tab.
  3. Access the general trigger creation form.
  4. Toggle the switch \"Instance trigger\".
  5. Choose the entities to monitor.

Method 2: Quick subscription

  1. On an entity's overview, locate the \"Instance trigger quick subscription\" button with the bell icon at the top right.
  2. Click on the button to create the instance trigger.
  3. (Optional) Click on it again to modify the instance trigger created.

"},{"location":"usage/notifications/#events-monitored-by-instance-triggers","title":"Events monitored by instance triggers","text":"

An instance trigger set on an entity X actively monitors the following events:

  • Update/Deletion of X: Stay informed when the selected entity undergoes changes or is deleted.
  • Creation/Deletion of relationships: Receive notifications about relationships being added or removed from/to X.
  • Creation/Deletion of related entities: Be alerted when entities that have X in its refs - i.e. contains X, is shared with X, is created by X, etc. - are created or deleted.
  • Adding/Removing X in ref: Stay in the loop when X is included or excluded from the ref of other entities - i.e. adding X in the author of an entity, adding X in a report, etc.).

Entity deletion notification

It's important to note that the notification of entity deletion can occur in two scenarios: - Real entity deletion: When the entity is genuinely deleted from the platform. - Visibility loss: When a modification to the entity results in the user losing visibility for that entity.

"},{"location":"usage/notifications/#digest","title":"Digest","text":"

Digests provide an efficient way to streamline and organize your notifications. By grouping notifications based on selected triggers and specifying the delivery period (daily, weekly, monthly), you gain the flexibility to receive consolidated updates at your preferred time, as opposed to immediate notifications triggered by individual events.

"},{"location":"usage/notifications/#creating-digests","title":"Creating digests","text":"
  1. Go on the \"Notifications and triggers\" window.
  2. Navigate to the \"Triggers and digests\" tab.
  3. Create a new digest.
  4. Configure digest: Set the parameters, including triggers to be included and the frequency of notifications (daily, weekly, monthly).
  5. Choose the notifier(s): Select the notification method(s) (e.g. within the OpenCTI interface, via email, etc.).
"},{"location":"usage/notifications/#benefits-of-digests","title":"Benefits of digests","text":"
  • Organized notifications: Digests enable you to organize and categorize notifications, preventing a flood of individual alerts.
  • Customized delivery: Choose the frequency of digest delivery based on your preferences, whether it's a daily overview, a weekly summary, or a monthly roundup.
  • Reduced distractions: Receive notifications at a scheduled time, minimizing interruptions and allowing you to focus on critical tasks.

Digests enhance your control over notification management, ensuring a more structured and convenient approach to staying informed about important events.

"},{"location":"usage/notifications/#notifiers","title":"Notifiers","text":"

In OpenCTI, notifiers serve as the channels for delivering notifications, allowing users to stay informed about critical events. The platform offers two built-in notifiers, \"Default mailer\" for email notifications and \"User interface\" for in-platform alerts.

"},{"location":"usage/notifications/#notifier-connectors","title":"Notifier connectors","text":"

OpenCTI features built-in notifier connectors that empower users to create personalized notifiers for notification and activity alerting. Three essential connectors are available:

  • Platform mailer connector: Enables sending notifications directly within the OpenCTI platform.
  • Simple mailer connector: Offers a straightforward approach to email notifications with simplified configuration options.
  • Generic webhook connector: Facilitates communication through webhooks.

OpenCTI provides two samples of webhook notifiers designed for Teams integration.

"},{"location":"usage/notifications/#configuration-and-access","title":"Configuration and Access","text":"

Notifiers are manageable in the \"Settings > Customization > Notifiers\" window and can be restricted through Role-Based Access Control (RBAC). Administrators can restrict access to specific Users, Groups, or Organizations, ensuring controlled usage.

For guidance on configuring custom notifiers and explore detailed setup instructions, refer to the dedicated documentation page.

"},{"location":"usage/overview/","title":"Overview","text":""},{"location":"usage/overview/#introduction","title":"Introduction","text":"

The following chapter aims at giving the reader a step-by-step description of what is available on the platform and the meaning of the different tabs and entries.

When the user connects to the platform, the home page is the Dashboard. This Dashboard contains several visuals summarizing the types and quantity of data recently imported into the platform.

Dashboard

To get more information about the components of the default dashboard, you can consult the Getting started.

The left side panel allows the user to navigate through different windows and access different views and categories of knowledge.

"},{"location":"usage/overview/#structure","title":"Structure","text":""},{"location":"usage/overview/#the-hot-knowledge","title":"The \"hot knowledge\"","text":"

The first part of the platform in the left menu is dedicated to what we call the \"hot knowledge\", which means this is the entities and relationships which are added on a daily basis in the platform and which generally require work / analysis from the users.

  • Analyses: all containers which convey relevant knowledge such as reports, groupings and malware analyses.
  • Cases: all types of case like incident responses, requests for information, for takedown, etc.
  • Events: all incidents & alerts coming from operational systems as well as sightings.
  • Observations: all technical data in the platform such as observables, artifacts and indicators.
"},{"location":"usage/overview/#the-cold-knowledge","title":"The \"cold knowledge\"","text":"

The second part of the platform in the left menu is dedicated to the \"cold knowledge\", which means this is the entities and relationships used in the hot knowledge. You can see this as the \"encyclopedia\" of all pieces of knowledge you need to get context: threats, countries, sectors, etc.

  • Threats: all threats entities from campaigns to threat actors, including intrusion sets.
  • Arsenal: all tools and pieces of malware used and/or targeted by threats, including vulnerabilities.
  • Techniques: all objects related to tactics and techniques used by threats (TTPs, etc.).
  • Entities: all non-geographical contextual information such as sectors, events, organizations, etc.
  • Locations: all geographical contextual information, from cities to regions, including precise positions.
"},{"location":"usage/overview/#hide-categories","title":"Hide categories","text":"

You can customize the experience in the platform by hiding some categories in the left menu, whether globally or for a specific role.

"},{"location":"usage/overview/#hide-categories-globally","title":"Hide categories globally","text":"

In the Settings > Parameters, it is possible for the platform administrator to hide categories in the platform for all users.

"},{"location":"usage/overview/#hide-categories-in-roles","title":"Hide categories in roles","text":"

In OpenCTI, the different roles are highly customizable. It is possible to defined default dashboards, triggers, etc. but also be able to hide categories in the roles:

"},{"location":"usage/overview/#presentation-of-a-typical-page-in-opencti","title":"Presentation of a typical page in OpenCTI","text":"

While OpenCTI features numerous entities and tabs, many of them share similarities, with only minor differences arising from specific characteristics. These differences may involve the inclusion or exclusion of certain fields, depending on the nature of the entity.

In this part will only be detailed a general outline of a \"typical\" OpenCTI page. The specifies of the different entities will be detailed in the corresponding pages below (Activities and Knowledge).

"},{"location":"usage/overview/#overview_1","title":"Overview","text":"

In the Overview tab on the entity, you will find all properties of the entity as well as the recent activities.

First, you will find the Details section, where are displayed all properties specific to the type of entity you are looking at, an example below with a piece of malware:

Thus, in the Basic information section, are displayed all common properties to all objects in OpenCTI, such as the marking definition, the author, the labels (i.e. tags), etc.

Below these two sections, you will find latest modifications in the Knowledge base related to the Entity:

  • Latest created relationships: display the latest relationships that have been created from or to this Entity. For example, latest Indicators of Compromise and associated Threat Actor of a Malware.
  • latest containers about the object: display all the Cases and Analyses that contains this Entity. For example, the latest Reports about a Malware.
  • External references: display all the external sources associated with the Entity. You will often find here links to external reports or webpages from where Entity's information came from.
  • History: display the latest chronological modifications of the Entity and its relationships that occurred in the platform, in order to traceback any alteration.

Last, all Notes written by users of the platform about this Entity are displayed in order to access unstructured analysis comments.

"},{"location":"usage/overview/#knowledge","title":"Knowledge","text":"

In the Knowledge tab, which is the central part of the entity, you will find all the Knowledge related to the current entity. The Knowledge tab is different for Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) entities than for all the other entity types.

  • The Knowledge tab of those entities (who represents Analyses or Cases that can contains a collection of Objects) is the place to integrate and link together entities. For more information on how to integrate information in OpenCTI using the knowledge tab of a report, please refer to the part Manual creation.
  • The Knowledge tabs of any other entity (that does not aim to contain a collection of Objects) gather all the entities which have been at some point linked to the entity the user is looking at. For instance, as shown in the following capture, the Knowledge tab of Intrusion set APT29, gives access to the list of all entities APT29 is attributed to, all victims the intrusion set has targeted, all its campaigns, TTPs, malware etc. For entities to appear in these tabs under Knowledge, they need to have been linked to the entity directly or have been computed with the inference engine.

"},{"location":"usage/overview/#focus-on-indicators-and-observables","title":"Focus on Indicators and Observables","text":"

The Indicators and Observables section offers 3 display modes: - The entities view, which displays the indicators/observables linked to the entity. - The relationship view, which displays the various relationships between the indicators/observables linked to the entity and the entity itself. - The contextual view, which displays the indicators/observables contained in the cases and analyses that contain the entity.

"},{"location":"usage/overview/#content","title":"Content","text":"

The Content tab is available for all entities. It allows for uploading and creating outcomes documents related to the content of the current entity (in PDF, text, HTML or markdown files). This specific tab enable to previzualize, manage and write deliverable associated with the entity. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc.

The Content mapping view and the Suggested mapping view are available for a subset of entities: Report, Grouping, Incident, Incident response, Request for Information, and Request for Takedown.

"},{"location":"usage/overview/#content-mapping-view","title":"Content mapping view","text":"

The Content mapping view displays the mappable content of your container on the left (Description and Content), and the objects contained in the container on the right.

This view allows you to map readable content to existing or new Objects by selecting text on the left. Mapping an object will add it to your container, and the object will then be displayed on the right. You can clear all mappings that you added by clicking on the Clear mappings button. This action will only remove the mapping: the objects will still be contained in your container.

This allows you to quickly append structured Knowledge in your Case before refining it with relationships and details, and makes it a great place to see the continuum between unstructured and structured Knowledge.

"},{"location":"usage/overview/#suggested-mapping-view","title":"Suggested mapping view","text":"

The Suggested mapping view displays the mappable content of your container on the left (Description and Content), and the suggested entity mapping on the right.

This view allows you to get a suggestion list of existing Objects based on your mappable content by clicking on Suggest new mapping. To be able to get a suggestion, you need to have at least one analysis connector of type INTERNAL_ANALYSIS configured. Once the suggestion has been computed by the connector, it will be available on the right. You can the remove the suggestion that you are not interested in, and click on the Validate button to add the mapped objects to your container.

This allows you to quickly fill your Container with the data that you need, without having to manually map every related Objects.

"},{"location":"usage/overview/#analyses","title":"Analyses","text":"

The Analyses tab contains the list of all Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) in which the entity has been identified.

By default, this tab display the list, but you can also display the content of all the listed Analyses on a graph, allowing you to explore all their Knowledge and have a glance of the context around the Entity.

"},{"location":"usage/overview/#data","title":"Data","text":"

The Data tab contains documents that are associated to the object and were either:

  • Uploaded to the platform : for instance the PDF document containing the text of the report
  • Generated from the platform to be downloaded : a JSON or CSV file containing information on the object and generated by the user.
  • associated to an external reference

Analyst Workbench can also be created from here. They will contain the entity by default.

In addition, the Data tab of Threat actors (group), Threat actors (individual), Intrusions sets, Organizations, Individuals have an extra panel:

  • Pictures Management: allows to manage the profile pictures attached to the entity.

"},{"location":"usage/overview/#history","title":"History","text":"

The History tab displays the history of change of the Entity, update of attributes, creation of relations, ...

Because of the volumes of information the history is written in a specific index that consume the redis stream to rebuild the history for the UI.

"},{"location":"usage/overview/#less-frequent-tabs","title":"Less frequent tabs","text":"
  • The Observables tab (for Reports and Observed data): A table containing all SCO (Stix Cyber Observable) contained in the Report or the Observed data, with search and filters available. It also displays if the SCO has been added directly or through inferences with the reasoning engine
  • the Entities tab (for Reports and Observed data): A table containing all SDO (Stix Domain Objects) contained in the Report or the Observed data, with search and filters available. It also displays if the SDO has been added directly or through inferences with the reasoning engine
  • Observables:
  • the Sightings tab (for Indicators and Observables): A table containing all Sightings relationships corresponding to events in which Indicators (IP, domain name, URL, etc.) are detected by or within an information system, an individual or an organization. Most often, this corresponds to a security event transmitted by a SIEM or EDR.
"},{"location":"usage/pivoting/","title":"Pivot and investigate","text":"

In OpenCTI, all data are structured as an extensive knowledge graph, where every element is interconnected. The investigation functionality provides a powerful tool for pivoting on any entity or relationship within the platform. Pivoting enables users to explore and analyze connections between entities and relationships, facilitating a comprehensive understanding of the data.

To access investigations, navigate to the top right corner of the toolbar:

Access restriction

When an investigation is created, it is initially visible only to the creator, allowing them to work on the investigation before deciding to share it. The sharing mechanism is akin to that of dashboards. For further details, refer to the Access control section in the dashboard documentation page.

"},{"location":"usage/pivoting/#perform-investigation","title":"Perform investigation","text":""},{"location":"usage/pivoting/#manipulate-entity","title":"Manipulate entity","text":"

We can add any existing entity of the platform to your investigation.

After adding an entity, we can choose the entity and view its details in the panel that appears on the right of the screen.

On each node, we'll notice a bullet with a number inside, serving as a visual indication of how many entities are linked to it but not currently displayed in the graph. Keep in mind that this number is an approximation, which is why there's a \"+\" next to it. If there's no bullet displayed, it means there's nothing to expand from this node.

"},{"location":"usage/pivoting/#expansion","title":"Expansion","text":"

To incorporate these linked entities into the graph, we just have to expand the nodes. Utilize the button with a 4-arrows logo in the mentioned menu, or double-click on the entity directly. This action opens a new window where we can choose the types of entities and relationships we wish to expand.

For instance, in the image above, selecting the target Malware and the relationship Uses implies expanding in my investigation graph all Malware linked to this node with a relationship of type Uses.

"},{"location":"usage/pivoting/#roll-back-expansion","title":"Roll back expansion","text":"

Expanding a graph can add a lot of entities and relations, making it not only difficult to read but sometimes counterproductive since it brings entities and relations that are not useful to your investigations. To solve this problem, there is a button to undo the last expansion.

When clicking on this button, we will retrieve the state in which your graph was before your expansion. As a result, please note that all add or remove actions made since the last expansion will be lost: in other words, if you have expanded your graph, and then have added some entities in your graph, when clicking on rollback button, the entities that you have added will not be in your graph.

You can roll back your investigation graph up to the last 10 expand actions.

"},{"location":"usage/pivoting/#manipulate-relationship","title":"Manipulate relationship","text":"

We can create a relationship between entities directly within our investigation. To achieve this, select multiple entities by clicking on them while holding down the shift key. Subsequently, a button appears at the bottom right to create one (or more, depending on the number of entities selected) relationships.

Relationship creation

Creating a relationship in the investigation graph will generate the relationship in your knowledge base.

"},{"location":"usage/pivoting/#capitalize-on-an-investigation","title":"Capitalize on an investigation","text":""},{"location":"usage/pivoting/#export-investigation","title":"Export investigation","text":"

Users have the capability to export investigations, providing a way to share, document, or archive their findings.

  • PDF and image formats: Users can export investigations in either PDF or image format, offering flexibility in sharing and documentation.
  • STIX bundle: The platform allows the export of the entire content of an investigation graph as a STIX bundle. In the STIX format, all objects within the investigation graph are automatically aggregated into a Report object.

"},{"location":"usage/pivoting/#turn-investigation-into-a-container","title":"Turn investigation into a container","text":"

Users can efficiently collect and consolidate the findings of an investigation by adding the content into dedicated containers. The contents of an investigation can be imported into various types of containers, including:

  • Grouping
  • Incident Response
  • Report
  • Request for Information
  • Request for Takedown

We have the flexibility to choose between creating a new container on the fly or adding investigation content to an existing container.

After clicking on the ADD button, the browser will redirect to the Knowledge tab of the container where we added the content of our investigation. If we added it to multiple containers, the redirection will be to the first of the list.

"},{"location":"usage/reliability-confidence/","title":"Reliability and Confidence","text":""},{"location":"usage/reliability-confidence/#generalities","title":"Generalities","text":"

In (Cyber) Threat Intelligence, evaluation of information sources and of information quality is one of the most important aspect of the work. It is of the utter most importance to assess situations by taking into account reliability of the sources and credibility of the information.

This concept is foundational in OpenCTI, and have real impact on:

  • the data deduplication process
  • the data stream filtering for ingestion and sharing
"},{"location":"usage/reliability-confidence/#what-is-the-reliability-of-a-source","title":"What is the Reliability of a source?","text":"

Reliability of a source of information is a measurement of the trust that the analyst can have about the source, based on the technical capabilities or history of the source. Is the source a reliable partner with long sharing history? A competitor? Unknown?

Reliability of sources are often stated at organizational level, as it requires an overview of the whole history with it.

In the Intelligence field, Reliability is often notated with the NATO Admiralty code.

"},{"location":"usage/reliability-confidence/#what-is-confidence-of-an-information","title":"What is Confidence of an information?","text":"

Reliability of a source is important but even a trusted source can be wrong. Information in itself has a credibility, based on what is known about the subject and the level of corroboration by other sources.

Credibility is often stated at the analyst team level, expert of the subject, able to judge the information with its context.

In the Intelligence field, Confidence is often notated with the NATO Admiralty code.

Why Confidence instead of Credibility?

Using both Reliability and Credibility is an advanced use case for most of CTI teams. It requires a mature organization and a well staffed team. For most of internal CTI team, a simple confidence level is enough to forge assessment, in particular for teams that concentrate on technical CTI.

Thus in OpenCTI, we have made the choice to fuse the notion of Credibility with the Confidence level that is commonly used by the majority of users. They have now the liberty to push forward their practice and use both Confidence and Reliability in their daily assessments.

"},{"location":"usage/reliability-confidence/#reliability-open-vocabulary","title":"Reliability open vocabulary","text":"

Reliability value can be set for every Entity in the platform that can be Author of Knowledge:

  • Organizations
  • Individuals
  • Systems
  • and also Reports

Reliability on Reports allows you to specify the reliability associated to the original author of the report if you received it through a provider.

For all Knowledge in the platform, the reliability of the source of the Knowledge (author) is displayed in the Overview. This way, you can always forge your assessment of the provided Knowledge regarding the reliability of the author.

You can also now filter entities by the reliability of its author.

Tip

This way, you may choose to feed your work with only Knowledge provided by reliable sources.

Reliability is an open vocabulary that can be customized in Settings -> Taxonomies -> Vocabularies : reliability_ov.

Info

The setting by default is the Reliability scale from NATO Admiralty code. But you can define whatever best fit your organization.

"},{"location":"usage/reliability-confidence/#confidence-scale","title":"Confidence scale","text":"

Confidence level can be set for:

  • Analyses: Report, Grouping, Malware analysis, Notes
  • Cases: Incident Response, Request for Information, Request for Takedown, Feedback
  • Events: Incident, Sighting, Observed data
  • Observations: Indicator, Infrastructure
  • Threats: Threat actor (Group), Threat actor (Individual), Intrusion Set, Campaign
  • Arsenal: Malware, Channel, Tool, Vulnerability

For all of these entities, the Confidence level is displayed in the Overview, along with the Reliability. This way, you can rapidly assess the Knowledge with the Confidence level representing the credibility/quality of the information.

"},{"location":"usage/reliability-confidence/#confidence-scale-customization","title":"Confidence scale customization","text":"

Confidence level is a numerical value between 0 and 100. But Multiple \"Ticks\" can be defined and labelled to provide a meaningful scale.

Confidence level can be customized for each entity type in Settings > Customization > Entity type.

As such customization can be cumbersome, three confidence level templates are provided in OpenCTI:

  • Admiralty: corresponding to the Admiralty code's credibility scale
  • Objective: corresponding to a full objective scale, aiming to leave any subjectivity behind. With this scale, an information confidence is:
    • \"Cannot be judged\": there is no data regarding the credibility of the information
    • \"Told\": the information is known because it has been told to the source. The source doesn't verify it by any means.
    • \"Induced\": the information is the result of an analysis work and is based on other similar information assumed to be true.
    • \"Deduced\": the information is the result of an analysis work, and is a logical conclusion of other information assumed to be true.
    • \"Witnessed\": the source have observed itself the described situation or object.
  • standard: the historic confidence level scale in OpenCTI defining a Low, Med and High level of confidence.

It is always possible to modify an existing template to define a custom scale adapted to your context.

Tip

If you use the Admiralty code setting for both reliability and Confidence, you will find yourself with the equivalent of NATO confidence notation in the Overview of your different entities (A1, B2, C3, etc.)

"},{"location":"usage/reliability-confidence/#max-confidence-level","title":"Max confidence level","text":""},{"location":"usage/reliability-confidence/#overview","title":"Overview","text":"

We know that in organizations, different users do not always have the same expertise or seniority. As a result, some specific users can be more \"trusted\" when creating or updating knowledge than others. Additionally, because connectors, TAXII feeds and streams are all linked to respectively one user, it is important to be able to differentiate which connector, stream or TAXII feed is more trustable than others.

This is why we have introduced the concept of max confidence level to tackle this use case.

Max confidence level per user allows organizations to fine tune their users to ensure knowledge updated and created stays as consistent as possible.

The maximum confidence level can be set at the Group level or at the User level, and can be overridden by entity type for fine-tuning your confidence policy.

"},{"location":"usage/reliability-confidence/#overall-way-of-working","title":"Overall way of working","text":"

The overall idea is that users with a max confidence level lower than a confidence level of an entity cannot update or delete this entity.

Also, in a conservative approach, when 2 confidence levels are possible, we would always take the lowest one.

To have a detailed understanding of the concept, please browse through this diagram:

"},{"location":"usage/reliability-confidence/#user-effective-confidence-level","title":"User effective confidence level","text":"

User and group confidence level configuration shall be viewed as:

  • a maximum confidence level between 0 and 100 (optional for users, mandatory for groups);
  • a list of overrides (a max confidence level between 0 and 100) per entity type (optional).

The user's effective confidence level is the result of this configuration from multiple sources (user and their groups).

To compute this value, OpenCTI uses the following strategy:

  • effective maximum confidence is the maximum value found in the user's groups;
  • effective overrides per entity type are cumulated from all groups, taking the maximum value if several overrides are set on the same entity type
  • if a user maximum confidence level is set, it overrides everything from groups, including the overrides per entity type defined at group level
  • if not, but the user has specific overrides per entity types, they override the corresponding confidence levels per entity types coming from groups
  • if a user has the administrator's \"Bypass\" capability, the effective confidence level will always be 100 without overrides, regardless of the group and user configuration on confidence level

The following diagram describes the different use-cases you can address with this system.

"},{"location":"usage/reliability-confidence/#how-to-set-a-confidence-level","title":"How to set a confidence level","text":"

You can set up a maximum confidence levels from the Confidences tab in the edition panel of your user or group. The value can be selected between 0 and 100, or using the admiralty scale selector.

At the group level, the maximum confidence level is mandatory, but is optional at the user level (you have to enable it using the corresponding toggle button).

"},{"location":"usage/reliability-confidence/#how-to-override-a-max-confidence-level-per-entity-type","title":"How to override a max confidence level per entity type","text":"

You also have the possibility to override a max confidence level per entity type, limited to Stix Domain Objects.

You can visualize the user's effective confidence level in the user's details view, by hovering the corresponding tooltip. It describes where the different values might come from.

"},{"location":"usage/reliability-confidence/#usage-in-opencti","title":"Usage in OpenCTI","text":""},{"location":"usage/reliability-confidence/#example-with-the-admiralty-code-template","title":"Example with the admiralty code template","text":"

Your organization have received a report from a CTI provider. At your organization level, this provider is considered as reliable most of the time and its reliability level has been set to \"B - Usually Reliable\" (your organization uses the Admiralty code).

This report concerns ransomware threat landscape and have been analysed by your CTI analyst specialized in cybercrime. This analyst has granted a confidence level of \"2 - Probably True\" to the information.

As a technical analyst, through the cumulated reliability and Confidence notations, you now know that the technical elements of this report are probably worth consideration.

"},{"location":"usage/reliability-confidence/#example-with-the-objective-template","title":"Example with the Objective template","text":"

As a CTI analyst in a governmental CSIRT, you build up Knowledge that will be shared within the platform to beneficiaries. Your CSIRT is considered as a reliable source by your beneficiaries, even if you play a role of a proxy with other sources, but your beneficiaries need some insights about how the Knowledge has been built/gathered.

For that, you use the \"Objective\" confidence scale in your platform to provide beneficiaries with that. When the Knowledge is the work of the investigation of your CSIRT, either from incident response or attack infrastructure investigation, you set the confidence level to \"Witnessed\", \"Deduced\" or \"Induced\" (depending on if you observed directly the data, or inferred it during your research). When the information has not been verified by the CSIRT but has value to be shared with beneficiaries, you can use the \"Told\" level to make it clear to them that the information is probably valuable but has not been verified.

"},{"location":"usage/search/","title":"Search for knowledge","text":"

In OpenCTI, you have access to different capabilities to be able to search for knowledge in the platform. In most cases, a search by keyword can be refined with additional filters for instance on the type of object, the author etc.

"},{"location":"usage/search/#global-search","title":"Global search","text":"

The global search is always available in the top bar of the platform.

This search covers all STIX Domain Objects (SDOs) and STIX Cyber Observables (SCOs) in the platform. The search results are sorted according to the following behaviour:

  • Priority 1 for exact matching of the keyword in one attribute of the objects.
  • Priority 2 for partial matching of the keyword in the name, the aliases and the description attributes (full text search).
  • Priority 3 for partial matching of the keyword in all other attributes (full text search).

If you get unexpected result, it is always possible to add some filters after the initial search:

Also, using the Advanced search button, it is possible to directly put filters in a global search:

Advanced filters

You have access to advanced filters all accross the UI, if you want to know more about how to use these filters with the API or the Python library, don't hesitate to read the dedicated page

"},{"location":"usage/search/#full-text-search-in-files-content","title":"Full text search in files content","text":"

Enterprise edition

Full text search in files content is available under the \"OpenCTI Enterprise Edition\" license.

Please read the dedicated page to have all information

It's possible to extend the global search by keywords to the content of documents uploaded to the platform via the Data import tab, or directly linked to an entity via its Data tab.

It is particularly useful to enable Full text indexing to avoid missing important information that may not have been structured within the platform. This situation can arise due to a partial automatic import of document content, limitations of a connector, and, of course, errors during manual processing.

In order to search in files, you need to configure file indexing.

"},{"location":"usage/search/#bulk-search","title":"Bulk search","text":"

The bulk search capabilities is available in the top bar of the platform and allows you to copy paste a list of keyword or objects (ie. list of domains, list of IP addresses, list of vulnerabilities, etc.) to search in the platform:

When searching in bulk, OpenCTI is only looking for an exact match in some properties:

  • name
  • aliases
  • x_opencti_aliases
  • x_mitre_id
  • value
  • subject
  • abstract
  • hashes.MD5
  • hashes.SHA-1
  • hashes.SHA-256
  • hashes.SHA-512
  • x_opencti_additional_names

When something is not found, it appears in the list as Unknown and will be excluded if you choose to export your search result in a JSON STIX bundle or in a CSV file.

"},{"location":"usage/search/#contextual-search","title":"Contextual search","text":"

In most of the screens of knowledge, you always have a contextual search bar allowing you to filter the list you are on:

The search keyword used here is taken into account if you decide to export the current view in a file such as a JSON STIX bundle or a CSV file.

"},{"location":"usage/search/#other-search-bars","title":"Other search bars","text":"

Some other screens can contain search bars for specific purposes. For instance, in the graph views to filter the nodes displayed on the graph:

"},{"location":"usage/tips-widget-creation/","title":"Pro-tips on widget creation","text":"

Previously, the creation of widgets has been covered. To help users being more confident in creating widgets, here are some details to master the widget creation.

"},{"location":"usage/tips-widget-creation/#how-to-choose-the-appropriate-widget-visualization-for-your-use-case","title":"How to choose the appropriate widget visualization for your use case?","text":"

We can classify the widgets in 3 different types.

"},{"location":"usage/tips-widget-creation/#single-dimension-widgets","title":"Single dimension widgets","text":"

Use these widgets when you would like to display information about one single type of object (entity or relation).

  • Widget visualizations: number, list, list (distribution), timeline, donuts, radar, map, bookmark, tree map.
  • Use case example: view the amount of malware in platform (number widget), view the top 10 threat actor group target a specific country (distribution list widget), etc.
"},{"location":"usage/tips-widget-creation/#multi-dimension-widgets","title":"Multi dimension widgets","text":"

Use these widgets if you would like to compare or have some insights about similar types of object (up to 5).

  • Widget visualizations: line, area, heatmap, vertical bars.
  • Use case example: view the amount of malware, intrusion sets, threat actor groups added in the course of last month in the platform (line or area widget).

Type of object in widget

These widgets need to use the same \"type\" of object to work properly. You always need to add relationships in the filter view if you have selected a \"knowledge graph\" perspective. If you have selected the knowledge graph entity, adding \"Entities\" (click on + entities) will not work, since you are not counting the same things.

"},{"location":"usage/tips-widget-creation/#break-down-widgets","title":"Break down widgets","text":"

Use this widget if you want to divide your data set into smaller parts to make it clearer and more useful for analysis.

  • Widget visualization: horizontal bars.
  • Use case example: view the list of malware targeting a country breakdown by the type of malware.

"},{"location":"usage/tips-widget-creation/#adding-datasets-to-your-widget","title":"Adding datasets to your widget","text":"

Adding datasets can serve two purposes: comparing data or breakdown a view to have deeper understanding on what a specific dataset is composed of.

"},{"location":"usage/tips-widget-creation/#use-case-1-compare-several-datasets","title":"Use Case 1: compare several datasets","text":"

As mentioned in How to choose the appropriate widget visualization for your use case? section you can add data sets to compare different data. Make sure to add the same type of objects (entities or relations) to be able to compare the same objects, by using access buttons like +, + Relationships, or + Entities.

You can add up to 5 different data sets. The Label field allows you to name a data set, and this label can then be shown as a legend in the widget using the Display legend button in the widget parameters (see the next section).

"},{"location":"usage/tips-widget-creation/#use-case-2-break-down-your-chart","title":"Use case 2: break down your chart","text":"

As mentioned in How to choose the appropriate widget visualization for your use case? section you can add data sets to decompose your graph into smaller meaningful chunks. In the below points, you can find some use cases that will help you understand how to structure your data.

You can break down a view either by entity or by relations, depending on what you need to count.

"},{"location":"usage/tips-widget-creation/#break-down-by-entity","title":"Break down by entity","text":"

Use case example: I need to understand what are the most targeted countries by malware, and have a breakdown for each country by malware type.

Process:

  1. To achieve this use case, you first need to select the horizontal bar vizualisation.
  2. Then you need to select the knowledge graph perspective.

In the filters view:

  1. Then input your main query Source type = Malware AND Target type = Countries AND Relation type = Targets. Add a label to your dataset.
  2. Add an entity data set by using access button + Entities.
  3. Add the following filters Entity type = Malware AND In regards of = targets. Add a label to your dataset.

In the parameter view:

  1. Attribute (of your relation) = entity (so that you display the different entities values)
  2. Display the source toggle = off
  3. Attribute (of your entity malware) = Malware type (since you want to break down your relations by the malware types)

As a result, you get a list of countries broken down by malware types.

"},{"location":"usage/tips-widget-creation/#break-down-by-relation","title":"Break down by relation","text":"

Use case example: I need to understand what are the top targeting malware and have a breakdown of the top targets per malware

Process:

  1. To achieve this use case, you first need to select the horizontal bar vizualisation.
  2. Then you need to select the knowledge graph perspective.

In the filters view:

  1. Then input your main query Source type = Malware AND Relation type = Targets. Add a label to your dataset.
  2. Add a relation data set by using access button + Relationships
  3. Add the following filters Source type = Malware AND Relation type = targets. Add a label to your dataset.

In the parameter view:

  1. Attribute (of your relation): entity (so that you display the different entities values)
  2. Display the source toggle = on
  3. Attribute (of your entity malware) = Malware type (since you want to break down your relations by the malware types)
  4. Display the source toggle = off

As a result, you get a list of malware with the breakdown of their top targets.

"},{"location":"usage/tips-widget-creation/#more-use-cases","title":"More use cases","text":"

To see more use cases, feel free to have a look at this blog post that will provide you additional information.

"},{"location":"usage/widgets/","title":"Widget creation","text":"

Creating widgets on the dashboard involves a four-step configuration process. By navigating through these configuration steps, users can design widgets that meet their specific requirements.

"},{"location":"usage/widgets/#widget-configuration","title":"Widget configuration","text":""},{"location":"usage/widgets/#1-visualization","title":"1. Visualization","text":"

Users can select from 15 diverse visualization options to highlight different aspects of their data. This includes simple views like counters and lists, as well as more intricate views like heatmaps and trees. The chosen visualization impacts the available perspectives and parameters, making it crucial to align the view with the desired data observations. Here are a few insights:

  • Line and Area views: Ideal for visualizing activity volumes over time.
  • Horizontal bar views: Designed to identify top entities that best satisfy applied filters (e.g., top malware targeting the Finance sector).
  • Tree views: Useful for comparing activity volumes.
  • ...

"},{"location":"usage/widgets/#2-perspective","title":"2. Perspective","text":"

A perspective is the way the platform will count the data to display in your widgets:

  • Entities Perspective: Focuses on entities, allowing observation of simple knowledge based on defined filters and criteria. The count will be based on entities only.
  • Knowledge Graph Perspective: Concentrates on relationships, displaying intricate knowledge derived from relationships between entities and specified filters. The count will be based on relations only.
  • Activity & History Perspective: Centers on activities within the platform, not the knowledge content. This perspective is valuable for monitoring user and connector activities, evaluating data sources, and more.

"},{"location":"usage/widgets/#3-filters","title":"3. Filters","text":""},{"location":"usage/widgets/#generic-knowledge","title":"Generic knowledge","text":"

Filters vary based on the selected perspective, defining the dataset to be utilized in the widget. Filters are instrumental in narrowing down the scope of data for a more focused analysis.

While filters in the \"Entities\" and \"Activity & History\" perspectives align with the platform's familiar search and feed creation filters, the \"Knowledge Graph\" perspective introduces a more intricate filter configuration.Therefore, they need to be addressed in more detail.

"},{"location":"usage/widgets/#filter-in-the-context-of-knowledge-graph","title":"Filter in the context of Knowledge Graph","text":"

Two types of filters are available in the Knowledge Graph perspective:

  • Main query filter

    • Classic filters (gray): Define the relationships to be retrieved, forming the basis on which the widget displays data. Remember, statistics in the Knowledge Graph perspective are based on relationships.

  • Pre-query filters

    • Pre-query filters are used to provide to your main query a specific dataset. In other words, instead of making a query on the whole data set of your platform, you can already target a subset of data that will match certain criteria. They are two types of pre-query filters:
      • Dynamic filters on the source (orange): Refine data by filtering on entities positioned as the source (in the \"from\" position) of the relationship.
      • Dynamic filters on the target (green): Refine data by filtering on entities positioned as the target (in the \"to\" position) of the relationship.

Pre-query limitation

The pre-query is limited to 5000 results. If your pre-query results in having more than 5000 results, your widget will only display statistics based on these 5000 results matching your pre-query, resulting in a wrong view. To avoid this issue, be specific in your pre-query filters.

Example scenario:

Let's consider an example scenario: Analyzing the initial access attack patterns used by intrusion sets targeting the finance sector.

  1. Classic filters: Define the relationships associated with the use of attack patterns by intrusion sets
  2. Dynamic filters on the source (Orange): Narrow down the data by filtering on intrusion sets targeting the finance sector.
  3. Dynamic filters on the target (Green): Narrow down the data by filtering on attack patterns associated with the kill chain's initial access phase.

By leveraging these advanced filters, users can conduct detailed analyses within the Knowledge Graph perspective, unlocking insights that are crucial for understanding intricate relationships and statistics.

In certain views, you can access buttons like +, + Relationships, or + Entities. These buttons enable you to incorporate different data into the same widget for comparative analysis. For instance, in a Line view, adding a second set of filters will display two curves in the widget, each corresponding to one of the filtered data sets. Depending on the view, you can work with 1 to 5 sets of filters. The Label field allows you to name a data set, and this label can then be shown as a legend in the widget using the Display legend button in the widget parameters (see the next section).

"},{"location":"usage/widgets/#4-parameters","title":"4. Parameters","text":"

Parameters depend on the chosen visualization and allow users to define widget titles, choose displayed elements from the filtered data, select data reference date, and configure various other parameters specific to each visualization.

For the \"Knowledge Graph\" perspective, a critical parameter is the Display the source toggle. This feature empowers users to choose whether the widget displays entities from the source side or the target side of the relationships.

  • Toggle ON (\"Display the source\"): The widget focuses on entities positioned as the source of the relationships (in the \"from\" position).
  • Toggle OFF (\"Display the target\"): The widget shifts its focus to entities positioned as the target of the relationships (in the \"to\" position).

This level of control ensures that your dashboard aligns precisely with your analytical objectives, offering a tailored perspective based on your data and relationship.

"},{"location":"usage/widgets/#prerequisite-knowledge","title":"Prerequisite knowledge","text":"

To successfully configure widgets in OpenCTI, having a solid understanding of the platform's data modeling is essential. Knowing specific relationships, entities, and their attributes helps refine filters accurately. Let's explore two examples.

Scenarios 1:

Consider the scenario where you aim to visualize relationships between intrusion sets and attack patterns. In this case, the relevant relationship type connecting intrusion sets to attack patterns is labeled as \"Uses\" (as illustrated in the \"Filters\" section).

Scenarios 2:

Suppose your goal is to retrieve all reports associated with the finance sector. In this case, it's essential to use the correct filter for the finance sector. Instead of placing the finance sector in the \"Related entity\" filter, it should be placed in the \"Contains\" filter. Since a Report is a container object (like Cases and Groupings), it contains entities within it and is not related to entities.

"},{"location":"usage/widgets/#key-data-modeling-aspects","title":"Key data modeling aspects","text":"
  • Entities: Recognizing container (e.g. Reports, Cases and Groupings) and understanding the difference with non-container.
  • Relationships: Identifying the relationship types connecting entities.
  • Attributes: Understanding entities and relationships attributes for effective filtering.

Having this prerequisite knowledge allows you to navigate the widget configuration process seamlessly, ensuring accurate and insightful visualizations based on your specific data requirements.

"},{"location":"usage/workbench/","title":"Analyst workbench","text":"

Workbenches serve as dedicated workspaces for manipulating data before it is officially imported into the platform.

"},{"location":"usage/workbench/#location-of-use","title":"Location of use","text":"

The workbenches are located at various places within the platform:

"},{"location":"usage/workbench/#data-import-and-analyst-workbenches-window","title":"Data import and analyst workbenches window","text":"

This window encompasses all the necessary tools for importing a file. Files imported through this interface will subsequently be processed by the import connectors, resulting in the creation of workbenches. Additionally, analysts can manually create a workbench by clicking on the \"+\" icon at the bottom right of the window.

"},{"location":"usage/workbench/#data-tabs-of-all-entities","title":"Data tabs of all entities","text":"

Workbenches are also accessible through the \"Data\" tabs of entities, providing convenient access to import data associated with the entity.

"},{"location":"usage/workbench/#operation","title":"Operation","text":"

Workbenches are automatically generated upon the import of a file through an import connector. When an import connector is initiated, it scans files for recognizable entities and subsequently creates a workbench. All identified entities are placed within this workbench for analyst reviews. Alternatively, analysts have the option to manually create a workbench by clicking on the \"+\" icon at the bottom right of the \"Data import and analyst workbenches\" window.

The workbench being a draft space, the analysts use it to review connector proposals before finalizing them for import. Within the workbench, analysts have the flexibility to add, delete, or modify entities to meet specific requirements.

Once the content within the workbench is deemed acceptable, the analyst must initiate the ingestion process by clicking on Validate this workbench. This action signifies writing the data in the knowledge base.

Workbenches are drafting spaces

Until the workbench is validated, the contained data remains in draft form and is not recorded in the knowledge base. This ensures that only reviewed and approved data is officially integrated into the platform.

For more information on importing files, refer to the Import from files documentation page.

Confidence level of created knowledge through workbench

The confidence level of knowledge created through workbench is affected by the confidence level of the user. Please navigate to this page to understand in more details.

"},{"location":"usage/workflows/","title":"Workflows and assignation","text":"

Efficiently manage and organize your work within the OpenCTI platform by leveraging workflows and assignment. These capabilities provide a structured approach to tracking the status of objects and assigning responsibilities to users.

"},{"location":"usage/workflows/#workflows","title":"Workflows","text":"

Workflows are designed to trace the status of objects in the system. They are represented by the \"Processing status\" field embedded in each object. By default, this field is disabled for most objects but can be activated through the platform settings. For details on activating and configuring workflows, refer to the dedicated documentation page.

Enabling workflows enhances visibility into the progress and status of different objects, providing a comprehensive view for effective management.

"},{"location":"usage/workflows/#assignment-attributes","title":"Assignment attributes","text":"

Certain objects, including Reports, Cases, and Tasks, come equipped with \"Assignees\" and \"Participants\" attributes. These attributes serve the purpose of designating individuals responsible for the object and those who actively participate in it.

Attributes can be set as mandatory or with default values, streamlining the assignment process. Users can also be assigned or designated as participants manually, contributing to a collaborative and organized workflow. For details on configuring attributes, refer to the dedicated documentation page.

Users can stay informed about assignments through notification triggers. By setting up notification triggers, users receive alerts when an object is assigned to them. This ensures timely communication and proactive engagement with assigned tasks or responsibilities.

"}]} \ No newline at end of file diff --git a/6.2.18/sitemap.xml b/6.2.18/sitemap.xml deleted file mode 100755 index f20dba3a..00000000 --- a/6.2.18/sitemap.xml +++ /dev/null @@ -1,371 +0,0 @@ - - - - https://docs.opencti.io/latest/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/csv-mappers/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/decay-rules/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/enterprise/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/entities/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/file-indexing/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/introduction/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/merging/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/notifier-samples/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/notifiers/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/ontologies/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/organization-segregation/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/parameters/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/policies/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/reasoning/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/retentions/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/segregation/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/support-package/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/users/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/audit/configuration/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/audit/events/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/audit/overview/ - 2024-09-07 - - - https://docs.opencti.io/latest/administration/audit/triggers/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/authentication/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/breaking-changes/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/clustering/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/configuration/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/connectors/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/installation/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/integrations/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/managers/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/map/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/overview/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/resources/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/rollover/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/troubleshooting/ - 2024-09-07 - - - https://docs.opencti.io/latest/deployment/upgrade/ - 2024-09-07 - - - https://docs.opencti.io/latest/development/api-usage/ - 2024-09-07 - - - https://docs.opencti.io/latest/development/connectors/ - 2024-09-07 - - - https://docs.opencti.io/latest/development/environment_ubuntu/ - 2024-09-07 - - - https://docs.opencti.io/latest/development/environment_windows/ - 2024-09-07 - - - https://docs.opencti.io/latest/development/platform/ - 2024-09-07 - - - https://docs.opencti.io/latest/development/python/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/api/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/data-intelligence/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/data-model/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/filters-migration/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/filters/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/fips/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/streaming/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/taxonomy/ - 2024-09-07 - - - https://docs.opencti.io/latest/reference/usage-telemetry/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/ask-ai/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/automation/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/background-tasks/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/case-management/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/containers/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/dashboards-share/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/dashboards/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/data-model/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/dates/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/deduplication/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/delete-restore/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/enrichment/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-analysis/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-arsenal/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-cases/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-entities/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-events/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-locations/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-observations/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-techniques/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/exploring-threats/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/export/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/feeds/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/getting-started/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/import-automated/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/import-files/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/indicators-lifecycle/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/inferences/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/manual-creation/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/merging/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/nested/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/notifications/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/overview/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/pivoting/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/reliability-confidence/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/search/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/tips-widget-creation/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/widgets/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/workbench/ - 2024-09-07 - - - https://docs.opencti.io/latest/usage/workflows/ - 2024-09-07 - - \ No newline at end of file diff --git a/6.2.18/sitemap.xml.gz b/6.2.18/sitemap.xml.gz deleted file mode 100755 index beb04cee..00000000 Binary files a/6.2.18/sitemap.xml.gz and /dev/null differ diff --git a/6.2.18/usage/ask-ai/index.html b/6.2.18/usage/ask-ai/index.html deleted file mode 100755 index dd16f43f..00000000 --- a/6.2.18/usage/ask-ai/index.html +++ /dev/null @@ -1,4232 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ask AI - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Ask AI

-
-

Enterprise edition

-

Ask AI is available under the "OpenCTI Enterprise Edition" license.

-

Please read the dedicated page to have all information

-
-

Prerequisites for using Ask AI

-

There are several possibilities for Enterprise Edition customers to use OpenCTI AI endpoints:

-
    -
  • Use the Filigran AI Service leveraging our custom AI model using the token given by the support team.
    • -
  • Use OpenAI or MistralAI cloud endpoints using your own tokens.
    • -
  • Deploy or use local AI endpoints (Filigran can provide you with the custom model).
    • -
-

Please read the configuration documentation

-
-

Beta Feature

-

Ask AI is a beta feature as we are currently fine-tuning our models. Consider checking important information.

-
-

How it works

-

Even if in the future, we would like to leverage AI to do RAG, for the moment we are mostly using AI to analyze and produce texts or images, based on data directly sent into the prompt.

-

This means that if you are using Filigran AI endpoint or a local one, your data is never used to re-train or adapt the model and everything relies on a pre-trained and fixed model. When using the Ask AI button in the platform, a prompt is generated with the proper instruction to generate the expected result and use it in the context of the button (in forms, rich text editor etc.).

-

Filigran custom model

-

We are hosting a scalable AI endpoint for all SaaS or On-Prem enterprise edition customers, this endpoint is based on MistralAI with a model that will be adapted over time to be more effective when processing threat intelligence related contents.

-

The model, which is still in beta version, will be adapted in the upcoming months to reach maturity at the end of 2024. It can be shared with on-prem enterprise edition customers under NDA.

-

Functionalities of Ask AI

-

Ask AI is represented by a dedicated icon wherever on of its functionalities is available to use.

-

Create a new playbook

-

Assistance for writing meaningful content

-

Ask AI can assist you for writing better textual content, for example better title, name, description and detailed content of Objects.

-
    -
  • Fix spelling & grammar: try to improve the text from a formulation and grammar perspective.
    • -
  • Make it shorter/longer: try to shorten or lengthen the text.
    • -
  • Change tone: try to change the tone of the text. You can select if you want the text to be written for Strategic (Management, decision makers), Tactical (for team leaders) or Operational (for technical CTI analysts) audiences.
    • -
  • Summarize: try to summarize the text in bullet points.
    • -
  • Explain: try to explain the context of the subject's text based on what is available to the LLM.
    • -
-

Assistance for importing data from documents

-

Fom the Content tab of a Container (Reports, Groupings and Cases), Ask AI can also assist you for importing data contained in uploaded documents into OpenCTI for further exploitation.

-
    -
  • Generate report document: Generate a text report based on the knowledge graph (entities and relationships) of this container.
    • -
  • Summarize associated files: Generate a summary of the selected files (or all files associated to this container).
    • -
  • Try to convert the selected files (or all files associated to this container) in a STIX 2.1 bundle you will then be able to use at your convenience (for example importing it into the platform).
    • -
-

Generating report with Ask AI

-

Example of a generated content

-

A short video on the FiligranHQ YouTube channel presents tha capabilities of AskAI: https://www.youtube.com/watch?v=lsP3VVsk5ds.

-

Improving generated elements of Ask AI

-

Be aware that the text quality is highly dependent on the capabilities of the associated LLM.

-

That is why every generated text by Ask AI is provided in a dedicated panel, allowing you to verify and rectify any error the LLM could have made.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/assets/Generate_an_export_panel.png b/6.2.18/usage/assets/Generate_an_export_panel.png deleted file mode 100755 index a9853f61..00000000 Binary files a/6.2.18/usage/assets/Generate_an_export_panel.png and /dev/null differ diff --git a/6.2.18/usage/assets/advanced-search.png b/6.2.18/usage/assets/advanced-search.png deleted file mode 100755 index 40affb97..00000000 Binary files a/6.2.18/usage/assets/advanced-search.png and /dev/null differ diff --git a/6.2.18/usage/assets/analyses-graphview.png b/6.2.18/usage/assets/analyses-graphview.png deleted file mode 100755 index 45315f60..00000000 Binary files a/6.2.18/usage/assets/analyses-graphview.png and /dev/null differ diff --git a/6.2.18/usage/assets/analysis-default-page.png b/6.2.18/usage/assets/analysis-default-page.png deleted file mode 100755 index 35e8bf52..00000000 Binary files a/6.2.18/usage/assets/analysis-default-page.png and /dev/null differ diff --git a/6.2.18/usage/assets/analysis.png b/6.2.18/usage/assets/analysis.png deleted file mode 100755 index 5316d447..00000000 Binary files a/6.2.18/usage/assets/analysis.png and /dev/null differ diff --git a/6.2.18/usage/assets/apt41_knowledge_view.png b/6.2.18/usage/assets/apt41_knowledge_view.png deleted file mode 100755 index 8c164b08..00000000 Binary files a/6.2.18/usage/assets/apt41_knowledge_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/areas_list_view.png b/6.2.18/usage/assets/areas_list_view.png deleted file mode 100755 index 74b75508..00000000 Binary files a/6.2.18/usage/assets/areas_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/artefact_overview.png b/6.2.18/usage/assets/artefact_overview.png deleted file mode 100755 index c21af036..00000000 Binary files a/6.2.18/usage/assets/artefact_overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/artefacts-list-view.png b/6.2.18/usage/assets/artefacts-list-view.png deleted file mode 100755 index 4c3fc16a..00000000 Binary files a/6.2.18/usage/assets/artefacts-list-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/askai_generatedcontent.png b/6.2.18/usage/assets/askai_generatedcontent.png deleted file mode 100755 index 927945fa..00000000 Binary files a/6.2.18/usage/assets/askai_generatedcontent.png and /dev/null differ diff --git a/6.2.18/usage/assets/askai_generatereport.png b/6.2.18/usage/assets/askai_generatereport.png deleted file mode 100755 index 9f6b8627..00000000 Binary files a/6.2.18/usage/assets/askai_generatereport.png and /dev/null differ diff --git a/6.2.18/usage/assets/askai_icon.png b/6.2.18/usage/assets/askai_icon.png deleted file mode 100755 index 8bf19269..00000000 Binary files a/6.2.18/usage/assets/askai_icon.png and /dev/null differ diff --git a/6.2.18/usage/assets/assignment-attributes.png b/6.2.18/usage/assets/assignment-attributes.png deleted file mode 100755 index 65753437..00000000 Binary files a/6.2.18/usage/assets/assignment-attributes.png and /dev/null differ diff --git a/6.2.18/usage/assets/background-tasks.png b/6.2.18/usage/assets/background-tasks.png deleted file mode 100755 index a882b4da..00000000 Binary files a/6.2.18/usage/assets/background-tasks.png and /dev/null differ diff --git a/6.2.18/usage/assets/basic.png b/6.2.18/usage/assets/basic.png deleted file mode 100755 index 710e4284..00000000 Binary files a/6.2.18/usage/assets/basic.png and /dev/null differ diff --git a/6.2.18/usage/assets/bulk-result.png b/6.2.18/usage/assets/bulk-result.png deleted file mode 100755 index f956c99a..00000000 Binary files a/6.2.18/usage/assets/bulk-result.png and /dev/null differ diff --git a/6.2.18/usage/assets/bulk-search.png b/6.2.18/usage/assets/bulk-search.png deleted file mode 100755 index 82bdafd1..00000000 Binary files a/6.2.18/usage/assets/bulk-search.png and /dev/null differ diff --git a/6.2.18/usage/assets/campaigns-cards.png b/6.2.18/usage/assets/campaigns-cards.png deleted file mode 100755 index 13ef27e1..00000000 Binary files a/6.2.18/usage/assets/campaigns-cards.png and /dev/null differ diff --git a/6.2.18/usage/assets/cards-threat-group.png b/6.2.18/usage/assets/cards-threat-group.png deleted file mode 100755 index 991a6857..00000000 Binary files a/6.2.18/usage/assets/cards-threat-group.png and /dev/null differ diff --git a/6.2.18/usage/assets/case-applying-template.png b/6.2.18/usage/assets/case-applying-template.png deleted file mode 100755 index 5419b306..00000000 Binary files a/6.2.18/usage/assets/case-applying-template.png and /dev/null differ diff --git a/6.2.18/usage/assets/case-content-mapping.png b/6.2.18/usage/assets/case-content-mapping.png deleted file mode 100755 index afc615b1..00000000 Binary files a/6.2.18/usage/assets/case-content-mapping.png and /dev/null differ diff --git a/6.2.18/usage/assets/case-graph.png b/6.2.18/usage/assets/case-graph.png deleted file mode 100755 index a2fc85ec..00000000 Binary files a/6.2.18/usage/assets/case-graph.png and /dev/null differ diff --git a/6.2.18/usage/assets/case-opinion.png b/6.2.18/usage/assets/case-opinion.png deleted file mode 100755 index 4994e0ca..00000000 Binary files a/6.2.18/usage/assets/case-opinion.png and /dev/null differ diff --git a/6.2.18/usage/assets/case-timeline.png b/6.2.18/usage/assets/case-timeline.png deleted file mode 100755 index 46768cf4..00000000 Binary files a/6.2.18/usage/assets/case-timeline.png and /dev/null differ diff --git a/6.2.18/usage/assets/cases-default-landing-page.png b/6.2.18/usage/assets/cases-default-landing-page.png deleted file mode 100755 index 0165f697..00000000 Binary files a/6.2.18/usage/assets/cases-default-landing-page.png and /dev/null differ diff --git a/6.2.18/usage/assets/cases-list.png b/6.2.18/usage/assets/cases-list.png deleted file mode 100755 index 668123d7..00000000 Binary files a/6.2.18/usage/assets/cases-list.png and /dev/null differ diff --git a/6.2.18/usage/assets/cases-observables.png b/6.2.18/usage/assets/cases-observables.png deleted file mode 100755 index 15c4b327..00000000 Binary files a/6.2.18/usage/assets/cases-observables.png and /dev/null differ diff --git a/6.2.18/usage/assets/channels_list_view.png b/6.2.18/usage/assets/channels_list_view.png deleted file mode 100755 index e1d968cb..00000000 Binary files a/6.2.18/usage/assets/channels_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/cities_list_view.png b/6.2.18/usage/assets/cities_list_view.png deleted file mode 100755 index ff2e5279..00000000 Binary files a/6.2.18/usage/assets/cities_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/confidence-level-customization.png b/6.2.18/usage/assets/confidence-level-customization.png deleted file mode 100755 index 490b2957..00000000 Binary files a/6.2.18/usage/assets/confidence-level-customization.png and /dev/null differ diff --git a/6.2.18/usage/assets/container-filters.png b/6.2.18/usage/assets/container-filters.png deleted file mode 100755 index a72dc54e..00000000 Binary files a/6.2.18/usage/assets/container-filters.png and /dev/null differ diff --git a/6.2.18/usage/assets/contextual-search.png b/6.2.18/usage/assets/contextual-search.png deleted file mode 100755 index 7fbb2d53..00000000 Binary files a/6.2.18/usage/assets/contextual-search.png and /dev/null differ diff --git a/6.2.18/usage/assets/countries_list_view.png b/6.2.18/usage/assets/countries_list_view.png deleted file mode 100755 index 66789368..00000000 Binary files a/6.2.18/usage/assets/countries_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/create-relationship.png b/6.2.18/usage/assets/create-relationship.png deleted file mode 100755 index 584416d5..00000000 Binary files a/6.2.18/usage/assets/create-relationship.png and /dev/null differ diff --git a/6.2.18/usage/assets/create-report.png b/6.2.18/usage/assets/create-report.png deleted file mode 100755 index 29ecc044..00000000 Binary files a/6.2.18/usage/assets/create-report.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feed.png b/6.2.18/usage/assets/csv-feed.png deleted file mode 100755 index 74ca862f..00000000 Binary files a/6.2.18/usage/assets/csv-feed.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feeds-connectors.png b/6.2.18/usage/assets/csv-feeds-connectors.png deleted file mode 100755 index 0ca51e31..00000000 Binary files a/6.2.18/usage/assets/csv-feeds-connectors.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feeds-creation-after-test.png b/6.2.18/usage/assets/csv-feeds-creation-after-test.png deleted file mode 100755 index ea045078..00000000 Binary files a/6.2.18/usage/assets/csv-feeds-creation-after-test.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feeds-creation-csv-mapper.png b/6.2.18/usage/assets/csv-feeds-creation-csv-mapper.png deleted file mode 100755 index cd65c45d..00000000 Binary files a/6.2.18/usage/assets/csv-feeds-creation-csv-mapper.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feeds-creation-list.png b/6.2.18/usage/assets/csv-feeds-creation-list.png deleted file mode 100755 index af3bff31..00000000 Binary files a/6.2.18/usage/assets/csv-feeds-creation-list.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feeds-creation-prior-test.png b/6.2.18/usage/assets/csv-feeds-creation-prior-test.png deleted file mode 100755 index 2ed14ac9..00000000 Binary files a/6.2.18/usage/assets/csv-feeds-creation-prior-test.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feeds-creation-start.png b/6.2.18/usage/assets/csv-feeds-creation-start.png deleted file mode 100755 index 0d83db08..00000000 Binary files a/6.2.18/usage/assets/csv-feeds-creation-start.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feeds-creation-test.png b/6.2.18/usage/assets/csv-feeds-creation-test.png deleted file mode 100755 index db29af05..00000000 Binary files a/6.2.18/usage/assets/csv-feeds-creation-test.png and /dev/null differ diff --git a/6.2.18/usage/assets/csv-feeds-importCSV-connector-tracking.png b/6.2.18/usage/assets/csv-feeds-importCSV-connector-tracking.png deleted file mode 100755 index 6e49c6c6..00000000 Binary files a/6.2.18/usage/assets/csv-feeds-importCSV-connector-tracking.png and /dev/null differ diff --git a/6.2.18/usage/assets/custom-notifiers.png b/6.2.18/usage/assets/custom-notifiers.png deleted file mode 100755 index d9664c24..00000000 Binary files a/6.2.18/usage/assets/custom-notifiers.png and /dev/null differ diff --git a/6.2.18/usage/assets/customize_your_export.png b/6.2.18/usage/assets/customize_your_export.png deleted file mode 100755 index 465ad961..00000000 Binary files a/6.2.18/usage/assets/customize_your_export.png and /dev/null differ diff --git a/6.2.18/usage/assets/dashboard-overview.png b/6.2.18/usage/assets/dashboard-overview.png deleted file mode 100755 index ebff2899..00000000 Binary files a/6.2.18/usage/assets/dashboard-overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/dashboard.png b/6.2.18/usage/assets/dashboard.png deleted file mode 100755 index c984fffb..00000000 Binary files a/6.2.18/usage/assets/dashboard.png and /dev/null differ diff --git a/6.2.18/usage/assets/data-import-and-workbenches.png b/6.2.18/usage/assets/data-import-and-workbenches.png deleted file mode 100755 index 84f76a9e..00000000 Binary files a/6.2.18/usage/assets/data-import-and-workbenches.png and /dev/null differ diff --git a/6.2.18/usage/assets/dates.png b/6.2.18/usage/assets/dates.png deleted file mode 100755 index f1a0801b..00000000 Binary files a/6.2.18/usage/assets/dates.png and /dev/null differ diff --git a/6.2.18/usage/assets/details.png b/6.2.18/usage/assets/details.png deleted file mode 100755 index f48d2d3f..00000000 Binary files a/6.2.18/usage/assets/details.png and /dev/null differ diff --git a/6.2.18/usage/assets/digest-creation.png b/6.2.18/usage/assets/digest-creation.png deleted file mode 100755 index 617232a2..00000000 Binary files a/6.2.18/usage/assets/digest-creation.png and /dev/null differ diff --git a/6.2.18/usage/assets/duplicate-dashboard-button.png b/6.2.18/usage/assets/duplicate-dashboard-button.png deleted file mode 100755 index c1400b66..00000000 Binary files a/6.2.18/usage/assets/duplicate-dashboard-button.png and /dev/null differ diff --git a/6.2.18/usage/assets/duplicate-dashboard-success-message.png b/6.2.18/usage/assets/duplicate-dashboard-success-message.png deleted file mode 100755 index c799021d..00000000 Binary files a/6.2.18/usage/assets/duplicate-dashboard-success-message.png and /dev/null differ diff --git a/6.2.18/usage/assets/enrichment-button.png b/6.2.18/usage/assets/enrichment-button.png deleted file mode 100755 index cd488084..00000000 Binary files a/6.2.18/usage/assets/enrichment-button.png and /dev/null differ diff --git a/6.2.18/usage/assets/enrichment-panel.png b/6.2.18/usage/assets/enrichment-panel.png deleted file mode 100755 index 479f999d..00000000 Binary files a/6.2.18/usage/assets/enrichment-panel.png and /dev/null differ diff --git a/6.2.18/usage/assets/entities-to-link.png b/6.2.18/usage/assets/entities-to-link.png deleted file mode 100755 index d5398de3..00000000 Binary files a/6.2.18/usage/assets/entities-to-link.png and /dev/null differ diff --git a/6.2.18/usage/assets/entities.png b/6.2.18/usage/assets/entities.png deleted file mode 100755 index ab1da1bb..00000000 Binary files a/6.2.18/usage/assets/entities.png and /dev/null differ diff --git a/6.2.18/usage/assets/entity-content-tab.png b/6.2.18/usage/assets/entity-content-tab.png deleted file mode 100755 index f3e29d7a..00000000 Binary files a/6.2.18/usage/assets/entity-content-tab.png and /dev/null differ diff --git a/6.2.18/usage/assets/entity-data-tab.png b/6.2.18/usage/assets/entity-data-tab.png deleted file mode 100755 index 9865587e..00000000 Binary files a/6.2.18/usage/assets/entity-data-tab.png and /dev/null differ diff --git a/6.2.18/usage/assets/entity-reliability-confidence.png b/6.2.18/usage/assets/entity-reliability-confidence.png deleted file mode 100755 index 03e3b5a6..00000000 Binary files a/6.2.18/usage/assets/entity-reliability-confidence.png and /dev/null differ diff --git a/6.2.18/usage/assets/entity_analysis-tab.png b/6.2.18/usage/assets/entity_analysis-tab.png deleted file mode 100755 index 68f2a2fe..00000000 Binary files a/6.2.18/usage/assets/entity_analysis-tab.png and /dev/null differ diff --git a/6.2.18/usage/assets/events_list_view.png b/6.2.18/usage/assets/events_list_view.png deleted file mode 100755 index 02bdd0f7..00000000 Binary files a/6.2.18/usage/assets/events_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/example-admiralty-code.png b/6.2.18/usage/assets/example-admiralty-code.png deleted file mode 100755 index 17e0aae0..00000000 Binary files a/6.2.18/usage/assets/example-admiralty-code.png and /dev/null differ diff --git a/6.2.18/usage/assets/example-objective-scale.png b/6.2.18/usage/assets/example-objective-scale.png deleted file mode 100755 index 6a635984..00000000 Binary files a/6.2.18/usage/assets/example-objective-scale.png and /dev/null differ diff --git a/6.2.18/usage/assets/export-dashboard-option.png b/6.2.18/usage/assets/export-dashboard-option.png deleted file mode 100755 index f8dac700..00000000 Binary files a/6.2.18/usage/assets/export-dashboard-option.png and /dev/null differ diff --git a/6.2.18/usage/assets/export-json-button.png b/6.2.18/usage/assets/export-json-button.png deleted file mode 100755 index 86eb6813..00000000 Binary files a/6.2.18/usage/assets/export-json-button.png and /dev/null differ diff --git a/6.2.18/usage/assets/export-widget-option.png b/6.2.18/usage/assets/export-widget-option.png deleted file mode 100755 index 69aa3be0..00000000 Binary files a/6.2.18/usage/assets/export-widget-option.png and /dev/null differ diff --git a/6.2.18/usage/assets/export_entity_content.png b/6.2.18/usage/assets/export_entity_content.png deleted file mode 100755 index cfe70e19..00000000 Binary files a/6.2.18/usage/assets/export_entity_content.png and /dev/null differ diff --git a/6.2.18/usage/assets/export_specific_elements.png b/6.2.18/usage/assets/export_specific_elements.png deleted file mode 100755 index 502eebda..00000000 Binary files a/6.2.18/usage/assets/export_specific_elements.png and /dev/null differ diff --git a/6.2.18/usage/assets/export_types.png b/6.2.18/usage/assets/export_types.png deleted file mode 100755 index bde8a3c8..00000000 Binary files a/6.2.18/usage/assets/export_types.png and /dev/null differ diff --git a/6.2.18/usage/assets/exported-files-list.png b/6.2.18/usage/assets/exported-files-list.png deleted file mode 100755 index 60a046f2..00000000 Binary files a/6.2.18/usage/assets/exported-files-list.png and /dev/null differ diff --git a/6.2.18/usage/assets/exports_list.png b/6.2.18/usage/assets/exports_list.png deleted file mode 100755 index 698c36d9..00000000 Binary files a/6.2.18/usage/assets/exports_list.png and /dev/null differ diff --git a/6.2.18/usage/assets/feed-access-restriction.png b/6.2.18/usage/assets/feed-access-restriction.png deleted file mode 100755 index 839f7450..00000000 Binary files a/6.2.18/usage/assets/feed-access-restriction.png and /dev/null differ diff --git a/6.2.18/usage/assets/feedback-overview.png b/6.2.18/usage/assets/feedback-overview.png deleted file mode 100755 index e094fe64..00000000 Binary files a/6.2.18/usage/assets/feedback-overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/feedbacks_list.png b/6.2.18/usage/assets/feedbacks_list.png deleted file mode 100755 index e483cc49..00000000 Binary files a/6.2.18/usage/assets/feedbacks_list.png and /dev/null differ diff --git a/6.2.18/usage/assets/filter-source-reliability.png b/6.2.18/usage/assets/filter-source-reliability.png deleted file mode 100755 index 74059a2e..00000000 Binary files a/6.2.18/usage/assets/filter-source-reliability.png and /dev/null differ diff --git a/6.2.18/usage/assets/filter-to-delete.png b/6.2.18/usage/assets/filter-to-delete.png deleted file mode 100755 index 98989c2e..00000000 Binary files a/6.2.18/usage/assets/filter-to-delete.png and /dev/null differ diff --git a/6.2.18/usage/assets/global-import-panel.png b/6.2.18/usage/assets/global-import-panel.png deleted file mode 100755 index 64923566..00000000 Binary files a/6.2.18/usage/assets/global-import-panel.png and /dev/null differ diff --git a/6.2.18/usage/assets/global-search-files.png b/6.2.18/usage/assets/global-search-files.png deleted file mode 100755 index 67cd5bd4..00000000 Binary files a/6.2.18/usage/assets/global-search-files.png and /dev/null differ diff --git a/6.2.18/usage/assets/graph.png b/6.2.18/usage/assets/graph.png deleted file mode 100755 index f19549fb..00000000 Binary files a/6.2.18/usage/assets/graph.png and /dev/null differ diff --git a/6.2.18/usage/assets/group-confidence-overrides.png b/6.2.18/usage/assets/group-confidence-overrides.png deleted file mode 100755 index 5ffe719c..00000000 Binary files a/6.2.18/usage/assets/group-confidence-overrides.png and /dev/null differ diff --git a/6.2.18/usage/assets/hide-global.png b/6.2.18/usage/assets/hide-global.png deleted file mode 100755 index 5cf22487..00000000 Binary files a/6.2.18/usage/assets/hide-global.png and /dev/null differ diff --git a/6.2.18/usage/assets/hide-roles.png b/6.2.18/usage/assets/hide-roles.png deleted file mode 100755 index a99276a6..00000000 Binary files a/6.2.18/usage/assets/hide-roles.png and /dev/null differ diff --git a/6.2.18/usage/assets/history.png b/6.2.18/usage/assets/history.png deleted file mode 100755 index 20034bd6..00000000 Binary files a/6.2.18/usage/assets/history.png and /dev/null differ diff --git a/6.2.18/usage/assets/import-dashboard-option.png b/6.2.18/usage/assets/import-dashboard-option.png deleted file mode 100755 index 4f20a9b4..00000000 Binary files a/6.2.18/usage/assets/import-dashboard-option.png and /dev/null differ diff --git a/6.2.18/usage/assets/import-widget-option.png b/6.2.18/usage/assets/import-widget-option.png deleted file mode 100755 index 68549c66..00000000 Binary files a/6.2.18/usage/assets/import-widget-option.png and /dev/null differ diff --git a/6.2.18/usage/assets/incident_overview.png b/6.2.18/usage/assets/incident_overview.png deleted file mode 100755 index 88a9fc4f..00000000 Binary files a/6.2.18/usage/assets/incident_overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/incidents_list_view.png b/6.2.18/usage/assets/incidents_list_view.png deleted file mode 100755 index ca138d11..00000000 Binary files a/6.2.18/usage/assets/incidents_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/indicator_overview.png b/6.2.18/usage/assets/indicator_overview.png deleted file mode 100755 index c1a7ca60..00000000 Binary files a/6.2.18/usage/assets/indicator_overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/indicators-lifecycle-example-dialog.png b/6.2.18/usage/assets/indicators-lifecycle-example-dialog.png deleted file mode 100755 index 48086bc0..00000000 Binary files a/6.2.18/usage/assets/indicators-lifecycle-example-dialog.png and /dev/null differ diff --git a/6.2.18/usage/assets/indicators-lifecycle-example-overview.png b/6.2.18/usage/assets/indicators-lifecycle-example-overview.png deleted file mode 100755 index 1839762f..00000000 Binary files a/6.2.18/usage/assets/indicators-lifecycle-example-overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/indicators-list-view.png b/6.2.18/usage/assets/indicators-list-view.png deleted file mode 100755 index 44eb2c55..00000000 Binary files a/6.2.18/usage/assets/indicators-list-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/individuals_list_view.png b/6.2.18/usage/assets/individuals_list_view.png deleted file mode 100755 index d19679a7..00000000 Binary files a/6.2.18/usage/assets/individuals_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/inferred-rel-in-graph.png b/6.2.18/usage/assets/inferred-rel-in-graph.png deleted file mode 100755 index 3f13c489..00000000 Binary files a/6.2.18/usage/assets/inferred-rel-in-graph.png and /dev/null differ diff --git a/6.2.18/usage/assets/inferred-rel-in-list.png b/6.2.18/usage/assets/inferred-rel-in-list.png deleted file mode 100755 index f62afb8f..00000000 Binary files a/6.2.18/usage/assets/inferred-rel-in-list.png and /dev/null differ diff --git a/6.2.18/usage/assets/infrastructures-list-view.png b/6.2.18/usage/assets/infrastructures-list-view.png deleted file mode 100755 index 4b69700d..00000000 Binary files a/6.2.18/usage/assets/infrastructures-list-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/instance-trigger-creation.png b/6.2.18/usage/assets/instance-trigger-creation.png deleted file mode 100755 index 32e0c5a5..00000000 Binary files a/6.2.18/usage/assets/instance-trigger-creation.png and /dev/null differ diff --git a/6.2.18/usage/assets/instrusion-set-cards.png b/6.2.18/usage/assets/instrusion-set-cards.png deleted file mode 100755 index 7b56ab42..00000000 Binary files a/6.2.18/usage/assets/instrusion-set-cards.png and /dev/null differ diff --git a/6.2.18/usage/assets/intrusionset_knowledge_view.png b/6.2.18/usage/assets/intrusionset_knowledge_view.png deleted file mode 100755 index 3edc84ca..00000000 Binary files a/6.2.18/usage/assets/intrusionset_knowledge_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-bottom-right-menu.png b/6.2.18/usage/assets/investigation-bottom-right-menu.png deleted file mode 100755 index affaab63..00000000 Binary files a/6.2.18/usage/assets/investigation-bottom-right-menu.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-create-relationship.png b/6.2.18/usage/assets/investigation-create-relationship.png deleted file mode 100755 index a77c08df..00000000 Binary files a/6.2.18/usage/assets/investigation-create-relationship.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-expand-entity.png b/6.2.18/usage/assets/investigation-expand-entity.png deleted file mode 100755 index 8428cf10..00000000 Binary files a/6.2.18/usage/assets/investigation-expand-entity.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-export.png b/6.2.18/usage/assets/investigation-export.png deleted file mode 100755 index 143d84bf..00000000 Binary files a/6.2.18/usage/assets/investigation-export.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-rollback-popup.png b/6.2.18/usage/assets/investigation-rollback-popup.png deleted file mode 100755 index 38d5e2a6..00000000 Binary files a/6.2.18/usage/assets/investigation-rollback-popup.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-entity-selection-add.png b/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-entity-selection-add.png deleted file mode 100755 index 9a0b89a6..00000000 Binary files a/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-entity-selection-add.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-entity-selection.png b/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-entity-selection.png deleted file mode 100755 index 1cbffba1..00000000 Binary files a/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-entity-selection.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-new-entity-form.png b/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-new-entity-form.png deleted file mode 100755 index 5a805d06..00000000 Binary files a/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-new-entity-form.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-new-entity.png b/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-new-entity.png deleted file mode 100755 index c1c82735..00000000 Binary files a/6.2.18/usage/assets/investigation-turn-to-report-or-case-dialog-new-entity.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-turn-to-report-or-case-success.png b/6.2.18/usage/assets/investigation-turn-to-report-or-case-success.png deleted file mode 100755 index 50022bfd..00000000 Binary files a/6.2.18/usage/assets/investigation-turn-to-report-or-case-success.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-turn-to-report-or-case.png b/6.2.18/usage/assets/investigation-turn-to-report-or-case.png deleted file mode 100755 index af349281..00000000 Binary files a/6.2.18/usage/assets/investigation-turn-to-report-or-case.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation-workspace.png b/6.2.18/usage/assets/investigation-workspace.png deleted file mode 100755 index 8b725128..00000000 Binary files a/6.2.18/usage/assets/investigation-workspace.png and /dev/null differ diff --git a/6.2.18/usage/assets/investigation.png b/6.2.18/usage/assets/investigation.png deleted file mode 100755 index fde57825..00000000 Binary files a/6.2.18/usage/assets/investigation.png and /dev/null differ diff --git a/6.2.18/usage/assets/knowledge_focus_indicators_observable_views.png b/6.2.18/usage/assets/knowledge_focus_indicators_observable_views.png deleted file mode 100755 index d140c614..00000000 Binary files a/6.2.18/usage/assets/knowledge_focus_indicators_observable_views.png and /dev/null differ diff --git a/6.2.18/usage/assets/latest_additions.png b/6.2.18/usage/assets/latest_additions.png deleted file mode 100755 index 06ef3157..00000000 Binary files a/6.2.18/usage/assets/latest_additions.png and /dev/null differ diff --git a/6.2.18/usage/assets/live-stream-additional-configuration.png b/6.2.18/usage/assets/live-stream-additional-configuration.png deleted file mode 100755 index d4b526e0..00000000 Binary files a/6.2.18/usage/assets/live-stream-additional-configuration.png and /dev/null differ diff --git a/6.2.18/usage/assets/live-stream-configuration.png b/6.2.18/usage/assets/live-stream-configuration.png deleted file mode 100755 index ef7b7031..00000000 Binary files a/6.2.18/usage/assets/live-stream-configuration.png and /dev/null differ diff --git a/6.2.18/usage/assets/live-stream.png b/6.2.18/usage/assets/live-stream.png deleted file mode 100755 index 17fb2f0b..00000000 Binary files a/6.2.18/usage/assets/live-stream.png and /dev/null differ diff --git a/6.2.18/usage/assets/magic-wand-icon.png b/6.2.18/usage/assets/magic-wand-icon.png deleted file mode 100755 index 703b04b9..00000000 Binary files a/6.2.18/usage/assets/magic-wand-icon.png and /dev/null differ diff --git a/6.2.18/usage/assets/malware_cards_view.png b/6.2.18/usage/assets/malware_cards_view.png deleted file mode 100755 index f932b4e9..00000000 Binary files a/6.2.18/usage/assets/malware_cards_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/malwareanalysis-overview.png b/6.2.18/usage/assets/malwareanalysis-overview.png deleted file mode 100755 index a33003f2..00000000 Binary files a/6.2.18/usage/assets/malwareanalysis-overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/manage-access-button.png b/6.2.18/usage/assets/manage-access-button.png deleted file mode 100755 index 54ef6bd5..00000000 Binary files a/6.2.18/usage/assets/manage-access-button.png and /dev/null differ diff --git a/6.2.18/usage/assets/manage-access-dialog.png b/6.2.18/usage/assets/manage-access-dialog.png deleted file mode 100755 index 0199d533..00000000 Binary files a/6.2.18/usage/assets/manage-access-dialog.png and /dev/null differ diff --git a/6.2.18/usage/assets/manual-import-connectors.png b/6.2.18/usage/assets/manual-import-connectors.png deleted file mode 100755 index 5edc62e8..00000000 Binary files a/6.2.18/usage/assets/manual-import-connectors.png and /dev/null differ diff --git a/6.2.18/usage/assets/menu.png b/6.2.18/usage/assets/menu.png deleted file mode 100755 index 4784d07b..00000000 Binary files a/6.2.18/usage/assets/menu.png and /dev/null differ diff --git a/6.2.18/usage/assets/new-relationship.png b/6.2.18/usage/assets/new-relationship.png deleted file mode 100755 index e1f93d39..00000000 Binary files a/6.2.18/usage/assets/new-relationship.png and /dev/null differ diff --git a/6.2.18/usage/assets/new-report.png b/6.2.18/usage/assets/new-report.png deleted file mode 100755 index 21d7f187..00000000 Binary files a/6.2.18/usage/assets/new-report.png and /dev/null differ diff --git a/6.2.18/usage/assets/notifications.png b/6.2.18/usage/assets/notifications.png deleted file mode 100755 index a304c5d3..00000000 Binary files a/6.2.18/usage/assets/notifications.png and /dev/null differ diff --git a/6.2.18/usage/assets/notifiers.png b/6.2.18/usage/assets/notifiers.png deleted file mode 100755 index 706cf76a..00000000 Binary files a/6.2.18/usage/assets/notifiers.png and /dev/null differ diff --git a/6.2.18/usage/assets/observable_overview.png b/6.2.18/usage/assets/observable_overview.png deleted file mode 100755 index 9b4cb6c4..00000000 Binary files a/6.2.18/usage/assets/observable_overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/observables-list-view.png b/6.2.18/usage/assets/observables-list-view.png deleted file mode 100755 index 9a56e90d..00000000 Binary files a/6.2.18/usage/assets/observables-list-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/open_export_panel.png b/6.2.18/usage/assets/open_export_panel.png deleted file mode 100755 index 29ac497b..00000000 Binary files a/6.2.18/usage/assets/open_export_panel.png and /dev/null differ diff --git a/6.2.18/usage/assets/organization_author_view.png b/6.2.18/usage/assets/organization_author_view.png deleted file mode 100755 index bdca8d96..00000000 Binary files a/6.2.18/usage/assets/organization_author_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/organizations_list_view.png b/6.2.18/usage/assets/organizations_list_view.png deleted file mode 100755 index c35c5a6f..00000000 Binary files a/6.2.18/usage/assets/organizations_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/override-confidence-tooltip.png b/6.2.18/usage/assets/override-confidence-tooltip.png deleted file mode 100755 index 9b499f05..00000000 Binary files a/6.2.18/usage/assets/override-confidence-tooltip.png and /dev/null differ diff --git a/6.2.18/usage/assets/overview-of-workbench.png b/6.2.18/usage/assets/overview-of-workbench.png deleted file mode 100755 index 7f6d98b8..00000000 Binary files a/6.2.18/usage/assets/overview-of-workbench.png and /dev/null differ diff --git a/6.2.18/usage/assets/playbook_components.png b/6.2.18/usage/assets/playbook_components.png deleted file mode 100755 index 4c67de2f..00000000 Binary files a/6.2.18/usage/assets/playbook_components.png and /dev/null differ diff --git a/6.2.18/usage/assets/playbook_create.png b/6.2.18/usage/assets/playbook_create.png deleted file mode 100755 index 6bf84480..00000000 Binary files a/6.2.18/usage/assets/playbook_create.png and /dev/null differ diff --git a/6.2.18/usage/assets/playbook_listen.png b/6.2.18/usage/assets/playbook_listen.png deleted file mode 100755 index c68edb2e..00000000 Binary files a/6.2.18/usage/assets/playbook_listen.png and /dev/null differ diff --git a/6.2.18/usage/assets/playbook_traces.png b/6.2.18/usage/assets/playbook_traces.png deleted file mode 100755 index 13d77d96..00000000 Binary files a/6.2.18/usage/assets/playbook_traces.png and /dev/null differ diff --git a/6.2.18/usage/assets/positions_list_view.png b/6.2.18/usage/assets/positions_list_view.png deleted file mode 100755 index 573a9536..00000000 Binary files a/6.2.18/usage/assets/positions_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/processing-status.png b/6.2.18/usage/assets/processing-status.png deleted file mode 100755 index 76d01b9d..00000000 Binary files a/6.2.18/usage/assets/processing-status.png and /dev/null differ diff --git a/6.2.18/usage/assets/profile_pictures_of_TA.png b/6.2.18/usage/assets/profile_pictures_of_TA.png deleted file mode 100755 index 51b15e31..00000000 Binary files a/6.2.18/usage/assets/profile_pictures_of_TA.png and /dev/null differ diff --git a/6.2.18/usage/assets/profile_pictures_panel.png b/6.2.18/usage/assets/profile_pictures_panel.png deleted file mode 100755 index 6f89ed38..00000000 Binary files a/6.2.18/usage/assets/profile_pictures_panel.png and /dev/null differ diff --git a/6.2.18/usage/assets/quick-subscription-button.png b/6.2.18/usage/assets/quick-subscription-button.png deleted file mode 100755 index f15aefc5..00000000 Binary files a/6.2.18/usage/assets/quick-subscription-button.png and /dev/null differ diff --git a/6.2.18/usage/assets/ref_and_history.png b/6.2.18/usage/assets/ref_and_history.png deleted file mode 100755 index a2bc0f14..00000000 Binary files a/6.2.18/usage/assets/ref_and_history.png and /dev/null differ diff --git a/6.2.18/usage/assets/region_overview.png b/6.2.18/usage/assets/region_overview.png deleted file mode 100755 index 8ee696ca..00000000 Binary files a/6.2.18/usage/assets/region_overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/regions_list_view.png b/6.2.18/usage/assets/regions_list_view.png deleted file mode 100755 index 44e9c1a6..00000000 Binary files a/6.2.18/usage/assets/regions_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/relation-with-container.png b/6.2.18/usage/assets/relation-with-container.png deleted file mode 100755 index 5e08e2d5..00000000 Binary files a/6.2.18/usage/assets/relation-with-container.png and /dev/null differ diff --git a/6.2.18/usage/assets/report-content-mapping-view.png b/6.2.18/usage/assets/report-content-mapping-view.png deleted file mode 100755 index 14b65499..00000000 Binary files a/6.2.18/usage/assets/report-content-mapping-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/report-correlation-view.png b/6.2.18/usage/assets/report-correlation-view.png deleted file mode 100755 index 44e2c61d..00000000 Binary files a/6.2.18/usage/assets/report-correlation-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/report-graph-view.png b/6.2.18/usage/assets/report-graph-view.png deleted file mode 100755 index 28345e7a..00000000 Binary files a/6.2.18/usage/assets/report-graph-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/report-matrix-view.png b/6.2.18/usage/assets/report-matrix-view.png deleted file mode 100755 index 060b9956..00000000 Binary files a/6.2.18/usage/assets/report-matrix-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/report-timeline-view.png b/6.2.18/usage/assets/report-timeline-view.png deleted file mode 100755 index 3b7ef7b6..00000000 Binary files a/6.2.18/usage/assets/report-timeline-view.png and /dev/null differ diff --git a/6.2.18/usage/assets/reset-state-msg.png b/6.2.18/usage/assets/reset-state-msg.png deleted file mode 100755 index 3e0ca878..00000000 Binary files a/6.2.18/usage/assets/reset-state-msg.png and /dev/null differ diff --git a/6.2.18/usage/assets/restricted-trigger.png b/6.2.18/usage/assets/restricted-trigger.png deleted file mode 100755 index a8a8b2c2..00000000 Binary files a/6.2.18/usage/assets/restricted-trigger.png and /dev/null differ diff --git a/6.2.18/usage/assets/rss-feed-configuration.png b/6.2.18/usage/assets/rss-feed-configuration.png deleted file mode 100755 index 25e61fc2..00000000 Binary files a/6.2.18/usage/assets/rss-feed-configuration.png and /dev/null differ diff --git a/6.2.18/usage/assets/schema.png b/6.2.18/usage/assets/schema.png deleted file mode 100755 index c1811586..00000000 Binary files a/6.2.18/usage/assets/schema.png and /dev/null differ diff --git a/6.2.18/usage/assets/search-bar.png b/6.2.18/usage/assets/search-bar.png deleted file mode 100755 index 1a05fbb2..00000000 Binary files a/6.2.18/usage/assets/search-bar.png and /dev/null differ diff --git a/6.2.18/usage/assets/search-filters.png b/6.2.18/usage/assets/search-filters.png deleted file mode 100755 index 597e6328..00000000 Binary files a/6.2.18/usage/assets/search-filters.png and /dev/null differ diff --git a/6.2.18/usage/assets/search-graph.png b/6.2.18/usage/assets/search-graph.png deleted file mode 100755 index f1c026b3..00000000 Binary files a/6.2.18/usage/assets/search-graph.png and /dev/null differ diff --git a/6.2.18/usage/assets/sector_overview.png b/6.2.18/usage/assets/sector_overview.png deleted file mode 100755 index 68eac4a0..00000000 Binary files a/6.2.18/usage/assets/sector_overview.png and /dev/null differ diff --git a/6.2.18/usage/assets/sectors_list_view.png b/6.2.18/usage/assets/sectors_list_view.png deleted file mode 100755 index f2f1c280..00000000 Binary files a/6.2.18/usage/assets/sectors_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/settings-reliability_ov.png b/6.2.18/usage/assets/settings-reliability_ov.png deleted file mode 100755 index 2a3e4a3d..00000000 Binary files a/6.2.18/usage/assets/settings-reliability_ov.png and /dev/null differ diff --git a/6.2.18/usage/assets/share-dashboard-button.png b/6.2.18/usage/assets/share-dashboard-button.png deleted file mode 100755 index 66487cf9..00000000 Binary files a/6.2.18/usage/assets/share-dashboard-button.png and /dev/null differ diff --git a/6.2.18/usage/assets/share-dashboard-enable.png b/6.2.18/usage/assets/share-dashboard-enable.png deleted file mode 100755 index df5563b7..00000000 Binary files a/6.2.18/usage/assets/share-dashboard-enable.png and /dev/null differ diff --git a/6.2.18/usage/assets/share-dashboard-list.png b/6.2.18/usage/assets/share-dashboard-list.png deleted file mode 100755 index 37c05d5d..00000000 Binary files a/6.2.18/usage/assets/share-dashboard-list.png and /dev/null differ diff --git a/6.2.18/usage/assets/share-dashboard-markings.png b/6.2.18/usage/assets/share-dashboard-markings.png deleted file mode 100755 index ee4ca503..00000000 Binary files a/6.2.18/usage/assets/share-dashboard-markings.png and /dev/null differ diff --git a/6.2.18/usage/assets/share-dashboard-name.png b/6.2.18/usage/assets/share-dashboard-name.png deleted file mode 100755 index ce545930..00000000 Binary files a/6.2.18/usage/assets/share-dashboard-name.png and /dev/null differ diff --git a/6.2.18/usage/assets/share-dashboard-panel.png b/6.2.18/usage/assets/share-dashboard-panel.png deleted file mode 100755 index 9ebbdc4e..00000000 Binary files a/6.2.18/usage/assets/share-dashboard-panel.png and /dev/null differ diff --git a/6.2.18/usage/assets/sightings_list.png b/6.2.18/usage/assets/sightings_list.png deleted file mode 100755 index fa5b878d..00000000 Binary files a/6.2.18/usage/assets/sightings_list.png and /dev/null differ diff --git a/6.2.18/usage/assets/stix.png b/6.2.18/usage/assets/stix.png deleted file mode 100755 index 7496c65e..00000000 Binary files a/6.2.18/usage/assets/stix.png and /dev/null differ diff --git a/6.2.18/usage/assets/suggested-mapping.png b/6.2.18/usage/assets/suggested-mapping.png deleted file mode 100755 index 2603aff7..00000000 Binary files a/6.2.18/usage/assets/suggested-mapping.png and /dev/null differ diff --git a/6.2.18/usage/assets/systems_list_view.png b/6.2.18/usage/assets/systems_list_view.png deleted file mode 100755 index a41af585..00000000 Binary files a/6.2.18/usage/assets/systems_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/taxii-collection.png b/6.2.18/usage/assets/taxii-collection.png deleted file mode 100755 index e4252371..00000000 Binary files a/6.2.18/usage/assets/taxii-collection.png and /dev/null differ diff --git a/6.2.18/usage/assets/taxii-feed-configuration.png b/6.2.18/usage/assets/taxii-feed-configuration.png deleted file mode 100755 index 8c115363..00000000 Binary files a/6.2.18/usage/assets/taxii-feed-configuration.png and /dev/null differ diff --git a/6.2.18/usage/assets/threat-actor-individual-biographics.png b/6.2.18/usage/assets/threat-actor-individual-biographics.png deleted file mode 100755 index 779e05bb..00000000 Binary files a/6.2.18/usage/assets/threat-actor-individual-biographics.png and /dev/null differ diff --git a/6.2.18/usage/assets/threat-actor-individual-demographics.png b/6.2.18/usage/assets/threat-actor-individual-demographics.png deleted file mode 100755 index 450e0b20..00000000 Binary files a/6.2.18/usage/assets/threat-actor-individual-demographics.png and /dev/null differ diff --git a/6.2.18/usage/assets/tools_list_view.png b/6.2.18/usage/assets/tools_list_view.png deleted file mode 100755 index 7bf1881c..00000000 Binary files a/6.2.18/usage/assets/tools_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/top-menu-investigation.png b/6.2.18/usage/assets/top-menu-investigation.png deleted file mode 100755 index d923b589..00000000 Binary files a/6.2.18/usage/assets/top-menu-investigation.png and /dev/null differ diff --git a/6.2.18/usage/assets/top-menu.png b/6.2.18/usage/assets/top-menu.png deleted file mode 100755 index d136f06b..00000000 Binary files a/6.2.18/usage/assets/top-menu.png and /dev/null differ diff --git a/6.2.18/usage/assets/trash-actions.png b/6.2.18/usage/assets/trash-actions.png deleted file mode 100755 index 7f370c2c..00000000 Binary files a/6.2.18/usage/assets/trash-actions.png and /dev/null differ diff --git a/6.2.18/usage/assets/trash-delete-confirm.png b/6.2.18/usage/assets/trash-delete-confirm.png deleted file mode 100755 index 3dbcfa06..00000000 Binary files a/6.2.18/usage/assets/trash-delete-confirm.png and /dev/null differ diff --git a/6.2.18/usage/assets/trash-error-dependency-in-trash.png b/6.2.18/usage/assets/trash-error-dependency-in-trash.png deleted file mode 100755 index 6ada8a0b..00000000 Binary files a/6.2.18/usage/assets/trash-error-dependency-in-trash.png and /dev/null differ diff --git a/6.2.18/usage/assets/trash-error-dependency-missing.png b/6.2.18/usage/assets/trash-error-dependency-missing.png deleted file mode 100755 index d2b674e8..00000000 Binary files a/6.2.18/usage/assets/trash-error-dependency-missing.png and /dev/null differ diff --git a/6.2.18/usage/assets/trash-restore-confirm.png b/6.2.18/usage/assets/trash-restore-confirm.png deleted file mode 100755 index 22507032..00000000 Binary files a/6.2.18/usage/assets/trash-restore-confirm.png and /dev/null differ diff --git a/6.2.18/usage/assets/trash.png b/6.2.18/usage/assets/trash.png deleted file mode 100755 index d15a890f..00000000 Binary files a/6.2.18/usage/assets/trash.png and /dev/null differ diff --git a/6.2.18/usage/assets/trigger-configuration.png b/6.2.18/usage/assets/trigger-configuration.png deleted file mode 100755 index ffebcddc..00000000 Binary files a/6.2.18/usage/assets/trigger-configuration.png and /dev/null differ diff --git a/6.2.18/usage/assets/trigger_notifier_configuration.png b/6.2.18/usage/assets/trigger_notifier_configuration.png deleted file mode 100755 index 60435ddc..00000000 Binary files a/6.2.18/usage/assets/trigger_notifier_configuration.png and /dev/null differ diff --git a/6.2.18/usage/assets/triggers.png b/6.2.18/usage/assets/triggers.png deleted file mode 100755 index c0e263cd..00000000 Binary files a/6.2.18/usage/assets/triggers.png and /dev/null differ diff --git a/6.2.18/usage/assets/update-confidence-level.png b/6.2.18/usage/assets/update-confidence-level.png deleted file mode 100755 index 065c1db7..00000000 Binary files a/6.2.18/usage/assets/update-confidence-level.png and /dev/null differ diff --git a/6.2.18/usage/assets/use-cases.png b/6.2.18/usage/assets/use-cases.png deleted file mode 100755 index baf2a573..00000000 Binary files a/6.2.18/usage/assets/use-cases.png and /dev/null differ diff --git a/6.2.18/usage/assets/user-confidence-overrides.png b/6.2.18/usage/assets/user-confidence-overrides.png deleted file mode 100755 index 47d1ea15..00000000 Binary files a/6.2.18/usage/assets/user-confidence-overrides.png and /dev/null differ diff --git a/6.2.18/usage/assets/vulnerabilities_list_view.png b/6.2.18/usage/assets/vulnerabilities_list_view.png deleted file mode 100755 index cac87a98..00000000 Binary files a/6.2.18/usage/assets/vulnerabilities_list_view.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-breakdown-by-entity-final.png b/6.2.18/usage/assets/widget-breakdown-by-entity-final.png deleted file mode 100755 index 277152fd..00000000 Binary files a/6.2.18/usage/assets/widget-breakdown-by-entity-final.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-breakdown-by-entity-parameter.png b/6.2.18/usage/assets/widget-breakdown-by-entity-parameter.png deleted file mode 100755 index c58ebe0b..00000000 Binary files a/6.2.18/usage/assets/widget-breakdown-by-entity-parameter.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-breakdown-by-relation-filter.png b/6.2.18/usage/assets/widget-breakdown-by-relation-filter.png deleted file mode 100755 index b25e958d..00000000 Binary files a/6.2.18/usage/assets/widget-breakdown-by-relation-filter.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-breakdown-by-relation-final.png b/6.2.18/usage/assets/widget-breakdown-by-relation-final.png deleted file mode 100755 index 5a8e2faf..00000000 Binary files a/6.2.18/usage/assets/widget-breakdown-by-relation-final.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-breakdown-example.png b/6.2.18/usage/assets/widget-breakdown-example.png deleted file mode 100755 index 236c4569..00000000 Binary files a/6.2.18/usage/assets/widget-breakdown-example.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-breakdwon-by-entity-filter.png b/6.2.18/usage/assets/widget-breakdwon-by-entity-filter.png deleted file mode 100755 index 7021ff90..00000000 Binary files a/6.2.18/usage/assets/widget-breakdwon-by-entity-filter.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-breakdwon-by-relation-parameter.png b/6.2.18/usage/assets/widget-breakdwon-by-relation-parameter.png deleted file mode 100755 index 974c6315..00000000 Binary files a/6.2.18/usage/assets/widget-breakdwon-by-relation-parameter.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-filters.png b/6.2.18/usage/assets/widget-filters.png deleted file mode 100755 index 7dbe3852..00000000 Binary files a/6.2.18/usage/assets/widget-filters.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-multiple-filters.png b/6.2.18/usage/assets/widget-multiple-filters.png deleted file mode 100755 index 2bbaa1c0..00000000 Binary files a/6.2.18/usage/assets/widget-multiple-filters.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-parameters.png b/6.2.18/usage/assets/widget-parameters.png deleted file mode 100755 index 5a72aaa6..00000000 Binary files a/6.2.18/usage/assets/widget-parameters.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-perspective.png b/6.2.18/usage/assets/widget-perspective.png deleted file mode 100755 index 9a2669de..00000000 Binary files a/6.2.18/usage/assets/widget-perspective.png and /dev/null differ diff --git a/6.2.18/usage/assets/widget-visualization.png b/6.2.18/usage/assets/widget-visualization.png deleted file mode 100755 index c1e6bbc8..00000000 Binary files a/6.2.18/usage/assets/widget-visualization.png and /dev/null differ diff --git a/6.2.18/usage/assets/workbench-data-manipulation.png b/6.2.18/usage/assets/workbench-data-manipulation.png deleted file mode 100755 index cfd332c0..00000000 Binary files a/6.2.18/usage/assets/workbench-data-manipulation.png and /dev/null differ diff --git a/6.2.18/usage/assets/workbench-in-data-tab.png b/6.2.18/usage/assets/workbench-in-data-tab.png deleted file mode 100755 index f4861a23..00000000 Binary files a/6.2.18/usage/assets/workbench-in-data-tab.png and /dev/null differ diff --git a/6.2.18/usage/automation/index.html b/6.2.18/usage/automation/index.html deleted file mode 100755 index f03ac046..00000000 --- a/6.2.18/usage/automation/index.html +++ /dev/null @@ -1,4438 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Automation - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Playbooks Automation

-
-

Enterprise edition

-

Playbooks automation is available under the "OpenCTI Enterprise Edition" license. Please read the dedicated page to have all information.

-
-

OpenCTI playbooks are flexible automation scenarios which can be fully customized and enabled by platform administrators to enrich, filter and modify the data created or updated in the platform.

-

Playbook automation is accessible in the user interface under Data > Processing > Automation.

-
-

Right needed

-

You need the "Manage credentials" capability to use the Playbooks automation, because you will be able to manipulate data simple users cannot access.

-
-

You will then be able to:

-
    -
  • add labels depending on enrichment results to be used in threat intelligence-driven detection feeds,
    • -
  • create reports and cases based on various criteria,
    • -
  • trigger enrichments or webhooks in given conditions,
    • -
  • modify attributes such as first_seen and last_seen based on other pieces of knowledge,
    • -
  • etc.
    • -
-

Playbook philosophy

-

Consider Playbook as a STIX 2.1 bundle pipeline.

-

Initiating with a component listening to a data stream, each subsequent component in the playbook processes a received STIX bundle. These components have the ability to modify the bundle and subsequently transmit the altered result to connected components.

-

In this paradigm, components can send out the STIX 2.1 bundle to multiple components, enabling the development of multiple branches within your playbook.

-

A well-designed playbook end with a component executing an action based on the processed information. For instance, this may involve writing the STIX 2.1 bundle in a data stream.

-
-

Validate ingestion

-

The STIX bundle processed by the playbook won't be written in the platform without specifying it using the appropriate component, i.e. "Send for ingestion".

-
-

Create a Playbook

-

It is possible to create as many playbooks as needed which are running independently. You can give a name and description to each playbook.

-

Create a new playbook

-

The first step to define in the playbook is the “triggering event”, which can be any knowledge event (create, update or delete) with customizable filters. To do so, click on the grey rectangle in the center of the workspace and choose the component to "listen knowledge events". Configure it with adequate filters. You can use same filters as in other part of the platform.

-

Listening creation event for TLP:GREEN IPs and domain names

-

Then you have flexible choices for the next steps to:

-
    -
  • filter the initial knowledge,
    • -
  • enrich data using external sources and internal rules,
    • -
  • modify entities and relationships by applying patches,
    • -
  • write the data, send notifications,
    • -
  • etc.
    • -
-

Do not forget to start your Playbook when ready, with the Start option of the burger button placed near the name of your Playbook.

-

By clicking the burger button of a component, you can replace it by another one.

-

By clicking on the arrow icon in the bottom right corner of a component, you can develop a new branch at the same level.

-

By clicking the "+" button on a link between components, you can insert a component between the two.

-

Components of playbooks

-

List of current components

-

Log data in standard output

-

Will write the received STIX 2.1 bundle in platform logs with configurable log level and then send out the STIX 2.1 bundle unmodified.

-

Send for ingestion

-

Will pass the STIX 2.1 bundle to be written in the data stream. This component has no output and should end a branch of your playbook.

-

Filter Knowledge

-

Will allow you to define filter and apply it to the received STIX 2.1 bundle. The component has 2 output, one for data matching the filter and one for the remainder.

-

By default, filtering is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all elements in the bundle (elements that might result from enrichment for example).

-

Enrich through connector

-

Will send the received STIX 2.1 bundle to the stated enrichment connector and send out the modified bundle. -Entities that are passed to this stage must be compatible with the enrichment connector being used, as otherwise the playbook may stop at this stage. The Reduce Knowledge component can be used to filter out incompatible entities from being passed to this stage.

-

Manipulate knowledge

-

Will add, replace or remove compatible attribute of the entities contains in the received STIX 2.1 bundle and send out the modified bundle.

-

By default, modification is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all elements in the bundle (elements that might result from enrichment for example).

-

Container wrapper

-

Will modify the received STIX 2.1 bundle to include the entities into an container of the type you configured. -By default, wrapping is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all elements in the bundle (elements that might result from enrichment for example).

-

Share with organizations

-

Will share every entity in the received STIX 2.1 bundle with Organizations you configured. Your platform needs to have declared a platform main organization in Settings/Parameters.

-

Apply predefined rule

-

Will apply a complex automation built-in rule. This kind of rule might impact performance. Current rules are:

-
    -
  • First/Last seen computing extension from report publication date: will populate first seen and last seen date of entities contained in the report based on its publication date,
    • -
  • Resolve indicators based on observables (add in bundle): will retrieve all indicators linked to the bundle's observables from the database,
    • -
  • Resolve observables an indicator is based on (add in bundle): retrieve all observables linked to the bundle's indicator from the database,
    • -
  • Resolve container references (add in bundle): will add to the bundle all the relationships and entities the container contains (if the entity having triggered the playbook is not a container, the output of this component will be empty),
    • -
  • Resolve neighbors relations and entities (add in bundle): will add to the bundle all relations of the entity having triggered the playbook, as well as all entities at the end of these relations, i.e. the "first neighbors" (if the entity is a container, the output of this component will be empty).
    • -
-

Send to notifier

-

Will generate a Notification each time a STIX 2.1 bundle is received.

-

Promote observable to indicator

-

Will generate indicator based on observables contained in the received STIX 2.1 bundle.

-

By default, it is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all observables in the bundle (e.g. observables that might result from predefined rule).

-

You can also add all indicators and relationships generated by this component in the entity having triggered the playbook, if this entity is a container.

-

Extract observables from indicator

-

Will extract observables based on indicators contained in the received STIX 2.1 bundle.

-

By default, it is applied to entities having triggered the playbook. You can toggle the corresponding option to apply it to all indicators in the bundle (e.g. indicators that might result from enrichment.

-

You can also add all observables and relationships generated by this component in the entity having triggered the playbook, if this entity is a container.

-

Reduce Knowledge

-

Will filter out any entities in the current stage that do not match the filter conditions in the stage. If the original triggering entity is a container, such as a report or case, then the container itself cannot be filtered out, and will be passed to subsequent stages.

-

Monitor playbook activity

-

At the top right of the interface, you can access execution trace of your playbook and consult the raw data after every step of your playbook execution.

-

Steps monitoring

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/background-tasks/index.html b/6.2.18/usage/background-tasks/index.html deleted file mode 100755 index a2e1378e..00000000 --- a/6.2.18/usage/background-tasks/index.html +++ /dev/null @@ -1,4174 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Background tasks - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Background tasks

-

Three types of tasks are done in the background:

-
    -
  • rule tasks,
    • -
  • knowledge tasks,
    • -
  • user tasks.
    • -
-

Rule tasks can be seen and activated in Settings > Customization > Rules engine. -Knowledge and user tasks can be seen and managed in Data > Background Tasks. The scope of each task is indicated.

-

Background_tasks

-

Rule tasks

-

If a rule task is enabled, it leads to the scan of the whole platform data and the creation of entities or relationships in case a configuration corresponds to the tasks rules. The created data are called 'inferred data'. Each time an event occurs in the platform, the rule engine checks if inferred data should be updated/created/deleted.

-

Knowledge tasks

-

Knowledge tasks are background tasks updating or deleting entities and correspond to mass operations on these data. To create one, select entities via the checkboxes in an entity list, and choose the action to perform via the toolbar.

-

Rights

-
    -
  • To create a knowledge task, the user should have the capability to Update Knowledge (or the capability to delete knowledge if the task action is a deletion).
    • -
  • To see a knowledge task in the Background task section, the user should be the creator of the task, or have the KNOWLEDGE capability.
    • -
  • To delete a knowledge task from the Background task section, the user should be the creator of the task, or have the KNOWLEDGE_UPDATE capability.
    • -
-

User tasks

-

User tasks are background tasks updating or deleting notifications. It can be done from the Notification section, by selecting several notifications via the checkboxes, and choosing an action via the toolbar.

-

Rights

-
    -
  • A user can create a user task on its own notifications only.
    • -
  • To see or delete a user task, the user should be the creator of the task or have the SET_ACCESS capability.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/case-management/index.html b/6.2.18/usage/case-management/index.html deleted file mode 100755 index df3ee2d2..00000000 --- a/6.2.18/usage/case-management/index.html +++ /dev/null @@ -1,4124 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Case management - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Case management

-

Why Case management?

-

Compiling CTI data in one place, deduplicate and correlate to transform it into Intelligence is very important. But ultimately, you need to act based on this Intelligence. Some situations will need to be taken care of, like cybersecurity incidents, requests for information or requests for takedown. Some actions will then need to be traced, to be coordinated and oversaw. Some actions will include feedback and content delivery.

-

OpenCTI includes Cases to allow organizations to manage situations and organize their team's work. Better, by doing Case management in OpenCTI, you handle your cases with all the context and Intelligence you need, at hand.

-

How to manage your Case in OpenCTI?

-

Multiple situations can be modelize in OpenCTI as a Case, either an Incident Response, a Request for Takedown or a Request for Information.

-

Incident Responses' list

-

All Cases can contain any entities and relationships you need to represent the Intelligence context related to the situation. At the beginning of your case, you may find yourself with only some Observables sighted in a system. At the end, you may have Indicators, Threat Actor, impacted systems, attack patterns. All representing your findings, ready to be presented and exported as graph, pdf report, timeline, etc.

-

Incident Responses' list

-

Some Cases may need some collaborative work and specific Tasks to be performed by people that have relevant skillsets. OpenCTI allows you to associate Tasks in your Cases and assign them to users in the platform. As some type of situation may need the same tasks to be done, it is also possible to pre-define lists of tasks to be applied on your case. You can define these lists by accessing the Settings/Taxonomies/Case templates panel. Then you just need to add it from the overview of your desire Case.

-

Tip: A user can have a custom dashboard showing him all the tasks that have been assigned to him.

-

Incident Responses' list

-

As with other objects in OpenCTI, you can also leverage the Notes to add some investigation and analysis related comments, helping you shaping up the content of your case with unstructured data and trace all the work that have been done.

-

You can also use Opinions to collect how the Case has been handled, helping you to build Lessons Learned.

-

Incident Responses' list

-

To trace the evolution of your Case and define specific resolution worflows, you can use the Status (that can be define in Settings/Taxonomies/Status templates).

-

At the end of your Case, you will certainly want to report on what has been done. OpenCTI allows you to export the content of the Case in a simple but customizable PDF (currently in refactor). But of course, your company has its own documents' templates, right? With OpenCTI, you will be able to include some nice graphics in it. For example, a Matrix view of the attacker attack pattern or even a graph display of how things are connected.

-

Also, we are currently working a more meaningfull Timeline view that will be possible to export too.

-

Use case example: A suspicious observable is sighted by a defense system. Is it important?

-
    -
  • Daily, your SIEM and EDR are fed Indicators of Compromise from your OpenCTI instance.
    • -
  • Today, your SIEM has sighted the domain name "bad.com" matching one of them. Its alert has been transfered to OpenCTI and has created a Sighting relationship between your System "SIEM permiter A" and the Observable "bad.com".
    • -
  • You are alerted immediatly, because you have activated the inference rule creating a corresponding Incident in this situation, and you have created an alert based on new Incident that sends you email notification and Teams message (webhook).
    • -
  • In OpenCTI, you can clearly see the link between the alerting System, the sighted Observable and the corresponding Indicator. Better, you can also see all the context of the Indicator. It is linked to a notorious and recent phishing campaign targeting your activity sector. "bad.com" is clearly something to investigate ASAP.
    • -
  • You quickly select all the context you have found, and add it to a new Incident responsecase. You position the priority to High, regarding the context, and the severity to Low, as you don't know yet if someone really interacted with "bad.com".
    • -
  • You also assign the case to one of your colleagues, on duty for investigative work. To guide him, you also create a Task in your case for verifying if an actual interaction happened with "bad.com".
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/containers/index.html b/6.2.18/usage/containers/index.html deleted file mode 100755 index 87fc747b..00000000 --- a/6.2.18/usage/containers/index.html +++ /dev/null @@ -1,4277 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Containers - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Containers

-

STIX standard

-

Definition

-

In the STIX 2.1 standard, some STIX Domain Objects (SDO) can be considered as "container of knowledge", using the object_refs attribute to refer multiple other objects as nested references. In object_refs, it is possible to refer to entities and relationships.

-

Example

-
{
-   "type": "report",
-   "spec_version": "2.1",
-   "id": "report--84e4d88f-44ea-4bcd-bbf3-b2c1c320bcb3",
-   "created_by_ref": "identity--a463ffb3-1bd9-4d94-b02d-74e4f1658283",
-   "created": "2015-12-21T19:59:11.000Z",
-   "modified": "2015-12-21T19:59:11.000Z",
-   "name": "The Black Vine Cyberespionage Group",
-   "description": "A simple report with an indicator and campaign",
-   "published": "2016-01-20T17:00:00.000Z",
-   "report_types": ["campaign"],
-   "object_refs": [
-      "indicator--26ffb872-1dd9-446e-b6f5-d58527e5b5d2",
-      "campaign--83422c77-904c-4dc1-aff5-5c38f3a2c55c",
-      "relationship--f82356ae-fe6c-437c-9c24-6b64314ae68a"
-   ]
-}
-
-

In the previous example, we have a nested reference to 3 other objects:

-
"object_refs": [
-   "indicator--26ffb872-1dd9-446e-b6f5-d58527e5b5d2",
-   "campaign--83422c77-904c-4dc1-aff5-5c38f3a2c55c",
-   "relationship--f82356ae-fe6c-437c-9c24-6b64314ae68a"
-]
-
-

Implementation

-

Types of container

-

In OpenCTI, containers are displayed differently than other entities, because they contain pieces of knowledge. Here is the list of containers in the platform:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Type of entitySTIX standardDescription
ReportNativeReports are collections of threat intelligence focused on one or more topics, such as a description of a threat actor, malware, or attack technique, including context and related details.
GroupingNativeA Grouping object explicitly asserts that the referenced STIX Objects have a shared context, unlike a STIX Bundle (which explicitly conveys no context).
Observed DataNativeObserved Data conveys information about cyber security related entities such as files, systems, and networks using the STIX Cyber-observable Objects (SCOs).
NoteNativeA Note is intended to convey informative text to provide further context and/or to provide additional analysis not contained in the STIX Objects.
OpinionNativeAn Opinion is an assessment of the correctness of the information in a STIX Object produced by a different entity.
CaseExtensionA case whether an Incident Response, a Request for Information or a Request for Takedown is used to convey an epic with a set of tasks.
TaskExtensionA task, generally used in the context of a case, is intended to convey information about something that must be done in a limited timeframe.
-

Containers behavior

-

In the platform, it is always possible to visualize the list of entities and/or observables referenced in a container (Container > Entities or Observables) but also to add / remove entities from the container.

-

Entities

-

As containers can also contain relationships, which are generally linked to the other entities in the container, it is also possible to visualize the container as a graph (Container > Knowledge)

-

Graph

-

Containers of an entity or a relationship

-

On the entity or the relationship side, you can always find all containers where the object is contained using the top menu Analysis:

-

Analysis

-

In all containers list, you can also filter containers based on one or multiple contained object(s):

-

Container filters

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/dashboards-share/index.html b/6.2.18/usage/dashboards-share/index.html deleted file mode 100755 index 89d5b08d..00000000 --- a/6.2.18/usage/dashboards-share/index.html +++ /dev/null @@ -1,4157 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Share custom dashboards - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Share custom dashboards

-

OpenCTI provides a simple way to share a visualisation of a custom dashboard to anyone, -even for people that are outside of the platform. We call those visualisations: public dashboards.

-

Public dashboards are a snapshot of a custom dashboard at a specific moment of time. -By this way you can share a version of a custom dashboard, then modify your custom dashboard -without worrying about the impact on public dashboards you have created.

-

On the contrary, if you want that your public dashboard is updated with the last version of the -associated custom dashboard, you can do it with few clicks by recreating a public dashboard using -the same name of the one to update.

-
-

To be able to share custom dashboards you need to have the Manage data sharing & ingestion capability.

-
-

Create a public dashboard

-

On the top-right of your custom dashboard page you will find a button that will open a panel to -manage the public dashboards associated to this custom dashboard.

-

Share dashboard button

-

In this panel you will find two parts: -- At the top you have a form allowing you to create public dashboards, -- And below, the list of the public dashboards you have created.

-

Share dashboard panel

-

Form to create a new public dashboard

-

First you need to specify a name for your public dashboard. This name will be displayed -on the dashboard page. The name is also used to generate an ID for your public dashboard -that will be used in the URL to access the dashboard.

-

The ID is generated as follow: replace all spaces with symbol - and remove special characters. -This ID also needs to be unique in the platform as it is used in the URL to access the dashboard.

-

Share dashboard name

-

Then you can choose if the public dashboard is enabled or not. A disabled dashboard means that -you cannot access the public dashboard through the custom URL. But you can still manage it from this -panel.

-

Share dashboard enable

-

Finally you choose the max level of marking definitions for the data to be displayed in the -public dashboard. For example if you choose TLP:AMBER then the data fetched by the widgets -inside the public dashboard will be at maximum AMBER, you won't retrieved data with RED -marking definition.

-

Also note that the list of marking definitions you can see is based on your current marking -access on the platform and the maximum sharable marking definitions defined in your groups.

-
-

Define maximum shareable markings in groups

-

As a platform administrator, you can define, for each group and for each type of marking definition, Maximum marking definitions shareable to be -shared through Public Dashboard, regardless of the definition set by users in their public dashboard.

-
-

Share dashboard markings

-

List of the public dashboards

-

When you have created a public dashboard, it will appear in the list below the form.

-

Share dashboard list

-

In this list each item represents a public dashboard you have created. For each you can see its -name, path of the URL, max marking definitions, the date of creation, the status to know if -the dashboard is enabled or not and some actions.

-

The possible actions are: copy the link of the public dashboard, disable or enable the dashboard -and delete the dashboard.

-

To share a public dashboard just copy the link and give the URL to the person you want to share -with. The dashboard will be visible even if the person is not connected to OpenCTI.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/dashboards/index.html b/6.2.18/usage/dashboards/index.html deleted file mode 100755 index e2f508d0..00000000 --- a/6.2.18/usage/dashboards/index.html +++ /dev/null @@ -1,4297 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Custom dashboards - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Custom dashboards

-

OpenCTI provides an adaptable and entirely customizable dashboard functionality. The flexibility of OpenCTI's dashboard ensures a tailored and insightful visualization of data, fostering a comprehensive understanding of the platform's knowledge, relationships, and activities.

-

Dashboard overview

-

You have the flexibility to tailor the arrangement of widgets on your dashboard, optimizing organization and workflow efficiency. Widgets can be intuitively placed to highlight key information. Additionally, you can resize widgets from the bottom right corner based on the importance of the information, enabling adaptation to specific analytical needs. This technical flexibility ensures a fluid, visually optimized user experience.

-

Moreover, the top banner of the dashboard offers a convenient feature to configure the timeframe for displayed data. This can be accomplished through the selection of a relative time period, such as "Last 7 days", or by specifying fixed "Start" and "End" dates, allowing users to precisely control the temporal scope of the displayed information.

-

Dashboard overview

-

-

Access control

-

In OpenCTI, the power to create custom dashboards comes with a flexible access control system, allowing users to tailor visibility and rights according to their collaborative needs.

-

When a user crafts a personalized dashboard, by default, it remains visible only to the dashboard creator. At this stage, the creator holds administrative access rights. However, they can extend access and rights to others using the "Manage access" button, denoted by a locker icon, located at the top right of the dashboard page.

-

Manage access button

-

Levels of access:

-
    -
  • View: Access to view the dashboard.
    • -
  • Edit: View + Permission to modify and update the dashboard and its widgets.
    • -
  • Manage: Edit + Ability to delete the dashboard and to control user access and rights.
    • -
-

It's crucial to emphasize that at least one user must retain admin access to ensure ongoing management capabilities for the dashboard.

-

Manage access dialog

-
-

Knowledge access restriction

-

The platform's data access restrictions also apply to dashboards. The data displayed in the widgets is subject to the user's access rights within the platform. Therefore, an admin user will not see the same results in the widgets as a user with limited access, such as viewing only TLP:CLEAR data (assuming the platform contains data beyond TLP:CLEAR).

-
-

Share dashboard and widget configurations

-

OpenCTI provides functionality for exporting, importing and duplicating dashboard and widget configurations, facilitating the seamless transfer of customized dashboard setups between instances or users.

-

Export

-

Dashboards can be exported from either the custom dashboards list or the dashboard view.

-

To export a dashboard configuration from the custom dashboards list:

-
    -
  1. Click on the burger menu button at the end of the dashboard line.
    2. -
  2. Select Export.
    3. -
-

Export dashboard option

-

To export a widget, the same mechanism is used, but from the burger menu button in the upper right-hand corner of the widget.

-

Export widget option

-

To export a dashboard configuration from the dashboard view:

-
    -
  1. Navigate to the desired dashboard.
    2. -
  2. Click on the Export button (file with an arrow pointing to the top right corner) located in the top-right corner of the dashboard.
    3. -
-

Export JSON button

-

Configuration file

-

The dashboard configuration will be saved as a JSON file, with the title formatted as [YYYYMMDD]_octi_dashboard_[dashboard title]. The expected configuration file content is as follows:

-
{
-  "openCTI_version": "5.12.0",
-  "type": "dashboard",
-  "configuration": {
-    "name": "My dashboard title",
-    "manifest": "eyJ3aWRn(...)uZmlnIjp7fX0="
-  }
-}
-
-

The widget configuration will be saved as a JSON file, with the title formatted as [YYYYMMDD]_octi_widget_[widget view]. The expected configuration file content is as follows:

-
{
-  "openCTI_version": "5.12.0",
-  "type": "widget",
-  "configuration": "eyJ0eXB(...)iOmZhbHNlfX0="
-}
-
-
-

Source platform-related filters

-

When exporting a dashboard or widget configuration, all filters will be exported as is. Filters on objects that do not exist in the receiving platform will need manual deletion after import. Filters to be deleted can be identified by their "delete" barred value.

-
-

Filter to delete

-

Import

-

Dashboards can be imported from the custom dashboards list:

-
    -
  1. Hover over the Add button (+) in the right bottom corner.
    2. -
  2. Click on the Import dashboard button (cloud with an upward arrow).
    3. -
  3. Select your file.
    4. -
-

Import dashboard option

-

To import a widget, the same mechanism is used, but from a dashboard view.

-

Import widget option

-
-

Configuration compatibility

-

Only JSON files with the required properties will be accepted, including "openCTI_version: [5.12.0 and above]", "type: [dashboard|widget]", and a "configuration". This applies to both dashboards and widgets configurations.

-
-

Duplicate

-

Dashboards can be duplicated from either the custom dashboards list or the dashboard view.

-

To duplicate a dashboard from the custom dashboards list:

-
    -
  1. Click on the burger menu button at the end of the dashboard line.
    2. -
  2. Select Duplicate.
    3. -
-

To duplicate a widget, the same mechanism is used, but from the burger menu button in the upper right-hand corner of the widget.

-

To duplicate a dashboard from the dashboard view:

-
    -
  1. Navigate to the desired dashboard.
    2. -
  2. Click on the Duplicate the dashboard button (two stacked sheets) located in the top-right corner of the dashboard.
    3. -
-

Duplicate dashboard button

-

Upon successful duplication, a confirmation message is displayed for a short duration, accompanied by a link for easy access to the new dashboard view. Nevertheless, the new dashboard can still be found in the dashboards list.

-

duplicate-dashboard-success-message

-
-

Dashboard access

-

The user importing or duplicating a dashboard becomes the only one with access to it. Then, access can be managed as usual.

-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/data-model/index.html b/6.2.18/usage/data-model/index.html deleted file mode 100755 index f1e2b87e..00000000 --- a/6.2.18/usage/data-model/index.html +++ /dev/null @@ -1,4220 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Data model - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Data model

-

Introduction

-

The OpenCTI core design relies on the concept of a knowledge graph, where you have two different kinds of object:

-
    -
  1. Nodes are used to describe entities, which have some properties or attributes.
    2. -
  2. Edges are used to describe relationships, which are created between two entity nodes and have some properties or attributes.
    3. -
-
-

Example

-

An example would be that the entity APT28 has a relationship uses to the malware entity Drovorub.

-
-

Standard

-

-

The STIX model

-

To enable a unified approach in the description of threat intelligence knowledge as well as importing and exporting data, the OpenCTI data model is based on the STIX 2.1 standard. Thus we highly recommend to take a look to the STIX Introductory Walkthrough and to the different kinds of STIX relationships to get a better understanding of how OpenCTI works.

-

Some more important STIX naming shortcuts are:

-
    -
  • STIX Domain Objects (SDO): Attack Patterns, Malware, Threat Actors, etc.
    • -
  • STIX Cyber Observable (SCO): IP Addresses, domain names, hashes, etc.
    • -
  • STIX Relationship Object (SRO): Relationships, Sightings
    • -
-

STIX meta model

-

Extensions

-

In some cases, the model has been extended to be able to:

-
    -
  • Support more types of SCOs to modelize information systems such as cryptocurrency wallets, user agents, etc.
    • -
  • Support more types of SDOs to modelize disinformation and cybercrime such as channels, events, narrative, etc.
    • -
  • Support more types of SROs to extend the new SDOs such asamplifies, publishes, etc.
    • -
-

Implementation in the platform

-

Diagram of types

-

You can find below the digram of all types of entities and relationships available in OpenCTI.

- - -

Attributes and properties

-

To get a comprehensive list of available properties for a given type of entity or relationship, you can use the GraphQL playground schema available in your "Profile > Playground". Then you can click on schema. You can for instance search for the keyword IntrusionSet:

-

STIX meta model

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/dates/index.html b/6.2.18/usage/dates/index.html deleted file mode 100755 index 87d94d0a..00000000 --- a/6.2.18/usage/dates/index.html +++ /dev/null @@ -1,4141 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Meaning of dates - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Meaning of dates

-

In OpenCTI, entities can contain various dates, each representing different types of information. The available dates vary depending on the entity types.

-

Dates

-

In OpenCTI, dates play a crucial role in understanding the context and history of entities. Here's a breakdown of the different dates you might encounter in the platform:

-
    -
  • “Platform creation date”: This date signifies the moment the entity was created within OpenCTI. On the API side, this timestamp corresponds to the created_at field. It reflects the initiation of the entity within the OpenCTI environment.
    • -
  • “Original creation date”: This date reflects the original creation date of the data on the source's side. It becomes relevant if the source provides this information and if the connector responsible for importing the data takes it into account. In cases where the source date is unavailable or not considered, this date defaults to the import date (i.e. the “Platform creation date”). On the API side, this timestamp corresponds to the created field.
    • -
  • “Modification date”: This date captures the most recent modification made to the entity, whether a connector automatically modifies it or a user manually edits the entity. On the API side, this timestamp corresponds to the updated_at field. It serves as a reference point for tracking the latest changes made to the entity.
    • -
  • Date not shown on GUI: There is an additional date which is not visible on the entity in the GUI. This date is the modified field on the API. This date reflects the original update date of the data on the source's side. The difference between modified and updated_at is identical to the difference between created and created_at.
    • -
-

Dates

-

Understanding these dates is pivotal for contextualizing the information within OpenCTI, ensuring a comprehensive view of entity history and evolution.

-

Date types

-

Technical dates

-

The technical dates refer to the dates directly associated to data management within the platform. The API fields corresponding to technical dates are:

-
    -
  • created_at: Indicates the date and time when the entity was created in the platform.
    • -
  • updated_at: Represents the date and time of the most recent update to the entity in the platform.
    • -
-

Functional dates

-

The functional dates are the dates functionally significant, often indicating specific events or milestones. The API fields corresponding to functional dates are:

-
    -
  • created: Denotes the date and time when the entity was created on the source's side.
    • -
  • modified: Represents the date and time of the most recent modification to the entity on the source's side.
    • -
  • start_time: Indicates the start date and time associated with a relationship.
    • -
  • stop_time: Indicates the stop date and time associated with a relationship.
    • -
  • first_seen: Represents the initial date and time when the entity/activity was observed.
    • -
  • last_seen: Represents the most recent date and time when the entity/activity was observed.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/deduplication/index.html b/6.2.18/usage/deduplication/index.html deleted file mode 100755 index f3d93065..00000000 --- a/6.2.18/usage/deduplication/index.html +++ /dev/null @@ -1,4331 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deduplication - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Deduplication

-

One of the core concept of the OpenCTI knowledge graph is all underlying mechanisms implemented to accurately de-duplicate and consolidate (aka. upserting) information about entities and relationships.

-

Creation behavior

-

When an object is created in the platform, whether manually by a user or automatically by the connectors / workers chain, the platform checks if something already exist based on some properties of the object. If the object already exists, it will return the existing object and, in some cases, update it as well.

-

Technically, OpenCTI generates deterministic IDs based on the listed properties below to prevent duplicate (aka "ID Contributing Properties"). Also, it is important to note that there is a special link between name and aliases leading to not have entities with overlapping aliases or an alias already used in the name of another entity.

-

Entities

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeAttributes
Area(name OR x_opencti_alias) AND x_opencti_location_type
Attack Pattern(name OR alias) AND optional x_mitre_id
Campaignname OR alias
Channelname OR alias
City(name OR x_opencti_alias) AND x_opencti_location_type
Country(name OR x_opencti_alias) AND x_opencti_location_type
Course Of Action(name OR alias) AND optional x_mitre_id
Data Componentname OR alias
Data Sourcename OR alias
Eventname OR alias
Feedback Casename AND created (date)
Groupingname AND context
Incidentname OR alias
Incident Response Casename OR alias
Indicatorpattern OR alias
Individual(name OR x_opencti_alias) and identity_class
Infrastructurename OR alias
Intrusion Setname OR alias
Languagename OR alias
Malwarename OR alias
Malware Analysisname OR alias
Narrativename OR alias
NoteNone
Observed Dataname OR alias
OpinionNone
Organization(name OR x_opencti_alias) and identity_class
Position(name OR x_opencti_alias) AND x_opencti_location_type
Regionname OR alias
Reportname AND published (date)
RFI Casename AND created (date)
RFT Casename AND created (date)
Sector(name OR alias) and identity_class
TaskNone
Threat Actorname OR alias
Toolname OR alias
Vulnerabilityname OR alias
-
-

Names and aliases management

-

The name and aliases of an entity define a set of unique values, so it's not possible to have the name equal to an alias and vice versa.

-
-

Relationships

-

The deduplication process of relationships is based on the following criterias:

-
    -
  • Type
    • -
  • Source
    • -
  • Target
    • -
  • Start time between -30 days / + 30 days
    • -
  • Stop time between -30 days / + 30 days
    • -
-

Observables

-

For STIX Cyber Observables, OpenCTI also generate deterministic IDs based on the STIX specification using the "ID Contributing Properties" defined for each type of observable.

-

Update behavior

-

In cases where an entity already exists in the platform, incoming creations can trigger updates to the existing entity's attributes. -This logic has been implemented to converge the knowledge base towards the highest confidence and quality levels for both entities and relationships.

-

To understand in details how the deduplication mechanism works in context of the maximum confidence level, you can navigate through this diagram (section deduplication):

- - - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/delete-restore/index.html b/6.2.18/usage/delete-restore/index.html deleted file mode 100755 index 521b1a74..00000000 --- a/6.2.18/usage/delete-restore/index.html +++ /dev/null @@ -1,4157 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Delete and restore knowledge - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Delete and restore knowledge

-

Knowledge can be deleted from OpenCTI either in an overview of an object or using background tasks. -When an object is deleted, all its relationships and references to other objects are also deleted.

-

The deletion event is written to the stream, to trigger automated playbooks or synchronize another platform.

-

Since OpenCTI 6.1, a record of the deleted objects is kept for a given period of a time, allowing to restore them on demand. This does not impact the stream events or other side effect of the deletion: the object is still deleted.

-

Trash

-

A view called "Trash" displays all "delete" operations, entities and relationships alike.

-

Trash

-

A delete operation contains not only the entity or relationship that has been deleted, but also all the relationships and references from (to) this main object to (from) other elements in the platform.

-

You can sort, filter or search this table using the usual UI controls. You are limited to the type of object, their representation (most of the time, the name of the object), the user who deleted the object, the date and time of deletion and the marking of the object.

-

Note that the delete operations (i.e. the entries in this table view) inherit the marking of the main entity that was deleted, and thus follow the same access restriction as the object that was deleted.

-

You can individually restore or permanently delete an object from the trash view using the burger menu at the end of the line.

-

Trash actions

-

Alternatively, you can use the checkboxes at the start of the line to select a subset of deleted objects, and trigger a background task to restore or permanently delete them by batch.

-

Restore

-

Restoring an element creates it again in the platform with the same information it had before its deletion. -It also restores all the relationships from or to this object, that have been also deleted during the deletion operation. -If the object had attached files (uploaded or exported), they are also restored.

-

Trash restore confirm

-

Permanent delete

-

From the Trash panel, it is also possible to delete permanently the object, its relationships, and attached files.

-

Trash delete confirm

-

Trash retention

-

Deleted objects are kept in trash during a fixed period of time (7 days by default), then they are permanently deleted by the trash manager.

-

Limitations

-

When it comes to restoring a deleted object from the trash, the current implementation shows several limitations. -First and foremost, if an object in the trash has lost a relationship dependency (i.e. the other side of a relationship from or to this object is no longer in live database), you will not be able to restore the object.

-

restore error: a dependency is in the trash

-

In such case, if the missing dependency is in the trash too, you can manually restore this dependency first and then retry.

-

If the missing dependency has been permanently deleted, the object cannot be recovered.

-

restore error: a dependency is in the trash

-

In other words: -* no partial restore: the object and all its relationships must be restored in one pass -* no "cascading" restore: restoring one object does not restore automatically all linked objects in the trash

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/enrichment/index.html b/6.2.18/usage/enrichment/index.html deleted file mode 100755 index 432447cd..00000000 --- a/6.2.18/usage/enrichment/index.html +++ /dev/null @@ -1,4093 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Enrichment connectors - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Enrichment connectors

-

Enriching the data within the OpenCTI platform is made seamlessly through the integration of enrichment connectors. These connectors facilitate the retrieval of additional data from external sources or portals.

-

Automatic enrichment

-

Enrichment can be conducted automatically in two distinct modes:

-
    -
  • Upon data arrival: Configuring the connector to run automatically when data arrives in OpenCTI ensures a real-time enrichment process, supplementing the platform's data. However, it's advisable to avoid automatic enrichment for quota-based connectors to paid sources to prevent quickly depleting all quotas. Additionally, this automatic enrichment contributes to increased data volume. On a large scale, with hundreds of thousands of objects, the disk space occupied by this data can be substantial, and it should be considered, especially if disk space is a concern. The automatic execution is configured at the connector level using the "auto: true|false" parameter.
    • -
  • Targeted enrichment via playbooks: Enrichment can also be performed in a more targeted manner using playbooks. This approach allows for a customized enrichment strategy, focusing on specific objects and optimizing the relevance of the retrieved data.
    • -
-

Manual enrichment

-

Manually initiating the enrichment process is straightforward. Simply locate the button with the cloud icon at the top right of an entity.

-

Enrichment button

-

Clicking on this icon unveils a side panel displaying a list of available connectors that can be activated for the given object. If no connectors appear in the panel, it indicates that no enrichment connectors are available for the specific type of object in focus.

-

Enrichment panel

-

Activation of an enrichment connector triggers a contact with the designated remote source, importing a set of data into OpenCTI to enrich the selected object. Each enrichment connector operates uniquely, focusing on a specific set of object types it can enrich and a distinct set of data it imports. Depending on the connectors, they may, establish relationships, add external references, or complete object information, thereby contributing to the comprehensiveness of information within the platform.

-

The list of available connectors can be found in our connectors catalog. In addition, further documentation on connectors is available on the dedicated documentation page.

-
-

Impact of the max confidence level

-
-

The maximum confidence level per user can have an impact on enrichment connectors, not being able to update data in the platform. To understand the concept and the potential issues you could face, please navigate to this page to understand.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-analysis/index.html b/6.2.18/usage/exploring-analysis/index.html deleted file mode 100755 index 7a047d35..00000000 --- a/6.2.18/usage/exploring-analysis/index.html +++ /dev/null @@ -1,4359 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Analysis - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Analyses

-

When you click on "Analyses" in the left-side bar, you see all the "Analyses" tabs, visible on the top bar on the left. By default, the user directly access the "Reports" tab, but can navigate to the other tabs as well.

-

From the Analyses section, users can access the following tabs:

-
    -
  • Reports: See Reports as a sort of containers to detail and structure what is contained on a specific report, either from a source or write by yourself. Think of it as an Intelligence Production in OpenCTI.
    • -
  • Groupings: Groupings are containers, like Reports, but do not represent an Intelligence Production. They regroup Objects sharing an explicit context. For example, a Grouping might represent a set of data that, in time, given sufficient analysis, would mature to convey an incident or threat report as Report container.
    • -
  • Malware Analyses: As define by STIX 2.1 standard, Malware Analyses captures the metadata and results of a particular static or dynamic analysis performed on a malware instance or family.
    • -
  • Notes: Through this tab, you can find all the Notes that have been written in the platform, for example to add some analyst's unstructured knowledge about an Object.
    • -
  • External references: Intelligence is never created from nothing. External references give user a way to link sources or reference documents to any Object in the platform.
    • -
-

Analyses Default page is Reports

-

Reports

-

General presentation

-

Reports are one of the central component of the platform. It is from a Report that knowledge is extracted and integrated in the platform for further navigation, analyses and exports. Always tying the information back to a report allows for the user to be able to identify the source of any piece of information in the platform at all time.

-

In the MITRE STIX 2.1 documentation, a Report is defined as such :

-
-

Reports are collections of threat intelligence focused on one or more topics, such as a description of a threat actor, malware, or attack technique, including context and related details. They are used to group related threat intelligence together so that it can be published as a comprehensive cyber threat story.

-
-

As a result, a Report object in OpenCTI is a set of attributes and metadata defining and describing a document outside the platform, which can be a threat intelligence report from a security reseearch team, a blog post, a press article a video, a conference extract, a MISP event, or any type of document and source.

-

When clicking on the Reports tab at the top left, you see the list of all the Reports you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of reports.

-

Visualizing Knowledge within a Report

-

When clicking on a Report, you land on the Overview tab. For a Report, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge contained in the report, accessible through different views (See below for a dive-in). As described here.
    • -
  • Content: a tab to provide access to content mapping, suggested mapping and allows to preview, manage and write the deliverables associated with the Report. For example, an analytical report to share with other teams, a markdown file to feed a collaborative wiki, etc. As described here.
    • -
  • Entities: A table containing all SDO (Stix Domain Objects) contained in the Report, with search and filters available. It also displays if the SDO has been added directly or through inferences with the reasoning engine
    • -
  • Observables: A table containing all SCO (Stix Cyber Observable) contained in the Report, with search and filters available. It also displays if the SCO has been added directly or through inferences with the reasoning engine
    • -
  • Data: as described here.
    • -
-

Exploring and modifying the structured Knowledge contained in a Report can be done through different lenses.

-

Graph View

-

Graph View of a Report

-

In Graph view, STIX SDO are displayed as graph nodes and relationships as graph links. Nodes are colored depending of their type. Direct relationship are displayed as plain link and inferred relationships in dotted link. -At the top right, you will find a serie of icons. From there you can change the current type of view. Here you can also perform global action on the Knowledge of the Report. Let's highlight 2 of them: -- Suggestions: This tool suggests you some logical relationships to add between your contained Object to give more consistency to your Knowledge. -- Share with an Organization: if you have designated a main Organization in the platform settings, you can here share your Report and its content with users of an other Organization. -At the bottom, you have many option to manipulate the graph: -- Multiple option for shaping the graph and applying forces to the nodes and links -- Multiple selection options -- Multiple filters, including a time range selector allowing you to see the evolution of the Knowledge within the Report. -- Multiple creation and edition tools to modify the Knowledge contained in the Report.

-

Timeline view

-

Timeline view of a Report

-

This view allows you to see the structured Knowledge chronologically. This view is really useful when the report describes an attack or a campaign that lasted some time, and the analyst payed attention to the dates. -The view can be filtered and displayed relationships too.

-

Correlation view

-

Correlation view of a Report

-

The correlation view is a great way to visualize and find other Reports related to your current subject of interest. This graph displays all Report related to the important nodes contained in your current Report, for example Objects like Malware or Intrusion sets.

-

Matrix view

-

Matrix view of a Report

-

If your Report describes let's say an attack, a campaign, or an understanding of an Intrusion set, it should contains multiple attack patterns Objects to structure the Knowledge about the TTPs of the Threat Actor. Those attack patterns can be displayed as highlighted matrices, by default the MITRE ATT&CK Enterprise matrix. As some matrices can be huge, it can be also filtered to only display attack patterns describes in the Report.

-

Groupings

-

Groupings are an alternative to Report for grouping Objects sharing a context without describing an Intelligence Production.

-

In the MITRE STIX 2.1 documentation, a Grouping is defined as such :

-
-

A Grouping object explicitly asserts that the referenced STIX Objects have a shared context, unlike a STIX Bundle (which explicitly conveys no context). A Grouping object should not be confused with an intelligence product, which should be conveyed via a STIX Report. A STIX Grouping object might represent a set of data that, in time, given sufficient analysis, would mature to convey an incident or threat report as a STIX Report object. For example, a Grouping could be used to characterize an ongoing investigation into a security event or incident. A Grouping object could also be used to assert that the referenced STIX Objects are related to an ongoing analysis process, such as when a threat analyst is collaborating with others in their trust community to examine a series of Campaigns and Indicators.

-
-

When clicking on the Groupings tab at the top of the interface, you see the list of all the Groupings you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of the groupings.

-

Clicking on a Grouping, you land on its Overview tab. For a Groupings, the following tabs are accessible: -- Overview: as described here. -- Knowledge: a complex tab that regroups all the structured Knowledge contained in the groupings, as for a Report, except for the Timeline view. As described here. -- Content: a tab to provide access to content mapping, suggested mapping and allows to preview, manage and write the deliverables associated with the Grouping. For example, an analytical report to share with other teams, a markdown file to feed a collaborative wiki, etc. As described here. -- Entities: A table containing all SDO (Stix Domain Objects) contained in the Grouping, with search and filters available. It also display if the SDO has been added directly or through inferences with the reasonging engine -- Observables: A table containing all SCO (Stix Cyber Observable) contained in the Grouping, with search and filters available. It also display if the SDO has been added directly or through inferences with the reasonging engine -- Data: as described here.

-

Malware Analyses

-

Malware analyses are an important part of the Cyber Threat Intelligence, allowing an precise understanding of what and how a malware really do on the host but also how and from where it receives its command and communicates its results.

-

In OpenCTI, Malware Analyses can be created from enrichment connectors that will take an Observable as input and perform a scan on a online service platform to bring back results. As such, Malware Analyses can be done on File, Domain and URL.

-

In the MITRE STIX 2.1 documentation, a Malware Analyses is defined as such :

-
-

Malware Analyses captures the metadata and results of a particular static or dynamic analysis performed on a malware instance or family.

-
-

When clicking on the Malware Analyses tab at the top of the interface, you see the list of all the Malware Analyses you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of the Malware Analyses.

-

Clicking on a Malware Analyses, you land on its Overview tab. The following tabs are accessible: -- Overview: This view contains some additions from the common Overview here. You will find here details about how the analysis have been performed, what is the global result regarding the malicioussness of the analysed artifact and all the Observables that have been found during the analysis. -- Knowledge: If you Malware analysis is linked to other Objects that are not part of the analysis result, they will be displayed here. As described here. -- Content: This specific tab allows to previzualize, manage and write deliverable associated with the Malware Analyses. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here. -- Data: as described here. -- History: as described here.

-

Malware Analyses Overview

-

Notes

-

Not every Knowledge can be structured. For allowing any users to share their insights about a specific Knowledge, they can create a Note for every Object and relationship in OpenCTI they can access to. All the Notes are listed within the Analyses menu for allowing global review of this unstructured addition to the global Knowledge.

-

In the MITRE STIX 2.1 documentation, a Note is defined as such :

-
-

A Note is intended to convey informative text to provide further context and/or to provide additional analysis not contained in the STIX Objects, Marking Definition objects, or Language Content objects which the Note relates to. Notes can be created by anyone (not just the original object creator).

-
-

Clicking on a Note, you land on its Overview tab. The following tabs are accessible: -- Overview: as described here. -- Data: as described here. -- History: as described here.

-

External references

-

Intelligence is never created from nothing. External references give user a way to link sources or reference documents to any Object in the platform. All external references are listed within the Analyses menu for accessing directly sources of the structured Knowledge.

-

In the MITRE STIX 2.1 documentation, a External references is defined as such :

-
-

External references are used to describe pointers to information represented outside of STIX. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.

-
-

Clicking on an External reference, you land on its Overview tab. The following tabs are accessible: -- Overview: as described here.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-arsenal/index.html b/6.2.18/usage/exploring-arsenal/index.html deleted file mode 100755 index 8a5ec67e..00000000 --- a/6.2.18/usage/exploring-arsenal/index.html +++ /dev/null @@ -1,4374 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Arsenal - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Arsenal

-

When you click on "Arsenal" in the left-side bar, you access all the "Arsenal" tabs, visible on the top bar on the left. By default, the user directly access the "Malware" tab, but can navigate to the other tabs as well.

-

From the Arsenal section, users can access the following tabs:

-
    -
  • Malware: Malware represents any piece of code specifically designed to damage, disrupt, or gain unauthorized access to computer systems, networks, or user data.
    • -
  • Channels: Channels, in the context of cybersecurity, refer to places or means through which actors disseminate information. This category is used in particular in the context of FIMI (Foreign Information Manipulation Interference).
    • -
  • Tools: Tools represent legitimate, installed software or hardware applications on an operating system that can be misused by attackers for malicious purposes. (e.g. LOLBAS).
    • -
  • Vulnerabilities: Vulnerabilities are weaknesses or that can be exploited by attackers to compromise the security, integrity, or availability of a computer system or network.
    • -
-

Malware

-

General presentation

-

Malware encompasses a broad category of malicious pieces of code built, deployed, and operated by intrusion set. Malware can take many forms, including viruses, worms, Trojans, ransomware, spyware, and more. These entities are created by individuals or groups, including state-nations, state-sponsored groups, corporations, or hacktivist collectives.

-

Use the Malware SDO to model and track these threats comprehensively, facilitating in-depth analysis, response, and correlation with other security data.

-

When clicking on the Malware tab on the top left, you see the list of all the Malware you have access to, in respect with your allowed marking definitions. These malware are displayed as Cards where you can find a summary of the important Knowledge associated with each of them: description, aliases, related intrusion sets, countries and sectors they target, and labels. You can then search and filter on some common and specific attributes of Malware.

-

At the top right of each Card, you can click the star icon to put it as favorite. It will pin the card on top of the list. You will also be able to display all your favorite easily in your Custom Dashboards.

-

The Malware cards

-

Visualizing Knowledge associated with a Malware

-

When clicking on an Malware card you land on its Overview tab. For a Malware, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Malware. Different thematic views are proposed to easily see the victimology, the threat actors and intrusion sets using the Malware, etc. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Malware. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Channels

-

General presentation

-

Channels - such as forums, websites and social media platforms (e.g. Twitter, Telegram) - are mediums for disseminating news, knowledge, and messages to a broad audience. While they offer benefits like open communication and outreach, they can also be leveraged for nefarious purposes, such as spreading misinformation, coordinating cyberattacks, or promoting illegal activities.

-

Monitoring and managing content within Channels aids in analyzing threats, activities, and indicators associated with various threat actors, campaigns, and intrusion sets.

-

When clicking on the Channels tab at the top left, you see the list of all the Channels you have access to, in respect with your allowed marking definitions. These channels are displayed in a list where you can find certain fields characterizing the entity: type of channel, labels, and dates. You can then search and filter on some common and specific attributes of Channels.

-

Channels list

-

Visualizing Knowledge associated with a Channel

-

When clicking on a Channel in the list, you land on its Overview tab. For a Channel, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Channel. Different thematic views are proposed to easily see the victimology, the threat actors and intrusion sets using the Malware, etc. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Channel. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Tools

-

General presentation

-

Tools refers to legitimate, pre-installed software applications, command-line utilities, or scripts that are present on a compromised system. These objects enable you to model and monitor the activities of these tools, which can be misused by attackers.

-

When clicking on the Tools tab at the top left, you see the list of all the Tools you have access to, in respect with your allowed marking definitions. These tools are displayed in a list where you can find certain fields characterizing the entity: labels and dates. You can then search and filter on some common and specific attributes of Tools.

-

Tools list

-

Visualizing Knowledge associated with an Observed Data

-

When clicking on a Tool in the list, you land on its Overview tab. For a Tool, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Tool. Different thematic views are proposed to easily see the threat actors, the intrusion sets and the malware using the Tool. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Tool. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Vulnerabilities

-

General presentation

-

Vulnerabilities represent weaknesses or flaws in software, hardware, configurations, or systems that can be exploited by malicious actors. This object assists in managing and tracking the organization's security posture by identifying areas that require attention and remediation, while also providing insights into associated intrusion sets, malware and campaigns where relevant.

-

When clicking on the Vulnerabilities tab at the top left, you see the list of all the Vulnerabilities you have access to, in respect with your allowed marking definitions. These vulnerabilities are displayed in a list where you can find certain fields characterizing the entity: CVSS3 severity, labels, dates and creators (in the platform). You can then search and filter on some common and specific attributes of Vulnerabilities.

-

Vulnerabilities list

-

Visualizing Knowledge associated with an Observed Data

-

When clicking on a Vulnerabilities in the list, you land on its Overview tab. For a Vulnerability, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Vulnerability. Different thematic views are proposed to easily see the threat actors, the intrusion sets and the malware exploiting the Vulnerability. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Vulnerability. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-cases/index.html b/6.2.18/usage/exploring-cases/index.html deleted file mode 100755 index c1417fea..00000000 --- a/6.2.18/usage/exploring-cases/index.html +++ /dev/null @@ -1,4287 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cases - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Cases

-

When you click on "Cases" in the left-side bar, you access all the "Cases" tabs, visible on the top bar on the left. By default, the user directly access the "Incident Responses" tab, but can navigate to the other tabs as well.

-

As Analyses, Cases can contain other objects. This way, by adding context and results of your investigations in the case, you will be able to get an up-to-date overview of the ongoing situation, and later produce more easily an incident report.

-

From the Cases section, users can access the following tabs:

-
    -
  • Incident Responses: This type of Cases is dedicated to the management of incidents. An Incident Response case does not represent an incident, but all the context and actions that will encompass the response to a specific incident.
    • -
  • Request for Information: CTI teams are often asked to provide extensive information and analysis on a specific subject, be it related to an ongoing incident or a particular trending threat. Request for Information cases allow you to store context and actions relative to this type of request and its response.
    • -
  • Request for Takedown: When an organization is targeted by an attack campaign, a typical response action can be to request the Takedown of elements of the attack infrastructure, for example a domain name impersonating the organization to phish its employees, or an email address used to deliver phishing content. As Takedown needs in most case to reach out to external providers and be effective quickly, it often needs specific workflows. Request for Takedown cases give you a dedicated space to manage these specific actions.
    • -
  • Tasks: In every case, you need tasks to be performed in order to solve it. The Tasks tab allows you to review all created tasks to quickly see past due date, or quickly see every task assigned to a specific user.
    • -
  • Feedbacks: If you use your platform to interact with other teams and provide them CTI Knowledge, some users may want to give you feedback about it. Those feedbacks can easily be considered as another type of case to solve, as it will often refer to Knowledge inconsistency or gaps.
    • -
-

Cases Default page is Incident Response

-

Incident Response, Request for Information & Request for Takedown

-

General presentation

-

Incident responses, Request for Information & Request for Takedown cases are an important part of the case management system in OpenCTI. Here, you can organize the work of your team to respond to cybersecurity situations. You can also give context to the team and other users on the platform about the situation and actions (to be) taken.

-

To manage the situation, you can issue Tasks and assign them to users in the platform, by directly creating a Task or by applying a Case template that will append a list of predefined tasks.

-

To bring context, you can use your Case as a container (like Reports or Groupings), allowing you to add any Knowledge from your platform in it. You can also use this possibility to trace your investigation, your Case playing the role of an Incident report. You will find more information about case management here.

-

Incident Response, Request for Information & Request for Takedown are not STIX 2.1 Objects.

-

When clicking on the Incident Response, Request for Information & Request for Takedown tabs at the top, you see the list of all the Cases you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes.

-

Visualizing Knowledge within an Incident Response, Request for Information & Request for Takedown

-

When clicking on an Incident Response, Request for Information or Request for Takedown, you land on the Overview tab. The following tabs are accessible:

-
    -
  • Overview: Overview of Cases are slightly different from the usual (described here). Cases' Overview displays also the list of the tasks associated with the case. It also let you highlight Incident, Report or Sighting at the origin of the case. If other cases contains some Observables with your Case, they will be displayed as Related Cases in the Overview.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge contained in the Case, accessible through different views (See below for a dive-in). As described here.
    • -
  • Content: a tab to provide access to content mapping, suggested mapping and allows to preview, manage and write the deliverables associated with the Case. For example, an analytical report to share with other teams, a markdown file to feed a collaborative wiki, etc. As described here.
    • -
  • Entities: A table containing all SDO (Stix Domain Objects) contained in the Case, with search and filters available. It also displays if the SDO has been added directly or through inferences with the reasoning engine
    • -
  • Observables: A table containing all SCO (Stix Cyber Observable) contained in the Case, with search and filters available. It also displays if the SDO has been added directly or through inferences with the reasoning engine
    • -
  • Data: as described here.
    • -
-

Exploring and modifying the structured Knowledge contained in a Case can be done through different lenses.

-

Graph View

-

Graph View of a Case

-

In Graph view, STIX SDO are displayed as graph nodes and relationships as graph links. Nodes are colored depending on their type. Direct relationship are displayed as plain link and inferred relationships in dotted link. -At the top right, you will find a series of icons. From there you can change the current type of view. Here you can also perform global action on the Knowledge of the Case. Let's highlight 2 of them:

-
    -
  • Suggestions: This tool suggests you some logical relationships to add between your contained Object to give more consistency to your Knowledge.
    • -
  • Share with an Organization: if you have designated a main Organization in the platform settings, you can here share your Case and its content with users of another Organization. -At the bottom, you have many option to manipulate the graph:
    • -
  • Multiple option for shaping the graph and applying forces to the nodes and links
    • -
  • Multiple selection options
    • -
  • Multiple filters, including a time range selector allowing you to see the evolution of the Knowledge within the Case.
    • -
  • Multiple creation and edition tools to modify the Knowledge contained in the Case.
    • -
-

Timeline view

-

Timeline view of a Case

-

This view allows you to see the structured Knowledge chronologically. This view is particularly useful in the context of a Case, allowing you to see the chain of events, either from the attack perspectives, the defense perspectives or both. -The view can be filtered and displayed relationships too.

-

Matrix view

-

If your Case contains attack patterns, you will be able to visualize them in a Matrix view.

-

Tasks

-

Tasks are actions to be performed in the context of a Case (Incident Response, Request for Information, Request for Takedown). Usually, a task is assigned to a user, but important tasks may involve more participants.

-

When clicking on the Tasks tab at the top of the interface, you see the list of all the Tasks you have access to, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of the tasks.

-

Clicking on a Task, you land on its Overview tab. For a Tasks, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Content: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Feedbacks

-

When a user fill a feedback form from its Profile/Feedback menu, it will then be accessible here.

-

This feature gives the opportunity to engage with other users of your platform and to respond directly to their concern about it or the Knowledge, without the need of third party software.

-

Feedback Overview

-

Clicking on a Feedback, you land on its Overview tab. For a Feedback, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Content: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-entities/index.html b/6.2.18/usage/exploring-entities/index.html deleted file mode 100755 index 60ff2b2d..00000000 --- a/6.2.18/usage/exploring-entities/index.html +++ /dev/null @@ -1,4479 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Entities - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Entities

-

OpenCTI's Entities objects provides a comprehensive framework for modeling various targets and attack victims within your threat intelligence data. With five distinct Entity object types, you can represent sectors, events, organizations, systems, and individuals. This robust classification empowers you to contextualize threats effectively, enhancing the depth and precision of your analysis.

-

When you click on "Entities" in the left-side bar, you access all the "Entities" tabs, visible on the top bar on the left. By default, the user directly access the "Sectors" tab, but can navigate to the other tabs as well.

-

From the Entities section, users can access the following tabs:

-
    -
  • Sectors: areas of activity.
    • -
  • Events: event in the real world.
    • -
  • Organizations: groups with specific aims such as companies and government entities.
    • -
  • Systems: technologies such as platforms and software.
    • -
  • Individuals: real persons.
    • -
-

Sectors

-

General presentation

-

Sectors represent specific domains of activity, defining areas such as energy, government, health, finance, and more. Utilize sectors to categorize targeted industries or sectors of interest, providing valuable context for threat intelligence analysis within distinct areas of the economy.

-

When clicking on the Sectors tab at the top left, you see the list of all the Sectors you have access to, in respect with your allowed marking definitions.

-

Sectors list

-

Visualizing Knowledge associated with a Sector

-

When clicking on a Sector in the list, you land on its Overview tab. For a Sector, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Sector. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Sector. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Sector. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in the Sector.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Sector overview

-

Events

-

General presentation

-

Events encompass occurrences like international sports events, summits (e.g., G20), trials, conferences, or any significant happening in the real world. By modeling events, you can analyze threats associated with specific occurrences, allowing for targeted investigations surrounding high-profile incidents.

-

When clicking on the Events tab at the top left, you see the list of all the Events you have access to, in respect with your allowed marking definitions.

-

Events list

-

Visualizing Knowledge associated with an Event

-

When clicking on an Event in the list, you land on its Overview tab. For an Event, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Event. Different thematic views are proposed to easily see the related entities, the threats, the locations, etc. linked to the Event. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Event. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted during an attack against the Event.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Organizations

-

General presentation

-

Organizations include diverse entities such as companies, government bodies, associations, non-profits, and other groups with specific aims. Modeling organizations enables you to understand the threat landscape concerning various entities, facilitating investigations into cyber-espionage, data breaches, or other malicious activities targeting specific groups.

-

When clicking on the Organizations tab at the top left, you see the list of all the Organizations you have access to, in respect with your allowed marking definitions.

-

Organizations list

-

Visualizing Knowledge associated with an Organization

-

When clicking on an Organization in the list, you land on its Overview tab. For an Organization, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Organization. Different thematic views are proposed to easily see the related entities, the threats, the locations, etc. linked to the Organization. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Organization. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in the Organization.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Furthermore, an Organization can be observed from an "Author" perspective. It is possible to change this viewpoint to the right of the entity name, using the "Display as" drop-down menu (see screenshot below). This different perspective is accessible in the Overview, Knowledge and Analyses tabs. When switched to "Author" mode, the observed data pertains to the entity's description as an author within the platform:

-
    -
  • Overview: The "Latest created relationships" and "Latest containers about the object" panels are replaced by the "Latest containers authored by this entity" panel.
    • -
  • Knowledge: A tab that presents an overview of the data authored by the Organization (i.e. counters and a graph).
    • -
  • Analyses: The list of all Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) for which the Organization is the author.
    • -
-

Organization author view

-

Systems

-

General presentation

-

Systems represent software applications, platforms, frameworks, or specific tools like WordPress, VirtualBox, Firefox, Python, etc. Modeling systems allows you to focus on threats related to specific software or technology, aiding in vulnerability assessments, patch management, and securing critical applications.

-

When clicking on the Systems tab at the top left, you see the list of all the Systems you have access to, in respect with your allowed marking definitions.

-

Systems list

-

Visualizing Knowledge associated with a System

-

When clicking on a System in the list, you land on its Overview tab. For a System, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the System. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the System. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the System. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in the System.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Furthermore, a System can be observed from an "Author" perspective. It is possible to change this viewpoint to the right of the entity name, using the "Display as" drop-down menu (see screenshot below). This different perspective is accessible in the Overview, Knowledge and Analyses tabs. When switched to "Author" mode, the observed data pertains to the entity's description as an author within the platform:

-
    -
  • Overview: The "Latest created relationships" and "Latest containers about the object" panels are replaced by the "Latest containers authored by this entity" panel.
    • -
  • Knowledge: A tab that presents an overview of the data authored by the System (i.e. counters and a graph).
    • -
  • Analyses: The list of all Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) for which the System is the author.
    • -
-

Individuals

-

General presentation

-

Individuals represent specific persons relevant to your threat intelligence analysis. This category includes targeted individuals, or influential figures in various fields. Modeling individuals enables you to analyze threats related to specific people, enhancing investigations into cyber-stalking, impersonation, or other targeted attacks.

-

When clicking on the Individuals tab at the top left, you see the list of all the Individuals you have access to, in respect with your allowed marking definitions.

-

Positions list

-

Visualizing Knowledge associated with an Individual

-

When clicking on an Individual in the list, you land on its Overview tab. For an Individual, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Individual. Different thematic views are proposed to easily see the related entities, the threats, the locations, etc. linked to the Individual. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Individual. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in the Individual.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Furthermore, an Individual can be observed from an "Author" perspective. It is possible to change this viewpoint to the right of the entity name, using the "Display as" drop-down menu (see screenshot below). This different perspective is accessible in the Overview, Knowledge and Analyses tabs. When switched to "Author" mode, the observed data pertains to the entity's description as an author within the platform:

-
    -
  • Overview: The "Latest created relationships" and "Latest containers about the object" panels are replaced by the "Latest containers authored by this entity" panel.
    • -
  • Knowledge: A tab that presents an overview of the data authored by the Individual (i.e. counters and a graph).
    • -
  • Analyses: The list of all Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) for which the Individual is the author.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-events/index.html b/6.2.18/usage/exploring-events/index.html deleted file mode 100755 index 2c9136ab..00000000 --- a/6.2.18/usage/exploring-events/index.html +++ /dev/null @@ -1,4285 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Events - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Events

-

When you click on "Events" in the left-side bar, you access all the "Events" tabs, visible on the top bar on the left. By default, the user directly access the "Incidents" tab, but can navigate to the other tabs as well.

-

From the Events section, users can access the following tabs:

-
    -
  • Incidents: In OpenCTI, Incidents correspond to a negative event happening on an information system. This can include a cyberattack (intrusion, phishing, etc.), a consolidated security alert generated by a SIEM or EDR that need to be qualified, and so on. It can also refer to an information warfare attack in the context of countering disinformation.
    • -
  • Sightings: Sightings correspond to the event in which an Observable (IP, domain name, certificate, etc.) is detected by or within an information system, an individual or an organization. Most often, this corresponds to a security event transmitted by a SIEM or an EDR.
    • -
  • Observed Data: Observed Data has been added in OpenCTI by compliance with the STIX 2.1 standard. You can see it has a pseudo-container that contains Observables, like a line of firewall log for example. Currently, it is rarely used.
    • -
-

Incidents

-

General presentation

-

Incidents usually represents negative events impacting resources you want to protect, but local definitions can vary a lot, from a simple security events send by a SIEM to a massive scale supply chain attack impacting a whole activity sector.

-

In the MITRE STIX 2.1, the Incident SDO has not yet been finalized and is the object of important work as part of a forthcoming STIX Extension.

-

When clicking on the Incidents tab at the top left, you see the list of all the Incidents you have access to, in respect with your allowed marking definitions.

-

Incidents list

-

Visualizing Knowledge associated with an Incident

-

When clicking on an Incident in the list, you land on its Overview tab. For an Incident, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity to display two distribution graphs of its related Entities (STIX SDO) and Observable (STIX SCO).
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Incident. Different thematic views are proposed to easily see the victimology, arsenal, techniques and so on used in the context of the Incident. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Incident. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Incident overview

-

Sightings

-

General presentation

-

The Sightings correspond to events in which an Observable (IP, domain name, url, etc.) is detected by or within an information system, an individual or an organization. Most often, this corresponds to a security event transmitted by a SIEM or EDR.

-

In OpenCTI, as we are in a cybersecurity context, Sightings are associated with Indicators of Compromise (IoC) and the notion of "True positive" and "False positive".

-

It is important to note that Sightings are a type of relationship (not a STIX SDO or STIX SCO), between an Observable and an Entities or Locations.

-

When clicking on the Sightings tab at the top left, you see the list of all the Sightings you have access to, in respect with your allowed marking definitions.

-

Sightings list

-

Visualizing Knowledge associated with a Sighting

-

When clicking on a Sighting in the list, you land on its Overview tab. As other relationships in the platform, Sighting's overview displays common related metadata, containers, external references, notes and entities linked by the relationship.

-

In addition, this overview displays: -- Qualification : if the Sighting is a True Positive or a False Positive -- Count : number of times the event has been seen

-

Observed Data

-

General presentation

-

Observed Data correspond to an extract from a log that contains Observables.

-

In the MITRE STIX 2.1, the Observed Data SDO is defined as such:

-
-

Observed Data conveys information about cybersecurity related entities such as files, systems, and networks using the STIX Cyber-observable Objects (SCOs). For example, Observed Data can capture information about an IP address, a network connection, a file, or a registry key. Observed Data is not an intelligence assertion, it is simply the raw information without any context for what it means.

-
-

When clicking on the Observed Data tab at the top left, you see the list of all the Observed Data you have access to, in respect with your allowed marking definitions.

-

Visualizing Knowledge associated with an Observed Data

-

When clicking on an Observed Data in the list, you land on its Overview tab. The following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity to display a distribution graphs of its related Observables (STIX SCO).
    • -
  • Entities : a sortable and filterable list of all Entities (SDO)
    • -
  • Observables: a sortable and filterable list of all Observables (SCO) in relation with the Observed Data
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-locations/index.html b/6.2.18/usage/exploring-locations/index.html deleted file mode 100755 index e6cadcd0..00000000 --- a/6.2.18/usage/exploring-locations/index.html +++ /dev/null @@ -1,4460 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Locations - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Location

-

OpenCTI's Locations objects provides a comprehensive framework for representing various geographic entities within your threat intelligence data. With five distinct Location object types, you can precisely define regions, countries, areas, cities, and specific positions. This robust classification empowers you to contextualize threats geographically, enhancing the depth and accuracy of your analysis.

-

When you click on "Locations" in the left-side bar, you access all the "Locations" tabs, visible on the top bar on the left. By default, the user directly access the "Regions" tab, but can navigate to the other tabs as well.

-

From the Locations section, users can access the following tabs:

-
    -
  • Regions: very large geographical territories, such as a continent.
    • -
  • Countries: the world's countries.
    • -
  • Areas: more or less extensive geographical areas and often not having a very defined limit
    • -
  • Cities: the world's cities.
    • -
  • Positions: very precise positions on the globe.
    • -
-

Regions

-

General presentation

-

Regions encapsulate broader geographical territories, often representing continents or significant parts of continents. Examples include EMEA (Europe, Middle East, and Africa), Asia, Western Europe, and North America. Utilize regions to categorize large geopolitical areas and gain macro-level insights into threat patterns.

-

When clicking on the Regions tab at the top left, you see the list of all the Regions you have access to, in respect with your allowed marking definitions.

-

Regions list

-

Visualizing Knowledge associated with a Region

-

When clicking on a Region in the list, you land on its Overview tab. For a Region, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity of not having a Details section but a map locating the Region.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Region. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Region. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Location. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in a Region.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Region Overview

-

Countries

-

General presentation

-

Countries represent individual nations across the world. With this object type, you can specify detailed information about a particular country, enabling precise localization of threat intelligence data. Countries are fundamental entities in geopolitical analysis, offering a focused view of activities within national borders.

-

When clicking on the Countries tab at the top left, you see the list of all the Countries you have access to, in respect with your allowed marking definitions.

-

Countries list

-

Visualizing Knowledge associated with a Country

-

When clicking on a Country in the list, you land on its Overview tab. For a Country, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity of not having a Details section but a map locating the Country.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Country. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Country. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Country. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in a Country.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Areas

-

General presentation

-

Areas define specific geographical regions of interest, such as the Persian Gulf, the Balkans, or the Caucasus. Use areas to identify unique zones with distinct geopolitical, cultural, or strategic significance. This object type facilitates nuanced analysis of threats within defined geographic contexts.

-

When clicking on the Areas tab at the top left, you see the list of all the Areas you have access to, in respect with your allowed marking definitions.

-

Areas list

-

Visualizing Knowledge associated with an Area

-

When clicking on an Area in the list, you land on its Overview tab. For an Area, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity of not having a Details section but a map locating the Area.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Area. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Area. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Area. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in an Area.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Cities

-

General presentation

-

Cities provide granular information about urban centers worldwide. From major metropolises to smaller towns, cities are crucial in understanding localized threat activities. With this object type, you can pinpoint threats at the urban level, aiding in tactical threat assessments and response planning.

-

When clicking on the Cities tab at the top left, you see the list of all the Cities you have access to, in respect with your allowed marking definitions.

-

Cities list

-

Visualizing Knowledge associated with a City

-

When clicking on a City in the list, you land on its Overview tab. For a City, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity of not having a Details section but a map locating the City.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the City. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the City. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the City. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted in a City.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Positions

-

General presentation

-

Positions represent highly precise geographical points, such as monuments, buildings, or specific event locations. This object type allows you to define exact coordinates, enabling accurate mapping of events or incidents. Positions enhance the granularity of your threat intelligence data, facilitating precise geospatial analysis.

-

When clicking on the Positions tab at the top left, you see the list of all the Positions you have access to, in respect with your allowed marking definitions.

-

Positions list

-

Visualizing Knowledge associated with a Position

-

When clicking on a Position in the list, you land on its Overview tab. For a Position, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity to display a map locating the Position.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Position. Different thematic views are proposed to easily see the related entities, the threats, the incidents, etc. linked to the Position. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Position. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which an Indicator (IP, domain name, url, etc.) is sighted at a Position.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-observations/index.html b/6.2.18/usage/exploring-observations/index.html deleted file mode 100755 index c6f1d97b..00000000 --- a/6.2.18/usage/exploring-observations/index.html +++ /dev/null @@ -1,4383 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Observations - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Observations

-

When you click on "Observations" in the left-side bar, you access all the "Observations" tabs, visible on the top bar on the left. By default, the user directly access the "Observables" tab, but can navigate to the other tabs as well.

-

From the Observations section, users can access the following tabs:

-
    -
  • Observables: An Observable represents an immutable object. Observables can encompass a wide range of entities such as IPv4 addresses, domain names, email addresses, and more.
    • -
  • Artefacts: In OpenCTI, the Artefacts is a particular Observable. It may contain a file, such as a malware sample.
    • -
  • Indicators: An Indicator is a detection object. It is defined by a search pattern, which could be expressed in various formats such as STIX, Sigma, YARA, among others.
    • -
  • Infrastructures: An Infrastructure describes any systems, software services and any associated physical or virtual resources intended to support some purpose (e.g. C2 servers used as part of an attack, devices or servers that are part of defense, database servers targeted by an attack, etc.).
    • -
-

Observables

-

General presentation

-

An Observable is a distinct entity from the Indicator within OpenCTI and represents an immutable object. Observables can encompass a wide range of entities such as IPv4 addresses, domain names, email addresses, and more. Importantly, Observables don't inherently imply malicious intent, they can include items like legitimate IP addresses or domains associated with an organization. Additionally, they serve as raw data points without the additional detection context found in Indicators.

-

When clicking on the Observables tab at the top left, you see the list of all the Observables you have access to, in respect with your allowed marking definitions.

-

Observables list

-

Visualizing Knowledge associated with an Observable

-

When clicking on an Observable in the list, you land on its Overview tab. For an Observable, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity to display Indicators composed with the Observable.
    • -
  • Knowledge: a tab listing all its relationships and nested objects.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Observation. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which the Observable (IP, domain name, url, etc.) has been sighted.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Observable overview

-

Artefacts

-

General presentation

-

An Artefact is a particular Observable. It may contain a file, such as a malware sample. Files can be uploaded or downloaded in encrypted archives, providing an additional layer of security against potential manipulation of malicious payloads.

-

When clicking on the Artefacts tab at the top left, you see the list of all the Artefacts you have access to, in respect with your allowed marking definitions.

-

Artefacts list

-

Visualizing Knowledge associated with an Artefact

-

When clicking on an Artefact in the list, you land on its Overview tab. For an Artefact, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity to be able to download the attached file.
    • -
  • Knowledge: a tab listing all its relationships and nested objects.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Artefact. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which the Artefact has been sighted.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Artefact overview

-

Indicators

-

General presentation

-

An Indicator is a detection object. It is defined by a search pattern, which could be expressed in various formats such as STIX, Sigma, YARA, among others. This pattern serves as a key to identify potential threats within the data. Furthermore, an Indicator includes additional information that enriches its detection context. This information encompasses:

-
    -
  • Validity dates: Indicators are accompanied by a time frame, specifying the duration of their relevance, and modeled by the Valid from and Valid until dates.
    • -
  • Actionable fields: Linked to the validity dates, the Revoked and Detection fields can be used to sort Indicators for detection purposes.
    • -
  • Kill chain phase: They indicate the phase within the cyber kill chain where they are applicable, offering insights into the progression of a potential threat.
    • -
  • Types: Indicators are categorized based on their nature, aiding in classification and analysis.
    • -
-

When clicking on the Indicators tab at the top left, you see the list of all the Indicators you have access to, in respect with your allowed marking definitions.

-

Indicators list

-

Visualizing Knowledge associated with an Indicator

-

When clicking on an Indicator in the list, you land on its Overview tab. For an Indicator, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity to display the Observables on which it is based.
    • -
  • Knowledge: a tab listing all its relationships.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Indicator. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Sightings: a table containing all Sightings relationships corresponding to events in which the Indicator has been sighted.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Indicator overview

-

Infrastructures

-

General presentation

-

An Infrastructure refers to a set of resources, tools, systems, or services employed by a threat to conduct their activities. It represents the underlying framework or support system that facilitates malicious operations, such as the command and control (C2) servers in an attack. Notably, like Observables, an Infrastructure doesn't inherently imply malicious intent. It can also represent legitimate resources affiliated with an organization (e.g. devices or servers that are part of defense, database servers targeted by an attack, etc.).

-

When clicking on the Infrastructures tab at the top left, you see the list of all the Infrastructures you have access to, in respect with your allowed marking definitions.

-

Infrastructures list

-

Visualizing Knowledge associated with an Infrastructure

-

When clicking on an Infrastructure in the list, you land on its Overview tab. For an Infrastructure, the following tabs are accessible:

-
    -
  • Overview: as described here, with the particularity to display distribution graphs of its related Observable (STIX SCO).
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Infrastructure. Different thematic views are proposed to easily see the threats, the arsenal, the observations, etc. linked to the Infrastructure. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Infrastructure. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-techniques/index.html b/6.2.18/usage/exploring-techniques/index.html deleted file mode 100755 index 8f41dedb..00000000 --- a/6.2.18/usage/exploring-techniques/index.html +++ /dev/null @@ -1,4392 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Techniques - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Techniques

-

When you click on "Techniques" in the left-side bar, you access all the "Techniques" tabs, visible on the top bar on the left. By default, the user directly access the "Attack pattern" tab, but can navigate to the other tabs as well.

-

From the Techniques section, users can access the following tabs:

-
    -
  • Attack pattern: attacks pattern used by the threat actors to perform their attacks. By default, OpenCTI is provisionned with attack patterns from MITRE ATT&CK matrices (for CTI) and DISARM matrix (for FIMI).
    • -
  • Narratives: In OpenCTI, narratives used by threat actors can be represented and linked to other Objects. Narratives are mainly used in the context of disinformation campaigns where it is important to trace which narratives have been and are still used by threat actors.
    • -
  • Courses of action: A Course of Action is an action taken either to prevent an attack or to respond to an attack that is in progress. It may describe technical, automatable responses (applying patches, reconfiguring firewalls) but can also describe higher level actions like employee training or policy changes. For example, a course of action to mitigate a vulnerability could describe applying the patch that fixes it.
    • -
  • Data sources: Data sources represent the various subjects/topics of information that can be collected by sensors/logs. Data sources also include data components,
    • -
  • Data components: Data components identify specific properties/values of a data source relevant to detecting a given ATT&CK technique or sub-technique.
    • -
-

Attack pattern

-

General presentation

-

Attacks pattern used by the threat actors to perform their attacks. By default, OpenCTI is provisionned with attack patterns from MITRE ATT&CK matrices and CAPEC (for CTI) and DISARM matrix (for FIMI).

-

In the MITRE STIX 2.1 documentation, an Attack pattern is defined as such :

-
-

Attack Patterns are a type of TTP that describe ways that adversaries attempt to compromise targets. Attack Patterns are used to help categorize attacks, generalize specific attacks to the patterns that they follow, and provide detailed information about how attacks are performed. An example of an attack pattern is "spear phishing": a common type of attack where an attacker sends a carefully crafted e-mail message to a party with the intent of getting them to click a link or open an attachment to deliver malware. Attack Patterns can also be more specific; spear phishing as practiced by a particular threat actor (e.g., they might generally say that the target won a contest) can also be an Attack Pattern.

-
-

When clicking on the Attack pattern tab at the top left, you access the list of all the attack pattern you have access too, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of attack patterns.

-

Visualizing Knowledge associated with an Attack pattern

-

When clicking on an Attack pattern, you land on its Overview tab. For an Attack pattern, the following tabs are accessible:

-
    -
  • -

    Overview: Overview of Attack pattern is a bit different as the usual described here. The "Details" box is more structured and contains information about:

    -
    • -
  • -

    parent or subtechniques (as in the MITRE ATT&CK matrices),

    -
    • -
  • related kill chain phases
    • -
  • Platform on which the Attack pattern is usable,
    • -
  • permission required to apply it
    • -
  • Related detection technique
    • -
  • Courses of action to mitigate the Attack pattern
    • -
  • Data components in which find data to detect the usage of the Attack pattern
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Attack pattern. Different thematic views are proposed to easily see Threat Actors and Intrusion Sets using this techniques, linked incidents, etc.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Attack pattern. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Narratives

-

General presentation

-

In OpenCTI, narratives used by threat actors can be represented and linked to other Objects. Narratives are mainly used in the context of disinformation campaigns where it is important to trace which narratives have been and are still used by threat actors.

-

An example of Narrative can be "The country A is weak and corrupted" or "The ongoing operation aims to free people".

-

Narrative can be a mean in the context of a more broad attack or the goal of the operation, a vision to impose.

-

When clicking on the Narrative tab at the top left, you access the list of all the Narratives you have access too, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of narratives.

-

Visualizing Knowledge associated with a Narrative

-

When clicking on a Narrative, you land on its Overview tab. For a Narrative, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Narratives. Different thematic views are proposed to easily see the Threat actors and Intrusion Set using the Narrative, etc.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the technique. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Courses of action

-

General presentation

-

In the MITRE STIX 2.1 documentation, an Course of action is defined as such :

-
-

A Course of Action is an action taken either to prevent an attack or to respond to an attack that is in progress. It may describe technical, automatable responses (applying patches, reconfiguring firewalls) but can also describe higher level actions like employee training or policy changes. For example, a course of action to mitigate a vulnerability could describe applying the patch that fixes it.

-
-

When clicking on the Courses of action tab at the top left, you access the list of all the Courses of action you have access too, in respect with your allowed marking definitions. You can then search and filter on some common and specific attributes of course of action.

-

Visualizing Knowledge associated with a Course of action

-

When clicking on a Course of Action, you land on its Overview tab. For a Course of action, the following tabs are accessible:

-
    -
  • Overview: Overview of Course of action is a bit different as the usual described here. In "Details" box, mitigated attack pattern are listed.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Narratives. Different thematic views are proposed to easily see the Threat actors and Intrusion Set using the Narrative, etc.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Course of action. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Data sources & Data components

-

General presentation

-

In the MITRE ATT&CK documentation, Data sources are defined as such :

-
-

Data sources represent the various subjects/topics of information that can be collected by sensors/logs. Data sources also include data components, which identify specific properties/values of a data source relevant to detecting a given ATT&CK technique or sub-technique.

-
-

Visualizing Knowledge associated with a Data source or a Data components

-

When clicking on a Data source or a Data component, you land on its Overview tab. For a Course of action, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/exploring-threats/index.html b/6.2.18/usage/exploring-threats/index.html deleted file mode 100755 index 6d91adb3..00000000 --- a/6.2.18/usage/exploring-threats/index.html +++ /dev/null @@ -1,4295 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Threats - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Threats

-

When you click on "Threats" in the left-side bar, you access all the "Threats" tabs, visible on the top bar on the left. By default, the user directly access the "Threat Actor (Group)" tab, but can navigate to the other tabs as well.

-

From the Threats section, users can access the following tabs:

-
    -
  • Threat actors (Group): Threat actor (Group) represents a physical group of attackers operating an Intrusion set, using malware and attack infrastructure, etc.
    • -
  • Threat actors (Indvidual): Threat actor (Individual) represents a real attacker that can be described by physical and personal attributes and motivations. Threat actor (Individual) operates Intrusion set, uses malware and infrastructure, etc.
    • -
  • Intrusion sets: Intrusion set is an important concept in Cyber Threat Intelligence field. It is a consistent set of technical and non-technical elements corresponding of what, how and why a Threat actor acts. it is particularly useful for associating multiple attacks and malicious actions to a defined Threat, even without sufficient information regarding who did them. Often, with you understanding of the threat growing, you will link an Intrusion set to a Threat actor (either a Group or an Individual).
    • -
  • Campaigns: Campaign represents a series of attacks taking place in a certain period of time and/or targeting a consistent subset of Organization/Individual.
    • -
-

Threat actors (Group and Individual)

-

General presentation

-

Threat actors are the humans who are building, deploying and operating intrusion sets. A threat actor can be an single individual or a group of attackers (who may be composed of individuals). A group of attackers may be a state-nation, a state-sponsored group, a corporation, a group of hacktivists, etc.

-

Beware, groups of attackers might be modelled as "Intrusion sets" in feeds, as there is sometimes a misunderstanding in the industry between group of people and the technical/operational intrusion set they operate.

-

The Threat actor (Group) cards

-

When clicking on the Threat actor (Group or Individual) tabs at the top left, you see the list of all the groups of Threat actors or Individual Threat actors you have access to, in respect with your allowed marking definitions. These groups or individual are displayed as Cards where you can find a summary of the important Knowledge associated with each of them: description, aliases, malware they used, countries and industries they target, labels. You can then search and filter on some common and specific attributes of Threat actors.

-

At the top right of each Card, you can click the star icon to put it as favorite. It will pin the card on top of the list. You will also be able to display all your favorite easily in your Custom Dashboards.

-

Demographic and Biographic Information

-

Individual Threat actors have unique properties to represent demographic and biographic information. Currently tracked demographics include their countries of residence, citizenships, date of birth, gender, and more.

-

Threat Actor (Individual) Demographics

-

Biographic information includes their eye and hair color, as well as known heights and weights.

-

Threat Actor (Individual) Biographics

-

An Individual Threat actor can also be tracked as employed by an Organization or a Threat Actor group. This relationship can be set under the knowledge tab.

-

Visualizing Knowledge associated with a Threat actor

-

When clicking on a Threat actor Card, you land on its Overview tab. For a Threat actor, the following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Threat actor. Different thematic views are proposed to easily see the victimology, arsenal and techniques used by the Threat actor, etc. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Threat actor. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Intrusion Sets

-

An intrusion set is a consistent group of technical elements such as "tactics, technics and procedures" (TTP), tools, malware and infrastructure used by a threat actor against one or a number of victims who are usually sharing some characteristics (field of activity, country or region) to reach a similar goal whoever the victim is. The intrusion set may be deployed once or several times and may evolve with time. -Several intrusion sets may be linked to one threat actor. All the entities described below may be linked to one intrusion set. There are many debates in the Threat Intelligence community on how to define an intrusion set and how to distinguish several intrusion sets with regards to:

-
    -
  • their differences
    • -
  • their evolutions
    • -
  • the possible reuse
    • -
  • "false flag" type of attacks
    • -
-

As OpenCTI is very customizable, each organization or individual may use these categories as they wish. Instead, it is also possible to use the import feed for the choice of categories.

-

Intrusion set Cards

-

When clicking on the Intrusion set tab on the top left, you see the list of all the Intrusion sets you have access to, in respect with your allowed marking definitions. These intrusion sets are displayed as Cards where you can find a summary of the important Knowledge associated with each of them: description, aliases, malware they used, countries and industries they target, labels. You can then search and filter on some common and specific attributes of Intrusion set.

-

At the top right of each Card, you can click the star icon to put it as favorite. It will pin the card on top of the list. You will also be able to display all your favorite easily in your Custom Dashboards.

-

Visualizing Knowledge associated with an Intrusion set

-

When clicking on an Intrusion set Card, you land on its Overview tab. The following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Intrusion Set. Different thematic views are proposed to easily see the victimology, arsenal and techniques used by the Intrusion Set, etc. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Intrusion set. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
-

Campaigns

-

A campaign can be defined as "a series of malicious activities or attacks (sometimes called a "wave of attacks") taking place within a limited period of time, against a defined group of victims, associated to a similar intrusion set and characterized by the use of one or several identical malware towards the various victims and common TTPs". -However, a campaign is an investigation element and may not be widely recognized. Thus, a provider might define a series of attacks as a campaign and another as an intrusion set. -Campaigns can be attributed to an Intrusion set.

-

Campaigns cards

-

When clicking on the Campaign tab on the top left, you see the list of all the Campaigns you have access to, in respect with your allowed marking definitions. These campaigns are displayed as Cards where you can find a summary of the important Knowledge associated with each of them: description, aliases, malware used, countries and industries they target, labels. You can then search and filter on some common and specific attributes of Campaigns.

-

At the top right of each Card, you can click the star icon to put it as favorite. It will pin the card on top of the list. You will also be able to display all your favorite easily in your Custom Dashboards.

-

Visualizing Knowledge associated with a Campaign

-

When clicking on an Campaign Card, you land on its Overview tab. The following tabs are accessible:

-
    -
  • Overview: as described here.
    • -
  • Knowledge: a complex tab that regroups all the structured Knowledge linked to the Campaign. Different thematic views are proposed to easily see the victimology, arsenal and techniques used in the context of the Campaign. As described here.
    • -
  • Content: This specific tab allows to previzualize, manage and write deliverable associated with the Campaign. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc. As described here.
    • -
  • Analyses: as described here.
    • -
  • Data: as described here.
    • -
  • History: as described here.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/export/index.html b/6.2.18/usage/export/index.html deleted file mode 100755 index 79339c81..00000000 --- a/6.2.18/usage/export/index.html +++ /dev/null @@ -1,4218 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Manual export - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Manual export

-

Introduction

-

With the OpenCTI platform, you can manually export your intelligence content in the following formats:

-
    -
  • JSON,
    • -
  • CSV,
    • -
  • PDF,
    • -
  • TXT.
    • -
-

Generate an export panel

-

Export in structured or document format

-

-

Generate an export

-

To export one or more entities you have two possibilities. First you can click on the button "Open export panel". The list of pre-existing exports will open, and in the bottom right-hand corner you can configure and generate a new export.

-

open export panel -This opens the export settings panel, where you can customize your export according to four fields:

-
    -
  • desired export format (text/csv, application/pdf, application/vnd.oasis.stix+json, text/plain)
    • -
  • export type (simple or full),
    • -
  • the max marking definition levels of the elements to be included in the export (a TLP level, for instance). The list of the available max markings is limited by the user allowed markings and its maximum shareable markings (more details about maximum shareable marking definitions in data segregation). For a marking definition type to be taken into account here, a marking definition from this type must be provided. For example, if you select TLP:GREEN for this field, AMBER and RED elements will be excluded but it will not take into account any PAP markings unless one is elected too.
    • -
  • the file marking definition levels of the export (a TLP level, for instance). This marking on the file itself will then restrain the access to it in accordance with users' marking definition levels. For example, if a file has the marking TLP:RED and INTERNAL, a user will need to have these marking to see and access the file in the platform.```
    • -
-

customize your export

-

The second way is to click directly on the "Generate an Export" button to export the content of an entity in the desired format. The same settings panel will open.

-

Export entity content

-

Both ways add your export in the Exported files list in the Data tab. -Exported files list

-

Export possibilities

-

All entities in your instance can be exported either directly via Generate Export or indirectly via Export List in .json and .csv formats.

-

Export a list of entities

-

You have the option to export either a single element, such as a report, or a collection of elements, such as multiple reports. These exports may contain not only the entity itself but also related elements, depending on the type of export you select: "simple" or "full". See the Export types (simple and full) section.

-

You can also choose to export a list of entities within a container. To do so, go to the container's entities tab. For example, for a report, if you only want to retrieve entity type attack pattern and indicators to design a detection strategy, go to the entities tab and select specific elements for export.

-

Export specific elements

-

-

Export types (simple and full)

-

When you wish to export only the content of a specific entity such as a report, you can choose a "simple" export type.

-

If you also wish to export associated content, you can choose a "full" export. With this type of export, the entity will be exported along with all entities directly associated with the central one (first neighbors).

-

Export types

-

Exports list panel

-

Once an export has been created, you can find it in the export list panel. Simply click on a particular export to download it.

-

You can also generate a new export directly from the Exports list, as explained in the Generate an export section.

-

Exports list

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/feeds/index.html b/6.2.18/usage/feeds/index.html deleted file mode 100755 index ae7fe69a..00000000 --- a/6.2.18/usage/feeds/index.html +++ /dev/null @@ -1,4248 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Native feeds - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Native feeds

-

OpenCTI provides versatile mechanisms for sharing data through its built-in feeds, including Live streams, TAXII collections, and CSV feeds.

-

Feed configuration

-

Feeds are configured in the "Data > Data sharing" window. Configuration for all feed types is uniform and relies on the following parameters:

-
    -
  • Filter setup: The feed can have specific filters to publish only a subset of the platform overall knowledge. Any data that meets the criteria established by the user's feed filters will be shared (e.g. specific types of entities, labels, marking definitions, etc.).
    • -
  • Access control: A feed can be either public, i.e. accessible without authentication, or restricted. By default, it's accessible to any user with the "Access data sharing" capability, but it's possible to increase restrictions by limiting access to a specific user, group, or organization.
    • -
-

Feed access restriction

-

By carefully configuring filters and access controls, you can tailor the behavior of Live streams, TAXII collections, and CSV feeds to align with your specific data-sharing needs.

-

-

Live streams

-

Introduction

-

Live streams, an exclusive OpenCTI feature, increase the capacity for real-time data sharing by serving STIX 2.1 bundles as TAXII collections with advanced capabilities. What distinguishes them is their dynamic nature, which includes the creation, updating, and deletion of data. Unlike TAXII, Live streams comprehensively resolve relationships and dependencies, ensuring a more nuanced and interconnected exchange of information. This is particularly beneficial in scenarios where sharing involves entities with complex relationships, providing a richer context for the shared data.

-

In scenarios involving data sharing between two OpenCTI platforms, Live streams emerge as the preferred mechanism. These streams operate like TAXII collections but are notably enhanced, supporting:

-
    -
  • create, update and delete events depending on the parameters,
    • -
  • caching already created entities in the last 5 minutes,
    • -
  • resolving relationships and dependencies even out of the filters,
    • -
  • can be public (without authentication).
    • -
-

Live stream

-
-

Resolve relationships and dependencies

-

Dependencies and relationships of entities shared via Live streams, as determined by specified filters, are automatically shared even beyond the confines of these filters. This means that interconnected data, which may not directly meet the filter criteria, is still included in the Live stream. However, OpenCTI data segregation mechanisms are still applied. They allow restricting access to shared data based on factors such as markings or organization. It's imperative to carefully configure and manage these access controls to ensure that no confidential data is shared.

-
-

Illustrative scenario

-

To better understand how live streams are working, let's take a few examples, from simple to complex.

-

Given a live stream with filters Entity type: Indicator AND Label: detection. Let's see what happens with an indicator with:

-
    -
  • Marking definition: TLP:GREEN
    • -
  • Author Crowdstrike
    • -
  • Relation indicates to the malware Emotet
    • -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ActionResult in stream (with Avoid dependencies resolution=true)Result in stream (with Avoid dependencies resolution=false)
1. Create an indicatorNothingNothing
2. Add the label detectionCreate TLP:GREEN, create CrowdStrike, create the indicatorCreate TLP:GREEN, create CrowdStrike, create the malware Emotet, create the indicator, create the relationship indicates
3. Remove the label detectionDelete the indicatorDelete the indicator and the relationship
4. Add the label detectionCreate the indicatorCreate the indicator, create the relationship indicates
5. Delete the indicatorDelete the indicatorDelete the indicator and the relationship
-

Details on how to consume these Live streams can be found on the dedicated page.

-

TAXII Collections

-

OpenCTI has an embedded TAXII API endpoint which provides valid STIX 2.1 bundles. If you wish to know more about the TAXII standard, please read the official introduction.

-

In OpenCTI you can create as many TAXII 2.1 collections as needed.

-

TAXII Collection

-

After creating a new collection, every system with a proper access token can consume the collection using different kinds of authentication (basic, bearer, etc.).

-

As when using the GraphQL API, TAXII 2.1 collections have a classic pagination system that should be handled by the consumer. Also, it's important to understand that element dependencies (nested IDs) inside the collection are not always contained/resolved in the bundle, so consistency needs to be handled at the client level.

-

-

CSV feeds

-

The CSV feed facilitates the automatic generation of a CSV file, accessible via a URL. The CSV file is regenerated and updated at user-defined intervals, providing flexibility. The entries in the file correspond to the information that matches the filters applied and that were created or modified in the platform during the time interval (between the last generation of the CSV and the new one).

-

CSV feed

-
-

CSV size limit

-

The CSV file generated has a limit of 5 000 entries. If more than 5 000 entities are retrieved by the platform, only the most recent 5 000 will be shared in the file.

-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/getting-started/index.html b/6.2.18/usage/getting-started/index.html deleted file mode 100755 index 991cfcf3..00000000 --- a/6.2.18/usage/getting-started/index.html +++ /dev/null @@ -1,4224 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Getting started - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Getting started

-

This guide aims to give you a full overview of the OpenCTI features and workflows. The platform can be used in various contexts to handle threats management use cases from a technical to a more strategic level. OpenCTI has been designed as a knowledge graph, taking inputs (threat intelligence feeds, sightings & alerts, vulnerabilities, assets, artifacts, etc.) and generating outputs based on built-in capabilities and / or connectors.

-

Here are some examples of use cases:

-
    -
  • Cyber Threat Intelligence knowledge base
    • -
  • Detection as code feeds for XDR, EDR, SIEMs, firewalls, proxies, etc.
    • -
  • Incident response artifacts & cases management
    • -
  • Vulnerabilities management
    • -
  • Reporting, alerting and dashboarding on a subset of data
    • -
-

Use Cases

-

-

Welcome dashboard

-

The welcome page gives any visitor on the OpenCTI platform an overview of what's happening on the platform. It can be replaced by a custom dashboard, created by a user (or the default dashboard set up in a role, a group or an organization).

-

Dashboard

-

Indicators in the dashboard

-

Numbers

- - - - - - - - - - - - - - - - - - - - - - - - - -
ComponentDescription
Intrusion setsNumber of intrusion sets .
MalwareNumber of malware.
ReportsNumber of reports.
IndicatorsNumber of indicators.
-

Charts & lists

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ComponentDescription
Most active threats (3 last months)Top active threats (threat actor, intrusion set and campaign) during the last 3 months.
Most targeted victims (3 last months)Intensity of the targeting tied to the number of relations targets for a given entities (organization, sector, location, etc.) during the last 3 months.
Relationships createdVolume of relationships created over the past 12 months.
Most active malware (3 last months)Top active malware during the last 3 months.
Most active vulnerabilities (3 last months)List of the vulnerabilities with the greatest number of relations over the last 3 months.
Targeted countries (3 last months)Intensity of the targeting tied to the number of relations targets for a given country over the past 3 months.
Latest reportsLast reports ingested in the platform.
Most active labels (3 last months)Top labels given to entities during the last 3 months.
-
-

Explore the platform

-

To start exploring the platform and understand how information is structured, we recommend starting with the overview documentation page.

-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/import-automated/index.html b/6.2.18/usage/import-automated/index.html deleted file mode 100755 index b3ea2818..00000000 --- a/6.2.18/usage/import-automated/index.html +++ /dev/null @@ -1,4427 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Automated import - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Automated import

-

Automated imports in OpenCTI streamline the process of data ingestion, allowing users to effortlessly bring in valuable intelligence from diverse sources. This page focuses on the automated methods of importing data, which serve as bridges between OpenCTI and diverse external systems, formatting it into a STIX bundle, and importing it into the OpenCTI platform.

-

Connectors

-

Connectors in OpenCTI serve as dynamic gateways, facilitating the import of data from a wide array of sources and systems. Every connector is designed to handle specific data types and structures of the source, allowing OpenCTI to efficiently ingest the data.

-

Connector behaviors

-

The behavior of each connector is defined by its development, determining the types of data it imports and its configuration options. This flexibility allows users to customize the import process to their specific needs, ensuring a seamless and personalized data integration experience.

-

The level of configuration granularity regarding the imported data type varies with each connector. Nevertheless, connectors empower users to specify the date from which they wish to fetch data. This capability is particularly useful during the initial activation of a connector, enabling the retrieval of historical data. Following this, the connector operates in real-time, continuously importing new data from the source.

-

Reset connector state

-

Resetting the connector state enables you to restart the ingestion process from the very beginning. -Additionally, resetting the connector state will purge the RabbitMQ queue for this specific connector.

-

However, this action requires the "Manage connector state" capability (more details about capabilities: List of capabilities). Without this specific capability, you will not be able to reset the connector state.

-

When the action is performed, a message is displayed confirming the reset and inform you about the number of messages that will be purged

-

Reset state message pop-up

-

Purging a message queue is necessary to remove any accumulated messages that may be outdated or redundant. It helps to avoid reprocessing messages that have already been ingested.

-

By purging the queue, you ensure that the connector starts with a clean slate, processing only the new data.

-

Connector Ecosystem

-

OpenCTI's connector ecosystem covers a broad spectrum of sources, enhancing the platform's capability to integrate data from various contexts, from threat intelligence providers to specialized databases. The list of available connectors can be found in our connectors catalog. Connectors are categorized into three types: import connectors (the focus here), enrichment connectors, and stream consumers. Further documentation on connectors is available on the dedicated documentation page.

-

In summary, automated imports through connectors empower OpenCTI users with a scalable, efficient, and customizable mechanism for data ingestion, ensuring that the platform remains enriched with the latest and most relevant intelligence.

-

Native automated import

-

In OpenCTI, the "Data > Ingestion" section provides users with built-in functions for automated data import. These functions are designed for specific purposes and can be configured to seamlessly ingest data into the platform. Here, we'll explore the configuration process for the four built-in functions: Live Streams, TAXII Feeds, RSS Feeds, and CSV Feeds.

-

Live streams

-

Live Streams enable users to consume data from another OpenCTI platform, fostering collaborative intelligence sharing. Here's a step-by-step guide to configure Live streams synchroniser:

-
    -
  1. Remote OpenCTI URL: Provide the URL of the remote OpenCTI platform (e.g., https://[domain]; don't include the path).
    2. -
  2. Remote OpenCTI token: Provide the user token. An administrator from the remote platform must supply this token, and the associated user must have the "Access data sharing" privilege.
    3. -
  3. After filling in the URL and user token, validate the configuration.
    4. -
  4. Once validated, select a live stream to which you have access.
    5. -
-

Live stream configuration

-

Additional configuration options:

-
    -
  • User responsible for data creation: Define the user responsible for creating data received from this stream. Best practice is to dedicate one user per source for organizational clarity. Please see the section "Best practices" below for more information.
    • -
  • Starting synchronization: Specify the date of the oldest data to retrieve. Leave the field empty to import everything.
    • -
  • Take deletions into account: Enable this option to delete data from your platform if it was deleted on the providing stream. (Note: Data won't be deleted if another source has imported it previously.)
    • -
  • Verify SSL certificate: Check the validity of the certificate of the domain hosting the remote platform.
    • -
  • Avoid dependencies resolution: Import only entities without their relationships. For instance, if the stream shares malware, all the malware's relationships will be retrieved by default. This option enables you to choose not to recover them.
    • -
  • Use perfect synchronization: This option is specifically for synchronizing two platforms. If an imported entity already exists on the platform, the one from the stream will overwrite it.
    • -
-

Live stream additional configuration

-

TAXII feeds

-

TAXII Feeds in OpenCTI provide a robust mechanism for ingesting TAXII collections from TAXII servers or other OpenCTI instances. Configuring TAXII ingester involves specifying essential details to seamlessly integrate threat intelligence data. Here's a step-by-step guide to configure TAXII ingesters:

-
    -
  1. TAXII server URL: Provide the root API URL of the TAXII server. For collections from another OpenCTI instance, the URL is in the form https://[domain]/taxii2/root.
    2. -
  2. TAXII collection: Enter the ID of the TAXII collection to be ingested. For collections from another OpenCTI instance, the ID follows the format 426e3acb-db50-4118-be7e-648fab67c16c.
    3. -
  3. Authentication type (if necessary): Enter the authentication type. For non-public collections from another OpenCTI instance, the authentication type is "Bearer token." Enter the token of a user with access to the collection (similar to the point 2 of the Live streams configuration above).
    4. -
-
-

TAXII root API URL

-

Many ISAC TAXII configuration instructions will provide the URL for the collection or discovery service. In these cases, remove the last path segment from the TAXII Server URL in order to use it in OpenCTI. eg. use https://[domain]/tipapi/tip21, and not https://[domain]/tipapi/tip21/collections.

-
-

Additional configuration options:

-
    -
  • User responsible for data creation: Define the user responsible for creating data received from this TAXII feed. Best practice is to dedicate one user per source for organizational clarity. Please see the section "Best practices" below for more information.
    • -
  • Import from date: Specify the date of the oldest data to retrieve. Leave the field empty to import everything.
    • -
-

TAXII feed configuration

-

RSS feeds

-

RSS Feeds functionality enables users to seamlessly ingest items in report form from specified RSS feeds. Configuring RSS Feeds involves providing essential details and selecting preferences to tailor the import process. Here's a step-by-step guide to configure RSS ingesters:

-
    -
  1. RSS Feed URL: Provide the URL of the RSS feed from which items will be imported.
    2. -
-

Additional configuration options:

-
    -
  • User responsible for data creation: Define the user responsible for creating data received from this RSS feed. Best practice is to dedicate one user per source for organizational clarity. Please see the section "Best practices" below for more information.
    • -
  • Import from date: Specify the date of the oldest data to retrieve. Leave the field empty to import everything.
    • -
  • Default report types: Indicate the report type to be applied to the imported report.
    • -
  • Default author: Indicate the default author to be applied to the imported report. Please see the section "Best practices" below for more information.
    • -
  • Default marking definitions: Indicate the default markings to be applied to the imported reports.
    • -
-

RSS feed configuration

-

CSV feeds

-

CSV feed ingester enables users to import CSV files exposed on URLs. Here's a step-by-step guide to configure TAXII ingesters:

-
    -
  1. CSV URL: Provide the URL of the CSV file exposed from which items will be imported.
    2. -
  2. CSV Mappers: Choose the CSV mapper to be used to import the data.
    3. -
  3. Authentication type (if necessary): Enter the authentication type.
    4. -
-
-

CSV mapper

-

CSV feed functionality is based on CSV mappers. It is necessary to create the appropriate CSV mapper to import the data contained in the file. See the page dedicated to the CSV mapper.

-
-

Additional configuration options:

-
    -
  • User responsible for data creation: Define the user responsible for creating data received from this CSV feed. Best practice is to dedicate one user per source for organizational clarity. Please see the section "Best practices" below for more information.
    • -
  • Import from date: Specify the date of the oldest data to retrieve. Leave the field empty to import everything.
    • -
-

CSV feeds creation: prior CSV mapper test

-

in CSV Mappers, if you created a representative for Marking definition, you could have chosen between 2 options:

-
    -
  • let the user choose marking definitions
    • -
  • Use default marking definitions of the user
    • -
-

This configuration applies when using a CSV Mapper for a CSV Ingester. If you select a CSV Mapper containing the option "Use default marking definitions of the user", the default marking definitions of the user you chose to be responsible for the data creation will be applied to all data imported. If you select a CSV Mapper containing the option "let the user choose marking definitions", you will be presented with the list of all the marking definitions of the user you chose to be responsible for the data creation (and not yours!)

-

To finalize the creation, click on "Verify" to run a check on the submitted URL with the selected CSV mapper. A valid URL-CSV mapper combination results in the identification of up to 50 entities.

-

CSV feeds creation: CSV mapper test

-

CSV feeds creation: list

-

To start your new ingester, click on "Start", in the burger menu.

-

CSV feeds creation: start

-

CSV feed ingestion is made possible thanks to the connector "ImportCSV". So you can track the progress in "Data > Ingestion > Connectors". On a regular basis, the ingestion is updated when new data is added to the CSV feed.

-

CSV feeds creation: connectors

-

CSV feeds creation: tracking

-

-

Best practices for feed import

-

Ensuring a secure and well-organized environment is paramount in OpenCTI. Here are two recommended best practices to enhance security, traceability, and overall organizational clarity:

-
    -
  1. Create a dedicated user for each source: Generate a user specifically for feed import, following the convention [F] Source name for clear identification. Assign the user to the "Connectors" group to streamline user management and permission related to data creation. Please see here for more information on this good practice.
    2. -
  2. Establish a dedicated Organization for the source: Create an organization named after the data source for clear identification. Assign the newly created organization to the "Default author" field in feed import configuration if available.
    3. -
-

By adhering to these best practices, you ensure independence in managing rights for each import source through dedicated user and organization structures. In addition, you enable clear traceability to the entity's creator, facilitating source evaluation, dashboard creation, data filtering and other administrative tasks.

-

Automated import behaviors

-

An ingestion manager runs periodically in background, and for each running feeds: -- fetches new data from the source. When data is paginated, fetches the next page -- compose a stix bundle for data and send it in queue to be processed by workers

-

!!! Note on timeline of data ingestion from Taxii feed, CSV feed, and RSS feed.

-
Depending on workers load, the data can take some time between the fetch from source and visibility in the platform.
-
-

Periodicity interval is configured with the manager with ingestion_manager:interval.

-

Digest

-

Users can streamline the data ingestion process using various automated import capabilities. Each method proves beneficial in specific circumstances.

-
    -
  • Connectors act as bridges to retrieve data from diverse sources and format it for seamless ingestion into OpenCTI.
    • -
  • Live Streams enable collaborative intelligence sharing across OpenCTI instances, fostering real-time updates and efficient data synchronization.
    • -
  • TAXII Feeds provide a standardized mechanism for ingesting threat intelligence data from TAXII servers or other OpenCTI instances.
    • -
  • RSS Feeds facilitate the import of items in report form from specified RSS feeds, offering a straightforward way to stay updated on relevant intelligence.
    • -
-

By leveraging these automated import functionalities, OpenCTI users can build a comprehensive, up-to-date threat intelligence database. The platform's adaptability and user-friendly configuration options ensure that intelligence workflows remain agile, scalable, and tailored to the unique needs of each organization.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/import-files/index.html b/6.2.18/usage/import-files/index.html deleted file mode 100755 index 0618742f..00000000 --- a/6.2.18/usage/import-files/index.html +++ /dev/null @@ -1,4299 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Import from files - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Import from files

-

Import mechanisms

-

The platform provides a seamless process for automatically parsing data from various file formats. This capability is facilitated by two distinct mechanisms.

-

File import connectors: Currently, there are two connectors designed for importing files and automatically identifying entities.

-
    -
  • ImportFileStix: Designed to handle STIX-structured files (json or xml format).
    • -
  • ImportDocument: Versatile connector supporting an array of file formats, including pdf, text, html, and markdown.
    • -
-

CSV mappers: The CSV mapper is a tailored functionality to facilitate the import of data stored in CSV files. For more in-depth information on using CSV mappers, refer to the CSV Mappers documentation page.

-

Manual import connectors

-

Usage

-

Locations

-

Both mechanisms can be employed wherever file uploads are possible. This includes the "Data" tabs of all entities and the dedicated panel named "Data import and analyst workbenches" located in the top right-hand corner (database logo with a small gear). Importing files from these two locations is not entirely equal; refer to the "Relationship handling from entity's Data tab" section below for details on this matter.

-

Entity identification process

-

For ImportDocument connector, the identification process involves searching for existing entities in the platform and scanning the document for relevant information. In additions, the connector use regular expressions (regex) to detect IP addresses and domains within the document.

-

As for the ImportFileStix connector and the CSV mappers, there is no identification mechanism. The imported data will be, respectively, the data defined in the STIX bundle or according to the configuration of the CSV mapper used.

-

Workflow overview

-
    -
  1. Upload file: Navigate to the desired location, such as the "Data" tabs of an entity or the "Data import and analyst workbenches" panel. Then, upload the file containing the relevant data by clicking on the small cloud with the arrow inside next to "Uploaded files".
    2. -
  2. Entity identification: For a CSV file, select the connector and CSV mapper to be used by clicking on the icon with an upward arrow in a circle. If it's not a CSV file, the connector will launch automatically. Then, the file import connectors or CSV mappers will identify entities within the uploaded document.
    3. -
  3. Workbench review and validation: Entities identified by connectors are not immediately integrated into the platform's knowledge base. Instead, they are thoughtfully placed in a workbench, awaiting review and validation by an analyst. Workbenches function as draft spaces, ensuring that no data is officially entered into the platform until the workbench has undergone the necessary validation process. For more information on workbenches, refer to the Analyst workbench documentation page.
    4. -
-
-

Review workbenches

-

Import connectors may introduce errors in identifying object types or add "unknown" entities. Workbenches were established with the intent of reviewing the output of connectors before validation. Therefore, it is crucial to be vigilant when examining the workbench to prevent the import of incorrect data into the platform.

-
-

Global import panel

-

Additional information

-

No workbench for CSV mapper

-

It's essential to note that CSV mappers operate differently from other import mechanisms. Unlike connectors, CSV mappers do not generate workbenches. Instead, the data identified by CSV mappers is imported directly into the platform without an intermediary workbench stage.

-

Relationship handling from entity's "Data" tab

-

When importing a document directly from an entity's "Data" tab, there can be an automatic addition of relationships between the objects identified by connectors and the entity in focus. The process differs depending on the type of entity in which the import occurs:

-
    -
  • If the entity is a container (e.g., Report, Grouping, and Cases), the identified objects in the imported file will be linked to the entity (upon workbench validation). In the context of a container, the object is said to be "contained".
    • -
  • For entities that are not containers, a distinct behavior unfolds. In this scenario, the identified objects are not linked to the entity, except for Observables. Related to relationships between the Observables and the entity are automatically added to the workbench and created after validation of this one.
    • -
-

File import in Content tab

-

Expanding the scope of file imports, users can seamlessly add files in the Content tab of Analyses or Cases. In this scenario, the file is directly added as an attachment without utilizing an import mechanism.

-

User capability requirement

-

In order to initiate file imports, users must possess the requisite capability: "Upload knowledge files." This capability ensures that only authorized users can contribute and manage knowledge files within the OpenCTI platform, maintaining a controlled and secure environment for data uploads.

-
-

Deprecation warning

-

Using the ImportDocument connector to parse CSV file is now disallowed as it produces inconsistent results. -Please configure and use CSV mappers dedicated to your specific CSV content for a reliable parsing. -CSV mappers can be created and configured in the administration interface.

-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/indicators-lifecycle/index.html b/6.2.18/usage/indicators-lifecycle/index.html deleted file mode 100755 index 6add56af..00000000 --- a/6.2.18/usage/indicators-lifecycle/index.html +++ /dev/null @@ -1,4202 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Indicators lifecycle - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Indicators Lifecycle Management

-

Introduction

-

OpenCTI enforces strict rules to determine the period during which an indicator is effective for usage. This period is defined by the valid_from and valid_until dates. All along its lifecycle, the indicator score will decrease according to configured decay rules. After the indicator expires, the object is marked as revoked and the detection field is automatically set to false. Here, we outline how these dates are calculated within the OpenCTI platform and how the score is updated with decay rules.

-

Setting validity dates

-

Data source provided the dates

-

If a data source provides valid_from and valid_until dates when creating an indicator on the platform, these dates are used without modification. But, if the creation is performed from the UI and the indicator is elligible to be manages by a decay rule, the platform will change this valid_until with the one calculated by the Decay rule.

-

Fallback rules for unspecified dates

-

If a data source does not provide validity dates, OpenCTI applies the decay rule matching the indicator to determine these dates. -The valid_until date is computed based on the revoke score of the decay rule : it is set at the exact time at which the indicator will reach the revoke score. -Past valid_until date, the indicator is marked as revoked.

-

Score decay

-

Indicators have an initial score at creation, either provided by data source, or 50 by default. -Over time, this score is going to decrease according to the configured decay rules. -Score is updated at each reaction point defined for the decay rule matching the indicator at creation.

-

Example

-

This URL indicator has matched the Built-in IP and URL decay rule. Its initial score at creation is 100.

-

Indicator overview

-

Right next to the indicator score, there is a button Lifecycle which enables to open a dialog to see the details of the indicator's lifecyle.

-

Indicator lifecycle

-

Conclusion

-

Understanding how OpenCTI calculates validity periods and scores is essential for effective threat intelligence analysis. These rules ensure that your indicators are accurate and up-to-date, providing a reliable foundation for threat intelligence data.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/inferences/index.html b/6.2.18/usage/inferences/index.html deleted file mode 100755 index b4c132ad..00000000 --- a/6.2.18/usage/inferences/index.html +++ /dev/null @@ -1,4173 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Inferences and reasoning - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Inferences and reasoning

-

Overview

-

OpenCTI’s inferences and reasoning capability is a robust engine that automates the process of relationship creation within your threat intelligence data. This capability, situated at the core of OpenCTI, allows logical rules to be applied to existing relationships, resulting in the automatic generation of new, pertinent connections.

-

Understanding inferences and reasoning

-

Inferences and reasoning serve as OpenCTI’s intelligent engine. It interprets your data logically. By activating specific predefined rules (of which there are around twenty), OpenCTI can deduce new relationships from the existing ones. For instance, if there's a connection indicating an Intrusion Set targets a specific country, and another relationship stating that this country is part of a larger region, OpenCTI can automatically infer that the Intrusion Set also targets the broader region.

-

Key benefits

-
    -
  • Efficiency: Reduces manual workload by automating relationship creation, saving valuable analyst time.
    • -
  • Completeness: Fills relationship gaps, ensuring a comprehensive and interconnected threat intelligence database.
    • -
  • Accuracy: Minimizes manual input errors by deriving relationships from predefined, accurate logic.
    • -
-

How it operates

-

When you activate an inference rule, OpenCTI continuously analyzes your existing relationships and applies the defined logical rules. These rules are logical statements that define conditions for new relationships. When the set of conditions is met, the OpenCTI creates the corresponding relationship automatically.

-

For example, if you activate a rule as follows:

-

IF [Entity A targets Identity B] AND [Identity B is part of Identity C] -THEN [Entity A targets Identity C]

-

OpenCTI will apply this rule to existing data. If it finds an Intrusion Set ("Entity A") targeting a specific country ("Identity B") and that country is part of a larger region ("Identity C"), the platform will automatically establish a relationship between the Intrusion Set and the region.

-

Identifying inferred relationships

-

In the knowledge graphs: Inferred relationships are represented by dotted lines of a different color, distinguishing them from non-inferred relations.

-

Inferred_relationships_in_graph

-

In the lists: In a relationship list, a magic wand icon at the end of the line indicates relationship created by inference.

-

Inferred_relationships_in_list

-

Additional resources

-
    -
  • Administration: To find out about existing inference rules and enable/disable them, refer to the Rules engine page in the Administration section of the documentation.
    • -
  • Playbooks: OpenCTI playbooks are highly customizable automation scenarios. This seamless integration allows for further automation, making your threat intelligence processes even more efficient and tailored to your specific needs. More information in our blog post.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/manual-creation/index.html b/6.2.18/usage/manual-creation/index.html deleted file mode 100755 index f6b77fb6..00000000 --- a/6.2.18/usage/manual-creation/index.html +++ /dev/null @@ -1,4194 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Manual creations - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Manual creations

-

Manual data creation in OpenCTI is an intuitive process that occurs throughout the platform. This page provides guidance on two key aspects of manual creation: Entity creation and Relationship creation.

-

Entity creation

-

To create an entity:

-
    -
  1. Navigate to the relevant section: Be on the section of the platform related to the object type you want to create.
    2. -
  2. Click on the "+" icon: Locate the "+" icon located at the bottom right of the window. New report
    3. -
  3. Fill in entity-specific fields: A form on the right side of the window will appear, allowing to fill in specific fields of the entity. Certain fields are inherently obligatory, and administrators have the option to designate additional mandatory fields (See here for more information).
    4. -
  4. Click on "Create": Once you've filled in the desired fields, click on "create" to initiate the entity creation process.
    5. -
-

Create report

-

Relationship creation

-

Before delving into the creation of relationships between objects in OpenCTI, it's crucial to grasp some foundational concepts. Here are key points to understand:

-
    -
  • On several aspects, including relationships, two categories of objects must be differentiated: containers (e.g., Reports, Groupings, and Cases) and others. Containers aren't related to but contains objects.
    • -
  • Relationships, like all other entities, are objects. They possess fields, can be linked, and share characteristics identical to other entities.
    • -
  • Relationships are inherently directional, comprising a "from" entity and a "to" entity. Understanding this directionality is essential for accurate relationship creation.
    • -
  • OpenCTI supports various relationship types, and their usage depends on the entity types being linked. For example, a "target" relationship might link malware to an organization, while linking malware to an intrusion set might involve a different relationship type.
    • -
-

Now, let’s explore the process of creating relationships. To do this, we will differentiate the case of containers from the others.

-

For container

-

When it comes to creating relationships within containers in OpenCTI, the process is straightforward. Follow these steps to attach objects to a container:

-
    -
  1. Navigate to the container: Go to the specific container to which you want to attach an object. This could be a Report, Grouping, or Cases.
    2. -
  2. Access the "Entities" tab: Within the container, locate and access the "Entities" tab.
    3. -
  3. Click on the "+" icon: Find the "+" icon located at the bottom right of the window. New relation with container
    4. -
  4. Search for entities: A side window will appear. Search for the entities you want to add to the container.
    5. -
  5. Add entities to the container: Click on the desired entities. They will be added directly to the container.
    6. -
-

For other

-

When creating relationships not involving a container, the creation method is distinct. Follow these steps to create relationships between entities:

-
    -
  1. Navigate to one of the entities: Go to one of the entities you wish to link. Please be aware that the entity from which you create the relationship will be designated as the "from" entity for that relationship. So the decision of which entity to choose for creating the relationship should be considered, as it will impact the outcome.
    2. -
  2. Access the "Knowledge" tab: Within the entity, go to the "Knowledge" tab.
    3. -
  3. Select the relevant categories: In the right banner, navigate to the categories that correspond to the object to be linked. The available categories depend on the type of entity you are currently on. For example, if you are on malware and want to link to a sector, choose "victimology."
    4. -
  4. Click on the "+" icon: Find the "+" icon located at the bottom right of the window. New relationhip
    5. -
  5. Search for entities: A side window will appear. Search for the entities you want to link.
    6. -
  6. Add entities and click on "Continue": Click on the entities you wish to link. Multiple entities can be selected. Then click on "Continue" at the bottom right. Entities to link
    7. -
  7. Fill in the relationship form: As relationships are objects, a creation form similar to creating an entity will appear.
    8. -
  8. Click on "Create": Once you've filled in the desired fields, click on "create" to initiate the relationship creation process.
    9. -
-

Create relationship

-

Additional methods

-

While the aforementioned methods are primary for creating entities and relationships, OpenCTI offers versatility, allowing users to create objects in various locations within the platform. Here's a non-exhaustive list of additional places that facilitate on-the-fly creation:

-
    -
  • Creating entities during relationship creation: During the "Search for entities" phase (see above) of the relationship creation process, click on the "+" icon to create a new entity directly.
    • -
  • Knowledge graph: Within the knowledge graph - found in the knowledge tab of the containers or in the investigation functionality - users can seamlessly create entities or relationships.
    • -
  • Inside a workbench: The workbench serves as another interactive space where users can create entities and relationships efficiently.
    • -
-

These supplementary methods offer users flexibility and convenience, allowing them to adapt their workflow to various contexts within the OpenCTI platform. As users explore the platform, they will naturally discover additional means of creating entities and relationships.

-
-

Max confidence level

-
-

When creating knowledge in the platform, the maximum confidence level of the users is used. Please navigate to this page to understand this concept and the impact it can have on the knowledge creation.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/merging/index.html b/6.2.18/usage/merging/index.html deleted file mode 100755 index b1deecd1..00000000 --- a/6.2.18/usage/merging/index.html +++ /dev/null @@ -1,4138 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Merge objects - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Merge objects

-

Introduction

-

OpenCTI’s merge capability stands as a pivotal tool for optimizing threat intelligence data, allowing to consolidate multiple entities of the same type. This mechanism serves as a powerful cleanup tool, harmonizing the platform and unifying scattered information. In this section, we explore the significance of this feature, the process of merging entities, and the strategic considerations involved.

-

-

Data streamlining

-

In the ever-expanding landscape of threat intelligence and the multitude of names chosen by different data sources, data cleanliness is essential. Duplicates and fragmented information hinder efficient analysis. The merge capability is a strategic solution for amalgamating related entities into a cohesive unit. Central to the merging process is the selection of a main entity. This primary entity becomes the anchor, retaining crucial attributes such as name and description. Other entities, while losing specific fields like descriptions, are aliased under the primary entity. This strategic decision preserves vital data while eliminating redundancy.

-

Preserving entity relationships

-

One of the key feature of the merge capability is its ability to preserve relationships. While merging entities, their interconnected relationships are not lost. Instead, they seamlessly integrate into the new, merged entity. This ensures that the intricate web of relationships within the data remains intact, fostering a comprehensive understanding of the threat landscape.

-

Conclusion

-

OpenCTI’s merge capability helps improve the quality of threat intelligence data. By consolidating entities and centralizing relationships, OpenCTI empowers analysts to focus on insights and strategies, unburdened by data silos or fragmentation. However, exercising caution and foresight in the merging process is essential, ensuring a robust and streamlined knowledge basis.

-

Additional resources

-
    -
  • Administration: To understand how to merge entities and the consideration to take into account, refer to the Merging page in the Administration section of the documentation.
    • -
  • Deduplication mechanism: the platform is equipped with deduplication processes that automatically merge data at creation (either manually or by importing data from different sources) if it meets certain conditions.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/nested/index.html b/6.2.18/usage/nested/index.html deleted file mode 100755 index f4616757..00000000 --- a/6.2.18/usage/nested/index.html +++ /dev/null @@ -1,4235 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Nested objects - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Nested references and objects

-

STIX standard

-

Definition

-

In the STIX 2.1 standard, objects can:

-
    -
  1. Refer to other objects in directly in their attributes, by referencing one or multiple IDs.
    2. -
  2. Have other objects directly embedded in the entity.
    3. -
-

Example

-
{
-   "type": "intrusion-set",
-   "spec_version": "2.1",
-   "id": "intrusion-set--4e78f46f-a023-4e5f-bc24-71b3ca22ec29",
-   "created_by_ref": "identity--f431f809-377b-45e0-aa1c-6a4751cae5ff", // nested reference to an identity
-   "object_marking_refs": ["marking-definition--34098fce-860f-48ae-8e50-ebd3cc5e41da"], // nested reference to multiple marking defintions
-   "external_references": [
-      {
-         "source_name": "veris",
-         "external_id": "0001AA7F-C601-424A-B2B8-BE6C9F5164E7",
-         "url": "https://github.com/vz-risk/VCDB/blob/125307638178efddd3ecfe2c267ea434667a4eea/data/json/validated/0001AA7F-C601-424A-B2B8-BE6C9F5164E7.json",    
-      }
-   ],
-   "created": "2016-04-06T20:03:48.000Z",
-   "modified": "2016-04-06T20:03:48.000Z",
-   "name": "Bobcat Breakin",
-   "description": "Incidents usually feature a shared TTP of a bobcat being released within the building containing network access...",
-   "aliases": ["Zookeeper"],
-   "goals": ["acquisition-theft", "harassment", "damage"]
-}
-
-

In the previous example, we have 2 nested references to other objects in:

-
"created_by_ref": "identity--f431f809-377b-45e0-aa1c-6a4751cae5ff", // nested reference to an identity
-"object_marking_refs": ["marking-definition--34098fce-860f-48ae-8e50-ebd3cc5e41da"], // nested reference to multiple marking defintions
-
-

But we also have a nested object within the entity (an External Reference):

-
"external_references": [
-   {
-      "source_name": "veris",
-      "external_id": "0001AA7F-C601-424A-B2B8-BE6C9F5164E7",
-      "url": "https://github.com/vz-risk/VCDB/blob/125307638178efddd3ecfe2c267ea434667a4eea/data/json/validated/0001AA7F-C601-424A-B2B8-BE6C9F5164E7.json",    
-   }
-]
-
-

Implementation

-

Modelization

-

In OpenCTI, all nested references and objects are modelized as relationships, to be able to pivot more easily on labels, external references, kill chain phases, marking definitions, etc.

-

Investigation

-

Import & export

-

When importing and exporting data to/from OpenCTI, the translation between nested references and objects to full-fledged nodes and edges is automated and therefore transparent for the users. Here is an example with the object in the graph above:

-
{
-   "id": "file--b6be3f04-e50f-5220-af3a-86c2ca66b719",
-   "spec_version": "2.1",
-   "x_opencti_description": "...",
-   "x_opencti_score": 50,
-   "hashes": {
-       "MD5": "b502233b34256285140676109dcadde7"
-   },
-   "labels": [
-       "cookiecutter",
-       "clouddata-networks-1"
-   ],
-   "external_references": [
-       {
-           "source_name": "Sekoia.io",
-           "url": "https://app.sekoia.io/intelligence/objects/indicator--3e6d61b4-d5f0-48e0-b934-fdbe0d87ab0c"
-       }
-   ],
-   "x_opencti_id": "8a3d108f-908c-4833-8ff4-4d6fc996ce39",
-   "type": "file",
-   "created_by_ref": "identity--b5b8f9fc-d8bf-5f85-974e-66a7d6f8d4cb",
-   "object_marking_refs": [
-       "marking-definition--613f2e26-407d-48c7-9eca-b8e91df99dc9"
-   ]
-}
-
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/notifications/index.html b/6.2.18/usage/notifications/index.html deleted file mode 100755 index 9bfcbc34..00000000 --- a/6.2.18/usage/notifications/index.html +++ /dev/null @@ -1,4395 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Notifications and alerting - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Notifications and alerting

-

In the evolving landscape of cybersecurity, timely awareness is crucial. OpenCTI empowers users to stay informed and act swiftly through its robust notifications and alerting system. This feature allows users to create personalized triggers that actively monitor the platform for specific events and notify them promptly when these conditions are met.

-

From individual users tailoring their alert preferences to administrators orchestrating collaborative triggers for Groups or Organizations, OpenCTI's notification system is a versatile tool for keeping cybersecurity stakeholders in the loop.

-

The main menu "Notifications and triggers" for creating and managing notifications is located in the top right-hand corner with the bell icon.

-

Notifications

-

Triggers

-

In OpenCTI, triggers serve as personalized mechanisms for users to stay informed about specific events that align with their cybersecurity priorities. Users can create and manage triggers to tailor their notification experience. Each trigger operates by actively listening to events based on predefined filters and event types, promptly notifying users via chosen notifiers when conditions are met.

-

Triggers

-

Trigger management

-

Individual user triggers: Each user possesses the autonomy to craft their own triggers, finely tuned to their unique preferences and responsibilities. By setting up personalized filters and selecting preferred notifiers, users ensure that they receive timely and relevant notifications aligned with their specific focus areas.

-

Administrative control: Platform administrators have the capability to create and manage triggers for Users, Groups and Organizations. This provides centralized control and the ability to configure triggers that address collective cybersecurity objectives. Users within the designated Group or Organization will benefit from triggers with read-only access rights. These triggers are to be created directly on the User|Group|Organization with whom to share them in "Settings > Security > Users|Groups|Organizations".

-

Restricted trigger

-

Trigger filters

-

Leveraging the filters, users can meticulously define the criteria that activate their triggers. This level of granularity ensures that triggers are accurate, responding precisely to events that matter most. Users can tailor filters to consider various parameters such as object types, markings, sources, or other contextual details. They can also allow notifications for the assignment of a Task, a Case, etc.

-

Beyond filters, a trigger can be configured to respond to three event types: creation, modification, and deletion.

-

Trigger configuration

-

Instance triggers

-

Instance triggers offer a targeted approach to live monitoring by allowing users to set up triggers specific to one or several entities. These triggers, when activated, keep a vigilant eye on a predefined set of events related to the selected entities, ensuring that you stay instantly informed about crucial changes.

-

Creating instance triggers

-

Method 1: Using the general trigger creation form

-
    -
  1. Go on the "Notifications and triggers" window.
    2. -
  2. Navigate to the "Triggers and digests" tab.
    3. -
  3. Access the general trigger creation form.
    4. -
  4. Toggle the switch "Instance trigger".
    5. -
  5. Choose the entities to monitor.
    6. -
-

Instance trigger creation

-

Method 2: Quick subscription

-
    -
  1. On an entity's overview, locate the "Instance trigger quick subscription" button with the bell icon at the top right.
    2. -
  2. Click on the button to create the instance trigger.
    3. -
  3. (Optional) Click on it again to modify the instance trigger created.
    4. -
-

Quick subscription button

-

Events monitored by instance triggers

-

An instance trigger set on an entity X actively monitors the following events:

-
    -
  • Update/Deletion of X: Stay informed when the selected entity undergoes changes or is deleted.
    • -
  • Creation/Deletion of relationships: Receive notifications about relationships being added or removed from/to X.
    • -
  • Creation/Deletion of related entities: Be alerted when entities that have X in its refs - i.e. contains X, is shared with X, is created by X, etc. - are created or deleted.
    • -
  • Adding/Removing X in ref: Stay in the loop when X is included or excluded from the ref of other entities - i.e. adding X in the author of an entity, adding X in a report, etc.).
    • -
-
-

Entity deletion notification

-

It's important to note that the notification of entity deletion can occur in two scenarios: - - Real entity deletion: When the entity is genuinely deleted from the platform. - - Visibility loss: When a modification to the entity results in the user losing visibility for that entity.

-
-

Digest

-

Digests provide an efficient way to streamline and organize your notifications. By grouping notifications based on selected triggers and specifying the delivery period (daily, weekly, monthly), you gain the flexibility to receive consolidated updates at your preferred time, as opposed to immediate notifications triggered by individual events.

-

Creating digests

-
    -
  1. Go on the "Notifications and triggers" window.
    2. -
  2. Navigate to the "Triggers and digests" tab.
    3. -
  3. Create a new digest.
    4. -
  4. Configure digest: Set the parameters, including triggers to be included and the frequency of notifications (daily, weekly, monthly).
    5. -
  5. Choose the notifier(s): Select the notification method(s) (e.g. within the OpenCTI interface, via email, etc.).
    6. -
-

Digest configuration

-

Benefits of digests

-
    -
  • Organized notifications: Digests enable you to organize and categorize notifications, preventing a flood of individual alerts.
    • -
  • Customized delivery: Choose the frequency of digest delivery based on your preferences, whether it's a daily overview, a weekly summary, or a monthly roundup.
    • -
  • Reduced distractions: Receive notifications at a scheduled time, minimizing interruptions and allowing you to focus on critical tasks.
    • -
-

Digests enhance your control over notification management, ensuring a more structured and convenient approach to staying informed about important events.

-

Notifiers

-

In OpenCTI, notifiers serve as the channels for delivering notifications, allowing users to stay informed about critical events. The platform offers two built-in notifiers, "Default mailer" for email notifications and "User interface" for in-platform alerts.

-

Notifiers

-

Notifier connectors

-

OpenCTI features built-in notifier connectors that empower users to create personalized notifiers for notification and activity alerting. Three essential connectors are available:

-
    -
  • Platform mailer connector: Enables sending notifications directly within the OpenCTI platform.
    • -
  • Simple mailer connector: Offers a straightforward approach to email notifications with simplified configuration options.
    • -
  • Generic webhook connector: Facilitates communication through webhooks.
    • -
-

OpenCTI provides two samples of webhook notifiers designed for Teams integration.

-

Custom notifiers

-

Configuration and Access

-

Notifiers are manageable in the "Settings > Customization > Notifiers" window and can be restricted through Role-Based Access Control (RBAC). Administrators can restrict access to specific Users, Groups, or Organizations, ensuring controlled usage.

-

For guidance on configuring custom notifiers and explore detailed setup instructions, refer to the dedicated documentation page.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/overview/index.html b/6.2.18/usage/overview/index.html deleted file mode 100755 index c963d103..00000000 --- a/6.2.18/usage/overview/index.html +++ /dev/null @@ -1,4561 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Overview - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Overview

-

Introduction

-

The following chapter aims at giving the reader a step-by-step description of what is available on the platform and the meaning of the different tabs and entries.

-

When the user connects to the platform, the home page is the Dashboard. This Dashboard contains several visuals summarizing the types and quantity of data recently imported into the platform.

-
-

Dashboard

-

To get more information about the components of the default dashboard, you can consult the Getting started.

-
-

The left side panel allows the user to navigate through different windows and access different views and categories of knowledge.

-
-

Menu

-
-

Structure

-

The "hot knowledge"

-

The first part of the platform in the left menu is dedicated to what we call the "hot knowledge", which means this is the entities and relationships which are added on a daily basis in the platform and which generally require work / analysis from the users.

-
    -
  • Analyses: all containers which convey relevant knowledge such as reports, groupings and malware analyses.
    • -
  • Cases: all types of case like incident responses, requests for information, for takedown, etc.
    • -
  • Events: all incidents & alerts coming from operational systems as well as sightings.
    • -
  • Observations: all technical data in the platform such as observables, artifacts and indicators.
    • -
-

The "cold knowledge"

-

The second part of the platform in the left menu is dedicated to the "cold knowledge", which means this is the entities and relationships used in the hot knowledge. You can see this as the "encyclopedia" of all pieces of knowledge you need to get context: threats, countries, sectors, etc.

-
    -
  • Threats: all threats entities from campaigns to threat actors, including intrusion sets.
    • -
  • Arsenal: all tools and pieces of malware used and/or targeted by threats, including vulnerabilities.
    • -
  • Techniques: all objects related to tactics and techniques used by threats (TTPs, etc.).
    • -
  • Entities: all non-geographical contextual information such as sectors, events, organizations, etc.
    • -
  • Locations: all geographical contextual information, from cities to regions, including precise positions.
    • -
-

Hide categories

-

You can customize the experience in the platform by hiding some categories in the left menu, whether globally or for a specific role.

-

Hide categories globally

-

In the Settings > Parameters, it is possible for the platform administrator to hide categories in the platform for all users.

-

Hide categories globally

-

Hide categories in roles

-

In OpenCTI, the different roles are highly customizable. It is possible to defined default dashboards, triggers, etc. but also be able to hide categories in the roles:

-

Hide categories in roles

-

Presentation of a typical page in OpenCTI

-

While OpenCTI features numerous entities and tabs, many of them share similarities, with only minor differences arising from specific characteristics. These differences may involve the inclusion or exclusion of certain fields, depending on the nature of the entity.

-

In this part will only be detailed a general outline of a "typical" OpenCTI page. The specifies of the different entities will be detailed in the corresponding pages below (Activities and Knowledge).

-
-

Top menu of an entity

-
-

-

Overview

-

In the Overview tab on the entity, you will find all properties of the entity as well as the recent activities.

-

First, you will find the Details section, where are displayed all properties specific to the type of entity you are looking at, an example below with a piece of malware:

-

Details

-

Thus, in the Basic information section, are displayed all common properties to all objects in OpenCTI, such as the marking definition, the author, the labels (i.e. tags), etc.

-

Basic information

-

Below these two sections, you will find latest modifications in the Knowledge base related to the Entity:

-
    -
  • Latest created relationships: display the latest relationships that have been created from or to this Entity. For example, latest Indicators of Compromise and associated Threat Actor of a Malware.
    • -
  • latest containers about the object: display all the Cases and Analyses that contains this Entity. For example, the latest Reports about a Malware.
    • -
  • External references: display all the external sources associated with the Entity. You will often find here links to external reports or webpages from where Entity's information came from.
    • -
  • History: display the latest chronological modifications of the Entity and its relationships that occurred in the platform, in order to traceback any alteration.
    • -
-

Latest relations and containers -References and History

-

Last, all Notes written by users of the platform about this Entity are displayed in order to access unstructured analysis comments.

-

-

Knowledge

-

In the Knowledge tab, which is the central part of the entity, you will find all the Knowledge related to the current entity. The Knowledge tab is different for Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) entities than for all the other entity types.

-
    -
  • The Knowledge tab of those entities (who represents Analyses or Cases that can contains a collection of Objects) is the place to integrate and link together entities. For more information on how to integrate information in OpenCTI using the knowledge tab of a report, please refer to the part Manual creation.
    • -
  • The Knowledge tabs of any other entity (that does not aim to contain a collection of Objects) gather all the entities which have been at some point linked to the entity the user is looking at. For instance, as shown in the following capture, the Knowledge tab of Intrusion set APT29, gives access to the list of all entities APT29 is attributed to, all victims the intrusion set has targeted, all its campaigns, TTPs, malware etc. For entities to appear in these tabs under Knowledge, they need to have been linked to the entity directly or have been computed with the inference engine.
    • -
-

The Intrusion Set's Knowledge tab

-

Focus on Indicators and Observables

-

The Indicators and Observables section offers 3 display modes: -- The entities view, which displays the indicators/observables linked to the entity. -- The relationship view, which displays the various relationships between the indicators/observables linked to the entity and the entity itself. -- The contextual view, which displays the indicators/observables contained in the cases and analyses that contain the entity.

-

The Knowledge Focus on Indicators and Observables views

-

-

Content

-

The Content tab is available for all entities. It allows for uploading and creating outcomes documents related to the content of the current entity (in PDF, text, HTML or markdown files). This specific tab enable to previzualize, manage and write deliverable associated with the entity. For example an analytic report to share with other teams, a markdown files to feed a collaborative wiki with, etc.

-

The Content mapping view and the Suggested mapping view are available for a subset of entities: Report, Grouping, Incident, Incident response, Request for Information, and Request for Takedown.

-

The Content tab of a Malware

-

Content mapping view

-

Content mapping view of a Case

-

The Content mapping view displays the mappable content of your container on the left (Description and Content), and the objects contained in the container on the right.

-

This view allows you to map readable content to existing or new Objects by selecting text on the left. Mapping an object will add it to your container, and the object will then be displayed on the right. -You can clear all mappings that you added by clicking on the Clear mappings button. This action will only remove the mapping: the objects will still be contained in your container.

-

This allows you to quickly append structured Knowledge in your Case before refining it with relationships and details, and makes it a great place to see the continuum between unstructured and structured Knowledge.

-

Suggested mapping view

-

Suggested mapping view of a Report

-

The Suggested mapping view displays the mappable content of your container on the left (Description and Content), and the suggested entity mapping on the right.

-

This view allows you to get a suggestion list of existing Objects based on your mappable content by clicking on Suggest new mapping. -To be able to get a suggestion, you need to have at least one analysis connector of type INTERNAL_ANALYSIS configured. -Once the suggestion has been computed by the connector, it will be available on the right. -You can the remove the suggestion that you are not interested in, and click on the Validate button to add the mapped objects to your container.

-

This allows you to quickly fill your Container with the data that you need, without having to manually map every related Objects.

-

-

Analyses

-

The Analyses tab contains the list of all Analyses (Report, Groupings) and Cases (Incident response, Request for Information, Request for Takedown) in which the entity has been identified.

-

Example of the list of reports in which the attack pattern "data obfuscation" has been identified.

-

By default, this tab display the list, but you can also display the content of all the listed Analyses on a graph, allowing you to explore all their Knowledge and have a glance of the context around the Entity.

-

Graph view of all the Knowledge contained in the listed analyses

-

-

Data

-

The Data tab contains documents that are associated to the object and were either:

-
    -
  • Uploaded to the platform : for instance the PDF document containing the text of the report
    • -
  • Generated from the platform to be downloaded : a JSON or CSV file containing information on the object and generated by the user.
    • -
  • associated to an external reference
    • -
-

Analyst Workbench can also be created from here. They will contain the entity by default.

-

The Data tab of a Threat Actor

-

In addition, the Data tab of Threat actors (group), Threat actors (individual), Intrusions sets, Organizations, Individuals have an extra panel:

-
    -
  • Pictures Management: allows to manage the profile pictures attached to the entity.
    • -
-

Profile pictures panel -Profile pictures of a Threat Actor

-

-

History

-

The History tab displays the history of change of the Entity, update of attributes, creation of relations, ...

-

Because of the volumes of information the history is written in a specific index that consume the redis stream to rebuild the history for the UI. -History tab of a Malware

-

Less frequent tabs

-
    -
  • The Observables tab (for Reports and Observed data): A table containing all SCO (Stix Cyber Observable) contained in the Report or the Observed data, with search and filters available. It also displays if the SCO has been added directly or through inferences with the reasoning engine
    • -
  • the Entities tab (for Reports and Observed data): A table containing all SDO (Stix Domain Objects) contained in the Report or the Observed data, with search and filters available. It also displays if the SDO has been added directly or through inferences with the reasoning engine
    • -
  • Observables:
    • -
  • the Sightings tab (for Indicators and Observables): A table containing all Sightings relationships corresponding to events in which Indicators (IP, domain name, URL, etc.) are detected by or within an information system, an individual or an organization. Most often, this corresponds to a security event transmitted by a SIEM or EDR.
    • -
- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/pivoting/index.html b/6.2.18/usage/pivoting/index.html deleted file mode 100755 index 1fa9e8f9..00000000 --- a/6.2.18/usage/pivoting/index.html +++ /dev/null @@ -1,4272 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Pivot and investigate - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Pivot and investigate

-

In OpenCTI, all data are structured as an extensive knowledge graph, where every element is interconnected. The investigation functionality provides a powerful tool for pivoting on any entity or relationship within the platform. Pivoting enables users to explore and analyze connections between entities and relationships, facilitating a comprehensive understanding of the data.

-

To access investigations, navigate to the top right corner of the toolbar:

-

Top menu investigation

-
-

Access restriction

-

When an investigation is created, it is initially visible only to the creator, allowing them to work on the investigation before deciding to share it. The sharing mechanism is akin to that of dashboards. For further details, refer to the Access control section in the dashboard documentation page.

-
-

Perform investigation

-

Manipulate entity

-

We can add any existing entity of the platform to your investigation.

-

Investigation bottom right menu

-

After adding an entity, we can choose the entity and view its details in the panel that appears on the right of the screen.

-

On each node, we'll notice a bullet with a number inside, serving as a visual indication of how many entities are linked to it but not currently displayed in the graph. Keep in mind that this number is an approximation, which is why there's a "+" next to it. If there's no bullet displayed, it means there's nothing to expand from this node.

-

Investigation workspace

-

Expansion

-

To incorporate these linked entities into the graph, we just have to expand the nodes. Utilize the button with a 4-arrows logo in the mentioned menu, or double-click on the entity directly. This action opens a new window where we can choose the types of entities and relationships we wish to expand.

-

Investigation expand entity

-

For instance, in the image above, selecting the target Malware and the relationship Uses implies expanding in my investigation graph all Malware linked to this node with a relationship of type Uses.

-

Roll back expansion

-

Expanding a graph can add a lot of entities and relations, making it not only difficult to read but sometimes counterproductive since it brings entities and relations that are not useful to your investigations. -To solve this problem, there is a button to undo the last expansion.

-

When clicking on this button, we will retrieve the state in which your graph was before your expansion. As a result, please note that all add or remove actions made since the last expansion will be lost: in other words, if you have expanded your graph, and then have added some entities in your graph, when clicking on rollback button, the entities that you have added will not be in your graph.

-

Investigation rollback popup

-

You can roll back your investigation graph up to the last 10 expand actions.

-

Manipulate relationship

-

We can create a relationship between entities directly within our investigation. To achieve this, select multiple entities by clicking on them while holding down the shift key. Subsequently, a button appears at the bottom right to create one (or more, depending on the number of entities selected) relationships.

-

Investigation create relationship

-
-

Relationship creation

-

Creating a relationship in the investigation graph will generate the relationship in your knowledge base.

-
-

Capitalize on an investigation

-

Export investigation

-

Users have the capability to export investigations, providing a way to share, document, or archive their findings.

-
    -
  • PDF and image formats: Users can export investigations in either PDF or image format, offering flexibility in sharing and documentation.
    • -
  • STIX bundle: The platform allows the export of the entire content of an investigation graph as a STIX bundle. In the STIX format, all objects within the investigation graph are automatically aggregated into a Report object.
    • -
-

Investigation export

-

Turn investigation into a container

-

Users can efficiently collect and consolidate the findings of an investigation by adding the content into dedicated containers. The contents of an investigation can be imported into various types of containers, including:

-
    -
  • Grouping
    • -
  • Incident Response
    • -
  • Report
    • -
  • Request for Information
    • -
  • Request for Takedown
    • -
-

investigation-turn-to-report-or-case.png

-

We have the flexibility to choose between creating a new container on the fly or adding investigation content to an existing container.

-

investigation-turn-to-report-or-case-dialog-new-entity.png

-

investigation-turn-to-report-or-case-dialog-new-entity-form.png

-

After clicking on the ADD button, the browser will redirect to the Knowledge tab of the container where we added the content of our investigation. If we added it to multiple containers, the redirection will be to the first of the list.

-

investigation-turn-to-report-or-case-success.png

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/reliability-confidence/index.html b/6.2.18/usage/reliability-confidence/index.html deleted file mode 100755 index 5466713a..00000000 --- a/6.2.18/usage/reliability-confidence/index.html +++ /dev/null @@ -1,4495 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Reliability and confidence - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Reliability and Confidence

-

Generalities

-

In (Cyber) Threat Intelligence, evaluation of information sources and of information quality is one of the most important aspect of the work. It is of the utter most importance to assess situations by taking into account reliability of the sources and credibility of the information.

-

This concept is foundational in OpenCTI, and have real impact on:

- -

What is the Reliability of a source?

-

Reliability of a source of information is a measurement of the trust that the analyst can have about the source, based on the technical capabilities or history of the source. Is the source a reliable partner with long sharing history? A competitor? Unknown?

-

Reliability of sources are often stated at organizational level, as it requires an overview of the whole history with it.

-

In the Intelligence field, Reliability is often notated with the NATO Admiralty code.

-

What is Confidence of an information?

-

Reliability of a source is important but even a trusted source can be wrong. Information in itself has a credibility, based on what is known about the subject and the level of corroboration by other sources.

-

Credibility is often stated at the analyst team level, expert of the subject, able to judge the information with its context.

-

In the Intelligence field, Confidence is often notated with the NATO Admiralty code.

-
-

Why Confidence instead of Credibility?

-

Using both Reliability and Credibility is an advanced use case for most of CTI teams. It requires a mature organization and a well staffed team. For most of internal CTI team, a simple confidence level is enough to forge assessment, in particular for teams that concentrate on technical CTI.

-

Thus in OpenCTI, we have made the choice to fuse the notion of Credibility with the Confidence level that is commonly used by the majority of users. They have now the liberty to push forward their practice and use both Confidence and Reliability in their daily assessments.

-
-

Reliability open vocabulary

-

Reliability value can be set for every Entity in the platform that can be Author of Knowledge:

-
    -
  • Organizations
    • -
  • Individuals
    • -
  • Systems
    • -
  • and also Reports
    • -
-

Reliability on Reports allows you to specify the reliability associated to the original author of the report if you received it through a provider.

-

For all Knowledge in the platform, the reliability of the source of the Knowledge (author) is displayed in the Overview. This way, you can always forge your assessment of the provided Knowledge regarding the reliability of the author.

-

Entity reliability and confidence

-

You can also now filter entities by the reliability of its author.

-
-

Tip

-

This way, you may choose to feed your work with only Knowledge provided by reliable sources.

-
-

Reliability is an open vocabulary that can be customized in Settings -> Taxonomies -> Vocabularies : reliability_ov.

-
-

Info

-

The setting by default is the Reliability scale from NATO Admiralty code. But you can define whatever best fit your organization.

-
-

Settings reliability

-

Confidence scale

-

Confidence level can be set for:

-
    -
  • Analyses: Report, Grouping, Malware analysis, Notes
    • -
  • Cases: Incident Response, Request for Information, Request for Takedown, Feedback
    • -
  • Events: Incident, Sighting, Observed data
    • -
  • Observations: Indicator, Infrastructure
    • -
  • Threats: Threat actor (Group), Threat actor (Individual), Intrusion Set, Campaign
    • -
  • Arsenal: Malware, Channel, Tool, Vulnerability
    • -
-

For all of these entities, the Confidence level is displayed in the Overview, along with the Reliability. This way, you can rapidly assess the Knowledge with the Confidence level representing the credibility/quality of the information.

-

Confidence scale customization

-

Confidence level is a numerical value between 0 and 100. But Multiple "Ticks" can be defined and labelled to provide a meaningful scale.

-

Confidence level can be customized for each entity type in Settings > Customization > Entity type.

-

Confidence level customization

-

As such customization can be cumbersome, three confidence level templates are provided in OpenCTI:

-
    -
  • Admiralty: corresponding to the Admiralty code's credibility scale
    • -
  • Objective: corresponding to a full objective scale, aiming to leave any subjectivity behind. With this scale, an information confidence is:
      -
    • "Cannot be judged": there is no data regarding the credibility of the information
      • -
    • "Told": the information is known because it has been told to the source. The source doesn't verify it by any means.
      • -
    • "Induced": the information is the result of an analysis work and is based on other similar information assumed to be true.
      • -
    • "Deduced": the information is the result of an analysis work, and is a logical conclusion of other information assumed to be true.
      • -
    • "Witnessed": the source have observed itself the described situation or object.
      • -
    -
    • -
  • standard: the historic confidence level scale in OpenCTI defining a Low, Med and High level of confidence.
    • -
-

It is always possible to modify an existing template to define a custom scale adapted to your context.

-
-

Tip

-

If you use the Admiralty code setting for both reliability and Confidence, you will find yourself with the equivalent of NATO confidence notation in the Overview of your different entities (A1, B2, C3, etc.)

-
-

-

Max confidence level

-

Overview

-

We know that in organizations, different users do not always have the same expertise or seniority. As a result, some specific users can be more "trusted" when creating or updating knowledge than others. Additionally, because connectors, TAXII feeds and streams are all linked to respectively one user, it is important to be able to differentiate which connector, stream or TAXII feed is more trustable than others.

-

This is why we have introduced the concept of max confidence level to tackle this use case.

-

Max confidence level per user allows organizations to fine tune their users to ensure knowledge updated and created stays as consistent as possible.

-

The maximum confidence level can be set at the Group level or at the User level, and can be overridden by entity type for fine-tuning your confidence policy.

-

Overall way of working

-

The overall idea is that users with a max confidence level lower than a confidence level of an entity cannot update or delete this entity.

-

Also, in a conservative approach, when 2 confidence levels are possible, we would always take the lowest one.

-

To have a detailed understanding of the concept, please browse through this diagram:

- - -

User effective confidence level

-

User and group confidence level configuration shall be viewed as:

-
    -
  • a maximum confidence level between 0 and 100 (optional for users, mandatory for groups);
    • -
  • a list of overrides (a max confidence level between 0 and 100) per entity type (optional).
    • -
-

The user's effective confidence level is the result of this configuration from multiple sources (user and their groups).

-

To compute this value, OpenCTI uses the following strategy:

-
    -
  • effective maximum confidence is the maximum value found in the user's groups;
    • -
  • effective overrides per entity type are cumulated from all groups, taking the maximum value if several overrides are set on the same entity type
    • -
  • if a user maximum confidence level is set, it overrides everything from groups, including the overrides per entity type defined at group level
    • -
  • if not, but the user has specific overrides per entity types, they override the corresponding confidence levels per entity types coming from groups
    • -
  • if a user has the administrator's "Bypass" capability, the effective confidence level will always be 100 without overrides, regardless of the group and user configuration on confidence level
    • -
-

The following diagram describes the different use-cases you can address with this system.

- - -

How to set a confidence level

-

You can set up a maximum confidence levels from the Confidences tab in the edition panel of your user or group. -The value can be selected between 0 and 100, or using the admiralty scale selector.

-

At the group level, the maximum confidence level is mandatory, but is optional at the user level (you have to enable it using the corresponding toggle button).

-

Update Confidence Level

-

How to override a max confidence level per entity type

-

You also have the possibility to override a max confidence level per entity type, limited to Stix Domain Objects.

-

Override Max Confidence Level Per Entity

-

You can visualize the user's effective confidence level in the user's details view, by hovering the corresponding tooltip. -It describes where the different values might come from.

-

Override Confidence Tooltip

-

Usage in OpenCTI

-

Example with the admiralty code template

-

Your organization have received a report from a CTI provider. At your organization level, this provider is considered as reliable most of the time and its reliability level has been set to "B - Usually Reliable" (your organization uses the Admiralty code).

-

This report concerns ransomware threat landscape and have been analysed by your CTI analyst specialized in cybercrime. This analyst has granted a confidence level of "2 - Probably True" to the information.

-

As a technical analyst, through the cumulated reliability and Confidence notations, you now know that the technical elements of this report are probably worth consideration.

-

Example with the admiralty code template

-

Example with the Objective template

-

As a CTI analyst in a governmental CSIRT, you build up Knowledge that will be shared within the platform to beneficiaries. Your CSIRT is considered as a reliable source by your beneficiaries, even if you play a role of a proxy with other sources, but your beneficiaries need some insights about how the Knowledge has been built/gathered.

-

For that, you use the "Objective" confidence scale in your platform to provide beneficiaries with that. When the Knowledge is the work of the investigation of your CSIRT, either from incident response or attack infrastructure investigation, you set the confidence level to "Witnessed", "Deduced" or "Induced" (depending on if you observed directly the data, or inferred it during your research). When the information has not been verified by the CSIRT but has value to be shared with beneficiaries, you can use the "Told" level to make it clear to them that the information is probably valuable but has not been verified.

-

Example with the Objective template

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/search/index.html b/6.2.18/usage/search/index.html deleted file mode 100755 index 484f813d..00000000 --- a/6.2.18/usage/search/index.html +++ /dev/null @@ -1,4204 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Search for knowledge - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Search for knowledge

-

In OpenCTI, you have access to different capabilities to be able to search for knowledge in the platform. In most cases, a search by keyword can be refined with additional filters for instance on the type of object, the author etc.

- -

The global search is always available in the top bar of the platform.

-
-

Search bar

-
-

This search covers all STIX Domain Objects (SDOs) and STIX Cyber Observables (SCOs) in the platform. The search results are sorted according to the following behaviour:

-
    -
  • Priority 1 for exact matching of the keyword in one attribute of the objects.
    • -
  • Priority 2 for partial matching of the keyword in the name, the aliases and the description attributes (full text search).
    • -
  • Priority 3 for partial matching of the keyword in all other attributes (full text search).
    • -
-

If you get unexpected result, it is always possible to add some filters after the initial search:

-

Search filters

-

Also, using the Advanced search button, it is possible to directly put filters in a global search:

-

Advanced search

-
-

Advanced filters

-

You have access to advanced filters all accross the UI, if you want to know more about how to use these -filters with the API or the Python library, don't hesitate to read the dedicated page

-
-

Full text search in files content

-
-

Enterprise edition

-

Full text search in files content is available under the "OpenCTI Enterprise Edition" license.

-

Please read the dedicated page to have all information

-
-

It's possible to extend the global search by keywords to the content of documents uploaded to the platform via the Data import tab, or directly linked to an entity via its Data tab.

-

It is particularly useful to enable Full text indexing to avoid missing important information that may not have been structured within the platform. This situation can arise due to a partial automatic import of document content, limitations of a connector, and, of course, errors during manual processing.

-

Files search

-

In order to search in files, you need to configure file indexing.

- -

The bulk search capabilities is available in the top bar of the platform and allows you to copy paste a list of keyword or objects (ie. list of domains, list of IP addresses, list of vulnerabilities, etc.) to search in the platform:

-

Bulk search

-

When searching in bulk, OpenCTI is only looking for an exact match in some properties:

-
    -
  • name
    • -
  • aliases
    • -
  • x_opencti_aliases
    • -
  • x_mitre_id
    • -
  • value
    • -
  • subject
    • -
  • abstract
    • -
  • hashes.MD5
    • -
  • hashes.SHA-1
    • -
  • hashes.SHA-256
    • -
  • hashes.SHA-512
    • -
  • x_opencti_additional_names
    • -
-

When something is not found, it appears in the list as Unknown and will be excluded if you choose to export your search result in a JSON STIX bundle or in a CSV file.

-

Bulk search results

- -

In most of the screens of knowledge, you always have a contextual search bar allowing you to filter the list you are on:

-

Contextual search

-

The search keyword used here is taken into account if you decide to export the current view in a file such as a JSON STIX bundle or a CSV file.

-

Other search bars

-

Some other screens can contain search bars for specific purposes. For instance, in the graph views to filter the nodes displayed on the graph:

-

Search in graph

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/tips-widget-creation/index.html b/6.2.18/usage/tips-widget-creation/index.html deleted file mode 100755 index 02b6e434..00000000 --- a/6.2.18/usage/tips-widget-creation/index.html +++ /dev/null @@ -1,4329 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Tips for widget creation - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Pro-tips on widget creation

-

Previously, the creation of widgets has been covered. To help users being more confident in creating widgets, here are some details to master the widget creation.

-

-

How to choose the appropriate widget visualization for your use case?

-

We can classify the widgets in 3 different types.

-

Single dimension widgets

-

Use these widgets when you would like to display information about one single type of object (entity or relation).

-
    -
  • Widget visualizations: number, list, list (distribution), timeline, donuts, radar, map, bookmark, tree map.
    • -
  • Use case example: view the amount of malware in platform (number widget), view the top 10 threat actor group target a specific country (distribution list widget), etc.
    • -
-

Multi dimension widgets

-

Use these widgets if you would like to compare or have some insights about similar types of object (up to 5).

-
    -
  • Widget visualizations: line, area, heatmap, vertical bars.
    • -
  • Use case example: view the amount of malware, intrusion sets, threat actor groups added in the course of last month in the platform (line or area widget).
    • -
-
-

Type of object in widget

-
-

These widgets need to use the same "type" of object to work properly. You always need to add relationships in the filter view if you have selected a "knowledge graph" perspective. If you have selected the knowledge graph entity, adding "Entities" (click on + entities) will not work, since you are not counting the same things.

-

Break down widgets

-

Use this widget if you want to divide your data set into smaller parts to make it clearer and more useful for analysis.

-
    -
  • Widget visualization: horizontal bars.
    • -
  • Use case example: view the list of malware targeting a country breakdown by the type of malware.
    • -
-

breakdown example

-

Adding datasets to your widget

-

Adding datasets can serve two purposes: comparing data or breakdown a view to have deeper understanding on what a specific dataset is composed of.

-

Use Case 1: compare several datasets

-

As mentioned in How to choose the appropriate widget visualization for your use case? section you can add data sets to compare different data. Make sure to add the same type of objects (entities or relations) to be able to compare the same objects, by using access buttons like +, + Relationships, or + Entities.

-

You can add up to 5 different data sets. The Label field allows you to name a data set, and this label can then be shown as a legend in the widget using the Display legend button in the widget parameters (see the next section).

-

Use case 2: break down your chart

-

As mentioned in How to choose the appropriate widget visualization for your use case? section you can add data sets to decompose your graph into smaller meaningful chunks. In the below points, you can find some use cases that will help you understand how to structure your data.

-

You can break down a view either by entity or by relations, depending on what you need to count.

-

Break down by entity

-

Use case example: I need to understand what are the most targeted countries by malware, and have a breakdown for each country by malware type.

-

Process:

-
    -
  1. To achieve this use case, you first need to select the horizontal bar vizualisation.
    2. -
  2. Then you need to select the knowledge graph perspective.
    3. -
-

In the filters view:

-
    -
  1. Then input your main query Source type = Malware AND Target type = Countries AND Relation type = Targets. Add a label to your dataset.
    2. -
  2. Add an entity data set by using access button + Entities.
    3. -
  3. Add the following filters Entity type = Malware AND In regards of = targets. Add a label to your dataset.
    4. -
-

filter view

-

In the parameter view:

-
    -
  1. Attribute (of your relation) = entity (so that you display the different entities values)
    2. -
  2. Display the source toggle = off
    3. -
  3. Attribute (of your entity malware) = Malware type (since you want to break down your relations by the malware types)
    4. -
-

parameter view

-

As a result, you get a list of countries broken down by malware types.

-

final result

-

Break down by relation

-

Use case example: I need to understand what are the top targeting malware and have a breakdown of the top targets per malware

-

Process:

-
    -
  1. To achieve this use case, you first need to select the horizontal bar vizualisation.
    2. -
  2. Then you need to select the knowledge graph perspective.
    3. -
-

In the filters view:

-
    -
  1. Then input your main query Source type = Malware AND Relation type = Targets. Add a label to your dataset.
    2. -
  2. Add a relation data set by using access button + Relationships
    3. -
  3. Add the following filters Source type = Malware AND Relation type = targets. Add a label to your dataset.
    4. -
-

filter view

-

In the parameter view:

-
    -
  1. Attribute (of your relation): entity (so that you display the different entities values)
    2. -
  2. Display the source toggle = on
    3. -
  3. Attribute (of your entity malware) = Malware type (since you want to break down your relations by the malware types)
    4. -
  4. Display the source toggle = off
    5. -
-

paramter view

-

As a result, you get a list of malware with the breakdown of their top targets.

-

final view

-

More use cases

-

To see more use cases, feel free to have a look at this blog post that will provide you additional information.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/widgets/index.html b/6.2.18/usage/widgets/index.html deleted file mode 100755 index d382fc77..00000000 --- a/6.2.18/usage/widgets/index.html +++ /dev/null @@ -1,4300 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Widget creation - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Widget creation

-

Creating widgets on the dashboard involves a four-step configuration process. By navigating through these configuration steps, users can design widgets that meet their specific requirements.

-

Widget configuration

-

1. Visualization

-

Users can select from 15 diverse visualization options to highlight different aspects of their data. This includes simple views like counters and lists, as well as more intricate views like heatmaps and trees. The chosen visualization impacts the available perspectives and parameters, making it crucial to align the view with the desired data observations. Here are a few insights:

-
    -
  • Line and Area views: Ideal for visualizing activity volumes over time.
    • -
  • Horizontal bar views: Designed to identify top entities that best satisfy applied filters (e.g., top malware targeting the Finance sector).
    • -
  • Tree views: Useful for comparing activity volumes.
    • -
  • ...
    • -
-

Widget visualization

-

2. Perspective

-

A perspective is the way the platform will count the data to display in your widgets:

-
    -
  • Entities Perspective: Focuses on entities, allowing observation of simple knowledge based on defined filters and criteria. The count will be based on entities only.
    • -
  • Knowledge Graph Perspective: Concentrates on relationships, displaying intricate knowledge derived from relationships between entities and specified filters. The count will be based on relations only.
    • -
  • Activity & History Perspective: Centers on activities within the platform, not the knowledge content. This perspective is valuable for monitoring user and connector activities, evaluating data sources, and more.
    • -
-

Widget perspective

-

3. Filters

-

Generic knowledge

-

Filters vary based on the selected perspective, defining the dataset to be utilized in the widget. Filters are instrumental in narrowing down the scope of data for a more focused analysis.

-

While filters in the "Entities" and "Activity & History" perspectives align with the platform's familiar search and feed creation filters, the "Knowledge Graph" perspective introduces a more intricate filter configuration.Therefore, they need to be addressed in more detail.

-

Filter in the context of Knowledge Graph

-

Two types of filters are available in the Knowledge Graph perspective:

-
    -
  • -

    Main query filter

    -
      -
    • Classic filters (gray): Define the relationships to be retrieved, forming the basis on which the widget displays data. Remember, statistics in the Knowledge Graph perspective are based on relationships.
      • -
    -
    • -
  • -

    Pre-query filters

    -
      -
    • Pre-query filters are used to provide to your main query a specific dataset. In other words, instead of making a query on the whole data set of your platform, you can already target a subset of data that will match certain criteria. They are two types of pre-query filters:
        -
      • Dynamic filters on the source (orange): Refine data by filtering on entities positioned as the source (in the "from" position) of the relationship.
        • -
      • Dynamic filters on the target (green): Refine data by filtering on entities positioned as the target (in the "to" position) of the relationship.
        • -
      -
      • -
    -
    • -
-
-

Pre-query limitation

-

The pre-query is limited to 5000 results. If your pre-query results in having more than 5000 results, your widget will only display statistics based on these 5000 results matching your pre-query, resulting in a wrong view. To avoid this issue, be specific in your pre-query filters.

-
-

Example scenario:

-

Let's consider an example scenario: Analyzing the initial access attack patterns used by intrusion sets targeting the finance sector.

-
    -
  1. Classic filters: Define the relationships associated with the use of attack patterns by intrusion sets
    2. -
  2. Dynamic filters on the source (Orange): Narrow down the data by filtering on intrusion sets targeting the finance sector.
    3. -
  3. Dynamic filters on the target (Green): Narrow down the data by filtering on attack patterns associated with the kill chain's initial access phase.
    4. -
-

By leveraging these advanced filters, users can conduct detailed analyses within the Knowledge Graph perspective, unlocking insights that are crucial for understanding intricate relationships and statistics.

-

Widget filters

-

In certain views, you can access buttons like +, + Relationships, or + Entities. These buttons enable you to incorporate different data into the same widget for comparative analysis. For instance, in a Line view, adding a second set of filters will display two curves in the widget, each corresponding to one of the filtered data sets. Depending on the view, you can work with 1 to 5 sets of filters. The Label field allows you to name a data set, and this label can then be shown as a legend in the widget using the Display legend button in the widget parameters (see the next section).

-

Widget multiple filters

-

4. Parameters

-

Parameters depend on the chosen visualization and allow users to define widget titles, choose displayed elements from the filtered data, select data reference date, and configure various other parameters specific to each visualization.

-

For the "Knowledge Graph" perspective, a critical parameter is the Display the source toggle. This feature empowers users to choose whether the widget displays entities from the source side or the target side of the relationships.

-
    -
  • Toggle ON ("Display the source"): The widget focuses on entities positioned as the source of the relationships (in the "from" position).
    • -
  • Toggle OFF ("Display the target"): The widget shifts its focus to entities positioned as the target of the relationships (in the "to" position).
    • -
-

This level of control ensures that your dashboard aligns precisely with your analytical objectives, offering a tailored perspective based on your data and relationship.

-

Widget parameters

-

Prerequisite knowledge

-

To successfully configure widgets in OpenCTI, having a solid understanding of the platform's data modeling is essential. Knowing specific relationships, entities, and their attributes helps refine filters accurately. Let's explore two examples.

-

Scenarios 1:

-

Consider the scenario where you aim to visualize relationships between intrusion sets and attack patterns. In this case, the relevant relationship type connecting intrusion sets to attack patterns is labeled as "Uses" (as illustrated in the "Filters" section).

-

Scenarios 2:

-

Suppose your goal is to retrieve all reports associated with the finance sector. In this case, it's essential to use the correct filter for the finance sector. Instead of placing the finance sector in the "Related entity" filter, it should be placed in the "Contains" filter. Since a Report is a container object (like Cases and Groupings), it contains entities within it and is not related to entities.

-

Key data modeling aspects

-
    -
  • Entities: Recognizing container (e.g. Reports, Cases and Groupings) and understanding the difference with non-container.
    • -
  • Relationships: Identifying the relationship types connecting entities.
    • -
  • Attributes: Understanding entities and relationships attributes for effective filtering.
    • -
-

Having this prerequisite knowledge allows you to navigate the widget configuration process seamlessly, ensuring accurate and insightful visualizations based on your specific data requirements.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/workbench/index.html b/6.2.18/usage/workbench/index.html deleted file mode 100755 index aadc5c6c..00000000 --- a/6.2.18/usage/workbench/index.html +++ /dev/null @@ -1,4146 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Analyst workbench - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Analyst workbench

-

Workbenches serve as dedicated workspaces for manipulating data before it is officially imported into the platform.

-

Location of use

-

The workbenches are located at various places within the platform:

-

Data import and analyst workbenches window

-

This window encompasses all the necessary tools for importing a file. Files imported through this interface will subsequently be processed by the import connectors, resulting in the creation of workbenches. Additionally, analysts can manually create a workbench by clicking on the "+" icon at the bottom right of the window.

-

Data import and workbenches panel

-

Data tabs of all entities

-

Workbenches are also accessible through the "Data" tabs of entities, providing convenient access to import data associated with the entity.

-

Workbench in "Data" tab

-

Operation

-

Workbenches are automatically generated upon the import of a file through an import connector. When an import connector is initiated, it scans files for recognizable entities and subsequently creates a workbench. All identified entities are placed within this workbench for analyst reviews. -Alternatively, analysts have the option to manually create a workbench by clicking on the "+" icon at the bottom right of the "Data import and analyst workbenches" window.

-

Overview of workbench

-

The workbench being a draft space, the analysts use it to review connector proposals before finalizing them for import. Within the workbench, analysts have the flexibility to add, delete, or modify entities to meet specific requirements.

-

Workbench data manipulation

-

Once the content within the workbench is deemed acceptable, the analyst must initiate the ingestion process by clicking on Validate this workbench. This action signifies writing the data in the knowledge base.

-
-

Workbenches are drafting spaces

-

Until the workbench is validated, the contained data remains in draft form and is not recorded in the knowledge base. This ensures that only reviewed and approved data is officially integrated into the platform.

-
-

For more information on importing files, refer to the Import from files documentation page.

-

Confidence level of created knowledge through workbench

-

The confidence level of knowledge created through workbench is affected by the confidence level of the user. Please navigate to this page to understand in more details.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/6.2.18/usage/workflows/index.html b/6.2.18/usage/workflows/index.html deleted file mode 100755 index 9a5ce334..00000000 --- a/6.2.18/usage/workflows/index.html +++ /dev/null @@ -1,4080 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Workflows and assignation - OpenCTI Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - -
- - - - - - -
- -
- - - - - - - - - -
-
- - - -
-
-
- - - - - - - -
-
-
- - - -
-
-
- - - -
-
-
- - - -
-
- - - - - - - - - - - - - - - - - - - - -

Workflows and assignation

-

Efficiently manage and organize your work within the OpenCTI platform by leveraging workflows and assignment. These capabilities provide a structured approach to tracking the status of objects and assigning responsibilities to users.

-

Workflows

-

Workflows are designed to trace the status of objects in the system. They are represented by the "Processing status" field embedded in each object. By default, this field is disabled for most objects but can be activated through the platform settings. For details on activating and configuring workflows, refer to the dedicated documentation page.

-

Enabling workflows enhances visibility into the progress and status of different objects, providing a comprehensive view for effective management.

-

Processing status

-

Assignment attributes

-

Certain objects, including Reports, Cases, and Tasks, come equipped with "Assignees" and "Participants" attributes. These attributes serve the purpose of designating individuals responsible for the object and those who actively participate in it.

-

Attributes can be set as mandatory or with default values, streamlining the assignment process. Users can also be assigned or designated as participants manually, contributing to a collaborative and organized workflow. For details on configuring attributes, refer to the dedicated documentation page.

-

Assignment attributes

-

Users can stay informed about assignments through notification triggers. By setting up notification triggers, users receive alerts when an object is assigned to them. This ensures timely communication and proactive engagement with assigned tasks or responsibilities.

- - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
- -
- - - -
-
-
-
- - - - - - - - - - - - - - \ No newline at end of file diff --git a/versions.json b/versions.json index e5225cc3..38ef65da 100644 --- a/versions.json +++ b/versions.json @@ -1,9 +1,4 @@ [ - { - "version": "6.2.18", - "title": "6.2.18", - "aliases": [] - }, { "version": "6.2.X", "title": "6.2.X",