Skip to content

Systancia Cleanroom

Overview

Systancia Cleanroom is a secure and isolated virtualized environment that ensures confidentiality and integrity for sensitive data and applications, offering a controlled and monitored workspace for high-security operations without compromising efficiency or user experience.

Warning

Important note - This format is currently in beta. We highly value your feedback to improve its performance.

The following Sekoia.io built-in rules match the intake Systancia Cleanroom [BETA]. This documentation is updated automatically and is based solely on the fields used by the intake which are checked against our rules. This means that some rules will be listed but might not be relevant with the intake.

SEKOIA.IO x Systancia Cleanroom [BETA] on ATT&CK Navigator

Cryptomining

Detection of domain names potentially related to cryptomining activities.

  • Effort: master
Dynamic DNS Contacted

Detect communication with dynamic dns domain. This kind of domain is often used by attackers. This rule can trigger false positive in non-controlled environment because dynamic dns is not always malicious.

  • Effort: master
Exfiltration Domain

Detects traffic toward a domain flagged as a possible exfiltration vector.

  • Effort: master
Remote Access Tool Domain

Detects traffic toward a domain flagged as a Remote Administration Tool (RAT).

  • Effort: master
SEKOIA.IO Intelligence Feed

Detect threats based on indicators of compromise (IOCs) collected by SEKOIA's Threat and Detection Research team.

  • Effort: elementary
Sekoia.io EICAR Detection

Detects observables in Sekoia.io CTI tagged as EICAR, which are fake samples meant to test detection.

  • Effort: master
TOR Usage Generic Rule

Detects TOR usage globally, whether the IP is a destination or source. TOR is short for The Onion Router, and it gets its name from how it works. TOR intercepts the network traffic from one or more apps on user’s computer, usually the user web browser, and shuffles it through a number of randomly-chosen computers before passing it on to its destination. This disguises user location, and makes it harder for servers to pick him/her out on repeat visits, or to tie together separate visits to different sites, this making tracking and surveillance more difficult. Before a network packet starts its journey, user’s computer chooses a random list of relays and repeatedly encrypts the data in multiple layers, like an onion. Each relay knows only enough to strip off the outermost layer of encryption, before passing what’s left on to the next relay in the list.

  • Effort: master

Event Categories

The following table lists the data source offered by this integration.

Data Source Description
Authentication logs Privileged Access Management mechanism

In details, the following table denotes the type of events produced by this integration.

Name Values
Kind ``
Category process, session
Type end, start

Event Samples

Find below few samples of events and how they are normalized by Sekoia.io.

{
    "message": "Connexion au portail web org:example, user:jdoe@local, ip:1.2.3.4",
    "event": {
        "category": "session",
        "outcome": "success",
        "reason": "Connexion au portail web",
        "type": "start"
    },
    "observer": {
        "product": "Systancia Cleanroom",
        "vendor": "Systancia"
    },
    "organization": {
        "name": "example"
    },
    "related": {
        "ip": [
            "1.2.3.4"
        ],
        "user": [
            "jdoe"
        ]
    },
    "source": {
        "address": "1.2.3.4",
        "ip": "1.2.3.4"
    },
    "user": {
        "domain": "local",
        "name": "jdoe"
    }
}
{
    "message": "Connexion d'un plugin utilisateur org:example, user:jdoe@local, ip:1.2.3.4",
    "event": {
        "category": "session",
        "outcome": "success",
        "reason": "Connexion d'un plugin utilisateur",
        "type": "start"
    },
    "observer": {
        "product": "Systancia Cleanroom",
        "vendor": "Systancia"
    },
    "organization": {
        "name": "example"
    },
    "related": {
        "ip": [
            "1.2.3.4"
        ],
        "user": [
            "jdoe"
        ]
    },
    "source": {
        "address": "1.2.3.4",
        "ip": "1.2.3.4"
    },
    "user": {
        "domain": "local",
        "name": "jdoe"
    }
}
{
    "message": "D\u00e9connexion du portail web org:example, user:jdoe@EXAMPLE, ip:1.2.3.4",
    "event": {
        "category": "session",
        "outcome": "success",
        "reason": "D\u00e9connexion du portail web",
        "type": "end"
    },
    "observer": {
        "product": "Systancia Cleanroom",
        "vendor": "Systancia"
    },
    "organization": {
        "name": "example"
    },
    "related": {
        "ip": [
            "1.2.3.4"
        ],
        "user": [
            "jdoe"
        ]
    },
    "source": {
        "address": "1.2.3.4",
        "ip": "1.2.3.4"
    },
    "user": {
        "domain": "EXAMPLE",
        "name": "jdoe"
    }
}
{
    "message": "D\u00e9connexion d'un plugin utilisateur org:example, user:jdoe@local, ip:10.48.178.33",
    "event": {
        "category": "session",
        "outcome": "success",
        "reason": "D\u00e9connexion d'un plugin utilisateur",
        "type": "end"
    },
    "observer": {
        "product": "Systancia Cleanroom",
        "vendor": "Systancia"
    },
    "organization": {
        "name": "example"
    },
    "related": {
        "ip": [
            "10.48.178.33"
        ],
        "user": [
            "jdoe"
        ]
    },
    "source": {
        "address": "10.48.178.33",
        "ip": "10.48.178.33"
    },
    "user": {
        "domain": "local",
        "name": "jdoe"
    }
}
{
    "message": "Fermeture d'une application  RDS  : DETECTION CENTRAL (RDP) AGENT CLIENT org:example, user:jdoe@EXAMPLE, ip:1.2.3.4",
    "event": {
        "category": "process",
        "outcome": "success",
        "reason": "Fermeture d'une application  RDS  : DETECTION CENTRAL (RDP) AGENT CLIENT",
        "type": "end"
    },
    "observer": {
        "product": "Systancia Cleanroom",
        "vendor": "Systancia"
    },
    "organization": {
        "name": "example"
    },
    "related": {
        "ip": [
            "1.2.3.4"
        ],
        "user": [
            "jdoe"
        ]
    },
    "source": {
        "address": "1.2.3.4",
        "ip": "1.2.3.4"
    },
    "user": {
        "domain": "EXAMPLE",
        "name": "jdoe"
    }
}
{
    "message": "Lancement d'une application RDS  : DETECTION CENTRAL (RDP) AGENT CLIENT org:example, user:jdoe@EXAMPLE, ip:1.2.3.4",
    "event": {
        "category": "process",
        "outcome": "success",
        "reason": "Lancement d'une application RDS  : DETECTION CENTRAL (RDP) AGENT CLIENT",
        "type": "start"
    },
    "observer": {
        "product": "Systancia Cleanroom",
        "vendor": "Systancia"
    },
    "organization": {
        "name": "example"
    },
    "related": {
        "ip": [
            "1.2.3.4"
        ],
        "user": [
            "jdoe"
        ]
    },
    "source": {
        "address": "1.2.3.4",
        "ip": "1.2.3.4"
    },
    "user": {
        "domain": "EXAMPLE",
        "name": "jdoe"
    }
}
{
    "message": "Echec de la connexion au portail web : erreur d'authentification d'un utilisateur org:example, user:jdoe@EXAMPLE, ip:1.2.3.4",
    "event": {
        "category": "session",
        "outcome": "failure",
        "reason": "Echec de la connexion au portail web : erreur d'authentification d'un utilisateur",
        "type": "start"
    },
    "observer": {
        "product": "Systancia Cleanroom",
        "vendor": "Systancia"
    },
    "organization": {
        "name": "example"
    },
    "related": {
        "ip": [
            "1.2.3.4"
        ],
        "user": [
            "jdoe"
        ]
    },
    "source": {
        "address": "1.2.3.4",
        "ip": "1.2.3.4"
    },
    "user": {
        "domain": "EXAMPLE",
        "name": "jdoe"
    }
}

Extracted Fields

The following table lists the fields that are extracted, normalized under the ECS format, analyzed and indexed by the parser. It should be noted that infered fields are not listed.

Name Type Description
event.category keyword Event category. The second categorization field in the hierarchy.
event.outcome keyword The outcome of the event. The lowest level categorization field in the hierarchy.
event.reason keyword Reason why this event happened, according to the source
event.type keyword Event type. The third categorization field in the hierarchy.
observer.product keyword The product name of the observer.
observer.vendor keyword Vendor name of the observer.
organization.name keyword Organization name.
source.ip ip IP address of the source.
user.domain keyword Name of the directory the user is a member of.
user.name keyword Short name or login of the user.

Configure

This setup guide will show you how to forward your Systancia Cleanroom logs to Sekoia.io by means of a syslog transport channel.

Forward logs to Sekoia.io

Please consult the Syslog Forwarding documentation to forward these logs to Sekoia.io.

Systancia Cleanroom

  1. In the Systancia Clearoom system console, go to Logger settings

    logger_settings.png

  2. In the Logger setting panel:

  3. Select Send events to a remote syslog
  4. Type the address and the port to the log concentrator
  5. Select TCP (recommended) or TLS as the transport protocol
  6. Click Validate

    logger_settings_panel.png

Create the intake

Go to the intake page and create a new intake from the format Systancia Cleanroom.