Vault Access Control for Beginners: Keypads, Turnstiles, and Audit Trails

A vault door is the least interesting part of vault security. The steel, the bolts, the hinges — they do exactly what they were built to do, every time. What decides whether the contents stay safe is the half-minute before the door opens: who is standing there, what they presented, and whether the system wrote it down. Get those three things right and the door rarely has to prove itself.

Vault access control comes down to three moving parts: credentials, which prove identity; barriers, which control the flow of people; and audit trails, which prove what happened afterward. Here is how each works in practice, and where beginners usually trip.

Credentials: Three Families, and Why One Is Rarely Enough

Every credential falls into one of three families. Mixing families is the whole point.

• Something you know: a PIN, a combination, a spoken phrase.
• Something you have: a key, a smart card, a fob, a physical token.
• Something you are: a fingerprint, a palm print, an iris scan.

A keypad alone is one family. So is a badge. That is why vaults usually require two: badge plus PIN, or badge plus fingerprint. If a badge is lost, the finder still needs the PIN. If a PIN is watched over someone's shoulder, the watcher still needs the badge. Two families mean two separate ways to fail.

Keypads: Simple Hardware, Complicated People

Keypads are cheap, durable, and easy to undermine. The hardware is rarely the problem.

The failures repeat. A department shares one code so nobody gets locked out at shift change. Someone writes the code inside a drawer. A code is never changed after an employee leaves. And a worn keypad — the same four digits polished smooth after two years — hints at more than any manual should.

Habits that prevent most keypad failures

• Assign one PIN per person. Shared codes erase accountability and make the log useless.
• Disable codes the same day someone leaves, not at the end of the month.
• Set a lockout after three to five failed attempts, with a short cooldown.
• Program a duress code that opens the door normally while quietly raising an alert.
• Inspect for wear patterns and rotate codes periodically, avoiding birthdays and sequential digits.

Dual Control and Sequential Entry

Dual control means two authorized people must both act before the vault opens. Neither can do it alone, and both appear in the log. It removes the lone insider as a threat, which is why it is standard for high-value storage.

Split knowledge is a close relative: the combination is divided so no one person knows all of it. The difference is that split knowledge protects the secret itself, while dual control protects the act of opening.

Sequential entry is the mechanical version of the same idea. Doors are arranged so the second will not release until the first has closed and locked. In a small vestibule, that turns a group of five into five separate, individually logged entries. It is slow on purpose.

Turnstiles and Mantraps: One Person at a Time

Tailgating is the friendly crime. Someone holds a door, a second person walks through, and the log shows one entry. Turnstiles make that courtesy impossible.

Optical turnstiles use infrared beams to count bodies, not just credentials. Tripod and full-height models add a physical barrier, and weight sensors catch the person who slips through beside a legitimate user. Mantraps, also called access control vestibules, go further: the first door must close and lock before the second opens.

Worth asking about when you compare systems:

• Anti-passback, which stops one credential entering twice without an exit — useful, but it needs tuning so legitimate repeat entries are not locked out.
• Tailgate alarms, which should alert someone, not just write a line in a file nobody opens.
• Fail-secure interlocks, so a power loss leaves doors closed rather than open.

Turnstiles manage flow and deter the casual intruder. They are not a substitute for the vault door itself or for alarms that respond when someone attacks the barrier directly.

What an Audit Trail Actually Records

A good vault log captures, for every event:

• The timestamp, to the second.
• A person or credential identifier — never a shared code.
• The reader and door involved.
• The result: granted, denied, or timed out.
• Door-held-open duration, forced-door alarms, and tamper signals.
• A camera reference for the matching footage.

Two details decide whether a trail holds up. First, clock accuracy: every reader should sync to the same time source, because a few minutes of drift between two doors makes a sequence impossible to reconstruct. Second, retention: logs kept for a week are not much help when a discrepancy turns up a month later.

How to Review a Trail Without Drowning in It

Nobody reads every line of a log, and nobody should pretend to. Review is a habit, not an event.

1. Start with exceptions. Denied attempts, forced doors, held-open alarms, and out-of-hours entries carry most of the signal.
2. Look for patterns, not single events. A 3 a.m. entry every Tuesday is either a scheduled cleaner or a habit worth questioning.
3. Pull video for the events that matter and confirm the timestamps line up.
4. Check for gaps. A reader that logs nothing for six hours is more suspicious than one that logs too much.
5. Document the review with a date and initials. It shows diligence and answers questions from insurers or auditors later.Photo: Brett Sayles / Pexels