USTA Account Takeover Prevention

Collects compromised credentials sourced from stealer malware attacks, helping organizations identify potential account takeovers and enhance their security posture. Provided by PRODAFT.

Data Enrichment & Threat Intelligence · USTAv4 Cyber Threat Intelligence Platform

Details

IDUSTA Account Takeover Prevention
ProviderPRODAFT
CategoryData Enrichment & Threat Intelligence
From Version6.10.0
Docker Imagedemisto/python3:3.12.13.10116658
Supported ModulesAgentix XSIAM

README

USTAv4 Account Takeover Prevention is designed to collect compromised credentials sourced from stealer malware attacks, helping organizations identify potential account takeovers and enhance their security posture. Provided by PRODAFT.
This integration was integrated and tested with version 4.1.0 of USTAv4 Account Takeover Prevention.

Configure USTAv4 Account Takeover Prevention in Cortex

  1. Navigate to Settings > Integrations > Servers & Services.
  2. Search for USTAv4 Account Takeover Prevention.
  3. Click Add instance to create and configure a new integration instance.

    Parameter Description Required
    Your server URL   True
    API Key The API Key to use for connection True
    Fetch incidents by status   False
    Trust any certificate (not secure)   False
    Use system proxy settings   False
    Fetch incidents   False
    First Fetch Time The time range to consider for the initial data fetch. Warning: Fetching a large time range may cause performance issues! True
  4. 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.

usta-atp-search-username


Search for compromised credentials by username

Base Command

usta-atp-search-username

Input

Argument Name Description Required
username Username to search. Required
page_size Number of result that should appear on each page. Optional
page 1-indexed page number to get a particular page of results. Optional

Context Output

Path Type Description
USTA.AccountTakeoverPrevention.id Number The ID of the alert
USTA.AccountTakeoverPrevention.username String The username of the compromised credential
USTA.AccountTakeoverPrevention.password String The password of the compromised credential
USTA.AccountTakeoverPrevention.url String The URL of the compromised credential
USTA.AccountTakeoverPrevention.is_corporate Boolean Whether the compromised credential is corporate
USTA.AccountTakeoverPrevention.created String The creation date of the compromised credential
USTA.AccountTakeoverPrevention.victim_detail.ip String The IP address of the victim
USTA.AccountTakeoverPrevention.victim_detail.country String The country of the victim
USTA.AccountTakeoverPrevention.victim_detail.phone_number String The phone number of the victim
USTA.AccountTakeoverPrevention.victim_detail.computer_name String The computer name of the victim computer
USTA.AccountTakeoverPrevention.victim_detail.victim_os String The OS of the victim computer
USTA.AccountTakeoverPrevention.victim_detail.language String The language of the victim computer
USTA.AccountTakeoverPrevention.victim_detail.memory String The memory of the victim computer
USTA.AccountTakeoverPrevention.victim_detail.cpu String The CPU of the victim computer
USTA.AccountTakeoverPrevention.victim_detail.gpu String The GPU of the victim computer
USTA.AccountTakeoverPrevention.victim_detail.malware String The family of the malware that infected the victim computer
USTA.AccountTakeoverPrevention.victim_detail.infection_date String The infection date of the victim computer

Command Example

!usta-atp-search-username username=user123456 page_size=1 page=1

Context Example

{
    "USTA" : {
        "AccountTakeoverPrevention": [
            {
                "id": 1234567,
                "status": "open",
                "username": "user123456",
                "password": "******",
                
                "url": "https://example.com/login",
                "is_corporate": "False",                
                "created": "2024-11-18T00:00:00.000000Z",
                "victim_detail": {
                    "username": "anonymous",
                    "ip": "0.0.0.0",
                    "country": "Unknown",
                    "phone_number": "N/A",
                    "computer_name": "DESKTOP-XXXXX",
                    "victim_os": "OS x64",
                    "language": "N/A",
                    "memory": "XXXX MB",
                    "cpu": "Generic CPU",
                    "gpu": "Generic GPU",
                    "malware": "Unknown",
                    "infection_date": "N/A",
                    "created": "2024-11-18T00:00:00.000000Z"
                }
            }
        ]
    }
}

Configuration parameters

  • url — Your server URL (required)
  • api_key — API Key (required)
  • status — Fetch incidents by status
  • max_fetch — Maximum number of alerts per fetch
  • insecure — Trust any certificate (not secure)
  • proxy — Use system proxy settings
  • isFetch — Fetch incidents
  • incidentFetchInterval — Incidents Fetch Interval
  • incidentType — Incident type
  • first_fetch — First Fetch Time (required)

Commands (1)

  • usta-atp-search-username

    Search for compromised credentials by username.

## USTAv4 Account Takeover Prevention

To obtain your USTAv4 API Token:
1. Go to **USTAv4** > **Company Settings** > **My Company** > **Integrations** > **API Keys**.

Please get in touch with USTAv4 operators if you don't have access to the API Keys section.

### How to Configure The Instance
- **Name** : Name of the instance. Feel free to choose any name you would.
- **Your Server URL**: Use default URL unless you specifically tell otherwise.
- **API Key**: Follow above instructions and get your API Key.
- **Fetch incidents by status**: Use default unless you want to specifically fetch by status.
- **First Fetch Time**: The time range to consider for the initial data fetch. Warning: Fetching a large time range may cause performance issues!