Google Earth Goes Nuclear

newsguy 0 485 Views

Reports suggest that Google Earth might have put the top secret British nuclear defence headquarters, at the Faslane HM Naval Base Clyde in Scotland, at risk from terrorist attack after the satellite mapping shows clear images of the facility.

The images are highly detailed and even show a couple of Vanguard Class submarines docked. Newspaper reports recount how a couple of years back Google was asked to blur British military bases in Iraq as well as certain strategic military installations in the UK on grounds of national security. I am led to believe that updates to Google Earth have meant that those previously blotted out areas are now visible once more.

These areas include the Faslane site, the nearby Trident Special Area (where the British nuclear submarine fleet store warheads) and further afield the SAS training facility in Hereford. The latter details everything from sleeping quarters to bunkers.

The Sun claims that senior officers in the military are "furious that such sites can be viewed by anyone" and that the Ministry of Defence is struggling to "maintain the security of all the UK's sensitive military sites."

A Google spokesperson declined to comment upon government requests for the obfuscation of military sites.

Given that there is even a Google Earth for mobile devices it would appear that without some kind of national security collaboration the application could be something of a terrorist wet dream. It would not seem to be a great leap for Google which has already banned violent Islamist videos following pressure from the US Senate Committee on Homeland Security and Governmental Affairs.

Dani AI

Generated

As points out, publicly available satellite and aerial imagery on consumer mapping platforms can legitimately expose operational details and poses a real security consideration. The essential context is that these services aggregate imagery from multiple commercial and governmental providers, so what appears (or disappears) on one map layer is not necessarily the whole picture. Treating platform blurring as a primary security control is risky.

A few technical clarifications that are often missing: imagery age, resolution and coverage vary by source; platform updates can change which source is shown; and an obfuscation request to one provider does not remove the original images from other vendors, archives or third‑party redistributors. Metadata and user‑posted photos (geotagged images from personnel) are a common, avoidable leak vector that is independent of mapping services.

Practical mitigation workflow (actionable steps for operators and administrators):

  1. Document: capture dated screenshots with coordinates and note the imagery timestamp shown by the platform.
  2. Report: submit the evidence through the mapping provider’s official “report/problem” channel and keep written records of the submission.
  3. Escalate: notify the agency’s security office and national mapping/defence authorities so formal requests or legal measures can be coordinated.
  4. Remediate: audit and remove geotagged content from public sites, enforce metadata stripping on issued devices, and update personnel policies about posting images.
  5. Harden: apply physical concealment where practical (covers, netting, reduced signatures), use operational discipline (move sensitive assets offsite when possible), and rely on layered controls rather than obscuration alone.

Caveat: platform-level blurring can help reduce casual exposure but does not eliminate risk from other suppliers, historical archives, or hobbyist imagery. The prudent course combines technical reporting with operational changes and formal escalation through national security channels.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Edit Preview