Skip to content

Commit 664ca5d

Browse files
jpipkin1kimsauce
andauthored
Update docs/cse/get-started-with-cloud-siem/intro-for-analysts.md
Co-authored-by: Kim (Sumo Logic) <[email protected]>
1 parent 733f1d8 commit 664ca5d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/cse/get-started-with-cloud-siem/intro-for-analysts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -381,7 +381,7 @@ Once a rule is in your system, whether it's a custom rule you created or one cre
381381

382382
If a record matches a rule, an entity is extracted from the record. The entity might be something like an IP address, a user name, a domain name. It tells you who the potential threat is.
383383

384-
<img src={useBaseUrl('img/cse/intro-records-to-signals.png')} alt="Reocrds to signals" width="450"/>
384+
<img src={useBaseUrl('img/cse/intro-records-to-signals.png')} alt="Records to signals" width="450"/>
385385

386386
Once an entity is in Cloud SIEM's system, Cloud SIEM tracks the total severity score of signals associated with each entity as an activity score. Once that activity score gets high enough, usually over 12 by default, then an insight is created.
387387

0 commit comments

Comments
 (0)