Windows SQL Server Startup Procedure
This detection identifies when a startup procedure is registered or executed in SQL Server. Startup procedures automatically execute when SQL Server starts, making them an attractive persistence mechanism for…
Description
This detection identifies when a startup procedure is registered or executed in SQL Server. Startup procedures automatically execute when SQL Server starts, making them an attractive persistence mechanism for attackers. The detection monitors for suspicious stored procedure names and patterns that may indicate malicious activity, such as attempts to execute operating system commands or gain elevated privileges.
Detection logic
Detection requirements
- Platform
- LinuxWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- windows_event_log_application_17135
Known benign triggers
- Legitimate startup procedures may be used by database administrators for maintenance, monitoring, or application functionality. Common legitimate uses include database maintenance and cleanup jobs, performance monitoring and statistics collection, application initialization procedures, and system health checks. To reduce false positives, organizations should document approved startup procedures, maintain an inventory of expected startup procedures, monitor for changes to startup procedure configurations, and create exceptions for known good procedures.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| attack.mitre.org/techniques/T1505/001/ | 5from 2 sources |
| learn.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-procoption-transact-sql | Only this detection cites it |
| www.netspi.com/blog/technical-blog/network-penetration-testing/sql-server-persistence-part-1-startup-stored-procedures/ | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 7bec7c5c-2262-4adb-ba56-c8028512bc58
- Tagged by the source as
- Hellcat RansomwareSQL Server AbuseWindowsendpointSplunk CloudSplunk EnterpriseSplunk Enterprise Securityendpoint
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1