Advanced Search Keywords:

opsec:low - Show techniques with low noise level (stealthy)
phase:"initial access" - Filter by phase (use quotes for spaces)
category:lateral - Filter by category
platform:windows - Filter by platform
tag:credential - Find items with specific tag in results
external:true - Show only external techniques

Combining Keywords:

tag:stealth phase:"initial access" password

Searches for "password" within low-noise techniques in the initial access phase

RTT· red team

RTT · red team

Advanced Search Keywords:

opsec:low - Show techniques with low noise level (stealthy)
phase:"initial access" - Filter by phase (use quotes for spaces)
category:lateral - Filter by category
platform:windows - Filter by platform
tag:credential - Find items with specific tag in results
external:true - Show only external techniques

Combining Keywords:

tag:stealth phase:"initial access" password

Searches for "password" within low-noise techniques in the initial access phase

Search techniques, tools, commands…⌘K

No scenario

No scenario · all techniques in scope

IdleStatus

0Scenarios

Advanced Search Keywords:

opsec:low - Show techniques with low noise level (stealthy)
phase:"initial access" - Filter by phase (use quotes for spaces)
category:lateral - Filter by category
platform:windows - Filter by platform
tag:credential - Find items with specific tag in results
external:true - Show only external techniques

Combining Keywords:

tag:stealth phase:"initial access" password

Searches for "password" within low-noise techniques in the initial access phase

Back to Techniques

Techniques›Persistence›SQL Stored Procedures

Persistence

SQL Stored Procedures

T1505.001 · MITRE ATT&CK

Adversaries may abuse SQL Server stored procedures to establish persistence. This T1505.001 example enables xp_cmdshell, creates a procedure that calls it, and invokes that procedure. SQL stored procedures may also be invoked by defined application events such as startup or restart, but this example does not configure automatic startup execution and does not demonstrate lateral movement.

ArtifactsRESTRICTED_ACCESS_BLUR_MARKER

Steps1

CategoryDatabase Client Abuse

SourceExternal

Discuss in Advisor

Walkthrough

Step 1

RESTRICTED_ACCESS_BLUR_MARKER

RESTRICTED_ACCESS_BLUR_MARKER

Requirements: none specified (operational prerequisites may still apply)

Check before starting: RESTRICTED_ACCESS_BLUR_MARKER

Coverage Gap: No catalog tool command currently produces this step's declared outcomes.

Detection signal

Detection 01

RESTRICTED_ACCESS_BLUR_MARKER

Mitigations

Mitigation 01

RESTRICTED_ACCESS_BLUR_MARKER

OPSEC notes

RESTRICTED_ACCESS_BLUR_MARKER

Related techniques

Related Entities (2)

RESTRICTED_ACCESS_BLUR_MARKER (RESTRICTED_ACCESS_BLUR_MARKER)

Use Valid Accounts (Initial Access)

References

Extended details

RESTRICTED_ACCESS_BLUR_MARKER