diff --git a/rules/cloud/aws_sts_getsessiontoken_abuse.yml b/rules/cloud/aws_sts_getsessiontoken_abuse.yml
deleted file mode 100644
index 682b1d005..000000000
--- a/rules/cloud/aws_sts_getsessiontoken_abuse.yml
+++ /dev/null
@@ -1,27 +0,0 @@
-title: AWS STS GetSessionToken Abuse
-id: b45ab1d2-712f-4f01-a751-df3826969807
-description: Identifies the suspicious use of GetSessionToken. Tokens could be created and used by attackers to move laterally and escalate privileges.
-author: Austin Songer
-status: experimental
-date: 2021/07/24
-references:
-    - https://docs.aws.amazon.com/STS/latest/APIReference/API_GetSessionToken.html
-logsource:
-    service: cloudtrail
-detection:
-    selection_source:
-        - eventSource: sts.amazonaws.com
-    selection_eventname1:
-        - eventName: GetSessionToken
-    selection_usertype:
-        - userIdentity.type: IAMUser
-    condition: all of them
-level: low
-tags:
-  - attack.lateral_movement
-	- attack.privilege_escalation
-	- attack.t1548
-  - attack.t1550
-	- attack.t1550.001
-falsepositives:
-- GetSessionToken may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. GetSessionToken from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.