mirror of
https://github.com/OpenCTI-Platform/opencti.git
synced 2025-12-22 08:17:08 +00:00
[docs] Backport of minor docs improvements from legacy repository (#13720)
This commit is contained in:
@@ -55,7 +55,7 @@ You can create a public dashboard either from the list of public dashboards or f
|
||||

|
||||
|
||||
In this panel you will find two parts:
|
||||
- At the top you have a form allowing you to create public dashboards,
|
||||
- At the top, you have a form allowing you to create public dashboards,
|
||||
- And below, the list of the public dashboards you have created.
|
||||
|
||||

|
||||
@@ -92,7 +92,7 @@ access on the platform **and the maximum sharable marking definitions** defined
|
||||
|
||||
!!! note "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](../administration/segregation.md) to be
|
||||
As a platform administrator, you can define, for each group and for each type of marking definition, [maximum marking definitions shareable](../administration/segregation.md) to be
|
||||
shared through Public Dashboard, regardless of the definition set by users in their public dashboard.
|
||||
|
||||

|
||||
|
||||
@@ -23,7 +23,7 @@ Purging a message queue is necessary to remove any accumulated messages that may
|
||||
|
||||
By purging the queue, you ensure that the connector starts with a clean slate, processing only the new data.
|
||||
|
||||
### Connector Ecosystem
|
||||
### 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](https://filigran.notion.site/OpenCTI-Ecosystem-868329e9fb734fca89692b2ed6087e76#c94bf651e08146c4855a25efeaabc574). Connectors are categorized into three types: import connectors (the focus here), [enrichment connectors](../enrichment.md), and stream consumers. Further documentation on connectors is available on [the dedicated documentation page](../../deployment/connectors.md).
|
||||
|
||||
|
||||
@@ -214,5 +214,4 @@ Because of the volumes of information the history is written in a specific index
|
||||
|
||||
- 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](inferences.md)
|
||||
- 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](inferences.md)
|
||||
- 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.
|
||||
|
||||
Reference in New Issue
Block a user