1. Links for 2010-09-13

     
  2. Comments
  3. Links for 2010-09-09

     
  4. Comments
  5. Links for 2010-09-08

     
  6. Comments
  7. Links for 2010-09-07

     
  8. Comments
  9. Links for 2010-08-26

     
  10. Comments
  11. “If you haven’t upgraded from XP/Server 2003, I can hack you in two minutes”

    I’ve just got back from a TechMesh event, and feel the need to rant. The speaker gave this quote (from memory):

    If you are still running Windows XP or Server 2003, upgrade. Just do it. We could walk into your network in, oh, two minutes. Upgrade

    If only life was that simple. Move to Windows 7 and all my problems will be over? Sign me up. Or, to be less unfair to the speaker, unless I move to Windows 7 my network is wide open? Not necessarily. 

    The trouble with this statement is that as a guide for action, it’s about as useful as this sign:

    It’s a useful sign, but the path is not anywhere near it.

    Let’s start with the obvious: Microsoft deserve a lot of credit for making their latest OSs harder to exploit. DEP (actually introduced in XP SP2…), ASLR and the rest mean exploiting Windows is now hard. Hard means it’s expensive to develop exploits and this is good. What it doesn’t mean is that it’s impossible, or even, in practice, much more work.

    Let’s say I want to exploit a company using only Windows 7 and Server 2008. A quick look at the MS Security patch list shows me plenty of targets. Look at the number of bugs ranked “critical” that apply to Windows XP, Vista and 7. And that’s before we move onto this year’s favoured target of choice, Adobe.

    Nothing about moving to Windows 7 makes this attack much harder. Even if we have to write the exploit ourself (very unlikely) DEP and ASLR make it harder to get a reliable exploit if needed, but there’s been enough examples of exploits this year to prove that they are also not a barrier. It’d be more expensive, but in most cases the attacker is just going to grab Metasploit rather than writing an exploit from scratch 

    But of course, in most cases the easy way to get in is to target an executive for spear phishing (high enough up to demand admin rights and get them) and send them either a malicious PDF or the old fashioned “click here to download the codec”. Even if the person attacked is clued up enough to understand code signing (which seems unlikely), we could go with signed malware 

    What about Server 2008? Isn’t that more secure? Well, yes. Again, it’s much improved (e.g. no NTLANMAN password hashes), but in most enterprises, it’s not going to be the weak spot. SQL Injection against a vulnerable web server followed by token stealing works fine. 

    Moving to Windows 7 and Server 2008 is good advice. If you have infinite resources, doing it now is good advice. If you don’t have infinite resource (my work certainly doesn’t), then blindly rushing in is probably not the best plan. 

    Upgrade in good time, but do it right, and in the meantime, look at everything else. It’s far more likely you have serious holes elsewhere (start with asking how many users have admin rights and go from there) where resource could be better used. Upgrade to Windows 7 for business reasons when ready, not before.

     
  12. Comments
  13. Links for 2010-08-25

     
  14. Comments
  15. Links for 2010-08-24

     
  16. Comments
  17. Links for 2010-08-23

     
  18. Comments
  19. Stages of an IT Project as a River

    My colleague Alistair Knock(@aknock) came up with the characterisation of an IT Project below after a recent discussion about enterprise collaboration software, which I reproduce here with permission.

    Stages of a IT project as a river

    - spring: random optimistic thoughts circulate online, IM, watercooler, pub.  The words ‘wouldn’t it be nice if’ are repeated over and over again, and a diagram emerges.  The guy with the Guinness already has a database schema designed.

    - stream: a space is created on online and someone, who will later regret it, offers to set up a test system.  Happy people promote it internally by setting up blogs and intentionally spam all the mailing lists but still apologise for cross-posting (I am convinced this self-referential act creates a small amount of dark matter).

    - river: lots of friendly people start using the BETA NO GUARANTEES BETA system, love it, and start breaking all sorts of policies, many of which are rewritten as a result.  Someone tries to put everything into Microsoft Project and consequently goes on sick leave.

    - waterfall: major panic and lots of talk about scalability.  General anger from management and calls for a review/subgroup.  Minutes are circulated in Word and there is great confusion about which version is current.  Two people miss the meeting because their diary doesn’t support meeting requests.

    - pool: general calm and lots of hard work crafting documentation which is published on a wiki.  The wiki begins to be abused as people try to make it do the things that the original project was supposed to do, including but not limited to booking train tickets.

    - evaporated pool: documentation is now hopelessly out of date and system is close to collapse due to near constant use by 3 users.  Rest of users have split into one segment who are using some new Google invention and continue to breach policies; the rest are very optimistic about an open-source product but have yet to get it to compile and/or have grave and insurmountable concerns about it being distributed under BSD rather than GPL.

    - cloud: yeah, right.

     
  20. Comments