Serenety

Details

ID	`Serenety`
Provider	XM Cyber
Category	Vulnerability Management
From Version	6.10.0
Docker Image	`demisto/python3:3.12.13.10116658`
Supported Modules	Agentix XSIAM

README

XMCO Serenety

Configure XMCO Serenety in Cortex

To configure an instance of XMCO Serenety integration in Cortex XSOAR:

Parameter	Required
Server URL (e.g. https://leportail.xmco.fr)	True
API Key	True
Trust any certificate (not secure)	False
Use system proxy settings	False

Commands

You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.

fetch-incidents

Fetch the Serenety lerts from XMCO LePortail

Base Command

fetch-incidents

Input

Argument Name	Description	Required
scope	A string representing the scope id to filter on	Optional

Command Example

!fetch-incidents
!fetch-incidents scope=123456789

Configuration parameters

url — XMCO LePortail instance URL (required)
api_key — (required)
insecure — Trust any certificate (not secure)
proxy — Use system proxy settings
isFetch — Fetch incidents
max_fetch — Maximum number of incidents per fetch
first_fetch — First fetch time
incidentType — Incident type
incidentFetchInterval — Incidents Fetch Interval

Commands (1)

fetch-incidents
Fetch Serenety alert from XMCO LePortail.

Source

Serenety.py Serenety_test.py Serenety.yml Serenety_description.md command_examples.txt

Download History Raw

## XMCO Serenety

To configure an instance of XMCO Serenety integration in Cortex XSOAR:

1. Select `XMCO Serenety Alert` in the Incident type section.
2. Select `XMCO - Serenety Mapper` in the Mapper section.
3. Provide 'Server URL'. The default server URL should be sufficient.

4. Provide 'API Key':

   Retrieve your authentication token via the [XMCO LePortail](https://leportail.xmco.fr)

   Keep the token safe, as it grants access to sensitive threat data related to your organization. Store it in a secure place, such as an encrypted password vault, and do not share it unless absolutely necessary. If you feel that the token has been compromised, please change it immediately.

5. Check the options `Trust any certificate (not secure)` and `Use system proxy settings` if needed. You can test with the `Test` button.
6. The options `Maximum number of incidents per fetch` and `First fetch time` are not used for the moment, so you can let the default values (50 et 3 days).