How Should Security Be Architected for Human Error?
Nie udało się dodać produktów
Nie udało się dodać tytułu do koszyka.
Nie udało się dodać tytułu do schowka.
„Usuń ze schowka“ nie powiodło się.
„Obserwuj podcast“ nie powiodło się
„Przestań obserwować podcast“ nie powiodło się
How Should Security Be Architected for Human Error?
-
Czyta:
-
Autor:
All links and images can be found on CISO Series
We've all internalized that humans are the weak link in cybersecurity. Why do we not account for that when we're building our cybersecurity programs?
Check out this post for the discussion that is the basis of our conversation on this week's episode, co-hosted by David Spark, the producer of CISO Series, and Geoff Belknap. Joining them is their sponsored guest, Kieran Human, lead cybersecurity engineer, ThreatLocker.
In this episode:
- Humans and automation checking each other
- Assume the click happens
- Catch it in the moment
- Take the manual step out entirely
A huge thanks to our sponsor, ThreatLocker
An AI-generated attack may be new, but it still needs to execute, access data, and move through your environment. ThreatLocker applies enforceable controls at each of those points, limiting what attackers can do regardless of how their code was created. Book a demo at threatlocker.com/ciso.