Lumu
SecOps operations - Reflect and manage the Lumu Incidents either from XSOAR Cortex or viceversa using the mirroring integration flow, https://lumu.io/
Utilities · Lumu
Configuration parameters
max_fetch— Maximum number of incidents to fetch every timefirst_fetch— First fetch time intervalurl— Server URL (required)proxy— Use system proxy settingsinsecure— Trust any certificate (not secure)api_key— API Key (required)fetch_offset— Incident Offsettotal_items_per_lumu_fetch— Total Incident per fetching using lumu endpointmax_time_fetching_lumu_incident— Max time in seconds per fetching using lumu endpointisFetch— Fetch incidentsincidentType— Incident typeincidentFetchInterval— Incidents Fetch Intervalmirror_direction— Incident Mirroring Directionmirror_tags— Mirror tags
Commands (21)
-
get-mapping-fieldsmirror process.
-
get-modified-remote-datamirror process.
-
get-remote-datamirror process.
-
lumu-clear-cacheLumu clear cache, only trigger if it mandatory.
-
lumu-close-incident| `{incident-uuid}` | uuid of the specific incident | |---|---| >To associate a specific user to this transaction, include the header `Lumu-User-Id` with the user id as a value. [Read more](#user-identification-considerations).
-
lumu-comment-a-specific-incidentGet a paginated list of open incidents for the company. The items are listed by the most recent.
-
lumu-consult-incidents-updates-through-restLumu provides an endpoint to consult real-time updates on incident operations through REST when Websocket is not available. Note: the date format in the updates received from the endpoint is in the UTC time zone and follows standards published in RFC 3339 and ISO 8601 | `{company-key}` | Your company's unique API key available at the [Lumu Portal](#access-and-authentication) | | --- | --- |.
-
lumu-get-cacheLumu get cache.
-
lumu-mark-incident-as-readThis transaction does not require any additional body parameters. | `{incident-uuid}` | uuid of the specific incident | |---|---| >To associate a specific user to this transaction, include the header `Lumu-User-Id` with the user id as a value. [Read more](#user-identification-considerations).
-
lumu-mute-incident| `{incident-uuid}` | uuid of the specific incident | |---|---| >To associate a specific user to this transaction, include the header `Lumu-User-Id` with the user id as a value. [Read more](#user-identification-considerations).
-
lumu-retrieve-a-specific-incident-contextGet details of a specific Incident. | `{incident-uuid}` | uuid of the specific incident | |---|---|.
-
lumu-retrieve-a-specific-incident-detailsGet details of a specific Incident. | `{incident-uuid}` | uuid of the specific incident | |---|---|.
-
lumu-retrieve-a-specific-labelGet details such as id, name and business relevance from a specific label. | `{label-id}` | ID of the specific label | |---|---|.
-
lumu-retrieve-closed-incidentsGet a paginated list of closed incidents for the company. The items are listed by the most recent.
-
lumu-retrieve-endpoints-by-incidentGet a paginated summary of the endpoints affected by a specified incident. | `{incident-uuid}` | uuid of the specific incident | |---|---|.
-
lumu-retrieve-incidentsGet a paginated list of incidents for the company. The items are listed by the most recent.
-
lumu-retrieve-labelsGet a paginated list of all the labels created for the company and its details such as id, name and business relevance. The items are sorted by the label id in ascending order.
-
lumu-retrieve-muted-incidentsGet a paginated list of muted incidents for the company. The items are listed by the most recent.
-
lumu-retrieve-open-incidentsGet a paginated list of open incidents for the company. The items are listed by the most recent.
-
lumu-unmute-incident| `{incident-uuid}` | uuid of the specific incident | |---|---| >To associate a specific user to this transaction, include the header `Lumu-User-Id` with the user id as a value. [Read more](#user-identification-considerations).
-
update-remote-systemmirror process.