Skip to content

Vade for M365

Overview

Vade for M365 offers AI-based protection against dynamic, email-borne cyberattacks targeting Microsoft 365. It improves user experience and catches 10x more advanced threats than Microsoft.

In this documenation we will explain how to collect and send Vade for M365 logs to SEKOIA.IO.

Benefit from SEKOIA.IO built-in rules and upgrade Vade M365 with the following detection capabilities out-of-the-box.

SEKOIA.IO x Vade M365 on ATT&CK Navigator

Malware Detected By Vade For M365

Vade Secure product Vade for M365 has detected a malware contained in the message.

  • Effort: master
Phishing Detected By Vade For M365

Vade Secure product Vade for M365 has detected a phishing attempt.

  • 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
Scam Detected By Vade For M365

Vade Secure product Vade for M365, has detected a scam e-mail.

  • Effort: master
Spam Detected By Vade For M365

Vade Secure product Vade for M365, has detected a spam e-mail.

  • Effort: master
Spearphishing (CEO Fraud) Detected By Vade For M365

Vade Secure product Vade for M365 has detected a spearphishing attempt with CEO fraud thematic. Impersonation of CEO or senior management members requesting urgent money transfer, usually on an unknown RIB.

  • Effort: master
Spearphishing (Gift Cards Fraud) Detected By Vade For M365

Vade Secure product Vade for M365 has detected a spear-phishing attempt with gift-cards fraud thematic. Executive impersonation requesting a money transfer to set up gift-cards for employees. Confidentiality and discretion are usually implied.

  • Effort: master
Spearphishing (Initial Contact Fraud) Detected By Vade For M365

Vade Secure product Vade for M365 has detected a spearphishing attempt with initial contact fraud thematic. Do not contains any malicious content or specific actions other than a request to reply to the email. “Are you available?”. The main goal is to incite a reply that could register the sending address as a known and legitimate address.

  • Effort: master
Spearphishing (Lawyer Fraud) Detected By Vade For M365

Vade Secure product Vade for M365 has detected a spearphishing attempt with lawyer fraud thematic. Impersonation of lawyers and lawyers' firms. The main goal is to make sure the victims will not raise awareness around them. Confidentiality restrictions are implied.

  • Effort: master
Spearphishing (W2 Fraud) Detected By Vade For M365

Vade Secure product Vade for M365 has detected a spearphishing attempt with W2 fraud thematic. Executive or HR impersonation phishing for social security numbers or tax identification numbers. Collected data are generally used for identity theft schemes.

  • Effort: master

Event Categories

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

Data Source Description
Anti-virus Vade performs behavioral-Based Anti-Malware
Email gateway Vade for M365 blocks attacks from the first email thanks to machine learning models that perform real-time behavioral analysis of the entire email, including any URLs and attachments.

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

Name Values
Kind event
Category email
Type change, deletion, denied, info

Event Samples

Find below few samples of events and how they are normalized by SEKOIA.IO.

{
    "event": {
        "outcome": "success",
        "category": "email",
        "kind": "event",
        "type": "info",
        "action": "nothing"
    },
    "message": " {\"id\": \"zekfnzejnf576rge8768\", \"date\": \"2022-02-10T13:00:05.454Z\", \"sender_ip\": \"192.168.1.1\", \"from\": \"test@sekoia.io\", \"from_header\": \"<test@sekoia.io>\", \"to\": \"test@vadesecure.com\", \"to_header\": \"\\\"test@vadesecure.com\\\" <test@vadesecure.com>\", \"subject\": \"Lorem ipsum dolor\", \"message_id\": \"<01de2305-f75b-49db-8c61-f661bd498e63.protection.outlook.com>\", \"urls\": [{\"url\": \"https://sekoia.io\"}], \"attachments\": [{\"id\": \"ca9ph2ostndl7735uht0\", \"filename\": \"image001.png\", \"extension\": \"png\", \"size\": 12894},{\"id\": \"ca9okt0kn1e8usdf633g\", \"filename\": \"archive.zip\", \"extension\": \"zip\", \"size\": 10558}], \"status\": \"LEGIT\", \"substatus\": \"\", \"remediation_type\": \"none\", \"remediation_ids\": [], \"action\": \"NOTHING\", \"folder\": \"\", \"size\": 113475, \"current_events\": [], \"whitelisted\": false} ",
    "sekoiaio": {
        "intake": {
            "parsing_status": "success"
        }
    },
    "email": {
        "from": {
            "address": "test@sekoia.io"
        },
        "local_id": "zekfnzejnf576rge8768",
        "message_id": "<01de2305-f75b-49db-8c61-f661bd498e63.protection.outlook.com>",
        "subject": "Lorem ipsum dolor",
        "to": {
            "address": "test@vadesecure.com"
        },
        "attachments": [
            {
                "file": {
                    "extension": "png",
                    "name": "image001.png",
                    "size": 12894
                }
            },
            {
                "file": {
                    "extension": "zip",
                    "name": "archive.zip",
                    "size": 10558
                }
            }
        ]
    },
    "source": {
        "address": "192.168.1.1",
        "ip": "192.168.1.1"
    },
    "related": {
        "ip": [
            "192.168.1.1"
        ]
    },
    "vadesecure": {
        "from_header": "<test@sekoia.io>",
        "status": "LEGIT",
        "to_header": "\"test@vadesecure.com\" <test@vadesecure.com>",
        "attachments": [
            {
                "filename": "image001.png",
                "id": "ca9ph2ostndl7735uht0"
            },
            {
                "filename": "archive.zip",
                "id": "ca9okt0kn1e8usdf633g"
            }
        ]
    }
}
{
    "event": {
        "outcome": "success",
        "category": "email",
        "kind": "event",
        "type": "info",
        "reason": "The email contains a URL that is flagged as Phishing by Vade Secure Global Threat Intelligence"
    },
    "vadesecure": {
        "status": "PHISHING",
        "campaign": {
            "actions": [
                {
                    "action": "MOVE"
                }
            ],
            "id": "zekfnzejnf576rge8768",
            "nb_messages_remediated": 1,
            "nb_messages_remediated_read": 0,
            "nb_messages_remediated_unread": 1
        }
    }
}
{
    "event": {
        "outcome": "success",
        "category": "email",
        "kind": "event",
        "type": "info"
    },
    "vadesecure": {
        "campaign": {
            "actions": [
                {
                    "action": "DELETE"
                },
                {
                    "action": "FAILED"
                }
            ],
            "id": "zekfnzejnf576rge8768",
            "nb_messages_remediated": 76,
            "nb_messages_remediated_read": 0,
            "nb_messages_remediated_unread": 76
        }
    }
}

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
email.attachments array email.attachments
email.from.address keyword email.from.address
email.local_id keyword email.local_id
email.message_id keyword email.message_id
email.subject keyword email.subject
email.to.address keyword email.to.address
event.action keyword The action captured by the event.
event.category keyword Event category. The second categorization field in the hierarchy.
event.kind keyword The kind of the event. The highest 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.
source.ip ip IP address of the source.
vadesecure.attachments array vadesecure.to_header
vadesecure.campaign.actions array The actions carried out for the remediation campaign.
vadesecure.campaign.id keyword The ID of the campaign
vadesecure.campaign.nb_messages_remediated long The total number of messages involved in the remediation.
vadesecure.campaign.nb_messages_remediated_read long The number of total read messages involved in the remediation.
vadesecure.campaign.nb_messages_remediated_unread long The number of total unread messages involved in the remediation.
vadesecure.folder keyword vadesecure.folder
vadesecure.from_header keyword vadesecure.from_header
vadesecure.status keyword vadesecure.status
vadesecure.substatus keyword vadesecure.substatus
vadesecure.to_header keyword vadesecure.to_header

Configure

First you need to reach the Playbooks page in order to initiate your playbook using the dedicated button.

You can directly choose the Get M365 Email Events trigger if you are creating a playbook from scratch otherwise you will have to find it within the Actions library panel under the Vade secure menu to drag and drop the trigger on the graph.

To start configuring the selected trigger, you'll need to bring Vade's documentation which can be found here. This documentation will allow you to get the following information: your client_id and your client_secret. You can also get the api_host and oauth2_authorization_url, if necessary.

Then you just have to configure the trigger itself by filling its name, by setting its frequency in seconds and by adding your 365 tenant identifier (tenant_id)

Lastly, you must add the Sekoia's action Push Events to intake to the graph and configure it using :

  • the api_key generated within the user center
  • the base_url
  • the events_path to push on Intake (your logs, you will probably fill it with {{ node.0['emails_path'] }})
  • the intake_key of the intake you have previously created (documentation can be found here)