Security Guides

What an Access-Control Log Can—and Can’t—Tell You

By Blue Storm Security · 2026.11.22 · 4 min read

What an Access-Control Log Can—and Can’t—Tell You

An access-control event log is useful for establishing what the system recorded at a particular reader and time. It may show that a credential was accepted or denied, or that a configured door sensor reported a change in status. That evidence can help organize an incident review, but it is a record of system activity—not a complete account of who entered or what happened.

Read the event fields before drawing a conclusion

Start with the fields in the individual entry rather than its label alone. Depending on the access-control system, a record may include the door or reader, a credential number or user record, a timestamp, and a result such as “granted” or “denied.” The event name describes how the system classified the transaction. A granted entry means the system accepted the presented credential for access at that reader; a denied entry means it did not accept that attempt under the rules applied at the time.

Door-status entries describe a different kind of event. If the installation includes a door-position sensor and the relevant event settings are enabled, the log may record conditions such as a door being held open. A credential result and a door-state alert answer different questions: one concerns an access decision, the other concerns a sensed door condition. When reviewing a report, note which kind of event each row represents and avoid treating every row as proof that a person passed through the opening.

Separate credential activity from a person’s actions

A credential is a token or record recognized by the system; it is not necessarily a verified identification of the person holding it. For example, a log associated with an employee’s card can establish that the card’s record was accepted, but the event alone cannot establish who presented the card. A card might be shared, misplaced, or used by someone other than its assigned holder. The log also may not show whether a person actually crossed the threshold after a grant.

Keep these distinctions clear when describing an incident. “The system recorded a granted event for this credential at this reader” is narrower and more useful than “this person entered.” A denied attempt is also specific: it records a failed access decision, not the reason a person was present or what happened afterward. If the system records door position, that information can add context about the opening, but it still does not identify everyone who passed through it. Treat the event record as one piece of the account, not a substitute for direct observation.

Build a focused timeline for the incident

Reviewing every event in a large system can obscure the sequence that matters. Use an ordered review so that each step answers a concrete question:

  1. Anchor the review. Write down the approximate incident time and the specific door or reader involved. Record how the incident time was established, such as a report or a separate camera clip.
  2. Set a useful window. Examine entries for that door before and after the estimated time, not just the single event closest to it. A surrounding window can reveal a denied attempt, a later grant, or a door-status event that changes the sequence you are considering.
  3. Compare related records. If a person could have moved through another controlled entrance, review the relevant nearby reader events for the same period. Look for a sequence that supports or contradicts a specific possibility rather than assuming that two close timestamps describe the same person.
  4. Correlate another record when available. Video may help answer whether someone crossed the threshold; an access log may help identify the time and credential event to examine. Keep the records’ timestamps and viewpoints in mind as you compare them.

For instance, suppose a report places an incident near a staff entrance. A granted credential event at that door gives the review a time and access point to investigate. A nearby camera view, if available, could help determine whether someone passed through. The log alone does not resolve that visual question, so describe separately what the access system recorded and what the other record shows.

Make records useful before an incident

Logs help only when the relevant entries still exist and can be interpreted later. Retention and storage depend on the system and its configuration, so set a review interval that accounts for how long it may take to notice an incident and begin examining it. A short retention period can leave no access record by the time a delayed concern is reported; keeping records longer than needed can create unnecessary exposure of access information. Choose a period deliberately rather than assuming the default fits the property.

Access to event records matters, too. Decide who needs permission to view or export logs and who can change access settings that affect what gets recorded. For an incident review, note who examined or exported the records, when they did so, and what question they were trying to answer. This context makes a later handoff easier to follow and helps distinguish an original system entry from a report prepared for review. Readers in St. Petersburg can find contact information for Anderson Access Control.

Adjacent intel

More from the watch log

Plan Security-Camera Coverage for Fewer Blind Spots
Security Guides

Plan Security-Camera Coverage for Fewer Blind Spots

Map important approaches, balance a wide camera view with usable detail, account for changing light, and test recorded footage before relyi…

Before You Add a Smart Lock to a Home Security System
Security Guides

Before You Add a Smart Lock to a Home Security System

Check door fit, define the integration you actually want, plan credential changes, and test the lock’s connected and manual operation befor…

Wired or Wireless Home Security: Which Fits Your Home?
Security Guides

Wired or Wireless Home Security: Which Fits Your Home?

Compare wired and wireless home security by installation needs, building constraints, sensor flexibility, and ongoing maintenance before ch…