Skip to main content

Securing Google Apps for Your Domain

(0 comments)

I think there are two markets for Google Apps for your domain.  One is in education where you want to get the management of student accounts off your shoulders.  The other is real companies that like the web, use the web and want to cloud-source their infrastructure.  Twitter is clearly one of the latter and they recently realized the risks they were taking in doing so

Managing IT assets is difficult to do securely while providing the access needed by today's workforce.  I think that for most small companies, outsourcing certain IT assets results in a net gain in security and a net financial gain as well. The assumption here is that you want to minimize the cost of IT while providing the most services at the lowest cost without taking excessive risk. 

So, then the question becomes, what do you keep in house?  You're giving up control of the storage, control of the client, the transport, etc.  You had better hang on to the keys to the kingdom.  Keep in mind that the more connected/mobile/twitterish your employees are, the more likely they will be re-using their credentials on some hip web service.  Password reuse is a fact of life.  The only way around it is two-factor authentication.  Luckily, your uber-connected workforce will all have iPhones and Blackberries on which to run software tokens.

For more on how to secure to Google Apps for Your Domain with two-factor authentication, please see the tutorial. 

Currently unrated

Comments

There are currently no comments

New Comment

required

required (not published)

optional

Recent Posts

Archive

2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008

Categories

Tags

Authors

Feeds

RSS / Atom