Skip to content

Vade Cloud

Overview

Vade Cloud offers all protections against threats for any email inbox.

In this documentation we will explain how to collect and send Vade Cloud logs to SEKOIA.IO.

  • Vendor: Vade
  • Supported environment: Cloud
  • Detection based on: Telemetry
  • Supported application or feature: Email gateway, Anti-virus

Configure

Create the intake in Sekoia.io

Go to the intake page and create a new intake from the format Vade Cloud. Copy the intake key.

Pull events

To start to pull events, you have to:

  1. Go to the playbooks page and create a new playbook with the Fetch new logs from Vade Cloud trigger

  2. Set up the module configuration with the:

    • Vade Cloud API hostname: the URL of your admin interface of Vade Cloud. Most of the time this is https://cloud.vadesecure.com; TO BE ADAPTED depending on your context.
    • The email of the user: the login you use to connect to the admin interface of Vade Cloud. The account type MUST be "Admin".
    • The user password: the password you use to connect to the admin interface of Vade Cloud.

  3. Set up the trigger configuration with the intake key from the previous step.

  4. Start the playbook and enjoy your events

Info

Please make sure that the login is your account email.

Info

The events collection will not take events older than 7 days into account.

Raw Events Samples

In this section, you will find examples of raw logs as generated natively by the source. These examples are provided to help integrators understand the data format before ingestion into Sekoia.io. It is crucial for setting up the correct parsing stages and ensuring that all relevant information is captured.

{
    "message": "2023-07-20T09:15:02+00:00 localhost ulog[568]: [0000F4E4] qid=aaa1bbb2cc3,ip=1.2.3.4,sender=test@test.com,site=VSC000001,domain=maildomain.com,recipient=demo_1@maildomain.com: action=drop,status=virus,spamlevel=unknwon,tag=[VIRUS],stop=nil,reply=2,subject=\"Some subject\"",
    "site": "VSC000001",
    "from": "test@test.com",
    "to": "demo_1@maildomain.com",
    "subject": "Some subject",
    "date": 1689844502000,
    "operationType": "DROP",
    "messageType": "VIRUS",
    "messageId": "aaa1bbb2cc3",
    "hostname": "localhost",
    "filterType": "UNKNOWN",
    "filterReason": "2",
    "spamLevel": "UNKNWON",
    "domain": "maildomain.com",
    "ip": "1.2.3.4",
    "tag": "[VIRUS]"
}

Detection section

The following section provides information for those who wish to learn more about the detection capabilities enabled by collecting this intake. It includes details about the built-in rule catalog, event categories, and ECS fields extracted from raw events. This is essential for users aiming to create custom detection rules, perform hunting activities, or pivot in the events page.

The following Sekoia.io built-in rules match the intake Vade Cloud. 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 Vade Cloud on ATT&CK Navigator

Burp Suite Tool Detected

Burp Suite is a cybersecurity tool. When used as a proxy service, its purpose is to intercept packets and modify them to send them to the server. Burp Collaborator is a network service that Burp Suite uses to help discover many kinds of vulnerabilities (vulnerabilities scanner).

  • Effort: intermediate
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
EvilProxy Phishing Domain

Detects subdomains potentially generated by the EvilProxy adversary-in-the-middle phishing platform. Inspect the other subdomains of the domain to identify the landing page, and determine if the user submitted credentials. This rule has a small percentage of false positives on legitimate domains.

  • Effort: intermediate
Exfiltration Domain

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

  • Effort: master
Potential DNS Tunnel

Detects domain name which is longer than 95 characters. Long domain names are distinctive of DNS tunnels.

  • Effort: advanced
Remote Access Tool Domain

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

  • Effort: master
Remote Monitoring and Management Software - AnyDesk

Detect artifacts related to the installation or execution of the Remote Monitoring and Management tool AnyDesk.

  • Effort: master
Remote Monitoring and Management Software - Atera

Detect artifacts related to the installation or execution of the Remote Monitoring and Management tool Atera.

  • 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
Suspicious TOR Gateway

Detects suspicious TOR gateways. Gateways are often used by the victim to pay and decrypt the encrypted files without installing TOR. 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: advanced
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
Telegram Bot API Request

Detects suspicious DNS queries to api.telegram.org used by Telegram Bots of any kind

  • Effort: advanced

Event Categories

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

Data Source Description
Email gateway Vade Cloud provides core email protection from phishing, malware, and spam.

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

Name Values
Kind ``
Category email
Type info

Transformed Events Samples after Ingestion

This section demonstrates how the raw logs will be transformed by our parsers. It shows the extracted fields that will be available for use in the built-in detection rules and hunting activities in the events page. Understanding these transformations is essential for analysts to create effective detection mechanisms with custom detection rules and to leverage the full potential of the collected data.

{
    "message": "{\"message\":\"2023-07-20T09:15:02+00:00 localhost ulog[568]: [0000F4E4] qid=aaa1bbb2cc3,ip=1.2.3.4,sender=test@test.com,site=VSC000001,domain=maildomain.com,recipient=demo_1@maildomain.com: action=drop,status=virus,spamlevel=unknwon,tag=[VIRUS],stop=nil,reply=2,subject=\\\"Some subject\\\"\",\"site\":\"VSC000001\",\"from\":\"test@test.com\",\"to\":\"demo_1@maildomain.com\",\"subject\":\"Some subject\",\"date\":1689844502000,\"operationType\":\"DROP\",\"messageType\":\"VIRUS\",\"messageId\":\"aaa1bbb2cc3\",\"hostname\":\"localhost\",\"filterType\":\"UNKNOWN\",\"filterReason\":\"2\",\"spamLevel\":\"UNKNWON\",\"domain\":\"maildomain.com\",\"ip\":\"1.2.3.4\",\"tag\":\"[VIRUS]\"}",
    "event": {
        "action": "DROP",
        "category": [
            "email"
        ],
        "reason": "2",
        "type": [
            "info"
        ]
    },
    "@timestamp": "2023-07-20T09:15:02Z",
    "destination": {
        "address": "maildomain.com",
        "domain": "maildomain.com",
        "ip": "1.2.3.4",
        "registered_domain": "maildomain.com",
        "top_level_domain": "com"
    },
    "email": {
        "from": {
            "address": [
                "test@test.com"
            ]
        },
        "local_id": "aaa1bbb2cc3",
        "subject": "Some subject",
        "to": {
            "address": [
                "demo_1@maildomain.com"
            ]
        }
    },
    "related": {
        "hosts": [
            "maildomain.com"
        ],
        "ip": [
            "1.2.3.4"
        ]
    },
    "vadecloud": {
        "filter_type": "UNKNOWN",
        "site": "VSC000001",
        "spam_level": "UNKNWON",
        "tag": "[VIRUS]"
    }
}

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
@timestamp date Date/time when the event originated.
destination.domain keyword The domain name of the destination.
destination.ip ip IP address of the destination.
email.from.address keyword The sender's email address.
email.local_id keyword Unique identifier given by the source.
email.subject keyword The subject of the email message.
email.to.address keyword Email address of recipient
event.action keyword The action captured by the event.
event.category keyword Event category. The second 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.
vadecloud.filter_type keyword
vadecloud.sandboxed keyword
vadecloud.site keyword
vadecloud.spam_level keyword
vadecloud.tag keyword

For more information on the Intake Format, please find the code of the Parser, Smart Descriptions, and Supported Events here.