Skip to content

From secret to least privilege

← Learning Atlas · Path 23 of 28 · Learn to handle secrets safely: API keys and environment variables, .gitignore and Git history leaks, revoking and rotating keys, and least privilege.

From secret to least privilegeWatch on YouTube

This is the Learning Atlas from Orbit. Get your invite

Misc tech termsConcepts and methodologyGit fundamentals

  1. Step 1: Secret

    Why this matters here

    Begin with the broad idea of a secret so the learner can recognize many sensitive values before focusing on one credential format.

    In short

    Private information that grants access or reveals something sensitive, such as an API key, password, signing key, or bearer token.

    Full definition of Secret →

    Next: API key ↓

  2. Step 2: API key

    Why this matters here

    An API key makes the abstract risk concrete: it shows how a secret authenticates a machine-to-machine request and can carry real cost or access.

    In short

    A credential that identifies an application or caller to an API, usually as a secret value sent with requests to authorize access to a service.

    Full definition of API key →

    Next: Environment variable ↓

  3. Step 3: Environment variable

    Why this matters here

    Environment variables introduce a practical way to deliver configuration at runtime without copying credentials into tracked source files.

    In short

    A named value supplied by the operating system or process environment, commonly used to configure software without hardcoding deployment-specific settings.

    Full definition of Environment variable →

    Next: .gitignore ↓

  4. Step 4: .gitignore

    Why this matters here

    The ignore file establishes a repository boundary before the learner sees the harder lesson that prevention only works before a secret is committed.

    In short

    A plain text file that specifies intentionally untracked files that Git should ignore and never commit to the repository.

    Full definition of .gitignore →

    Next: Git history ↓

  5. Step 5: Git history

    Why this matters here

    Git history exposes why deletion is not erasure, making the persistence of an accidental commit visible before incident response begins.

    In short

    The recorded sequence of commits in a repository, including earlier versions of files that may no longer exist in the current working tree.

    Full definition of Git history →

    Next: Revoke ↓

  6. Step 6: Revoke

    Why this matters here

    Revocation comes first in response because an exposed credential must be made unusable before cleanup and replacement can be trusted.

    In short

    To invalidate a credential or permission so it can no longer authenticate or authorize the actions it previously allowed.

    Full definition of Revoke →

    Next: Rotation ↓

  7. Step 7: Rotation

    Why this matters here

    Rotation follows revocation by showing how to restore the access that is still needed with a fresh value and a controlled cutover.

    In short

    The planned replacement of an active credential with a new one, followed by updating consumers and retiring the old value.

    Full definition of Rotation →

    Next: Vault ↓

  8. Step 8: Vault

    Why this matters here

    Once the replacement exists, a Vault gives it a deliberate home instead of moving the same secret back into source files or chat.

    In short

    Encrypted local storage for API keys and secrets. Keys are AES-256-GCM encrypted, never sent to Sivants servers, and available across all your projects.

    Full definition of Vault →

    Next: Least privilege ↓

  9. Step 9: Least privilege

    Why this matters here

    Least privilege closes the loop by reducing what the next credential can reach, limiting the blast radius when prevention or handling fails.

    In short

    The security practice of granting each person, process, or credential only the access required for its current job and no more.

    Full definition of Least privilege →

    Continue with The right way to write a prompt: talk, loop, or spell it out →