top of page
Federal Security Compliance


The Uncleared Badge Office: Who Vets the People Who Issue Credentials
Most facility security programs spend their vetting attention on the population that carries badges. Far less attention lands on the small group that manufactures them. The badge office can enroll an identity, alter an access level, print a replacement, and quietly ignore an expiration date. That is a concentration of capability that no other role in the building holds, and in many organizations it sits with the least scrutinized personnel on the roster. Blue Violet Security,
kate frese
5 hours ago2 min read


The Urgent Badge Request: Social Engineering Against Access Administration
The Attack That Bypasses Every Reader Modern PACS hardware is genuinely difficult to defeat at the door: cryptography, challenge-response, tamper detection. So attackers do not attack the door. They attack the office that issues credentials. The single most productive exploit against an access control program is an urgent request that reaches the badge office by email or phone, invoking authority and a deadline, and produces a working credential hours before anyone checks its
kate frese
Nov 62 min read


Cross-Agency Badging: The Limits of Facility Access Reciprocity
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
kate frese
Nov 52 min read


Access Appeals and Due Process: What Happens After a Badge Is Pulled
Revocation Is a Decision, Not Just a Switch Most access control programs treat revocation as a technical action: the credential is disabled, the record grayed out, the matter closed. But for the person holding the badge, revocation is an adverse action with due process implications, and for the facility, the appeal that follows is a test of whether the decision was governance or improvisation. Federal facilities that pull credentials without documented criteria and a review p
kate frese
Nov 42 min read


Interns, Seasonals, and Term Employees: Short-Term Access, Full-Length Risk
The Population With No Expiration Discipline Every organization carries a population whose badges should come with a countdown clock: interns, seasonal staff, term employees, detailees, and contract-to-hire personnel. In practice, short-term credentials routinely outlive their owners' appointments. A summer intern's badge activates in June with a mental note to disable it in August, and the note never becomes an action. The credential sits active in the PACS for years, attach
kate frese
Nov 22 min read


Contract Turnover: When the Guard Force Changes Overnight
The Riskiest Week in Entry Control Is the One Nobody Plans For Every guard services contract ends. Yet few facility security plans treat the transition between the outgoing and incoming force as the security event it actually is. The people who know your post orders, your duress codes, your keys, and your rosters walk out on the last day, and a new set walks in the next morning. For a window measured in days, your entry control operation is new at exactly the moment it is mos
kate frese
Nov 12 min read
Fitness for Duty at the Door: When Behavior, Not the Badge, Is the Risk
The Assumption Behind Every Reader Every access decision is really two decisions. The first is authorization, which the system handles: the credential is valid, the clearance holds, the door opens. The second is never encoded anywhere: is this person fit to be here right now? Fitness for duty is a personnel security concern with a physical access surface. The person swiping in is the same person every day, but their condition is not. Impairment, extreme distress, and coercion
kate frese
Oct 302 min read
The Notice-Period Risk Window: A Resignation Letter Is Not Deactivation
The Gap Nobody Schedules Termination workflows get the attention. Offboarding checklists, same-day deactivation, and last-day escort procedures exist across most federal programs. But before termination comes the notice period: two weeks to two months in which a departing employee still holds full access while their commitment to the organization has already ended. This is a population with a different risk profile, and almost no program treats it that way. The badge works th
kate frese
Oct 292 min read
Just-in-Time Access: Short-Window Credentials That Sunset Themselves
The Liability of Standing Access Most credential programs still run on permanence. A person needs access for a four-hour task, so they are issued a credential that works until someone remembers to remove it. The gap between the task and the term is pure accumulated risk, and in federal environments it is exactly what assessors probe for. Just-in-time access flips the default. Credentials are issued for the window the work actually requires, carry a hard expiration, and termin
kate frese
Oct 282 min read
The Shared Credential Problem: Why 'Just Use Mine' Breaks Accountability
The Convenience That Ends Investigations Every federal access control program rests on one assumption: the credential and the person holding it are the same. When a badge is lent, borrowed, or passed hand-to-hand, that assumption fails quietly. The audit log still records a valid entry, but it no longer records who actually walked through the door. The problem rarely announces itself. A technician forgets a badge at home. A supervisor lends theirs to speed up a delivery. A ni
kate frese
Oct 272 min read
'The Executive Exception: When Leadership Bends the Rules'
Every access control policy meets its real test in the same place: the door the senior leader does not want to badge through. What happens next decides what the policy actually is. When the exception is granted informally, quietly, or through a protocol that exists only for the powerful, the organization has published two policies, the written one and the real one, and trained every employee which one governs. Federal expectations are blunt about this: access is a function of
kate frese
Oct 232 min read
'Credential Destruction: The End of the Lifecycle Nobody Watches'
Access control is built around issuance: enrollment, activation, and audit all get attention because they are where access begins. Then a credential is returned, the PACS deactivates it, and the physical card goes into a drawer, a box, or a shredder nobody supervises. The electronic half of the lifecycle just ended; the physical half quietly persists. A deactivated card is harmless, until a clone, a legacy system, or a downstream hole gives it new life. As a technical integra
kate frese
Oct 232 min read
'Pretext Testing: Auditing the Human Layer of Access Control'
Physical security gets tested constantly: door forces, alarm activations, credential misuse. The human layer almost never does. Yet in most real intrusions, the weak link is not a failed reader but a persuaded person: an employee who holds the door for a "tech from the phone company," a guard who accepts a story because challenging it feels rude. Pretext testing, structured attempts to gain access using invented identities and scenarios, is how an organization finds those sea
kate frese
Oct 232 min read
'Separation of Duties for Access Administration: No Single Hand Creates Access'
Cybersecurity teams treat separation of duties as a foundation: no one person can both create a payment and approve it. Physical access administration rarely gets the same discipline. In many facilities, a single administrator can enroll an employee, assign access to the server room, activate the credential, and later edit the log of what happened. That concentrated power is a standing insider risk, and it is exactly what NIST SP 800-53 separation-of-duties thinking exists to
kate frese
Oct 232 min read
'Security Violations: From PACS Evidence to Adjudication'
Federal facilities do not lack detection. Tailgating shows up as door-held events, shared badges as anti-passback violations, unauthorized entries as alarm records. What most facilities lack is the middle of the process: a defined path from "the system saw something" to "a person made a documented decision about it." The result is a PACS full of incidents with no disposition, which reads to an assessor as a detection system wired to nothing. NIST SP 800-53 families expect vio
kate frese
Oct 152 min read
'Your PACS Is Full of PII: Protecting Personnel Data in Physical Security Systems'
Facilities spend enormous effort controlling who can open a door and almost none controlling what the access control system knows about everyone behind it. A PACS is a personnel database with a security function: photos, full names, credential identifiers, role assignments, schedule patterns, and entry histories that reveal where specific people were, when, over years. When that data is handled for a federal contract, it frequently lands inside the same protection obligations
kate frese
Oct 152 min read
'Vetting the Vendor: PS-7 and Third-Party Security Personnel'
The technician installing your PACS holds privileged knowledge of your facility: door schedules, credential formats, network paths, and the quiet logic of every lock. NIST SP 800-53 PS-7 exists because those facts make third-party service personnel an insider population, and the control places responsibility on the facility to ensure outside personnel are screened to the same expectations as employees, not waved in under the warranty. Most facilities never ask. As a technical
kate frese
Oct 152 min read
'Lost, Stolen, and Damaged Credentials: Running the Revocation Clock'
Every facility eventually loses credentials. Badges get left in gym bags, run through washing machines, lifted from vehicles, and worn to unreadable condition. The measure of a facility's security posture is not whether it loses credentials; it is how fast the loss turns from a live vulnerability into a closed, documented event. Under FIPS 201-2-aligned thinking, a credential's trustworthiness ends the moment it leaves its holder's control in an unexplained way, and the syste
kate frese
Oct 152 min read
SCIF Doors and ICD 705: What Accredited Spaces Ask of Physical Access
A Sensitive Compartmented Information Facility is a room whose construction is its own control. Under ICD 705-aligned standards, the walls, the door, the floor, and the ceiling are all part of the protection, which means every component an integrator touches, locks, readers, alarms, access configuration, is subject to accreditation review rather than just installation approval. Physical security integration in accredited spaces is a different discipline than commercial or eve
kate frese
Oct 112 min read
FPCON to PACS: Turning Force Protection Levels into Access Rules
Force Protection Conditions exist so a facility can change its security posture faster than it can change its security staff. When the threat level rises, the postures change: entry inspection intensifies, visitor access tightens, and low-priority movement gets deferred. The doctrine is clear. The implementation usually is not, because at most facilities, a FPCON change is communicated by email, enforced by memory, and verified by nobody. The gap is between policy and configu
kate frese
Oct 112 min read
bottom of page