top of page

Cross-Agency Badging: The Limits of Facility Access Reciprocity

Writer: kate frese
kate frese
Nov 5
2 min read

Updated: Nov 9

The Credential You Trust but Did Not Issue

Federal employees increasingly work across agency lines: detailees, joint task forces, shared campuses, and interagency facilities. The credential at the door belongs to another agency's identity infrastructure, and your PACS can read it, which is not the same as your program owning it. Cross-agency badging reciprocity is real, valuable, and frequently overestimated as an authorization control.

Reciprocity Authenticates, It Does Not Authorize

The FICAM architecture and the Federal PIV credential give a facility reasonable assurance about who is holding the card: the credential is authentic, the certificate is valid, the person is who the card says. What the credential does not carry is any statement about what that person should access inside your facility. Authorization decisions, which floors, which labs, which CUI areas, remain entirely local. A cross-agency badge at your reader means you have a verified identity, not a verified permission.

Sponsorship Still Owns the Visit

Under NIST SP 800-53 controls PS-7 and PE-3 as applied to interagency visits, the host organization still exercises visitor control. Someone inside your agency sponsors the visit, the visit duration is bounded, and the access granted is scoped to the mission of the visit, not the seniority of the visitor. The failure pattern at shared campuses is treating a fellow federal credential as an implicit all-access grant, which converts your authorization boundary into a courtesy.

Three Credential Tiers, Not Two

Facility PACS policies should draw explicit lines between three populations: your own enrolled personnel, personnel holding Federal PIV credentials from other agencies, and everyone else. The PIV-holder tier is legitimate but its access profile should be drafted deliberately: authenticated identity, escort or unescorted per local policy, floor-level restrictions, and time-bounded validity. Configuration should revolve the local authorization on top of the federal authentication rather than inheriting access from it.

Auditing the Trust

Each population tier should have its own audit trail. If your PACS can report cross-agency credential uses separately, you get visibility into how much of your daily traffic is riding on reciprocity trust, and that visibility lets you manage the controls. The security posture is material for interagency facilities under NIST RMF review.

Schedule a Consultation

Schedule a consultation to review how your PACS treats credentials your program did not issue.

This content is provided for general informational purposes only and does not constitute legal or regulatory advice. Compliance requirements and regulations are subject to change. Blue Violet Security, LLC recommends consulting with appropriate legal and regulatory counsel before making compliance determinations.

Comments


bottom of page