Cyber Triage

Allows you to conduct a mini-forensic investigation on an endpoint. It pushes a collection tool to the remote endpoint, collects volatile and file system data, and analyzes the data.

Endpoint · Cyber Triage

Details

ID	`Cyber Triage`
Provider	Basis Technology
Category	Endpoint
From Version	5.0.0
Docker Image	`demisto/python3:3.12.13.10116658`
Supported Modules	Agentix XSIAM

README

Overview

Use the Cyber Triage integration to collect and analyze endpoint data

This integration requires Team version of Cyber Triage (not the Standalone desktop version).

This integration was integrated and tested with Cyber Triage v2.4.0.

Configure Cyber Triage on Cortex XSOAR

Navigate to Settings > Integrations > Servers & Services.
Search for Cyber Triage.
Click Add instance to create and configure a new integration instance.
- Name: a textual name for the integration instance.
- Hostname of Cyber Triage server (e.g. 192.168.1.2) : the ip or hostname where the Cyber Triage server is setup.
- REST Port : REST port for Cyber Triage server. 9443 is the default port and currently cannot be changed in Cyber Triage.
- API Key : can be retrieved from the Cyber Triage server by going to Options -> Deployment Mode -> REST API Key.
- Username : the username and password of a Windows account with administrative privileges on all endpoints that need to be investigated.
- Use proxy : select if you have a proxy setup in your environment and need to use it to reach the Cyber Triage server.
Click Test to validate the URLs, token, and connection.

Commands

You can execute these commands from the Cortex XSOAR 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.

Initiate a collection on an endpoint: ct-triage-endpoint

Initiate a collection on an endpoint

Initiates a Cyber Triage collection on an endpoint.

Base Command

ct-triage-endpoint

Input

Argument Name	Description	Required
endpoint	IP or hostname of a Windows endpoint	Required
full_scan	Scan the entire file system for suspicious files	Optional
malware_hash_upload	Send MD5 hashes to an external malware analysis service	Optional
malware_file_upload	Send unknown files to an external malware analysis service. Hash upload must be enabled to execute file uploads.	Optional

Context Output

Path	Type	Description
CyberTriage.SessionId	string	The session ID for the newly created session
Endpoint.IPAddress	string	The endpoint IP address that Cyber Triage investigated
Endpoint.Hostname	string	The endpoint hostname that Cyber Triage investigated

Command Example

!ct-triage-endpoint endpoint=ct-win10-01 full_scan=no

Context Example

CyberTriage.SessionID: ct-win10-01|1538074422288
CyberTriage.Hostname: ct-win10-01

Human Readable Output

A collection has been scheduled for ct-win10-01

Configuration parameters

server — Hostname of Cyber Triage server (e.g. 192.168.1.2) (required)
rest_port — REST Port (required)
api_key —
credentials — Username (required)
use_proxy — Use proxy

Commands (1)

ct-triage-endpoint
initiates a cyber triage collection on an endpoint.

Source

CyberTriage.py CyberTriage_test.py CyberTriage.yml CyberTriage_description.md

Download History Raw

from inspect import isclass
from unittest.mock import MagicMock

import pytest
from CyberTriage import IS_2XX, CyberTriageClient

SERVER_URL = "https://test_url.com"


@pytest.fixture()
def client():
    client = CyberTriageClient(
        server=SERVER_URL,
        rest_port="test",
        api_key="test",
        user="test",
        password="test",
        verify_server_cert=True,
        ok_codes=(200,),
    )
    return client


def test_test_connection_command(client: CyberTriageClient):
    """
    Args:
        client (pytest.fixture): CyberTriageClient instance whose methods will be mocked

    Given:
        - a CyberTriage client
    Then:
        - ensure triage_endpoint is called once
    """
    from CyberTriage import test_connection_command

    mock1 = MagicMock()
    client.test_connection = mock1
    test_connection_command(client)
    client.test_connection.assert_called_once()


def test_triage_endpoint_command(client: CyberTriageClient):
    """
    Args:
        client (pytest.fixture): CyberTriageClient instance whose methods will be mocked

    Given:
        - a CyberTriage client
    When:
        - the command arguments are as in the fake data below
    Then:
        - ensure triage_endpoint is called once with the expected arguments
    """
    from CyberTriage import triage_endpoint_command

    args = {"malware_hash_upload": "yes", "malware_file_upload": "no", "endpoint": "made-up-endpoint", "incident_name": "MADEUP"}
    mock2 = MagicMock()
    client.triage_endpoint = mock2
    triage_endpoint_command(client, args)
    client.triage_endpoint.assert_called_once_with(True, False, "made-up-endpoint", "", "MADEUP")


is_2xx_test_data = [
    (200, True),
    (201, True),
    (234, True),
    (288, True),
    (300, False),
    (391, False),
    (101, False),
    (404, False),
    (505, False),
    (606, False),
    (-200, False),
    (-245, False),
    ("200", TypeError),
    ("help", TypeError),
]


@pytest.mark.parametrize("argument,expected", is_2xx_test_data)
def test_IS_2XX(argument, expected):
    if isclass(expected) and issubclass(expected, Exception):
        with pytest.raises(expected_exception=expected):
            IS_2XX(argument)
    else:
        assert IS_2XX(argument) == expected