SATELLITE SECRETS

Duda Owner IONOS • February 24, 2015

Quick!  How do satellites keep their location information secret without crashing into other satellites?  That is a very good question, and one that many companies and governments are trying to solve.  No one wants any more satellite collisions such as the one in 2009 when US’s Iridium 33 collided with Russia’s Cosmos 2251, destroying both satellites.

Here is the problem:  Satellite stakeholders view location data as proprietary information.  Leaking that data could degrade competitive advantage.  Simultaneously, governments rightfully have concerns over national security.

Currently, the conundrum is being handled by empowering an independent third party, Analytical Graphics, to receive everyone’s satellite location data confidentially.  Analytical Graphics then runs the calculations and alerts relevant parties about possible collisions.  The one downfall to this arrangement is that all parties must unequivocally trust Analytical Graphics.

Recognizing that the current solution will not necessarily hold together, an interesting new approach is being developed.  It involves some pretty sophisticated cryptographic programming, as Brett Hemenway and Bill Welser explain (“Insecure Skies” Scientific American , February 2015, pp. 28–29):

In the 1980s specialists developed algorithms that allowed many people to jointly compute a function on private data without revealing any number of secrets.  In 2010 DARPA tasked teams of cryptographers to apply this technology to develop so-called secure multiparty computation (MPC) protocols for satellite data sharing.  . . . The [MPC] design guarantees that participants can compute a desired output (for example, the probability of collision) but nothing else.  And because the protocol design is public, anyone involved can write their own software client—there would be no need for all parties to trust one another. ” (p. 29)

One of the disadvantages to the encrypted process is speed.  Using a secured process can take seconds when a nonsecured process can be performed in milliseconds.  The expectation is that technology’s speed will come to the rescue.

Let’s hope that happens faster rather than slower.  We don’t need any more space debris cluttering the orbital highways or tumbling on our heads.





By James Meadows July 13, 2026
What every front desk professional should know about credit card surcharging
By James Meadows September 7, 2025
Is a college degree still worth the investment? It depends of the path you craft.
By James Meadows August 12, 2025
You need to give serious thought to taming the tiger before you are in its cage.
By James Meadows June 8, 2025
My transparent reflection about my five-year post-layoff experience, how I navigated it, learned through it, and identified some wisdom that might inspire others.
By James Meadows June 29, 2024
The earliest days of this series present fundamentally significant leadership content.
By James Meadows August 22, 2023
What we should expect from fidelity to science.
Honesty, honest,  honestly
By James Meadows August 9, 2023
We explore the overuse or inappropriate use of the words "honest," "honesty," and "honestly." Much of the overuse or inappropriate use of these words is in contexts that intrinsically message the audience that the speaker is not trustworthy. I call the overuse or inappropriate use of these words in this context HONESTY VALIDATORS because the speaker believes they validate the truth being spoken. We need a solution to this problem. My solution is to replace these honesty validators with CLARITY VALIDATORS. Instead of trying to be honest, try to be clear. Replacing "honest," "honesty," and "honestly," with "clear," "clarity," and "clearly," produces significantly more benefit to the speaker and to the audience.
By James Meadows August 7, 2023
It's the real thing alright!
By James Meadows May 30, 2023
Reflecting on 30 years as a PC user.
By James Meadows July 26, 2020
What the Boeing 737 Max crashes teach us about training, corporate culture, and communication.