Security information and event management (SIEM) technology provides foundational support for threat detection. The high costs of SIEMs once made them feasible only for larger enterprise clients, but they have become more reasonable solutions for smaller organizations over time.<\/p>\n
While a properly configured SIEM can provide effective threat protection, misuse of SIEM technology can increase costs and undermine security. To understand if SIEM technology fits your organization\u2019s needs, you should understand what a SIEM is, how to use it, and how to avoid some of its common pitfalls.<\/p>\n
See our in-depth look at the top SIEM tools<\/em><\/a><\/p>\n Gartner first coined the term SIEM in 2005 to combine the technologies of security event management (SEM) and security information management (SIM). SIEM technology was designed to collect, analyze, and store log files generated by endpoints<\/a> (typically PCs). If the SIEM analysis detected malware<\/a> or malicious activity, it could generate alerts for a security engineer or security operations center (SOC)<\/a> to investigate.<\/p>\n Modern SIEM technologies have expanded this original scope in many directions. The log files collected will now typically include data center servers, cloud resources<\/a>, networking equipment, and even devices that fit into the Internet of Things (IoT)<\/a> or operational technology (OT)<\/a> categories.<\/p>\n SIEM tools now also offer features that can automatically respond to threats instead of waiting for a security technician to review the alerts. Advanced SIEM tools also incorporate artificial intelligence (AI)<\/a> and machine learning (ML) algorithms to analyze logs and trends to proactively identify new alerts and new threats.<\/p>\n In an ideal deployment, SIEMs leverage computers to quickly analyze devices; rapidly detect threats; and enable the computers or humans managing security responses to develop or utilize automated security responses, improved investigation resources, or robust reporting capabilities.<\/p>\n SIEM technologies empower an existing security program, so an IT team cannot deploy a SIEM and expect security responses to magically take place.<\/p>\n Even highly automated SIEM tools require intelligent log file collection, proper configuration, and expert review of results. Fortunately, many consultants and outsourcing experts are available to help those without the internal resources for SIEM setup.<\/p>\n However, even for those intending to make use of extensive outsourcing, a basic understanding of the SIEM technology will help to make sure the chosen vendor is doing their job well. The basics apply to all SIEM technology:<\/p>\n For a more thorough overview, check out our SIEM checklist<\/a>.<\/p>\n Our SIEM checklist covers a number of potential issues, but we will highlight the most critical issues here relating to pitfalls that could undermine the most carefully established SIEM deployment.<\/p>\n In deployment, garbage in, garbage out and alert fatigue represent the most critical issues. These issues will undermine powerful AI engines and cause a security team to miss attacks.<\/p>\n Garbage in, garbage out pertains to the quality of the log files. During implementation, IT teams must investigate the devices generating log files and the log files themselves very carefully to verify their quality. If log files are generated from infected endpoints, there is a risk in establishing a corrupted device as a baseline and future alerts are jeopardized.<\/p>\n However, if the correct or sufficient log files are not collected, the SIEM will not have the data necessary to generate alerts or to properly analyze the health of the IT environment. Sending garbage to a SIEM will only result in more garbage in the form of bad analysis.<\/p>\n Alert fatigue develops when alerts are triggered too easily by everyday events in the IT environment. Too many false alarms can make a security team unable to see the real problems lost in the noise. The number of devices, the number of alerts, and the type of issues generating alerts may need to be adjusted to avoid alert fatigue.<\/p>\n Penetration testing<\/a> is one way security teams can reduce unnecessary alerts and check for missing alerts. By intentionally performing activity designed to trigger alerts, security teams and SIEM managers can verify that the most likely attacks will be properly alerted and countered.<\/p>\n Beyond the initial setup, it is important to verify that there are sufficient supporting resources for the SIEM. Alert fatigue may be caused by perfectly reasonable alerts delivered to a short-staffed and overworked security team<\/a>. Reducing alert fatigue can be as simple as right-sizing a security team, so legitimate alerts will not be overlooked by exhausted personnel.<\/p>\n Also read: <\/span>Testing & Evaluating SIEM Systems: A Review of Rapid7 InsightIDR<\/span><\/a><\/p>\n When developing a SIEM strategy, be sure to consider storage needs for log files. Some popular SIEM solutions charge by the amount of data processed and stored by their system, and some data centers may have limited internal storage for log files.<\/p>\n While it may be tempting to cut costs in terms of storage, in the event of an attack, investigators may need an extensive number of logs over an extended period of time to track an attacker\u2019s activities and identify the original entry points. Arbitrary limits on storage for log files could leave an investigation without sufficient information or with increased investigation costs.<\/p>\n Fortunately, modern technology offers many possible solutions for storage. Different SIEM solutions can offer different pricing options, outsourcing can offer discounted rates, and cloud storage resources can be cheap to expand. For those looking to implement or expand a SIEM, be sure to consider future growth, current resources, and SIEM capabilities.<\/p>\n SIEMs hold enormous potential to turbo-charge security<\/a> for organizations of many sizes. However, the SIEM solution needs to be selected in the context of organization needs and resources. Companies need to frankly consider their capabilities to avoid undermining their security teams with too many alerts, bad alerts, and misaligned infrastructure.<\/p>\n Read next: Managed SIEM: A Faster Way to Great Security<\/a><\/p>\n\n\nWhat is a SIEM?<\/h2>\n
How Can You Use a SIEM Tool?<\/h2>\n
\n
Common SIEM Pitfalls and How to Avoid Them<\/h2>\n
Garbage in, garbage out<\/h3>\n
Alert fatigue<\/h3>\n
Insufficient file storage<\/h3>\n
Choose Your SIEM Carefully<\/h2>\n