dwoj

Not only are they fun and informative, they hook users into visiting the page often. Smart for SW to do this. It's a good way to get revisits that benefits both parties.

If you wanted to do a whole series of articles about virtualization, I wouldn't complain.

I like the analogy you present here. It is clear and conveys the concept in a few words. I hope you don't mind, but I am definitely stealing this one.

There is a definite need for this.

There a lot of good choices to go with here. My answer is simple: Whatever tool gets me closest to the answer in the shortest time. No, not a blow-off answer, it's just a matter of selecting the right tool for the situation. In a NOC setting, there isn't a single tool or method that is the go-to. You know the possible…

I always like when people share resources. Thanks!

This also cleared up a few things for me. Many thanks arjantim

This methodology is the one I see most often. It definitely has its drawbacks, but the protection of the internal network is more than worth eating those up.

As long as I can find cool peeps that like to share knowledge and a few drinks, I'm good to go.

"VMs with multiple vCPU when only single vCPU needed - start with less to add more later." Outside of technical context, this is good advice for life. (/end random thought)

Local events are great for this. Get some knowledge, network a bit, and have fun. Can't beat that. Home labs... yeah, that can be fun, but sometimes it feels like a second job. Cost can be an issue too, depending on how elaborate you want to be. Something that works well for me is find a group of people that are interested…

This would definitely make my life easier.

No, you get extra points.

The problem with logs is that no one wants to bother with them besides turning them on and waiting. Of course, then an event happens, they need the logs, and there is no useful data there or, even worse, no data at all. With the amount of tools available to do most of the heavily lifting with log management, a tedious job…

The balance of humor and realistic info is nice in this post. Blending the two together also worked well, like here: "This is not perfect, and indeed determined users will always find a way past, but it might deter that idiot in Sales from abusing his ex-girlfriend in Accounts on company time and equipment." This made me…

Surprised I haven't seen the 'just make a chart' joke here yet. 

That last point was something I didn't even realize. Thanks for smacking that one into my brain.

Found an announcement vid about it, if you're interested: Shmoocon 2014: Introducing Darpa's Cyber Grand Challenge

Both are necessary to have the full picture. Cost is a challenge, so is laying out processes for both systems (no matter how minor the differences are).

Good info, but the whole beginning part was fun to read. Thanks for a few laughs.

Going along with that, make sure you take the time to learn what the tool does before you start playing with it. You don't want to ring all the alarms on Freeside like Dixie Flatline.

Isn't that DARPA event this year is all about automated solutions and artificial network intelligence? Yes, from more of a sec perspective, but still of those topics, right? Feel free to correct me if I'm wrong. Blame the caffeine gods for not gracing me with their presence this morning on my lack of recall. *sadface*

Chip told me to reboot the server, so I just did that. Have to run, have a Skype call coming in... (Yes, I just made that terrible joke. You're welcome. )

Scripts in the past, but now tools make the job soooooo much easier.

Sometimes the best way to learn is to dive in blind and try to build your own scripts... on a test box, of course.

I hear that Maryland is fun for local events. Maybe I should pop out that way some time to check one out.

On a lot of topics, people say you either pay on the front end or you pay on that back end. I think this cliche does apply in this case.

I like how you used "a repository for ‘just in case the device dies’ recovery" instead of "The 'Oh @^#$' repository".

I'd like to name this method "The Battle to Finish YouTube Video without Rage Quitting".

More often then not, I've seen the guessing method. However, I'm delighted that the mix has shifted more in favor of trying to predict by collecting data and using tools. Depends on the org, their size and resources available, but they are now seeing that a more data influenced method is more useful than throwing a dart…