There are basically three areas of risk:
- Terms of service when using a third party
- Vulnerabilities in the application programming interface (APIs) used to interface with the service
- Images providing sensitive information.
The first area of risk has caused a lot of debate and misunderstanding. Various governments, including those of the Dutch and Australians, and military personnel have expressed concern over how easy it is to get detailed imagery of military bases, government buildings, airports and ports, which could aid terrorists in planning and conducting an attack. Google does blur images of some buildings, like the U.S. Capitol Building, but this type of information is not unique to Google Earth, and commercial high-resolution satellite and aerial imagery of every country in the world is already in the public domain or widely available from numerous sources.
The second area of risk involves mash-ups, which are developed by integrating data from internal and external sources. Information mashed together with Google Maps can support a wide range of applications, such as routing and customer analysis. However, organizations implementing mash-ups using external sources need to consider the reliability of that data. How good is the quality of the information? Are there copyright or other restrictions on its use? What level of data availability is guaranteed? Do the APIs create security holes in the internal applications? APIs that have been deprecated instead of deleted have caused problems in the past for developers integrating applications with MySpace, for example. There is a risk that third-party data could come from hackers or other unknown sources, and DoD data and servers could be compromised. These factors could pose an unacceptable risk for business-critical applications at the DoD.
Finally, according to Google Earth's terms of service, section 11.1 states that Google retains the right to reproduce, adapt, modify, translate, publish, publicly display and distribute any content which is displayed on or through its services. Google's irrevocable right to use its data would certainly be an issue for the DoD.
Dig Deeper on Web application and API security best practices
Related Q&A from Michael Cobb
Sending sensitive information in attachments is inherently unsafe, and the main way to secure them -- encryption -- can be implemented inconsistently... Continue Reading
Spyware can steal mundane information, track a user's every move and everything in between. Read up on the types of spyware and how to best fix ... Continue Reading
Explore the differences between symmetric vs. asymmetric encryption algorithms, including common uses and examples of both, as well as their pros and... Continue Reading