← Back to Concept Contrast

Concept Contrast Fable

Access control and permission models

Conclusion first:Access control is the iron lock on the warehouse door—it verifies who you are and whether you should enter. The permission model is the key register on the desk—it records who can enter which door, when keys were issued, and whether they were recovered after departure. No matter how expensive the lock is, it cannot manage a key register that is not updated—if the register is wrong, the lock only helps you let the wrong people in faster.

Access control is the iron lock on the warehouse door—it verifies who you are and whether you should enter. The permission model is the key register on the desk—it records who can enter which door, when keys were issued, and whether they were recovered after departure. No matter how expensive the lock is, it cannot manage a key register that is not updated—if the register is wrong, the lock only helps you let the wrong people in faster.

Fable

The Iron Lock and the Key Register

Sister Fang managed a large warehouse divided into north and south zones. She first installed good locks, then gave each worker a key. The gatekeeper only recognized keys: if the key was right, the door opened; if not, it was blocked. At first the warehouse became much quieter.

Half a year later something strange happened. Xiao Li transferred from the fabric section to the accounts office but still had the key to the south zone; the temp worker A Quan had left three months ago but his old key could still open the back door; the new supervisor needed to enter the north zone for inventory but no one knew which key to give him. The locks weren't broken; the key register was a mess.

Sister Fang first replaced the lock with a more expensive one. But an expensive lock still only judges whether a key is genuine; it does not know that Xiao Li's role has changed, nor does it remind anyone that A-Quan has left. When an audit came, the auditor did not look at the lock first, but asked: who can enter which door, who approves, how often is it reviewed, and who collects the key when someone leaves?

Only then did Sister Fang redo the key register. Each department listed the areas it needed to enter, and the person in charge confirmed quarterly; keys expired automatically, and renewal required a new stamp; on the day someone left, the gatehouse collected and deactivated keys according to the list. Exceptional entry required a written reason and time limit.

The warehouse did not change its locks again, yet many hidden dangers were reduced. The action at the door remained "verify the key, then let through," while the key register determined who should hold which type of key, and how those rights were issued, changed, and revoked.

Sister Fang later redid the key register: when a role changed, the keys changed with it; when a temp worker's term ended, the keys were automatically recalled; when a supervisor did inventory, only the inventory window and the corresponding area were granted. The gatekeeper still used keys to open doors, but the rules behind the keys were finally clear.

When the auditor reviewed, she looked at the key register first, then the door lock. A good lock can stop people without keys, but it cannot answer who should have keys, when they expire, or how temporary exceptions are approved. Only after Sister Fang separated these two things did the warehouse become truly secure.

Later, when the government project came up for acceptance, the auditor tried both the door lock and reviewed the key register. Sister Fang finally distinguished: the lock governs whether a single entry passes, while the key register governs where the rights come from, when they should change, and who is responsible. Focusing only on the door means missing the most dangerous changes in a permission's lifetime.

Access control

Technical mechanisms that enforce authentication and authorization decisions at runtime, including authentication protocols, gateway interception, and session management, ensuring that "people who should not get in cannot get in."

Permission model

A policy framework defining "who can do what under what conditions," including role definitions, permission inheritance, approval workflows and periodic review systems; it is the basis for access control enforcement.

Story Mapping

  • Iron lock (access control): a runtime enforcement mechanism that verifies identity and determines release
  • Key register (permission model): policy definition and lifecycle management, determining who should have keys
  • Xiao Li could still enter the South District after changing roles: lagging updates to the permission model let in people who shouldn't have access
  • Amin isn't on the roster: permission model out of sync caused access control to block someone who should have been allowed
  • Three things that don't change the lock: governance improvements to the permission model don't require replacing access control hardware
  • The auditor flipped through the key register for two hours: the focus of compliance review is the permission model, not the technical implementation

Applying it to Andy Ren Xu's project

When a client does a security review and asks how you handle permission management—that question actually asks two things. Split your answer into two parts: the first covers your access control technology stack (OAuth, API gateway, session policy), the second covers your permission model governance process (who defines roles, who approves permissions, how many hours until revocation takes effect after departure). If both parts are only one line, it means you have a lock but no register, or a register but no lock—a security review won't let any line pass empty.

京ICP备2026014272号