1. Lessons from the Google hack for Universities, part I

    More details are coming out about the Google/China hacking incident. There’s even talk of how resistance is futile

    Dave Aitel from Immunity, who is one the top guys out there on the offensive side, has been making this point for a while. Given a modern penetration toolkit (Canvas for the flush, Metasploit for the cheap), breaking into nearly any organisation is possible. Given more resource, pretty much anything softer than GCHQ/NSA is a target. It’s just a matter of time, effort and economics. How many person-days is it worth the attacker spending on breaking in?

    For the defender, things are muddied even further by the issue of unpatched bugs, or zero-days. How do you defend against an attack for which no patch, anti-virus signature or IPS rule exists? To quote Dave again:

    Everyone says an attack is “sophisticated” whenever any 0day is involved. But that should be the baseline. Or rather, it IS the baseline and everyone seems to just be finding out

    Universities maybe can be less worried by this than most, but not for good reasons. Attackers use their resources wisely: there’s no need to use an expensively developed zero-day Internet Explorer exploit when there’s an unpatched copy of WordPress running on the user webserver and no DMZ.

    For most people and organistations this is somewhere between unpalatable and unacceptable. It’s saying that even if we keep all our systems patched and make sure every PHP app anywhere on the network is secure we’ll still be 0wn3d. And the reality is that most Universities (especially the older ones) are so devolved that even getting everything patched is a Sisyphean task.

    So if a senior manager asks “What is the point of employing these InfoSec staff if we are going to be broken into anyway” it’d be best to have a good response ready. That’s something we’ll return to in a future post (along with a post on the mechanics of how targetted attacks work)

     
  2. Comments
  3. Passwords: the failure of two factor auth

    Although the leak of 32 million passwords from RockYou is somewhat old news, two things that happened today brought it back to mind.

    First, there was an excellent discussion on the Security Metrics list about the incident. The most obvious take away from it is how bad the passwords people choose are. From CXO we learn that the most common passwords are:

    1. 123456
    2. 12345
    3. 123456789
    4. Password
    5. iloveyou
    6. princess
    7. rockyou
    8. 1234567
    9. 12345678
    10. abc123

    with the “123456” being choosen by ~1% of the sample. Clearly these weren’t sites that placed any restrictions on the strength of passwords!

    This agrees with my findings from running cracklib against a NIS file from a site that didn’t enforce any password complexity requirements. The most common choice for a password was to make it the same as the username, with “abc123” and “123456” also making a strong showing. (When we suggested to one of these users that “abc123” wasn’t a great password, he replied that it was an excellent password as no hacker would think he’d be stupid enough to choose such a bad password!)

    Read More

     
  4. Comments