The Tech Herald

NCSAM: Security in 140 characters or less…

by Steve Ragan - Oct 5 2011, 12:00

Tom Liston, the Senior Security Consultant for InGuardians, Inc, has written a great blog on the SANS ISC diary, focusing on the basics of information security. His tips were sourced from Twitter; hence this story’s title, but they are a perfect fit for National Cyber Security Awareness Month.

Liston’s blog starts out by recounting a recent job. “I had just spent a week immersed in a corporate culture that seemed to have focused itself on so many higher-level security issues that the basics – the ‘Security 101’ stuff – was just plain overlooked,” he wrote.

“The more I thought about it, the more it bothered me.  It wasn't some fancy-schmancy 'leet h@x0r 0-day that let us take down this organization from the inside: it was stupid-simple low-hanging fruit… Think about it: Over the past year, how many high-profile hacks have been the result of awesome cutting edge skillz?  How many have happened because someone just flat-out did something dumb? We truly are neglecting the basics.”

Liston went to Twitter and asked other security professionals to share their wisdom. Some of the highlights are below, the rest can be seen on the SANS post, or on Twitter here.

If you can guess where PHPmyAdmin is installed, then so can attackers.

You are already pwn3d. The question is, "What will you do about it?"

Don't leave default passwords on the administrative interfaces of your 3rd party web applications.

Know your network - and all devices in it - well enough to spot unusual activity.

Security 101: If you don't need it, turn it off.

Computers remember a lot. Even more if you contact security personnel before you reboot.

If your product allows remote connections somebody WILL write a python/perl/ruby script to connect to it and send whatever THEY want.

A backup is not a backup until you do a restore.

Attack vectors and regulatory requirements change. "That's how we've always done it" is a poor and lazy excuse.

In your encryption system, your key is the weakest link. If it isn't, you're doing it wrong.

If you don't log "accepts" in your FW logs for admin protocols you will have no way of knowing when those accounts are abused.

Analyse your logs in detail, it is those with their heads buried in your logs that hold the key to prevent, detect and recover.

Give only the permissions required to do the normal daily duties, nothing more. Special logons for special occasions.

Unencrypted Wi-Fi is never secure. WEP = Unencrypted Wi-Fi. Trust me. Stop using it. Now. Really.

Around the Web

Comment on this Story

comments powered by Disqus

From Autosaur.com

Chevrolet shows off the 2015 Colorado with digital experience

Chevrolet has launched a new website to show buyers all the bells and whistles available on ...

Mazda to debut CX-3 and MX-5 at Los Angeles Auto Show

Mazda has announced plans to premiere the new Mazda CX 3, its new compact crossover SUV, at ...

Ford issues safety recall for 204,448 Ford Edge and Lincoln MKX

Ford has issued a safety recall for 204,448 of the 2007-2008 Ford Edge and Lincoln MKX in No...

Mopar Previews SEMA Custom Rides

We have added a set of pictures released by Mopar ahead of the SEMA Show. Mopar are bri...

Audi R8 Competition – The Most Powerful Production Audi Ever

Audi has revealed details of their new super-fast Audi R8 Competititon — the most powerful a...