diff --git a/detections/endpoint/malicious_powershell_executed_as_a_service.yml b/detections/endpoint/malicious_powershell_executed_as_a_service.yml
new file mode 100644
index 0000000000..96cb82c4ee
--- /dev/null
+++ b/detections/endpoint/malicious_powershell_executed_as_a_service.yml
@@ -0,0 +1,47 @@
+name: Malicious Powershell Executed As A Service
+id: 8e204dfd-cae0-4ea8-a61d-e972a1ff2ff8
+version: 1
+date: '2021-04-07'
+author: Ryan Becwar
+type: batch
+datamodel:
+- Endpoint
+description: This detection is to identify the abuse the Windows SC.exe to
+ execute malicious commands or payloads via PowerShell. 
+search: ' `wineventlog_system` EventCode=7045 Service_File_Name IN ("*powershell.exe*", "*-nop*", "*hid*") 
+| stats count min(_time) as firstTime max(_time)
+  as lastTime by EventCode Service_File_Name Service_Name Service_Start_Type Service_Type Service_Account user
+| `security_content_ctime(firstTime)` 
+| `security_content_ctime(lastTime)`
+| `malicious_powershell_executed_as_a_service_filter`'
+how_to_implement: To successfully implement this search, you need to be ingesting Windows System
+  logs with the Service name, Service File Name Service Start type, and Service Type
+  from your endpoints.
+known_false_positives: Creating a hidden powershell service is rare and could key off of those instances.
+references:
+- https://www.fireeye.com/content/dam/fireeye-www/blog/pdfs/dosfuscation-report.pdf
+- http://az4n6.blogspot.com/2017/
+- https://www.danielbohannon.com/blog-1/2017/3/12/powershell-execution-argument-obfuscation-how-it-can-make-detection-easier
+tags:
+  analytic_story:
+  - Malicious Powershell
+  dataset:
+  - https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1569.002/atomic_red_team/windows-system.log
+  kill_chain_phases:
+  - Privilege Escalation
+  mitre_attack_id:
+  - T1569.002
+  product:
+  - Splunk Enterprise
+  - Splunk Enterprise Security
+  - Splunk Cloud
+  required_fields:
+  - EventCode
+  - Service_File_Name
+  - Service_Type
+  - _time
+  - Service_Name
+  - Service_Start_Type
+  - Service_Account 
+  - user
+  security_domain: endpoint
diff --git a/tests/endpoint/malicious_powershell_executed_as_a_service.test.yml b/tests/endpoint/malicious_powershell_executed_as_a_service.test.yml
new file mode 100644
index 0000000000..b2d93a1a8f
--- /dev/null
+++ b/tests/endpoint/malicious_powershell_executed_as_a_service.test.yml
@@ -0,0 +1,12 @@
+name: Malicious Powershell Executed As A Service Unit Test
+tests:
+- name: Malicious Powershell Executed As A Service
+  file: endpoint/malicious_powershell_executed_as_a_service.yml
+  pass_condition: '| stats count | where count > 0'
+  earliest_time: '-24h'
+  latest_time: 'now'
+  attack_data:
+  - file_name: windows-system.log
+    data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1569.002/atomic_red_team/windows-system.log
+    source: WinEventLog:System
+    sourcetype: WinEventLog