To my wife: thank you for more than twenty years of love, patience, encouragement, and steady support. You have been beside me through most of my professional journey—through long days, changing roles, difficult decisions, and the many demands that come with building a career. Your belief in me has meant more than I can put into words.

To my children: thank you for the joy, perspective, and motivation you bring to my life. I hope you always know that growth does not require having every answer at the beginning. It begins with curiosity, hard work, humility, and the willingness to keep learning.

I am grateful as well to the guards, officers, supervisors, mentors, colleagues, partners, and leaders who shaped my career. Every opportunity, challenge, mistake, conversation, and lesson contributed to the perspective behind this book.

This book is better because of all of you.

— Brian

If you are reading this book from a lobby desk, patrol post, control room, access-control office, dispatch center, or your first supervisory role, I want you to know something important: your current assignment does not define the limit of your career.

I began as a frontline security guard. Early in my career, I experienced a serious workplace incident that left me feeling unprepared and uncertain. People needed Security to bring calm, clarity, and direction. Instead, I realized how much I did not yet understand about the systems, decisions, communication, and preparation behind the uniform, cameras, radios, and post orders around me.

That experience changed me.

I began reading procedures more closely. I asked better questions. I learned why policies existed, how access decisions were made, what happened after an incident report was submitted, and how Security worked with facilities, human resources, operations, technology, leaders, vendors, and public-safety partners. Over time, that curiosity led to opportunities in access control, executive protection, supervision, crisis management, and corporate-security leadership.

I did not begin with all the answers. I did not have a perfect plan. I learned one responsibility, one system, one conversation, and one difficult lesson at a time.

Frontline security work is often undervalued or misunderstood. Yet it can build the habits that matter throughout a corporate-security career: observation, composure, professionalism, reporting, customer service, discretion, follow-through, and the ability to notice what others miss. Those are not small skills. They are the foundation of trust.

You do not need to know everything today to begin growing. You need the willingness to learn, to ask questions, to prepare, to accept feedback, and to take responsibility for the part of the work you can influence.

Your next role may begin before anyone gives you the title.

Brian J. Ilg, Author

We Had Guards, But Not a Security Program

Early in my career, I worked as a security guard in a control room at a large corporate facility. The room had old monitors, radios in charging racks, phones, logbooks, and binders full of post orders. On a typical shift, the work felt simple: watch the cameras, answer calls, record activity, and report anything unusual.

Most shifts were quiet. I checked screens, made routine log entries, and tried to stay alert through the slow parts of the day. At that point, I thought being good at security meant following instructions, noticing obvious problems, and calling for help when something went wrong.

Then an incident unfolded in an office area outside camera coverage.

A radio call came in about a disturbance. I started scanning the cameras nearest the reported location, expecting to see movement or people gathered in a hallway. I saw nothing. The incident was happening in an area the cameras did not cover.

As the situation developed, people were trying to do the right thing. A supervisor was managing the immediate problem. An officer was working to get help. First responders arrived but did not have clear direction to the location. From the control room, I watched people work hard without a shared response process.

Later, we learned that someone who should not have entered the facility had reached an employee. The incident was frightening, but the lesson was larger than the incident itself.

We had guards. We had cameras. We had radios, procedures, and a supervisor.

But at that moment, we did not have a prepared security program.

That experience changed the way I saw the profession. I did not want to remain someone who simply watched and reported. I wanted to understand how access decisions were made, how emergencies were managed, who owned the systems around me, and how security could help the business operate safely when conditions changed.

This book is about that transition.

It is not a promise that a guard can become a corporate-security leader overnight. It is a practical guide to building the habits, judgment, relationships, and evidence that make greater responsibility possible.

Corporate-security advancement is not earned through ambition alone. It is earned through evidence:

• Reliable work
• Applied judgment
• Accurate communication
• Discretion
• Better questions
• Improved processes
• Trusted relationships
• Follow-through

The transformation is simple to describe, even if it takes disciplined practice:

Start: “I am a guard performing assigned tasks.”

Finish: “I understand the corporate-security system, communicate risk professionally, influence within my authority, help others prepare, and have a credible plan to advance.”

The incident described in the introduction changed how I viewed security. We had visible resources, committed people, and written instructions. What we lacked was a coordinated system that clarified roles, communication, decision-making, and follow-through under pressure.

I did not fully understand that in the moment. I only knew that everything we were supposed to have in place had not come together when it mattered most. Looking back, the equipment and the procedures were never the real problem. The gap was in how those pieces connected under real conditions, at real speed, with real consequences.

That distinction—between looking secure and being prepared—became the foundation for how I understood corporate security, and it shapes every chapter that follows.

Security Presence Is Not a Security Program

We had guards at the gate, a security desk in the lobby, a control room full of cameras and radios, post orders, and a supervisor on duty. From the outside, we looked secure. But when an employee needed us most, we were not prepared to act as one coordinated team.

That day taught me a lesson I carried throughout my career: a visible security presence is not the same thing as a security program.

Security is not guards, cameras, radios, access badges, or binders collecting dust. Those are tools and components. They matter, but none of them will protect people effectively if they are not connected through planning, training, communication, leadership, and continuous improvement.

A security program answers questions before an incident forces people to guess:

• What risks are most likely to affect our people, facilities, assets, and operations?
• What are the early warning signs that something may be wrong?
• Who is responsible for making decisions during an incident?
• How will guards, employees, managers, and emergency responders communicate?
• How do we verify that access-control procedures actually work in real conditions?
• What do we do when the situation does not match a post order exactly?
• How will we review what happened and improve before the next event?

When those questions have not been considered in advance, people default to what they know. A guard may wait for direction. A manager may assume someone else has the plan. A security officer may document an incident and move on because that is what the procedure appears to require. Meanwhile, the organization may believe it has invested in security because guards are present, cameras are visible, and badges are required.

That is how a false sense of security develops.

I do not say this to criticize frontline guards. I started as one. Guards and officers are often given limited training, narrow instructions, and little exposure to the broader security function. They may be told to observe, report, enforce post orders, and call for help. Those responsibilities are important. In fact, effective observation, accurate reporting, professionalism, and composure under pressure are foundational skills.

But they are not the entire job of a corporate security professional.

As your responsibilities grow, you must learn to see beyond the immediate event. You begin asking what created the conditions for the event, what could happen next, who needs to be involved, and what can be changed. You learn that a missing badge is not always just an access-control problem; it may be an opportunity to balance identity verification with employee service. A minor theft complaint may be an isolated event—or it may be the first visible sign of a pattern that deserves review.

A professional security mindset does not mean treating every situation as an emergency. It means recognizing that every unusual situation deserves thought. The question is not simply, “What do I do right now?” It is also, “What does this tell us, what could it become, and what should happen next?”

That shift—from reacting to events to preparing for them—is where corporate security begins.

The Prepared Security Cycle

The goal of security is not to predict every possible event. That is impossible. The goal is to build a team and a program that can recognize risk, prepare for likely situations, respond with discipline, and become stronger after every incident, near miss, complaint, or exercise.

Over the years, I came to think of this as a continuous cycle:

The cycle is simple, but it separates organizations that merely look secure from those that are genuinely prepared.

Anticipate

To anticipate is to look ahead and identify what could disrupt people, facilities, assets, or business operations. That does not mean living in fear or assuming the worst will happen every day. It means recognizing that a workplace can face more than routine access-control issues. Severe weather, earthquakes, power outages, fire, workplace violence, suspicious behavior, theft, intrusion, medical emergencies, and other events may affect an organization depending on its location, industry, operating hours, and workforce.

A new security professional often focuses on what is directly in front of them: the door, the camera monitor, the visitor, the employee badge, or the immediate report. Those details matter. But advancement requires you to widen the view. Ask yourself:

• What could happen at this location that would place people at risk?
• What events could interrupt business operations?
• What vulnerabilities have we accepted without reviewing?
• What repeated complaints, unusual behaviors, or minor incidents could be early warning signs?
• What would make it difficult for us to respond quickly if an incident occurred today?

Anticipation starts with curiosity. You do not need a formal title to notice that a process is weak, a camera does not cover a critical area, a guard does not know who to call, or employees do not understand how to report a concern. You do need the discipline to recognize that these observations may matter.

Plan

Once you identify a meaningful risk, the next question is: what will we do about it? Planning means deciding in advance how an organization will reduce harm, communicate, make decisions, and recover. A plan does not need to be a massive binder full of language no one will read. The best plans are practical enough that people understand their role when stress is high. At a minimum, planning should clarify:

• Who must be notified when an incident occurs
• Who has authority to make key decisions
• How the team communicates internally and with first responders
• Where employees, visitors, or responders should go
• How security, facilities, HR, IT, operations, and leadership work together
• What resources may be needed quickly
• What actions should happen immediately, and what actions can wait

Train

A plan that sits in a binder is not a plan the organization can rely on. People need to understand their roles before an incident occurs. Training is where security expectations become real. It includes teaching guards what to look for, when to escalate, how to communicate, how to verify identity, and how to handle situations that do not fit neatly into a post order. It also includes making sure managers, employees, and partner departments understand what security can do, what security needs from them, and how they should report concerns.

In my early control-room role, I knew how to watch cameras and log routine activity. But I had not been trained on how to support a developing emergency when there was no camera view, no clear notification process, and no immediate direction. That was not a personal failure. It was a training failure. Training gives people confidence. It replaces guesswork with a clear understanding of what they are expected to do—and when they are expected to ask for help.

Test

Testing is how you find out whether the plan and training will work before a real incident exposes the gaps. A tabletop exercise is one of the most practical ways to test preparedness. It does not require a full-scale drill, expensive consultants, or a complicated scenario. It can begin with a group of the right people in a room asking, “What would we do if this happened today?”

A tabletop exercise reveals what people do not know. It may show that emergency contacts are outdated, that notification responsibilities are unclear, that a guard post lacks critical instructions, or that the organization has never decided who communicates with employees during an emergency. The point is not to create perfect performance. The point is to discover gaps while there is still time to fix them.

Respond

When an incident occurs, preparation must become action. A response requires people to use the training and plans they have practiced, communicate clearly, protect people first, and adapt to the reality in front of them. No plan will match every event perfectly. A professional team understands the plan well enough to use it as a guide, not as a substitute for judgment.

During an incident, confusion grows quickly when no one knows who is in charge, what has already happened, or what must happen next. Good response depends on clear roles, timely escalation, reliable communication, and coordination with the people who can help. This is where the work done before the incident becomes visible.

Improve

The cycle does not end when the incident is over. Every incident, exercise, near miss, or unusual complaint is an opportunity to learn. The professional question is not, “Did we get through it?” The better question is, “What did this reveal, and what must we do differently next time?”

An after-action review should be straightforward:

• What happened?
• What did we expect to happen?
• What worked well?
• What was unclear, delayed, missing, or ineffective?
• What specific improvement should be made?
• Who owns that improvement, and by when?

Too many organizations document an incident, discuss it briefly, and then return to routine without changing anything. That is not improvement. That is repetition waiting to happen.

The Prepared Security Cycle is not reserved for security directors or executives. You can begin using it now, regardless of your title. Every time you encounter an unusual situation, ask yourself what should have been anticipated, planned, trained, tested, responded to, or improved. That is how you begin moving from simply observing security to thinking like a security professional.

From Reporting Problems to Taking Ownership

Early in my career, I believed good security work meant doing what I had been instructed to do: observe, report, document, and wait for direction. Those are important responsibilities. Accurate reporting creates a record, helps leaders understand what occurred, and can become essential during an investigation or review.

But reporting is only the beginning.

A report answers: What happened?
A security professional also asks: What does this mean, what could happen next, and what should we do about it?

Taking ownership does not mean ignoring the chain of command, making decisions outside your authority, or taking on responsibilities that belong to HR, Facilities, Legal, senior leadership, or law enforcement. It means refusing to treat documentation as the final step when an event, pattern, or condition may require additional attention.

A guard may not have authority to change a policy, install a camera, hire more staff, or approve a new vendor. But a guard can identify a gap, document the facts accurately, explain the risk, recommend a reasonable next step, and make sure the concern reaches the person who has authority to act. That is how professionals become trusted.

A Simple Way to Frame Any Security Concern

When you are new to corporate security, it can feel intimidating to raise a concern with a supervisor, manager, or another department. A simple structure can help you move from “I noticed something” to “Here is a professional recommendation.”

Observation

Start with the facts. What did you observe, receive, or learn? Avoid assumptions, labels, or conclusions that you cannot support. Note the date, time, location, people involved when appropriate, and the basic sequence of events.

Risk

Next, ask what the event could reveal or lead to. A single assault report near the office may indicate a personal-safety concern along a route used by multiple employees. It may affect employees arriving early, leaving late, or using nearby public transportation. A risk statement does not declare liability. It identifies a concern that may affect people.

Impact

Then consider who or what could be affected if the concern continues. Impact can involve people, operations, property, employee confidence, attendance, reputation, compliance, or business continuity. The purpose is not to exaggerate the problem. It is to help the right decision-makers understand why it deserves attention.

Recommendation

A recommendation is not a demand. It is a reasonable proposed next step based on the facts available. It may be a review, a conversation, a training update, a procedure change, or an assessment. It does not have to involve spending money.

Owner

Finally, identify who needs to review or act on the recommendation. Security rarely owns every part of a solution. Identifying the owner prevents a report from becoming an orphaned document—submitted, stored, and forgotten.

The Work Starts Before the Incident

The employee in the story that opened this chapter came to work expecting a safe environment. We had a guard at the parking entrance, a security presence in the lobby, a supervisor, radios, cameras, post orders, and a control room. Yet a determined person was able to reach her, and our response exposed how unprepared we were.

I stopped seeing security as the work that occurs when something bad happens. I began to understand that the most important work often happens before the incident: identifying vulnerabilities, anticipating likely threats, clarifying responsibilities, training people, testing the plan, and improving the system when it falls short.

You will not prevent every incident. You also will not always have the authority, budget, technology, or staffing you believe would make a situation better. But you can learn to recognize what matters, elevate concerns professionally, and help the organization prepare instead of merely react.

That is where your advancement begins.

As a guard, officer, supervisor, or newly assigned security lead, you may not yet control the security budget or write the company’s emergency plans. You can still start thinking like someone who one day will. You can notice gaps. You can ask better questions. You can document facts clearly. You can offer reasonable next steps. You can learn what happens after you raise a concern. And you can review every unusual event with the mindset that the next response should be better than the last.

A security program is not defined by how it appears on an ordinary day. It is defined by how well people, procedures, technology, communication, and leadership come together when the ordinary day ends.

In the next chapter, we will step back and look at the full corporate security function—the people, systems, partnerships, plans, and responsibilities that work together to protect an organization.