The person responsible for maintaining a list of people authorized to access secure areas is the security manager or facility security officer (FSO) who owns the access-control program, not the IT team that runs the badge system and usually not the front-desk staff who hand out badges. That individual holds formal accountability for the list's accuracy; system administrators and department supervisors hold execution duties that feed it. Federal facilities under the Interagency Security Committee's standards and organizations following ISO 27001 split the work the same way: one named owner, several feeders, and an audit trail that proves both did their jobs.
The named owner behind every access list
Accountability for an authorized-person list sits with a single position at almost every organization that takes physical security seriously, and that position is usually called the facility security officer, security manager, or physical security lead. In U.S. federal contracting, the FSO is the person designated by the contractor to supervise security, including control of access to secure spaces, per the National Industrial Security Program Operating Manual. That manual, which governs contractor facilities handling classified information, places the authorized-access roster squarely in the FSO's domain rather than in general management.
ISO/IEC 27001 makes the same assignment in less specific language. Its access-control requirements, spelled out in Annex A of the 2022 revision, expect an organization to define who approves access, who reviews it, and how it is revoked, and auditors look for a single accountable role rather than a diffuse committee. An owner without a named backup is a common finding, because the standard effectively asks what happens on the day the security manager is on leave.
The owner's job is not data entry. It is deciding who gets on the list, approving additions, ordering removals, and signing off on periodic reviews. The badge software generates the printable roster, but the badge software is a tool, not an accountable party. When an auditor asks who vouched for a contractor's presence in a server room six months ago, "the system" is not an acceptable answer.
Get this wrong and the failure is easy to spot. A site where no one can name the access-list owner will almost always show stale entries, departed staff with active badges, and no documented review dates, which is exactly what regulators cite in enforcement actions and what plaintiffs point to after an incident.
Why the badging system administrator is never the accountable party
Physical access-control systems such as Lenel OnGuard, Genetec Security Center, and Avigilon Unity are administered by a security systems administrator whose job is to make the software work, provision cards, program door schedules, and maintain integrations with HR and video systems. That person holds the keys to the database. Accountability for the contents of the authorization list sits elsewhere, with the security manager who signs off on who should be in the database at all.
This split matters because it is the most commonly blurred boundary in the whole process. If you let the system administrator decide who gets access, you have handed a technical operator a governance decision with no oversight. Most mature programs write this into policy explicitly: the administrator executes changes, the security manager approves them, and neither may do the other's job without a documented exception.
There is a practical test for whether the split is real. Ask the administrator what they would do if a director emailed asking for their own badge authority to be expanded to a restricted laboratory. In a program with a clean boundary, the answer is that the request goes to the security manager for approval. In a program where the roles have collapsed, the administrator just does it.
Some small organizations genuinely cannot separate the two roles because one person runs both the system and the program. That is a structural weakness rather than a reason to merge the duties. The compensating control is a second signature, typically from the facility director or operations head, on every addition to a restricted area.
Which department supplies the names — and which one only consumes them
Human resources owns the employment facts that make a name valid: who was hired, when they started, what department they joined, and when they left. HR does not own the access list itself, but no list can stay accurate without a reliable feed from HR, and the most common root cause of a stale roster is a broken connection between HR and security. Payroll and offboarding data are the two most useful HR signals a security manager has.
Department supervisors carry the functional judgment. The supervisor knows whether a maintenance technician actually needs the chemical storage room, and knows when a researcher's project ends and the lab badge should. A policy that requires supervisor sign-off on each request creates a record that answers the question "who asked for this" far more reliably than an email chain.
Contractor coordinators add a third feeder. Contract staff turn over faster than employees, and their access often expires on a date tied to a statement of work rather than to employment. Organizations that treat contractors as honorary employees in their access database end up with the largest clusters of stale entries.
The clean model looks like a supply chain. HR and supervisors supply names and justifications, security holds the authoritative list, and the system administrator reflects the list in the badge database. Finance, legal, IT, and everyone else consume the list without editing it.
What an approved-list workflow looks like in practice
Building the workflow once, in the right order, prevents most of the failures described later. The sequence below matches how security programs under ISO 27001 and the Interagency Security Committee's Facility Security Level framework typically structure physical access authorization for controlled and restricted spaces.
1: Classify the space first: public, controlled, or restricted, using your organization's definitions, because the approval authority changes at each tier. 2: Identify the accountable owner in writing — name the FSO or security manager and a designated alternate in the access-control policy. 3: Define who may request access: the employee, their supervisor, or a project lead, with a required business justification. 4: Establish approval authority per tier: supervisor for controlled areas, security manager plus facility director for restricted areas, and the FSO for classified or highly sensitive spaces. 5: Route the request through a documented channel, so the approval is recorded in the system rather than in a hallway conversation. 6: Have the security manager approve or deny and record the decision and date. 7: Have the system administrator provision the badge and door schedules only after the approval record exists. 8: Schedule the review cadence: at minimum quarterly for restricted areas and annually for controlled areas, with a full reconciliation after any major reorganization. 9: Tie removal triggers to HR events, contract end dates, and supervisor notifications, and require the security manager to confirm revocation within a defined window. 10: Log every change with who requested it, who approved it, who executed it, and when, then retain the log for the period your auditor or regulator requires.
Failure handling matters as much as the happy path. If HR fails to notify security of a termination, the revocation clock does not start. Most programs close that gap by requiring the system administrator to run a weekly comparison of active badges against the current employee roster and escalate mismatches to the security manager.
Where access authorization shifts for classified and restricted spaces
For facilities handling classified information under the National Industrial Security Program, the FSO's authority is not merely internal policy. The FSO maintains the facility's access roster and is responsible for ensuring only cleared, need-to-know personnel enter classified spaces, and the Defense Counterintelligence and Security Agency, which administers the program, expects that roster to be current and auditable during a security vulnerability assessment.
The Interagency Security Committee's standards for federal facilities use a Facility Security Level scale from I to V to determine how much oversight a space requires, and higher levels bring more formal documentation of who may enter. A Level V facility with a restricted area will typically require an approved access list with named approvers, review intervals, and records that survive personnel turnover.
Cleared contractor access adds a time dimension. A person's security clearance eligibility and their need-to-know are separate determinations, and the FSO must confirm both before adding a name to a classified-space roster. An employee whose clearance is suspended mid-project comes off the list regardless of what the supervisor wants.
This tier is where organizations most often discover that their access policy was written for offices and never adapted. A general badge policy that lets supervisors approve access is fine for a supply closet and unacceptable for a Sensitive Compartmented Information Facility, where the approving authority is defined by regulation rather than by managerial convenience.
When the security manager is unavailable: delegation and continuity
The access list must survive vacations, illnesses, and departures, and that means the policy has to name an alternate with the same authority as the primary. ISO 27001 auditors routinely ask for evidence that access approvals continued during the owner's absence, and a gap in the approval log during a two-week leave is treated as a control failure rather than a scheduling accident.
Delegation should be written, time-bounded, and specific. An acting FSO appointed for a defined period with the same approval rights is a control. An informal arrangement where a colleague approves requests because the manager is out is not, because the record cannot show that the delegate had the authority to sign.
Continuity also covers the painful case of the owner leaving. A transition plan should name the successor, transfer the approval records, and have the successor re-review the full restricted-area roster within a set period, usually 30 days, before making any new approvals. Programs that skip the re-review inherit whatever the previous owner was willing to approve.
The reverse failure is just as common: a delegated approver who keeps approving after the delegation expires. Build an expiry date into the delegation record and have the system administrator flag approvals made after that date during the next audit cycle.
How system owners hold accountability for the list itself
Information security teams own a parallel obligation, because the access list is data, and data needs an owner, a classification, and protection. The system owner of the physical access-control platform is accountable for the integrity, availability, and confidentiality of the roster and its audit logs, even though they do not decide who is on it. NIST's Special Publication 800-53, in its access control family, treats account management as a formal control with defined roles and review requirements, which many organizations map to their badge system.
That accountability shows up in concrete duties: controlling who can edit the database, backing up the roster and logs, restricting export of the list, and ensuring the audit trail cannot be silently altered. A security manager who approves access into a system whose logs anyone can edit has an accountability problem they did not create.
The system owner also owns the review evidence. When the security manager conducts a quarterly roster review, the system owner should be able to produce a report showing every active badge, every door it opens, and every change since the last review. If that report takes three days to assemble by hand, the review will not happen on schedule.
Separating these two accountabilities is what makes the whole structure auditable. The security manager answers "should this person be here," and the system owner answers "can we prove who is here and who changed it."
Who audits the list, and how often
Independent verification closes the loop, and the auditing function belongs to internal audit, compliance, or an external assessor rather than to the security department itself. Self-audits are useful for finding problems but weak as assurance, because the same person who approved an entry is judging whether the entry was appropriate.
Review cadence is usually set by risk tier rather than by convenience. Restricted and classified spaces warrant quarterly reviews, controlled spaces annual reviews, and public areas need only periodic spot checks. The Federal Information Security Modernization Act's annual assessment cycle shapes how many federal-adjacent organizations schedule their access reviews, and the Defense Counterintelligence and Security Agency's assessment cycle does the same for cleared contractor facilities.
Auditors should sample, not merely count. Counting badges proves the database is populated; sampling twenty restricted-area entries and tracing each to an approved request, a current HR status, and a supervisor justification proves the list means something.
The audit output should name the owner and the due date for each finding. A finding of "stale contractor entries" with no name attached will still be open at the next audit, which is the pattern that turns a minor issue into a compliance citation.
The failure cases that expose unclear ownership
The most expensive access-list failures are not exotic. They are the predictable result of a broken handoff, and each one maps to a specific role that should have acted.
| Failure case | Who should have caught it | Typical consequence |
|---|---|---|
| Terminated employee badge stays active 45 days | HR notification to security; system administrator's weekly reconciliation | Unauthorized entry risk; audit finding |
| Contractor badge outlives the statement of work | Contractor coordinator and security manager's review | Restricted-area access by a non-cleared person |
| Supervisor approves access they have no authority to grant | Security manager's approval gate | Unauthorized expansion; possible policy violation |
| Roster edited directly in the badge database, no approval record | System administrator's change control and audit log review | Unexplainable access history during investigation |
| No alternate approver during owner's leave | Policy owner's continuity plan | Access requests stall or bypass the control |
The 45-day revocation window is worth dwelling on because it is measurable. If HR sends termination data to security the same business day and security revokes within one business day, the exposure is two days. Every additional handoff adds days, and organizations that consolidate the HR-to-security handoff into a single automated feed consistently report shorter windows than those relying on email.
Edge scenarios test the structure more than routine cases. A merger brings two badge systems, two rosters, and two owners, and the question of whose list is authoritative has to be answered before the systems are merged. A long-term contractor working across three sites may appear on three lists with three different approvals, and the security manager at each site has to confirm the justification independently.
FAQ
Does IT own the access list because IT runs the badge system?
No. IT or the security systems administrator operates the platform that stores the list, but accountability for whether names belong on it rests with the security manager or FSO. Splitting the roles is the standard arrangement in ISO 27001-aligned programs, and merging them removes the check that catches unauthorized additions.
What happens if the named owner of the access list leaves the organization?
The policy should name a successor and require a full re-review of restricted-area rosters within 30 days of the transition. Without that re-review, the successor inherits approvals they never evaluated, and auditors treat unreviewed inherited access as a control gap rather than as continuity.
How often should the authorized-person list be reviewed?
Quarterly for restricted and classified spaces, annually for controlled areas, and by spot check for public zones. The cadence follows the risk tier of the space rather than organizational preference, and federal-adjacent programs often align their schedule with the annual FISMA assessment cycle.
Can a supervisor approve access for their own staff?
Only if the policy grants that authority for the specific space tier. Supervisors commonly approve controlled-area access and almost never approve classified or restricted-area access, which requires the security manager or FSO plus a facility-level signature. Self-approval by a supervisor for their own badge is a conflict of interest in every tier.
What is the difference between the access authorization list and the cardholder database?
The authorization list is the governance record of who is approved to be in a space and why; the cardholder database is the technical record of which credential opens which door. They should agree, but the list is the source of truth. An entry in the database with no matching approval on the list is the most common audit finding in physical access control.
Who confirms that a cleared contractor still needs access to a classified space?
The FSO confirms both clearance eligibility and need-to-know before adding a name, and re-confirms need-to-know at each review cycle. A supervisor's request alone is insufficient, because need-to-know is a separate determination from operational preference and the FSO is the designated authority for the facility.
How quickly should access be removed after someone leaves?
The target is same-day or next-business-day revocation once security receives termination notice, which requires an automated HR feed rather than email. Every manual handoff adds delay; a weekly reconciliation between active badges and the current employee roster catches whatever the automated feed misses.
Do small organizations need a separate security manager and system administrator?
Not always, but they should still separate the approval from the execution with a second signature, typically from the facility director. The risk in a small organization is that one person holds both roles and no one reviews their decisions, which is a structural weakness even when the person is trustworthy.