Looking at different players promising to solve the security data problem, what each of them brings to the table, and the trends defining what the cybersecurity data stack of the future is going to be
Anyone who doesn't understand this should do a background check search for their name. Last week, I found out that one of my names is apparently Mora JMcgougal. This is the kind of name that mean kids at school would turn my real name into.
35 pages? Ross, I print out and markup all your newsletters. And I'll do the same for this one - but 35 pages??? ; ) Great job. More content. More value. More food for thought. Thank you, Steven Palange.
lol, so far I’ve reached “Data Gravity & Building the industry on Data Lakes. Only 3 more pages to go before I go back and read my Underlines, Notes and Comments. Ty, Steven.
Anyone who doesn't understand this should do a background check search for their name. Last week, I found out that one of my names is apparently Mora JMcgougal. This is the kind of name that mean kids at school would turn my real name into.
35 pages? Ross, I print out and markup all your newsletters. And I'll do the same for this one - but 35 pages??? ; ) Great job. More content. More value. More food for thought. Thank you, Steven Palange.
lol, so far I’ve reached “Data Gravity & Building the industry on Data Lakes. Only 3 more pages to go before I go back and read my Underlines, Notes and Comments. Ty, Steven.
Data is half of it.
The other half is a threat model that:
(i) survives changes in Entry Points,
(ii) is focused on critical events/behaviors (as opposed to every little technical hiccup), and,
(iii) related to (ii), is fast enough to stop stuff in minutes.
Fantastic commentary - thank you. The “Data lakes don’t silo your data” piece is gold.
Onum is missing in the ETL layer. Comcast DataBee in the Next Gen SIEM