Skip to main content

Google Wave Security

Have Google thought about security or got caught up in a Wave of enthusiasm?

The big advantage of email has always been the firmware independence; it doesn't matter if I'm using a Vista machine, a Mac Book Air or my mobile phone, I can always send and receive email. Google have argued that this is a 40-year-old technology that is ripe for an update. This is true, but if Google want widespread adoption of Wave, they need to have two things. Firstly, it needs to be open and platform independent - they have announced that it will be open-source, so that checks out. Although they say that they want to give something back to the community, this project would fall flat if the only way to communicate was via their web app that people have to sign up to. I don't need to sign up to Google to get my email or to receive gmail messages. I have choice. This is critical to the success of the new platform, but, as my wife says, it's always good to turn a necessity into a virtue.

The second thing that Google need is to have security built-in to the architecture from the start. If this is to be used by businesses, rather than become just another social media site, then it must support authentication, message integrity and confidentiality.
  • Login = authentication + confidentiality?

  • Can I forward message?

  • Is message encrypted at rest?

  • Can it be signed?

  • Can I change the attachment of another user?

  • Digital Leakage

  • Can I add another user to the thread?

  • Can it be read-only & non-forwardable?

Comments

Popular Posts

Trusteer or no trust 'ere...

...that is the question. Well, I've had more of a look into Trusteer's Rapport, and it seems that my fears were justified. There are many security professionals out there who are claiming that this is 'snake oil' - marketing hype for something that isn't possible. Trusteer's Rapport gives security 'guaranteed' even if your machine is infected with malware according to their marketing department. Now any security professional worth his salt will tell you that this is rubbish and you should run a mile from claims like this. Anyway, I will try to address a few questions I raised in my last post about this. Firstly, I was correct in my assumption that Rapport requires a list of the servers that you wish to communicate with; it contacts a secure DNS server, which has a list already in it. This is how it switches from a phishing site to the legitimate site silently in the background. I have yet to fully investigate the security of this DNS, however, as most

Security Through Obscurity

I have been reminded recently, while looking at several products, that people still rely on the principle of 'security through obscurity.' This is the belief that your system/software/whatever is secure because potential hackers don't know it's there/how it works/etc. Although popular, this is a false belief. There are two aspects to this, the first is the SME who thinks that they're not a target for attack and nobody knows about their machines, so they're safe. This is forgivable if misguided and false. See my post about logging attack attempts on a home broadband connection with no advertised services or machines. The second set of people is far less forgivable, and those are the security vendors. History has shown that open systems and standards have a far better chance of being secure in the long run. No one person can think of every possible attack on a system and therefore they can't secure a system alone. That is why we have RFCs to arrive at ope

Web Hosting Security Policy & Guidelines

I have seen so many websites hosted and developed insecurely that I have often thought I should write a guide of sorts for those wanting to commission a new website. Now I have have actually been asked to develop a web hosting security policy and a set of guidelines to give to project managers for dissemination to developers and hosting providers. So, I thought I would share some of my advice here. Before I do, though, I have to answer why we need this policy in the first place? There are many types of attack on websites, but these can be broadly categorised as follows: Denial of Service (DoS), Defacement and Data Breaches/Information Stealing. Data breaches and defacements hurt businesses' reputations and customer confidence as well as having direct financial impacts. But surely any hosting provider or solution developer will have these standards in place, yes? Well, in my experience the answer is no. It is true that they are mostly common sense and most providers will conform