Homemade Security Video #2: Castle Assault

Later in 2002, having cut my teeth on the first video, I decided to try for something a little more ambitious: to illustrate the concepts of Defence-in-Depth and highlight some of the technical security issues that you’ld encounter in a modern “Enterprise” Compute Network.

castle video
[ webpage ] [ quicktime ] [ 19Mb ]

So – cutting a long story short – I decamped to a Bronze-Age Hill Fortress and “assaulted it” – ran up it as quickly as possible for realism – while videoing the effort.

I completely knackered myself, got covered in mud, fell over (the final cut audio is looped slightly to hide the swearing) and sliced myself open on barbed wire (“Ah, blood! That always makes for excitement!”) – all in pursuit of a real race: the sun was setting fast and I would lose any hint of daylight within the hour, plus I had another 200 miles to drive that evening.

It’s not bad for an amateur effort – although I am not going to vouch for the 100% historical accuracy of the piece, it does get the ideas across.

Comments

5 responses to “Homemade Security Video #2: Castle Assault”

  1. Steve Lodin
    re: Homemade Security Video #2: Castle Assault

    This is a classic!! Thanks for sharing.

    Steve

  2. alecm
    re: Homemade Security Video

    Glad you liked it, Steve.

    If you’re interested in more, spread the word and drop me some topics; I am considering one on secure disk destruction soon.

  3. Stephen Usher
    re: Homemade Security Video

    Would this be a take off of Brainiac, trying to destroy a disk drive through all sorts of strange and explosive means?

  4. Stephen Usher
    PS.

    One, of course, would have to involve blowing up a caravan.

  5. alecm
    re: Homemade Security Video

    I hadn’t quite considered framing it as that, although sledgehammers do figure in what I have in mind.

    I am not sure I can pull off enough of Richard Hammond’s gravitas, to do it justice, but it’s a good idea to start from.

Leave a Reply

Your email address will not be published. Required fields are marked *