Search

Muhammad Zain
Muhammad Zain @mzain2004 ·
Replying to @mzain2004
The average dwell time for a breach is 207 days. Attackers are sitting in networks for 6 months because standard SIEMs only flag what they already know. 🥷 I built Phish-Slayer to stop reacting, and start predicting. #SOC #IncidentResponse #SIEM
1
1
Dock Vulner
Dock Vulner @DVulner ·
Breaking: Databricks drops a cybersecurity bombshell 🚨. Introducing Lakewatch SIEM, a game-changing security info & event management system. Acquiring 2 startups raises competition concerns. Is this the start of a cybersecurity monopoly? #Cybersecurity #SIEMf
11
Timeplus
Timeplus @timeplusdata ·
The reality of most #SOC pipelines: #Detection happens after ingestion & storage. By the time you query logs in your #SIEM, the attack is already underway. 💡 In our CEO Ting Wang's latest blog, we explore why you need a #realtime context & control layer:timeplus.com/post/from-logs…Y
From Logs to Context: Why Your SOC Detection Needs a Real-Time Context and Control Layer

In the traditional pipeline, every step after ingestion is retroactive. The SIEM owns the data, and all analysis depends on querying stored records. Alternatively, the new architecture inserts a...

From timeplus.com
11
SIEM XPERT
SIEM XPERT @SiemXpert ·
Cybersecurity teams need SOC Analysts 👨‍💻 Learn practical skills on: • Splunk • Microsoft Sentinel • CrowdStrike • Cortex XSOAR • AI for Cybersecurity 💻 Hands-on Labs 📅 Weekday Batch – April DM SOC for details 🚀 #CyberSecurity #SOCAnalyst #SIEM #TechCarj3YRW
142
Sven O. Rimmelspacher
Sven O. Rimmelspacher @sorimmelspacher ·
Databricks launched Lakewatch as an open SIEM on a security lakehouse with decoupled storage and compute. Keeping full telemetry enables agents to cut false alarms and response time. Security starts with retention. #SIEM #Lakehouse linkly.link/2eVFO
16
Shubham Khuspe
Shubham Khuspe @shubham_khuspe ·
With AI and Cloud Era: What changed in SIEM so it's called Next-Gen SIEM Cloud/Architecture - Logs normalized to OCSF Schema - Stored in data lakes (no storage limits) - Petabyte-scale fast queries - Detection as Code (YAML/Git) #cybersecurity #soc #siem #logs #socanalyst
1
16
Borne Systems
Borne Systems @BorneSystems ·
Replying to @BorneSystems
Set up detection rules in your SIEM (like Wazuh) to monitor for unusual access patterns. Windows Event ID 4624 (successful login) can help you identify potential breaches tied to this CVE. #Detection #SIEM
1
21
Arthur Wilms BEng
Arthur Wilms BEng @BengWilms85361 ·
when sound waves get lost in translation, I'm the quiet guardian of signal fidelity Collaborations like a symphony - harmony found in unexpected places #SIEM Symphony
1
AptXXhunter
AptXXhunter @AptXXhunter ·
Please check on your Siem: 45[.]148[.]10[.]212 83[.]142[.]209[.]11 46[.]151[.]182[.]203 you can have surprises. #siem #trivy
Cyber_OSINT Cyber_OSINT @Cyber_O51NT ·
Cybersecurity researchers found malicious Docker Hub artifacts tied to the Trivy supply chain attack, with clean Trivy last at 0.69.3 and versions 0.69.4–0.69.6 removed after distributing malware. thehackernews.com/2026/03/trivy-…
Trivy Hack Spreads Infostealer via Docker, Triggers Worm and Kubernetes Wiper

Trivy supply chain attack pushed malicious Docker images on March 22, enabling credential theft and worm spread, impacting cloud environments.

From thehackernews.com
1
3
1K