diff --git a/detections/cloud/aws_multi_factor_authentication_disabled.yml b/detections/cloud/aws_multi_factor_authentication_disabled.yml
new file mode 100644
index 0000000000..3172088b23
--- /dev/null
+++ b/detections/cloud/aws_multi_factor_authentication_disabled.yml
@@ -0,0 +1,73 @@
+name: AWS Multi-Factor Authentication Disabled
+id: 374832b1-3603-420c-b456-b373e24d34c0
+version: 1
+date: '2022-10-04'
+author: Bhavin Patel, Splunk
+type: TTP
+datamodel:
+- Endpoint
+description: The following analytic identifies an attempt to disable multi-factor authentication for an AWS IAM user. An adversary who has obtained access to an AWS tenant may disable multi-factor authentication as a way to plant a backdoor and maintain persistence using a valid account. This way the attackers can keep persistance in the environment without adding new users.
+search: '`cloudtrail` (eventName= DeleteVirtualMFADevice OR eventName=DeactivateMFADevice) 
+ | stats count min(_time) as firstTime max(_time) as lastTime by src eventName eventSource aws_account_id 
+  userAgent eventID awsRegion user_name userIdentity.arn status | `security_content_ctime(firstTime)`
+  | `security_content_ctime(lastTime)` | `aws_multi_factor_authentication_disabled_filter`'
+how_to_implement: The Splunk AWS Add-on is required to utilize this data. The search requires AWS Cloudtrail logs.
+known_false_positives: AWS Administrators may disable MFA but it is highly unlikely for this event to occur without prior notice to the company
+references:
+- https://attack.mitre.org/techniques/T1621/
+- https://aws.amazon.com/what-is/mfa/
+tags:
+  analytic_story:
+  - AWS Identity and Access Management Account Takeover
+  asset_type: AWS Account
+  cis20:
+  - CIS 3
+  - CIS 5
+  - CIS 16
+  confidence: 80
+  context:
+  - Source:Cloud Data
+  - Outcome:Blocked
+  - Stage:Recon
+  - Other:Brute Force
+  dataset:
+  - https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1621/aws_mfa_disabled/cloudtrail.json
+  impact: 80
+  kill_chain_phases:
+  - Exploitation
+  message: User $user_name$ has disabled Multi-Factor authentication for AWS account $aws_account_id$
+  mitre_attack_id:
+  - T1621
+  nist:
+  - DE.CM
+  observable:
+  - name: aws_account_id
+    type: Other
+    role:
+    - Victim
+  - name: user_name
+    type: User
+    role:
+    - Victim
+  - name: src
+    type: IP Address
+    role:
+    - Attacker
+  product:
+  - Splunk Enterprise
+  - Splunk Enterprise Security
+  - Splunk Cloud
+  required_fields:
+  - src 
+  - eventName 
+  - eventSource 
+  - aws_account_id 
+  - errorCode 
+  - errorMessage
+  - userAgent 
+  - eventID 
+  - awsRegion
+  - user_name 
+  - userIdentity.arn 
+  risk_score: 64
+  security_domain: threat
diff --git a/tests/cloud/aws_multi_factor_authentication_disabled.test.yml b/tests/cloud/aws_multi_factor_authentication_disabled.test.yml
new file mode 100644
index 0000000000..b1704828cf
--- /dev/null
+++ b/tests/cloud/aws_multi_factor_authentication_disabled.test.yml
@@ -0,0 +1,13 @@
+name: AWS Multi-Factor Authentication Disabled Unit Test
+tests:
+- name: AWS Multi-Factor Authentication Disabled
+  file: cloud/aws_multi_factor_authentication_disabled.yml
+  pass_condition: '| stats count | where count > 0'
+  earliest_time: -24h
+  latest_time: now
+  attack_data:
+  - file_name: cloudtrail.json
+    data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1621/aws_mfa_disabled/cloudtrail.json
+    sourcetype: aws:cloudtrail
+    source: aws_cloudtrail
+    update_timestamp: true
\ No newline at end of file