Skip to content

Commit e6b5e1b

Browse files
jpipkin1kimsauce
andauthored
Update docs/cloud-soar/introduction.md
Co-authored-by: Kim (Sumo Logic) <[email protected]>
1 parent e21acb2 commit e6b5e1b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/cloud-soar/introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -657,7 +657,7 @@ Automation rules define what happens when data is received from a source. These
657657

658658
Automation rules can automatically pull information from sources. They can also execute playbooks based on certain criteria. For example, you might want to pull Insights from Cloud SIEM once an hour and create incidents from them. Then, you could configure a rule that runs a playbook based on the tags in the incident. This way, the entire incident response cycle is automated: Cloud SIEM identifies a threat, and playbooks in Cloud SOAR are automatically deployed to contain and eradicate the threats, restore systems, and email a final report for an analyst to review.
659659

660-
Let's create a custom automation rule. This rule will pull information from Cloud SIEM every five hours.
660+
Let's create a custom automation rule. This rule will pull information from Cloud SIEM every 5 hours.
661661

662662
1. [**Classic UI**](/docs/cloud-soar/overview#classic-ui). Click the gear icon <img src={useBaseUrl('img/cloud-soar/cloud-soar-settings-icon.png')} alt="Settings menu icon" style={{border: '1px solid gray'}} width="25"/> in the top right, select **Automation**, and then select **Rules** in the left nav bar. <br/>[**New UI**](/docs/cloud-soar/overview#new-ui). In the main Sumo Logic menu select **Automation > Rules**.
663663
1. Near the top, click the **+** icon to create a new rule.

0 commit comments

Comments
 (0)