Sign in Subscribe

Tara Everding

Canada

Marketing Lead at SpaceComputer. Bachelor of Sciences at Dalhousie University.

Image displaying 'Why put a key management service on a satellite' with a shield and a PCB board in the background.

Why Put a Key Management Service on a Satellite?

Every three months, a small group of people meets in a secure room in Culpeper, Virginia, or El Segundo, California to use the root key behind DNS security. The hardware holding that key stays sealed in a tamper-evident bag, inside a safe, inside a metal cage, and it can&

Image of the SpaceComputer team in attendance at Silicon Valley Space Week, smiling in front of the booth backdrop.

SpaceComputer at Silicon Valley Space Week Recap: Orbital Compute, Security, and Verifiable Data

From October 27th to 29th, our team set up our booth at the Computer History Museum in Mountain View, California, for Silicon Valley Space Week, hosted by Sat News. Over three days, our co-founders and team held many conversations with startups and established companies in the global space sector,

Image of a 3u smallsat with a lock representing security orbiting above earth, being able to provide remote attestation to the computing tasks it runs and processes on board.

What Is Remote Attestation? How Computers Prove What They're Running

Most cloud security still runs on promises, and remote attestation is how a computer replaces a promise with evidence. What Is Remote Attestation? Remote attestation is a process that lets a computer prove to a remote party what software it's running and what hardware it's running

image of an active rocket booster, launching into orbit

Who Signs the Proof? Attestation and Verifiability in Sovereign Space Technology

A government can own a satellite's payload and control its tasking, yet still rely on a chipmaker's attestation service to confirm that the satellite is running the code it was given. That's how remote attestation typically works, with a protected environment in the device

Image of a a map of the world with large cities highlighted on the screen. Title reads KMS vs Secrets Manager: How Key Management and Secrets Management Differ

KMS vs Secrets Manager: How Key Management and Secrets Management Differ

When GitGuardian analyzed thousands of compromised developer machines, on average, each live secret turned up in eight different places, from .env files and shell history to IDE settings and build artifacts. Credentials spread to wherever developers and their tools need them, and the two systems built to contain that spread,

image of an Earth with network lines and lights over the land surfaces. Title of the blog reads: KMS vs HSM: The Difference Between a Key Management Service and a Hardware Security Module.

KMS vs HSM: The Difference Between a Key Management Service and a Hardware Security Module

If you use AWS KMS, your security keys already live inside hardware security modules. AWS states that keys created in the service are protected by FIPS 140-3 Security Level 3 validated HSMs. However, choosing between a standalone key management service (KMS) and a dedicated hardware security module (HSM) is

image of a bunch of security keys hanging on a wall, a simplified physical representation of a Key Management Service.

What is a Key Management Service?

In 2025, developers pushed 28.65 million new hardcoded secrets to public GitHub repositories, a 33.9% jump from the year before, while leaked credentials for AI services rose 81%. Each of those secrets is a password, token, or key sitting where anyone who reads the code can copy it,