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

Fixed parsing errors on how_to_implement

Browse Source
This commit is contained in:
Kelby Shelton
2023-04-13 12:57:48 -05:00
parent f42f8d28a7
commit e0b6575f57
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
playbooks/Mission_Control_Identifier_Reputation_Analysis.yml
+1 -1
View File
@@ -6,7 +6,7 @@ author: Kelby Shelton, Splunk
type: Investigation
description: Launches "reputation analysis" input playbooks, adds reputation reports, and then concludes the Response Tasks where this playbook appears.
playbook: Mission_Control_Identifier_Reputation_Analysis
how_to_implement: - Requires Input Playbooks with the supported inputs and outputs.\n- Task update function requires that this playbook be present in a Mission Control Response Task.\n- Playbook inputs can be modified to include or omit variables from the incident.\n- Markdown merge function must be modified when adding or removing input playbooks.
how_to_implement: "- Requires Input Playbooks with the supported inputs and outputs.\n- Task update function requires that this playbook be present in a Mission Control Response Task.\n- Playbook inputs can be modified to include or omit variables from the incident.\n- Markdown merge function must be modified when adding or removing input playbooks."
references: []
app_list:
- Mission Control
playbooks/Mission_Control_Related_Tickets_Search.yml
+1 -1
View File
@@ -6,7 +6,7 @@ author: Kelby Shelton, Splunk
type: Investigation
description: Launches "related tickets" input playbooks, creates events, and then concludes the Response Tasks where this playbook appears.
playbook: Mission_Control_Related_Tickets_Search
how_to_implement: - Requires Input Playbooks with the supported inputs and outputs.\n- Task update function requires that this playbook be present in a Mission Control Response Task.\n- Playbook inputs can be modified to include or omit variables from the incident.\n- Markdown merge function must be modified when adding or removing input playbooks.
how_to_implement: "- Requires Input Playbooks with the supported inputs and outputs.\n- Task update function requires that this playbook be present in a Mission Control Response Task.\n- Playbook inputs can be modified to include or omit variables from the incident.\n- Markdown merge function must be modified when adding or removing input playbooks."
references: []
app_list:
- Mission Control
playbooks/PhishTank_URL_Reputation_Analysis.yml
+1 -1
View File
@@ -6,7 +6,7 @@ author: Kelby Shelton, Splunk
type: Investigation
description: "Accepts a URL and does reputation analysis on the objects. Generates a global report and a per observable sub-report and normalized score. The score can be customized as desired."
playbook: PhishTank_URL_Reputation_Analysis
how_to_implement: This input playbook requires the PhishTank connector to be configured. It is designed to work in conjunction with the Dynamic Identifier Reputation Analysis playbook or other playbooks in the same style.
how_to_implement: "This input playbook requires the PhishTank connector to be configured. It is designed to work in conjunction with the Dynamic Identifier Reputation Analysis playbook or other playbooks in the same style."
references:
- https://d3fend.mitre.org/technique/d3f:IdentifierReputationAnalysis/
app_list: