When opening and closing a security container, you are required to document the action in the container's security container register (Standard Form 700, or an approved equivalent) — recording the date, time, container identifier, your name, and the purpose each time the container is unlocked and relocked. This record creates an auditable chain of custody for classified material. The log entry itself is a security control, not paperwork. A missing or altered entry is treated as a potential compromise until proven otherwise.
The mechanism: why a signature gates a combination
A security container is a controlled-access volume. The lock proves authorization at the moment of entry; the register proves accountability across time. These are different controls solving different problems. The lock cannot tell an investigator who opened the container at 02:14 on a Sunday. Only the register can.
The register works because it forces a one-to-one coupling between a physical event (the door swinging open) and an identity (a cleared person with need-to-know). Each entry captures four data points that together reconstruct the event: who, when, which container, and why. The "why" field is the one most often skipped and the one auditors weight most heavily, because purpose establishes whether the access fell inside the person's authorized scope.
The counterintuitive detail: the register's deterrent value exceeds its forensic value. Most unauthorized-access attempts are deterred not by cameras but by the knowledge that a signature will exist. The log is read before it is ever audited.
Quantified context: what the record actually contains
A compliant entry has a defined field set. Omitting any field breaks the chain. Typical required fields:
Date and time of opening and of closing (both, not just one) Container identifier or location code Printed name and signature of the person opening and closing Purpose of access or the material involved Signature of a second person when two-person integrity is required Notation of any anomaly, forced entry, or combination change
Timing thresholds matter. Most facilities require the closing entry within the same duty period as the opening. A container left open and unattended for more than a defined interval — commonly 15 to 30 minutes depending on local policy — is a reportable security incident even if nothing is missing. The window exists because an open, unattended container has no access control at all.
Retention is typically tied to the classification level and the inspection cycle. Registers are commonly retained for at least two years and often for the life of the container plus one audit cycle. When a container is decommissioned, the register is not simply discarded; it is closed out and archived per the facility's records schedule.
Edge cases: when the routine breaks
The register's rules bend at predictable points, and each bend is where real facilities get cited.
Combination changes are logged in the register itself, with the date, the person making the change, and confirmation that the new combination was tested before the container was closed. A change logged after the fact is an audit finding.
Two-person integrity alters the signature requirement. When policy mandates that no single person may have both the combination and the container open alone, the register must show two distinct signatures for the same open interval. One person signing twice defeats the control and is treated as a single-person access.
Shared containers create ambiguity. When several offices use one container, the register must still attribute every opening to a named individual, not a section. "Opened by vault custodian" fails attribution when the custodian role rotates.
After-hours and emergency access is the highest-risk edge case. Fire, medical emergency, or maintenance can force an opening outside normal procedure. The register still gets an entry, often within a defined short window afterward, with the reason documented and a supervisor's acknowledgment.
Misconceptions that fail audits
The most common misconception is that the register documents possession of the material. It does not. It documents access to the container. Material accountability lives in a separate accountability record. Conflating the two means a container can show a clean register while individual documents inside are unaccounted for.
A second misconception: backfilling entries is acceptable if the facts are accurate. It is not. An entry made after the fact, even truthfully, destroys the contemporaneity that gives the log its evidentiary weight. Auditors compare ink, sequence, and timing against access-control logs.
A third: the register is a facilities document. It is a security document, owned by the security office, subject to inspection, and discoverable. Treating it as office stationery is how registers end up with coffee stains, torn pages, and missing months.
Red flags that trigger a formal inquiry:
A gap in the date sequence with no corresponding anomaly note An opening entry with no matching closing entry Signatures that match another entry's handwriting Pages removed, taped, or rewritten A combination change with no test confirmation Access times that conflict with badge or alarm logs
Comparison: register formats and their tradeoffs
| Format | Contemporaneity | Tamper evidence | Audit speed | Best fit |
|---|---|---|---|---|
| Paper log bound in container | High | Moderate | Slow | Low-volume, single-custodian |
| Electronic access log with badge | High | High | Fast | High-traffic shared containers |
| Hybrid paper plus electronic | High | High | Moderate | Facilities mid-transition |
| Standalone spreadsheet | Low | Low | Fast | Not acceptable for classified |
| Unsigned clipboard sheet | Low | Very low | Fast | Fails audit |
The pattern: tamper evidence and audit speed trade against each other, and paper wins on neither at scale. Electronic logs win on both only when the identity binding is real — a badge swipe tied to a named, cleared person, not a shared PIN.
Timeline: what a compliant open-and-close cycle looks like
| Stage | Action | Typical window |
|---|---|---|
| Pre-open | Verify need-to-know and purpose | Before unlocking |
| Open | Record date, time, name, purpose | At the moment of opening |
| Access | Material handled under supervision if required | Duration of task |
| Close | Record date, time, name, relock confirmation | Same duty period |
| Anomaly note | Document any irregularity | Before end of shift |
| Supervisor review | Acknowledge after-hours or emergency entries | Within one duty day |
| Periodic audit | Reconcile register against access logs | Per inspection cycle |
The single most-missed stage is the relock confirmation. An entry that records the closing time but not verification that the lock engaged leaves the container's status ambiguous. A door that looks shut but did not latch is a common real-world failure.
Practical actions and thresholds
Treat the register as a living control with measurable performance. Concrete steps:
Standardize the field set facility-wide and print it on every page so no entry can omit a required field by habit. Set an unattended-open threshold (commonly 15 to 30 minutes) and post it at the container. Require the closing entry to include an explicit relock-confirmation notation, not just a time. Reconcile the register against badge and alarm logs at least monthly; treat mismatches as incidents, not clerical errors. Log combination changes in the register with a test confirmation before the container is closed. Train on the "why" field specifically, because purpose is the field auditors weight most and staff skip most.
The reconciliation step is where most programs improve fastest. Access-control systems already record every badge event. Comparing those events to register entries exposes missing closes, ghost opens, and shared-credential problems in a single pass.
Limitations and what the record cannot prove
The register proves that a named person claimed access at a stated time. It does not prove what they did, what they removed, or whether the combination was shared. A perfect register can coexist with internal theft, because the log tracks the container, not the contents.
Electronic systems introduce their own limits. A badge event proves a credential was presented, not that the named holder presented it. Shared credentials, tailgating, and propped doors all defeat the log while leaving it pristine. Paper registers defeat themselves through illegibility, lost pages, and backfilling.
No register format substitutes for physical inspection. The lock, the door, and the container's structural integrity are separate controls, and a clean log over a compromised container is the most dangerous combination in the file.
This article is general educational information about security-container documentation practices, not a legal opinion, compliance determination, or facility-specific procedure. Actual requirements depend on your classification level, agency, and local security policy, so confirm the applicable standard with your facility security officer or a qualified local professional before relying on any threshold described here.