jperezduerto.info
Security in depth · Unit 22 · Lesson 13 of 44
Local secrets need a lifecycle
Separate deleting a local secret from ending the access it grants.
Helpful before thisLinux privilege escalation
After this lesson you can
- Specify separate evidence for removing a secret copy and retiring its authority.
A deleted file can leave a working key behind.
Two separate lifecycles
A local secret is a copy of something another system accepts as authority. Deleting that copy changes storage; revocation changes acceptance. Rotation introduces a replacement, but the old credential may remain valid during a transition. A reliable review distinguishes all three.
Disk encryption protects some storage situations. It does not prevent an already authorized process from reading an unlocked file, and it cannot undo an earlier disclosure.
Supplied record: the garden club
This fictional review contains no usable secret. Mira owns the club’s newsletter service. Its incident ticket records:
Sample configuration: key identifier K17 removed today.
Issuer inventory: K17 still active, newsletter sending only.
Dependency register: two scheduled jobs use K17.
Backup catalogue: yesterday’s sample retained for thirty days.
Assume the issuer inventory is current and supports explicit key revocation. The record confirms one copy was removed. It does not establish whether anyone copied K17 or used it without approval.
A defensible closure decision
Mira needs a coordinated replacement or revocation decision, an inventory of dependent jobs, and treatment of retained copies under the backup policy. Deleting every backup immediately could conflict with recovery needs; leaving them accessible without review is not a solution either.
Write three closure conditions: the issuer no longer accepts K17, both approved jobs work with their intended replacement, and remaining copies have documented access and retention treatment. Keep unknown historical use separate from these confirmed outcomes.
Check yourself
No timer. No penalties. Read the explanation and try again whenever you like.
This lesson’s questions have changed. Your reading progress is saved; review the updated questions.
-
Mira has deleted the sample file, but key K17 is still active. Which closure statement fits the supplied record?
Show the answer
Correct answer: One copy is removed; retirement of K17 and migration of its jobs still need evidence. The ticket proves a file change. The issuer still accepts K17, and two jobs depend on it, so both authority and continuity remain open.
Try it
- WriteWrite a closure note for Mira with three rows: copies, credential, and dependent jobs. Give each an owner, a required confirmation, and one remaining uncertainty.