About 20 years ago we used to play BZFlag in the office during lunch, maybe 6-8 of us in a company of ~50. Someone complained that we were using up the network bandwidth, although I knew the BW for the game was tiny. I bought a bunch of USB Wi-Fi adapters from Woot! and we would place them on the tops of the cubicle walls when we played. We wouldn't actually plug them in. We played on and off for several more years without any network complaints. I even built a map of the office, taking pics to use as textures, so we could drive tanks around the office, jump on our desks and shoot each other.
I have a fun story. I was allowed to set up an HTTP server on the network at work. Boss wanted me to be an Apache expert. I didn't get permission to run a BZFlag server, modded to allow infinite reload. I had rotating servers with goofy stuff like blank maps, all flags Laser, with infinite reload. I remember the frantic call from my boss about a DDoS attack hitting my server. The thing I missed was each shot is a single UDP packet, so I was basically DDoSing the entire network. Woops
The Long Run by Daniel Keys Moran takes place in 2069 but was written in 1989 and the tech still holds up decently (to me at least). Sort of a Snow Crash vibe but less satire. AI's exist on the network (called the Crystal Wind) but haven't taken over or anything. Many Players (hackers) use "Image" software that are essentially AI agents.
This is pretty much the plot of the Daemon book series by Daniel Suarez. I always thought this series was a decent example of starting with somewhat realistic tech (well, maybe realistic to a non-expert like me) and extrapolating it exponentially. I'm going to need to read the series again because I'm guessing what I would consider "realistic" extends quite a bit further into the plot than it did 20 years ago.
I grew up in the boonies back in the 80's. The only real contact I had with juggling was probably cartoons like described above. I really wanted to learn though and would walk around the woods for hours trying to juggle oak galls in that "circle style" only able to keep it up for a few seconds at a time.
My first day at college, before classes started, I was in the dorms. Everyone was getting to know each other, and I saw someone juggling the right way. It instantly clicked. All the hand-eye practice the 'wrong' way actually helped. That's why I always tell people that the first thing I learned in college was how to juggle.
Just curious, what come first and second in this use of the phrase applied to computer security? I came to know the expression from fire circus performance and adjacent circles, where first and second are safety of the audience and the venue, and third is your own. I use it often when I'm about to knowingly do something sketchy or potentially dangerous without applying safety practices required "by the book", acknowledging the present danger to myself and accepting the risk. I never saw it used in infosec context.
Interesting, I haven't heard of safety third from circus circles, I've always known it as more along the liens of if safety were actually the number one priority, no one would actually do anything because it's too risky.
In terms of cybersecurity, I see it as "security first" culture means people rely on the system to keep them safe. "Safety third" (or security third) emphasizes that everyone should already know they are operating in a risky and dangerous environment and take security as a personal responsibility.
It's just a reminder that no one cares about your life more than you do, so stay vigilant and take personal responsibility.
edit just realized I didn't actually answer your question on the first and second priorities.
I suppose First would be the reason the system exists in the first place (buy something online, for example). Second would be the user experience of doing the thing. Security should help you take calculated risks rather than prevent you from taking any risks at all.
reply