THANK YOU FOR SUBSCRIBING
Enterprise Security Magazine | Monday, May 31, 2021
Building and identifying the required use cases assist in separating false positives from real ones. It also implies taking steps in response to recent or past activity that may be part of a current or potential threat.
FREMONT, CA: Security analysts and threat monitoring objectives benefit from and are assisted by use cases. So, what exactly is a use case? Depending on the need, a use case may be a combination of several technical rules within the SIEM (Security Information and Event Management) tool or a mix of acts from multiple rules. Business threats are translated into SIEM technical guidelines, identifying potential threats and submitting warnings to the SOC (Security Operations Center). Building and identifying the required use cases assist in separating false positives from real ones. It also implies taking steps in response to recent or past activity that may
be part of a current or potential threat. Learn how to build SIEM use cases and how they can support the SOC.
Stay ahead of the industry with exclusive feature stories on the top companies, expert insights and the latest news delivered straight to your inbox. Subscribe today.
There are three main components of all use cases:
• Rules, which detect and send warnings in response to particular events.
• Logic, a term that explains how events or rules can be perceived.
• Action, which defines what action is needed if logic or conditions are met.
How to Build SIEM Use Cases
It is essential to pick a framework for use cases before choosing them.
1. Pick a method for modeling and plotting the use case structure. Upon settling on a framework, start prioritizing and reflecting on market challenges and hazards that might harm the company's finances, reputation, and data.
2. Consider the various forms of attacks. This involves knowing the kinds of market risks that are most likely to affect the business, such as phishing, data loss, and so on. Each form of attack that affects one should be linked to one or more business threats. Thus, one will have a map showing the relationship between market threats and attacks at the end of this stage.
3. Create a new relationship to specify when and how these attacks can be dealt with. Identify the attack forms mentioned and put them in the relevant framework. An external scan assault, for example, would be categorized as reconnaissance/target within the system.
4. Connect both relationships: business risks to attacks and attacks to framework.
Check out: Top CyberSecurity Companies
More in News