Ft. Knox

I wrote a blog series on the lessons that can be learned from physical security and applied to network security. I presented a webinar on October 18, 2012 to summarize the series. For those interested, you can view the archive here: http://www.lancope.com/resource-center/recorded-webinars/the-network-security-school-of-fort-knox-1/

The blog series had six parts and are listed below:

  1. Perimeter Defenses: http://www.lancope.com/blog/fort-knox-part-one/
  2. Detection Methods: http://www.lancope.com/blog/fort-knox-part-two/
  3. Attack Payloads: http://www.lancope.com/blog/fort-knox-part-three/
  4. Data Visibility: http://www.lancope.com/blog/fort-knox-part-four/
  5. Types of Attackers: http://www.lancope.com/blog/fort-knox-part-five/
  6. Incident Response: http://www.lancope.com/blog/fort-knox-part-six/

 

About the Author

Charles Herring

Charles Herring

Co-founder & Chairman, WitFoo

I started WitFoo in 2016 to make information and operations shareable across the craft of cybersecurity — between companies, law enforcement, national security and insurers, who mostly cannot see what each other sees. Before that I was at Lancope and Cisco, and I began in 2002 as Network Security Officer for the Naval Postgraduate School.

I lead research and development on a platform that ingests trillions of messages a day across hundreds of clusters. It is sold as Conductor, Reporter and Analytics, licensed flat per appliance with unlimited data — because a team charged by the gigabyte ends up making coverage decisions on a spreadsheet, months before the incident that needed the logs they dropped.

Everything here is mine, not the company's, and it wanders. Corrections are genuinely welcome — I would rather be right than consistent.

A note on how this was written: I use artificial intelligence tools to help me research, check facts, and edit these posts. The ideas, the arguments, and any mistakes are mine. I read the sources, I check the claims, and I take full responsibility for what I publish here. The views are my own and the writing is my intellectual property.