TegoSafe
EN

What is AES-256-GCM, and what does the name tell you about a vault app?

AES-256-GCM is a public standard for locking a file. What AES, 256 and GCM each mean, why the key and passcode matter more, and what a vault app should say.

A vault app says "AES-256 encrypted" on its store page, and your passport is about to go inside. The words sound like a promise. They only name the lock model, and tell you nothing about the door it is fitted to.

What is AES?

AES stands for Advanced Encryption Standard. The US standards body NIST published it as FIPS 197 in November 2001 and last updated it in May 2023, with no technical changes. NIST describes it as a block cipher: it works on data in blocks of 128 bits. The standard is public.

The same key locks and unlocks. Whoever holds the key can read the file, and whoever does not, cannot.

What does the 256 mean?

NIST's page names three versions, AES-128, AES-192 and AES-256. The number "indicates the bit length of the associated cryptographic keys". A 256-bit key is 32 bytes.

Each extra bit doubles the number of keys an attacker would have to try. Two apps that both use AES-256 have the same key length. The difference between them is how each one makes the key and where it keeps it.

What does GCM add?

AES is the cipher. GCM is the Galois/Counter Mode, a way of using a block cipher. NIST's SP 800-38D describes it as "an algorithm for authenticated encryption with associated data". The words "authenticated encryption" mean the mode does more than hide the contents. It also adds authentication.

In TegoSafe each locked file carries a 16-byte GCM tag.

Why do the key and the passcode matter more?

The key is the only thing that opens the file. Where it came from decides how strong the lock is.

  • Where it is made. If the maker generates your key on a server, the maker may keep a copy. How to judge a vault app covers this.
  • How it comes from your passcode. A vault can turn the passcode into a key by running it through a slow function many times. A 6-digit passcode has only a million possible values, so the slow function and the length of the passcode set the real strength. The 256 does not help here. A key kept beside the file it locks adds nothing either, so where the key is kept matters too.

Apple's CryptoKit documentation says to "Prefer CryptoKit over lower-level interfaces", and lists symmetric keys and encryption among what it handles. An app that uses it follows that advice. It still leaves the questions above open.

What should a vault app tell you?

A short, checkable answer to each of these, on its own pages:

  1. The algorithm by name, such as AES-256-GCM. "Strong encryption" is not a name.
  2. Where the keys are made. On your phone is the answer you want.
  3. How the passcode becomes a key, and what slows down guessing.
  4. What happens if you forget the passcode, and who can reset it.
  5. What the app cannot protect against, in plain words.
  6. Whether an outside firm has reviewed it, with the firm's name and the date. A review claim with no name cannot be checked.

An app that answers only the first has told you the lock model and nothing else.

Where TegoSafe's key comes from

The cipher is the easy part of the list above. TegoSafe locks each document with AES-256-GCM from Apple's own libraries, not a cipher of its own. The keys are made on your iPhone. Your passcode is stretched 600,000 times and mixed with a secret kept in the iPhone's Keychain, and wrong tries are slowed down. There is no account and no TegoSafe server that could hold a copy of the key.

The scan is free, and so are your first 25 documents. See how it is protected, with an answer to each question in the list.

Is AES-256 unbreakable?

No vault should claim that. The NIST pages describe the standard and make no such promise. A weak passcode, or a copy of the app's files from an unlocked phone, is a way in that the key length does not cover.

Is AES-256 better than AES-128?

It has a longer key, and NIST's page lists it as a separate version. What protects your document also depends on the passcode and where the key is kept.

Does GCM mean the file cannot be changed?

No. Anyone who holds the file can still change or delete it. NIST describes GCM as authenticated encryption, which adds authentication. It does not stop a file from being changed.

Does AES-256-GCM make an app audited?

No. It names the algorithm. An audit is a separate review by an outside firm. Look for the firm's name and the date.

We make TegoSafe, an iPhone app for locking documents. This guide works without it.