Are you using a SIEM product? If yes, which one and what has been your experience so far w.r.t 1. Implementation 2. Effectiveness 3. TCO

Security & GRC Threat Intelligence & Incident Response

163 views1 Upvote3 Comments

Sort by:

VP of IT Operations in Software5 years ago

We keep cycling through different options. The SaaS models for this get expensive fast, or you sacrifice data because of cost. The on prem or open source options require a lot of dedicated time to configure.

Chief Security Officer in Software5 years ago

Elastic and Splunk. Easy, effective, but expensive.

Principal Information Security Officer in Education5 years ago

Elastic SIEM with DIY customizations.
1. Fairly straightforward OOTB.
2. Very. Does exactly what we ask it to do.
3. TCO is much better than the RSA Security Analytics / Netwitness SIEM it replaced.

Content you might like

Does your company have policies in place to protect access to cloud-based documents?

Yes, we have many27%

Yes, we have a few62%

We have some but don’t really enforce them8%

We don’t have policies in place to protect documents1%

View Results

Why do you think there are so few mature AI-driven autonomous pentesting solutions on the market, and why does this topic seem to generate more hype than in-depth technical discussion?

Which pitfalls—model bias, false positives/negatives, data quality, regulatory constraints—often impede AI-based security tools, and how can they be mitigated in a financial-services context?

What is the most important factor to consider when developing a patching strategy?

Compliance requirements25%

Operational objectives65%

Ease of implementation8%

Cost

View Results

Are you using a SIEM product? If yes, which one and what has been your experience so far w.r.t 1. Implementation 2. Effectiveness 3. TCO

Sort by:

Content you might like

Does your company have policies in place to protect access to cloud-based documents?

Why do you think there are so few mature AI-driven autonomous pentesting solutions on the market, and why does this topic seem to generate more hype than in-depth technical discussion?

Which pitfalls—model bias, false positives/negatives, data quality, regulatory constraints—often impede AI-based security tools, and how can they be mitigated in a financial-services context?

What is the most important factor to consider when developing a patching strategy?

Which key pentesting capability do current AI-driven vendor solutions most fail to cover?

What sets us apart?

RELATED ONE-MINUTE INSIGHTS

How are U.S. CISOs Addressing Liability Risk?

CrowdStrike Outage: Impact And Recovery

Impact & Perceptions of A Privacy-First Digital Era

Challenges & Tools For A Privacy-First Internet Age

IT and Infosec Collaboration on Vulnerability Patching

Take Your Insights On-the-Go