admin/splunk-security_content
1
0
Fork 0
mirror of https://github.com/splunk/security_content synced 2026-06-08 17:32:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Branch was auto-updated.

Browse Source
This commit is contained in:
srv-rr-gh-researchbt
2023-08-07 14:23:37 -07:00
committed by GitHub
parent 8e612f4a36 e8fa5ab05d
commit fcb2f5fc14
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
playbooks/AWS_IAM_Account_Locking.json
+1 -1
View File
@@ -4,7 +4,7 @@
"category": "Account Locking",
"coa": {
"data": {
"description": "Accepts user name that needs to be disabled in AWS IAM Active Directory. Generates an observable output based on the status of account locking or disabling.",
"description": "Accepts user name that needs to be disabled in AWS IAM Active Directory. Disabling an account involves deleting their login profile which will clear the user's password. Generates an observable output based on the status of account locking or disabling.",
"edges": [
{
"id": "port_0_to_port_2",
playbooks/AWS_IAM_Account_Locking.yml
+1 -1
View File
@@ -4,7 +4,7 @@ version: 1
date: '2023-05-08'
author: Teoderick Contreras, Splunk
type: Investigation
description: "Accepts user, to be disabled using AWS IAM connector. This playbook produces a normalized observables output for each user and device."
description: "Accepts user name that needs to be disabled in AWS IAM Active Directory. Disabling an account involves deleting their login profile which will clear the user's password. Generates an observable output based on the status of account locking or disabling."
playbook: AWS_IAM_Account_Locking
how_to_implement: This input playbook requires the AWS IAM connector to be configured.
It is designed to work in conjunction with the Dynamic Attribute Lookup playbook or other playbooks in the same style.