top of page

New concepts and design ideas

Public·46 Engineers
Jordan Murphy
Jordan Murphy

SIEM Still Creates Complexity And Administration Challenges

The challenges of SIEM, including multi-cloud compatibility, data complexity, and scalability, as well as the learning curve for analyzing cloud data through a SIEM, simply cannot be ignored. These are tough challenges that few SIEMs can overcome, especially when considering the velocity of cloud data and how dynamic cloud instances are created and destroyed very quickly. While many SIEMs claim to support multi-cloud environments, when put to the test, they often fall short of expectations.

SIEM Still Creates Complexity and Administration Challenges


With real-time threat detection, comprehensive event reporting and retention, and context to cut through the noise, the benefits of SIEM solutions are significant. However, their complexity and staffing requirements made these benefits too frustrating and elusive for many. The keys to overcoming the challenges are choosing the right SIEM solution for your organization and engaging a knowledgeable technology partner to help you implement and manage it.

Cerium Networks partners with Blumira to deliver cost-effective, automated SIEM solutions that provide actionable threat detection & response. By providing insights into cybersecurity risks, Blumira helps organizations efficiently and effectively reduce their overall cyberattack surface. We recognize the challenges legacy SIEMs can pose and have some innovative approaches to help our customers realize the benefits of a SIEM solution without the complexity.

When asked to identify their top challenges, CIOs often rank a cybersecurity skills gap highly. One of the big challenges pertaining specifically to SIEM platforms is the complexity of creating query strings. Security analysts must write a query string in order to use their SIEM to answer a specific question.

The high volume of individual tools creates complex security environments that diminish efficiency and introduces challenges to modernizing security operations. By consolidating multiple security tools under one Security Intelligence umbrella, Sumo Logic makes it easier to manage these challenges.

In our first two contributions, we presented the overall structure for a SIEM/SOC project and derived best practices for building the technical infrastructure of a SIEM. In this article, we introduce you to the complexity of use case development and its challenges, and propose some best practices.

The latest Gartner Hype Cycle for SecOps is a great reflection of the complexity and demands security teams are dealing with. In laying out a maturation timeline of all technologies available to support security operations, it provides a menu of technologies intended to help SOCs stay on top of current threats, and equip themselves to deal with emerging (and future) challenges.

Today, mostIT administrators are dealing with a wide range of legacy equipment, physicaland virtual servers, applications, and cloud-based resources. The logsgenerated by these systems and applications help administrators ensure theirdistributed environment maintains high availability. These logs are alsohelpful for meeting numerous security and compliance requirements. Asorganizations grow, however, their IT environments become more complex. Thiscreates many challenges in log management and analysis. You cannot SSH intoindividual servers and monitor logs individually when you have to monitorhundreds of log files. Managing a massive volume of logs with traditionalself-managed tools and processes can get hectic and costly. This is where logaggregator tools offer a solution.

Our unified data resilience platform solves the data protection and business continuity challenges of any organization, regardless of size and complexity. Manage and protect critical business data across systems and applications, on-premises or in the cloud.

Monitoring system logs has grown more prevalent as complex cyber-attacks force compliance and regulatory mechanisms to mandate logging security controls within a Risk Management Framework. Logging levels of a system started with the primary function of troubleshooting system errors or debugging code compiled and run. As operating systems and networks have increased in complexity, so has the event and log generation on these systems. In comparison, the logging of system, security, and application logs is not the only way to perform incident response. They do offer the capability to trace the activities of nearly any system or user-related movement throughout a given period. From the late 1970s, there was a formation of working groups to help establish the criteria for the management of auditing and monitoring programs and what and how system logs can be used for insider threat, incident response, and troubleshooting. This also established a base discussion for many of the concepts still used in modern cybersecurity. See, Basis for Audit and Evaluation of Computer Security from National Institute of Standards and Technology (NIST) Special Publication 500-19 published in 1977.[3]