惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

小众软件
小众软件
量子位
博客园 - 叶小钗
Apple Machine Learning Research
Apple Machine Learning Research
U
Unit 42
IT之家
IT之家
F
Fortinet All Blogs
GbyAI
GbyAI
MongoDB | Blog
MongoDB | Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
大猫的无限游戏
大猫的无限游戏
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The Register - Security
The Register - Security
NISL@THU
NISL@THU
Webroot Blog
Webroot Blog
A
Arctic Wolf
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
Visual Studio Blog
Recent Announcements
Recent Announcements
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Blog — PlanetScale
Blog — PlanetScale
L
LangChain Blog
P
Palo Alto Networks Blog
Y
Y Combinator Blog
WordPress大学
WordPress大学
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
AWS News Blog
AWS News Blog
有赞技术团队
有赞技术团队
Engineering at Meta
Engineering at Meta
C
Cybersecurity and Infrastructure Security Agency CISA
aimingoo的专栏
aimingoo的专栏
Know Your Adversary
Know Your Adversary
Cyberwarzone
Cyberwarzone
Martin Fowler
Martin Fowler
The Hacker News
The Hacker News
P
Privacy International News Feed
T
Threat Research - Cisco Blogs
G
GRAHAM CLULEY
宝玉的分享
宝玉的分享
博客园 - 聂微东
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
The GitHub Blog
The GitHub Blog
S
Securelist
T
The Exploit Database - CXSecurity.com
T
Threatpost
Microsoft Azure Blog
Microsoft Azure Blog
The Cloudflare Blog
F
Full Disclosure

Black Hills Information Security, Inc.

Bad Habits: An ANTISOC Operation Same Problem, Different Angles: When Red Team and Blue Team Actually Talk to Each Other How to Identify and Exploit New Vulnerabilities Swapper – A Pure Regex Match/Replace Burp Extension A Practical Guide to BloodHound Data Collection Network Engineering Basics Signed, Trusted, and Abused: Proxy Execution via WebView2 Getting Started In Pentesting – Advice From The BHIS Pentest Lead Cloud Security: Tips and Resources for Securing the Cloud Lessons From A Chatbot Incident How to Lead Effective Tabletops Understanding GRC: How to Navigate Risks and Compliance Standards The “P” in PAM is for Persistence: Linux Persistence Technique Malware Analysis: How to Analyze and Understand Malware OSINT: How to Find, Use, and Control Open-Source Intelligence What to Do with Your First Home Lab When the SOC Goes to Deadwood: A Night to Remember Social Engineering and Microsoft SSPR: The Road to Pwnage is Paved with Good Intentions Common Cyber Threats Finding the Right Penetration Testing Company Deceptive-Auditing: An Active Directory Honeypots Tool The Curious Case of the Comburglar How to Set Smart Goals (That Actually Work For You) Inside the BHIS SOC: A Conversation with Hayden Covington Abusing Delegation with Impacket (Part 3): Resource-Based Constrained Delegation Why You Got Hacked – 2025 Super Edition Abusing Delegation with Impacket (Part 2): Constrained Delegation Abusing Delegation with Impacket (Part 1): Unconstrained Delegation GoSpoof – Turning Attacks into Intel Model Context Protocol (MCP) Bypassing WAFs Using Oversized Requests Getting Started with AI Hacking Part 2: Prompt Injection Wrangling Windows Event Logs with Hayabusa & SOF-ELK (Part 2) DomCat: A Domain Categorization Tool Wrangling Windows Event Logs with Hayabusa & SOF-ELK (Part 1) Microsoft Store and WinGet: Security Risks for Corporate Environments Default Web Content MailFail Commonly Abused Administrative Utilities: A Hidden Risk to Enterprise Security Stop Spoofing Yourself! Disabling M365 Direct Send Bypassing CSP with JSONP: Introducing JSONPeek and CSP B Gone Offensive Tooling Cheatsheets: An Infosec Survival Guide Resource DNS Triage Cheatsheet GraphRunner Cheatsheet Burp Suite Cheatsheet Impacket Cheatsheet Wireshark Cheatsheet Hashcat Cheatsheet EyeWitness Cheatsheet Nmap Cheatsheet Netcat (nc) Cheatsheet Hunt for Weak Spots in Your Wireless Network with Airodump-ng from the Aircrack-ng Suite Detecting ADCS Privilege Escalation Vulnerability Scanning with Nmap Getting Started with NetExec: Streamlining Network Discovery and Access How to Use Dirsearch Augmenting Penetration Testing Methodology with Artificial Intelligence – Part 3: Arcanum Cyber Security Bot How to Design and Execute Effective Social Engineering Attacks by Phone Abusing S4U2Self for Active Directory Pivoting Why Use a Macro Pad? Espanso: Text Replacement, the Easy Way Caging Copilot: Lessons Learned in LLM Security Augmenting Penetration Testing Methodology with Artificial Intelligence – Part 2: Copilot Augmenting Penetration Testing Methodology with Artificial Intelligence – Part 1: Burpference Intercepting Traffic for Mobile Applications that Bypass the System Proxy How to Root Android Phones Communicating Security to the C-Suite: A Strategic Approach Offline Memory Forensics With Volatility Getting Started with AI Hacking: Part 1 Go-Spoof: A Tool for Cyber Deception How to Test Adversary-in-the-Middle Without Hacking Tools Canary in the Code: Alert()-ing on XSS Exploits How to Hack Wi-Fi with No Wi-Fi Why Your Org Needs a Penetration Test Program Burp Suite Extension: Copy For Light at the End of the Dark Web Wi-Fi Forge: Practice Wi-Fi Security Without Hardware Avoiding Dirty RAGs: Retrieval-Augmented Generation with Ollama and LangChain Gone Phishing: Installing GoPhish and Creating a Campaign 5 Things We Are Going to Continue to Ignore in 2025 John Strand’s 5 Phase Plan For Starting in Computer Security Questions From a Beginner Threat Hunter GRC for Security Managers: From Checklists to Influence AI Large Language Models and Supervised Fine Tuning Attack Tactics 9: Shadow Creds for PrivEsc w/ Kent & Jordan One Active Directory Account Can Be Your Best Early Warning Introduction to Zeek Log Analysis Indecent Exposure: Your Secrets are Showing Creating Burp Extensions: A Beginner’s Guide Pitting AI Against AI: Using PyRIT to Assess Large Language Models (LLMs) The Top Ten List of Why You Got Hacked This Year (2023/2024) ICS Hard Knocks: Mitigations to Scenarios Found in ICS/OT Backdoors & Breaches Intro to Data Analytics Using SQL Finding Access Control Vulnerabilities with Autorize The Detection Engineering Process Cyber Risk Lessons We Can Learn From Hurricane Preparedness Intro to Desktop Application Testing Methodology What Is Penetration Testing? Adversary in the Middle (AitM): Post-Exploitation Pentesting, Threat Hunting, and SOC: An Overview
The Art of the Badge: A Hard Truth About Physical Security
BHIS · 2026-06-10 · via Black Hills Information Security, Inc.

by Robert Boettger | Guest Author

He walked into the lobby with a fake badge clipped to his shirt. He had bought it online the week before. It was not perfect, and it did not need to be. From a few feet away, it looked close enough: a logo, a name, a photo, and a lanyard. The kind of thing most people glance at for half a second before their brain decides, “Looks fine.”

That was all he needed.

He stepped through the front entrance like he had done it a hundred times. Calm, confident, and familiar enough. He smiled at reception, nodded at an employee walking past, and kept moving. Nobody stopped him. Nobody leaned forward to actually look at the badge. Nobody asked who he was there to see. He looked like he belonged. That is where the failure started.

He walked down the hallway and said good morning to two employees passing in the opposite direction. They said good morning back. One of them looked at the badge but did not really read it. The other did not look at all. He stopped at the vending machine, bought a coffee, checked his phone, and stood there for a moment like anyone else taking a break. Nothing about him caused alarm.

A few minutes later, he followed an employee toward a controlled door. The employee badged in, the door unlocked, and they both reached the entrance at almost the same time. The employee glanced back. The man smiled, lifted his drink slightly, and gave a polite nod. “Morning.” The employee smiled back and said, “Morning.” And just like that, he was in.

No force. No alarms. No broken locks. No dramatic breach. Just a door held open by habit and a human being who did not want to create an awkward moment.

He made his way deeper into the building, past offices, conference rooms, and people who were busy, distracted, and comfortable. Eventually, he reached a restricted area where he had no business being. Inside, he found access to equipment that mattered. Maybe it was a server. Maybe it was a workstation used for operations. Maybe it was a system tied to something the organization could not afford to lose. He plugged in a USB device. Then he walked out.

No one noticed. No one stopped him. No one remembered his name. No one could say for sure where he went. Later, when people started asking questions, the answers sounded familiar. “I thought he worked here.” “I saw a badge.” “He looked like he knew where he was going.” “I assumed someone else checked.”

That is the part nobody likes to admit. The attacker did not beat the system. The people inside the building helped him move through it.

What a Badge Really Means

A badge is not decoration. It is not workplace jewelry. It is not a corporate accessory employees wear when convenient and forget when they are busy. A badge is a boundary. It tells everyone in the facility, “This person is authorized to be here right now.” Not yesterday. Not last month. Not before they were fired. Not before their contract ended. Not because people remember their face. Right now.

That distinction matters. Organizations love to talk about security culture, but basic badge discipline is where that culture gets tested. Anyone can say security matters. Anyone can hang posters in the break room or write policy language in an employee handbook. The real test happens at the front door, in the lobby, near the elevator, at the badge reader, and in the hallway when someone without proper identification walks by. That is where security either becomes real or becomes theater.

“You Know What They Say About Assumptions…”

Most employees are not trying to be careless. They are busy. They are distracted. They do not want conflict. They do not want to seem rude. They do not want to challenge someone who might be important. So they guess. They tell themselves the person probably works there. The visitor is probably with someone. The badge probably looks real. They have probably seen that person before.

“Probably” is not a security control. “Probably” is how people get into places they should never reach.

This is why organizations need to have uncomfortable conversations with employees and managers. Not because security is trying to be difficult. Not because someone enjoys correcting people. Not because badge checks are about power or ego. These conversations matter because people actually care about the place they work. They care about their coworkers, their customers, the building, the equipment, the information, and the mission. They care enough to say something when something does not look right. That is not annoying. That is ownership.

Simple Rules That Work

The solution does not need to be complicated. In fact, it should not be. Physical security needs some KISS: Keep It Simple, Stupid rules!

Repeated often, enforced fairly, and practiced until they become normal.

Basic Badge Requirements

If the badge is not visible, the person should be challenged. Badges should be worn above the waist where people can actually see them. Every person must badge in separately at controlled doors. No piggybacking. No tailgating. No “they’re with me” unless the policy allows it and they are properly escorted.

Visitor Badge Design

Visitor badges should be obvious. They should not look almost the same as employee badges. Use a different color, large “VISITOR” wording, date or time expiration, and a simple design that employees can recognize from a distance. If every badge looks the same, employees are being asked to inspect instead of recognize. That slows people down, creates confusion, and gives the wrong person more room to blend in.

Access Management

Access also must be removed immediately when someone is terminated, resigns, transfers, or finishes a contract. Yesterday’s access cannot become today’s risk. A person who belonged last week may have no reason to be inside the building today.

Make Reporting Easy

The back of every badge should include a security contact number. That could be the security desk, SOC, guard force, or emergency contact. Employees should not have to search for who to call when something feels wrong. If you want people to report issues, make reporting easy.

Building a Badge-Friendly Culture

Badge checks should also happen during patrols, but this cannot be only a security officer problem. Everyone has a role. Security can lead the culture, but employees have to live it. Bring people into an open area and run simple mock scenarios. Show them what a badge challenge sounds like. Let them practice saying, “Hi, I don’t see your badge. Can I walk you to the security office?” Make it friendly. Make it normal. Make it expected.

Security teams should test this periodically. Once a month or so, have an approved person walk through a hallway or common area without a visible badge and observe what happens. Who notices? Who says something? Who looks uncomfortable but stays quiet? This should not be used to embarrass people. It should be used to train them, encourage them, and build confidence.

When someone does the right thing, recognize it. Give them credit. Thank them. Hand out challenge coins or small awards to employees who do an exceptional job. The goal is to make badge challenges part of the culture, not something people fear. A strong challenge culture is not hostile. It is professional, friendly, and serious about protecting the workplace.

Professional Testing

When the organization wants the highest level of validation, a physical penetration test can show whether the culture actually works. Not in theory. Not on paper. In real conditions. A good test shows whether people challenge, whether doors are controlled, whether visitor processes hold up, and whether the badge program is more than plastic and policy.

Lead By Example

A real badge program only works when people are willing to enforce it. If employees do not look for badges, the badge does not matter. If leaders walk around without badges and expect special treatment, the badge policy does not matter. At that point, the badge program is not security. It is theater.

And attackers love theater.

They love organizations where people look the part but do not enforce the rules. They love doors where employees hold them open without thinking. They love lobbies where visitors are loosely managed. They love hallways where people assume someone else already checked. They love executives who believe security policy is for everyone beneath them.

From the CEO down — especially from the CEO down — the rule has to be visible, enforced, and respected. If leadership treats the badge like a suggestion, everyone else will too. And once that happens, the building is no longer protected by policy. It is protected by luck.

The Hard Truth

The art of the badge is not complicated. That is exactly why it gets ignored. It feels too basic, too small, too obvious. But physical security usually fails in the ordinary moments people excuse every day: one door held open, one badge turned backward, one fake badge accepted, one familiar face waved through, one employee who noticed and said nothing.

Every time someone sees it, ignores it, challenges it, or respects it, they are deciding what kind of security culture they actually work in.

And the wrong person only needs that decision to go their way once.



Explore the Infosec Survival Guide and more… for FREE!

Get instant access to all issues of the Infosec Survival Guide, as well as content like our self-published infosec zine, PROMPT#, and exclusive Darknet Diaries comics—all available at no cost.

You can check out all current and upcoming issues here: https://www.blackhillsinfosec.com/prompt-zine/