■

Official Google Blog: How Google keeps your information secure

昨日は、東京大空襲を警視庁のカメラマンが撮影したエピソード・ドラマを
観賞した。
米軍が東京をTargetに定めて、ナパーム弾を落とすエリアを決定する。
その時、使っている地図のテクノロジーは、全部Google Map やGoogle Earth
の機能を使えば、誰でも、使用できるようになっていた。
そう、こんなプロジェクトが進行して実行に移された一方で、
敬愛するファインマン大先生は、ロスアラモスにいた。
Googleを見ていると、
整然と、規律が行き届いた「軍隊」を思い出す。
ニコヤカにしているけど、でも、やっていることは「戦争の遂行」だと
思った。
「Web進化論」はすごい本だと思う。
でも、どこかで、何か、違和感を覚えるのは、
この「軍隊」に対する違和感なのだろうか。
いつの時代も、「軍隊」を笑顔で話すのは、難しい。

As many of you know, we spend a lot of time around here thinking about new products to help you run your life more efficiently, whether that’s organizing email in a better way, sharing pictures with friends, or collaborating in real time on documents. What you may not know is that we also spend a lot of time thinking about the security that goes into those products, and more specifically the ways we can protect you and your private information.

People: The most important part of our approach to security is our people. Google employs some of the best and brightest security engineers in the world. Many of our engineers came from very high-profile security environments, such as banks, credit card companies, and high-volume retail organizations, and a large number of them hold PhDs and patents in security and software engineering. As you can imagine, our engineers are smart and curious and are on the lookout for security anomalies and best practices in the industry. Our engineers have published hundreds of academic papers on technically detailed topics such as drive-by downloads that install malware (PDF file) or hostile virtualized environments. (You can find some of these papers here.) What's more, we cultivate a collaborative approach to security among all of our engineers, requiring everyone to pass a coding style review (which enables us to control the type of code used here and how it's used in order to prevent software problems) and ensuring that all code at Google is reviewed by multiple engineers so that it meets our software and security standards.