Customer Perspectives on Evaluating the Security of Going Google

Editor's Note: Please join us for a webcast on Thursday where two Google Apps customers will share their approach to evaluating the security of Google's cloud computing solutions. MeadWestvaco (MWV), a $6.6 billion packaging company recently consolidated 10 email systems to Google Apps and Boise State University deployed Google Apps to 23,000 students, faculty, and staff.

Chet Loveland, Global Information Security and Privacy Officer at MWV, holds 23 years of experience in the Information Technology industry and was formerly an Information Security Manager for Federal Reserve Information Technology. Brian Bolt, Lead Systems Engineer for Boise State's Office of Information Technology, holds 15 years of experience in the Information Technology industry, with an MBA from Boise State, where he has worked to emphasize the alignment of IT infrastructure and services to support the business needs of the university.

Chet and Brian will be joined on the webcast by Eran Feigenbaum, Director of Security for Google Apps. Eran defines and implements security strategy for Google's suite of solutions for enterprises. Prior to joining Google in 2007, Eran was the US Chief Information Security Officer for PricewaterhouseCoopers (PwC).

Learn what security and compliance questions to ask of a cloud computer provider and how Google addresses them on a live webcast on Thursday, July 22, 2010 at 2:00 p.m. EDT / 11:00 a.m. PDT / 6:00 p.m. GMT. Register today.

Google Apps is one of the fastest growing cloud computing solutions available today. Not surprisingly, many organizations considering solutions like Google Apps have questions about security and compliance. When moving into the cloud, it is important to consider factors such as how the cloud provider fights spam, malware, and phishing, designs identity management systems for hosted web apps, and monitors its network for potential threats. Institutions must consider ways to protect intellectual property, compliance with regulations, and evaluating information about the cloud provider's data center and network infrastructure.

At MWV, the main considerations were reducing IT costs and consolidating ten different email systems into one. At Boise State University, the primary concern was safeguarding student records and information. Despite differing priorities, most organizations today face common underlying security challenges and needs.

Both MWV and Boise State asked themselves:

• Where is the best place for my applications and data?
• Why is security so tough? What are some of the issues with the traditional model?
• Can hosting data in the cloud be as secure or perhaps more secure, than in traditional environments?
• What are the full costs if security is handled internally? (considering firewalls, server upgrades, maintenance, mail filtering, anti-spam, and more)
• How can we maximize productivity by enabling people to work anytime, anywhere while minimizing the amount of data that is stored on distributed devices?
• How will the cloud provider affect costs and the reliability of security systems?
• How do we educate internal stakeholders and users on security and compliance issues to mitigate risks and help ensure adherence to best practices?
• And, ultimately, what are Google's practices and technologies that can help us maximize security while reducing costs?

There are always plenty of questions and follow up discussions when considering the people, best practices, and technologies required to minimize security threats. There are also many lessons to learn from two Google Apps customers who have moved into the cloud – with security and compliance at the top of their lists to address. Learn more from experienced Google Apps customers and from Google's security chief for enterprise applications.

Please join us for a lively discussion of the security and compliance considerations for moving into the cloud.

Boise State and MWV on Evaluating the Security of Going Google
Thursday, July 22, 2010
2:00 p.m. EDT / 11:00 a.m. PDT / 6:00 p.m. GMT

Posted by Serena Satyasai, the Google Apps team

For more information on the security of Google Apps, please visit www.google.com/apps/trust