T1136 IBM QRadar · QRadar

Detect Create Account in IBM QRadar

Adversaries may create an account to maintain access to victim systems. With sufficient privilege, creating accounts establishes secondary credentialed access that does not require persistent remote access tools. Accounts may be created on local systems, within a domain, or in cloud tenants. Threat actors including Indrik Spider (WastedLocker), LockBit 2.0, Scattered Spider, and Salt Typhoon have all used account creation as a persistence mechanism. In cloud environments, attackers may create accounts with access limited to specific services to reduce detection likelihood.

MITRE ATT&CK

Tactic
Persistence
Technique
T1136 Create Account
Canonical reference
https://attack.mitre.org/techniques/T1136/

QRadar Detection Query

IBM QRadar (QRadar)
sql
SELECT
  DATEFORMAT(devicetime, 'yyyy-MM-dd HH:mm:ss') AS event_time,
  sourceip,
  destinationip,
  username,
  QIDNAME(qid) AS event_name,
  CATEGORYNAME(category) AS category_name,
  "AccountName" AS new_account,
  LOGSOURCENAME(logsourceid) AS log_source,
  CASE
    WHEN HOUR(devicetime) < 7 OR HOUR(devicetime) > 19 THEN 1
    ELSE 0
  END AS off_hours_flag
FROM events
WHERE
  (
    -- Windows Security Event 4720: User Account Created
    (LOGSOURCETYPEID(logsourceid) = 12 AND qid = 4720)
    OR
    -- Sysmon Process Create (Event 1) matching account creation commands
    (
      LOGSOURCETYPEID(logsourceid) = 12 AND qid = 1 AND
      (
        ("CommandLine" ILIKE '%net user%/add%' OR "CommandLine" ILIKE '%net1 user%/add%') OR
        ("CommandLine" ILIKE '%wmic useraccount create%') OR
        ("CommandLine" ILIKE '%New-LocalUser%') OR
        ("Image" ILIKE '%\\useradd' OR "Image" ILIKE '%\\adduser')
      )
    )
  )
  AND LOGSOURCEGROUPNAME(logsourceid) != 'Excluded Sources'
LAST 24 HOURS
ORDER BY devicetime DESC
high severity medium confidence

AQL query detecting account creation via Windows Security Event 4720 and process-based creation (net.exe, wmic, PowerShell, Linux useradd) sourced from Windows and Sysmon log sources in QRadar. Flags off-hours activity as a risk multiplier.

Data Sources

IBM QRadar Windows Security log source (DSM)Sysmon operational logs via Windows Log SourceLinux OS log source

Required Tables

events

False Positives & Tuning

  • IT helpdesk provisioning accounts for new hires via standard tooling
  • Software installers creating local service accounts (e.g., database engines, monitoring agents)
  • Automated provisioning pipelines using net.exe or PowerShell during business hours
Download portable Sigma rule (.yml)

Other platforms for T1136


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Create Local User Account via net.exe

    Expected signal: Security Event 4720: 'A user account was created' with TargetUserName=df00tech-testacct, SubjectUserName=<running user>. Sysmon Event ID 1: Process Create with Image=net.exe (or net1.exe), CommandLine='net user df00tech-testacct P@ssw0rd123! /add'. Security Event 4722 (account enabled) may follow immediately.

  2. Test 2Create Local User via WMIC (Indrik Spider TTP)

    Expected signal: Sysmon Event ID 1: Process Create with Image=wmic.exe, CommandLine containing 'useraccount'. Followed by net.exe process create. Security Event 4720 generated by the net user /add call. Parent process chain visible in Sysmon logs.

  3. Test 3Create Local User via PowerShell New-LocalUser

    Expected signal: Sysmon Event ID 1: Process Create with Image=powershell.exe, CommandLine containing 'New-LocalUser'. Security Event 4720: new account df00tech-pstest created, SubjectUserName shows running user. PowerShell ScriptBlock Log Event ID 4104 will show the full New-LocalUser command with parameters.

  4. Test 4Linux Account Creation via useradd

    Expected signal: Syslog / /var/log/auth.log: 'useradd: new user: name=df00tech-linuxtest, UID=<uid>, GID=<gid>'. If auditd is configured with -a always,exit -F arch=b64 -S execve rules: audit log entry for useradd execution with full command line. If Sysmon for Linux is deployed: process creation event for useradd.

Unlock Pro Content

Get the full detection package for T1136 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections