Where to report suspected espionage: the FBI is the right contact for FSOs.

Espionage isn’t a movie plot you can laugh off. It’s a real-world risk that can show up in everyday places—your facility’s lobby, the back offices, even during late shifts when the building hums with a quiet kind of routine. For Facility Security Officers (FSOs), staying aware of how to handle whispers of suspicion isn’t glamorous, but it’s essential. The moment you sense something off, you’re not just protecting a doorway—you’re protecting people, data, and critical operations.

Who you call first when espionage whispers pop up

Let me explain the important part in plain terms: reports of suspected espionage belong with the Federal Bureau of Investigation (FBI). That’s the agency charged with counterintelligence investigations here in the United States. The FBI has the training, the resources, and the jurisdiction to dig into activities that might hint at foreign intelligence services or agents playing fast and loose with sensitive information.

Now you might wonder, what about other big-name agencies? DoD, CIA, DHS all play meaningful roles in national security. They do. But when it comes to handling reports tied to espionage inside U.S. borders, the FBI is the primary point of contact. In practice, this means your internal reporting channels should route anything that smells like espionage straight to the FBI, or at least to your organization’s security leadership who will coordinate forwarding to the right place. It’s not about who handles the case later; it’s about getting the signal to the right people promptly so the right protective measures can kick in.

What counts as espionage, and what to report

Here’s the thing: you don’t need a certain “proof” before you raise a red flag. Suspicious behavior is enough to start a careful, documented report. Some examples that might trigger FBI involvement include:

• Unusual attempts to access or remove sensitive information, equipment, or documents without a clear, legitimate purpose.

• Repeated attempts to obtain special access or permissions by someone outside their normal role, especially if they show unusual persistence or pressure tactics.

• Offers or attempts to introduce someone to obtain or leak classified or sensitive information.

• A pattern of unexplained data transfers, hidden emails, or encrypted communications related to sensitive topics.

• Suspicious meetings or conduct that seems designed to covertly gather information.

When you file, give the FBI a crisp, factual account. Include the who, what, where, when, and how—plus any observable indicators (that phrase you’ve heard at security briefings: “risk indicators” or “red flags”). Do not confront the person you suspect. Your job is to observe, document, and escalate through the proper channels.

If you’re new to this, you might picture it like reporting a maintenance issue. If a light flickers or a panel squeaks, you log the details: when, where, who was nearby, what you observed. With espionage, the stakes are higher, but the principle is the same: record what you see, and hand it off to the right experts.

The FBI as your first responder in this scenario

Why the FBI? Because espionage sits at the intersection of security, intelligence, and law enforcement. The agency has the authority to investigate foreign influence, identify spy networks, and protect national security while keeping civil liberties in balance. For FSOs, that means your role is to provide timely, accurate information that helps investigators map out the threat landscape.

It’s tempting to want to “handle it” yourself, especially when your facility runs on tight schedules and you’re juggling access control, cameras, incident reports, and the next drill. But handling suspected espionage without proper procedures can inadvertently tip off a suspect or contaminate evidence. Your job is to collect, preserve, and report—so investigators can reconstruct what happened, why it happened, and who might be involved.

How to report: a practical, step-by-step guide

• Document the observation: note dates, times, exact locations, and what you witnessed. If possible, capture non-sensitive artifacts (like a non-secure email header, a suspicious document left on a desk, or unusual access patterns) without altering or destroying evidence.

• Preserve the scene: don’t touch or move items that might be involved in the incident. If you can, photograph or log the state of things without interfering.

• Gather contextual information: any related conversations, observed patterns, or alerts from security systems. Was there a specialty visitor, a contractor, or a vendor who stood out recently?

• Report through your chain of command: alert your supervisor or the designated security lead per your facility’s procedures. The goal is to ensure a timely, formal handoff to the right team within your organization and to the FBI when appropriate.

• Contact the FBI: if your internal chain determine it should escalate, or if the indicators clearly point toward espionage, reach out to the FBI. They maintain the tips portal at tips.fbi.gov and offer guidance on how to report suspicious activity. If you’re unsure, it’s safer to route the information to your security leadership first; they’ll know the proper escalation path.

A quick note on avoiding false alarms

Not every odd coworker interaction or locked file is espionage. FSOs juggle many “what-if” scenarios every day. The trick is to differentiate genuine risk indicators from everyday quirks. If you’re ever in doubt, it’s better to document and ask than to ignore and later regret. And remember: you’re not alone. Your organization’s security framework should give you a clear path to escalate when the signs don’t fit routine patterns.

Beyond the FBI: how other agencies support security work (without stealing the show)

Yes, the FBI leads the charge on espionage reports, but collaboration matters. DoD, CIA, and DHS participate in broader national security operations and information-sharing ecosystems. For example:

• DoD may provide technical expertise or support in cases involving defense-related information or critical infrastructure that has dual-use implications.

• CIA’s insights shine when intelligence gaps need to be filled that cross into foreign intelligence domains, especially in overseas or highly sensitive contexts.

• DHS contributes to protecting critical infrastructure and coordinating with civilian authorities on security programs that touch on domestic resilience.

In the end, though, the FBI is the main destination for reported espionage activity inside the United States. Your internal team is the bridge that gets the right facts into the right hands. This isn’t about hierarchy for its own sake; it’s about ensuring that the right agency has the right information to act, quickly and effectively.

FSO duties that keep you ahead of the curve

Staying vigilant isn’t just about reacting to a single incident. It’s about building a culture where people feel confident reporting oddities without fear of blowing things out of proportion. Here are some practical habits that make a real difference:

• Maintain a clear, easy-to-follow reporting path: everyone should know who to tell, what to document, and how to escalate. Regular drills or tabletop exercises can help the team stay sharp.

• Keep a logbook of suspicious activity: a simple, structured form can capture essential details and preserve them in a non-destructive way.

• Foster secure information handling: remind staff about data handling policies, even for shadow IT or informal networks. The less ambiguity around sensitive data, the easier it is to spot unusual behavior.

• Build relationships with local authorities: a known contact at the FBI or local field office can streamline communication during an incident. It’s not “bureaucracy”; it’s preparedness.

• Educate through real-world scenarios: share anonymized case studies in safety briefings to illustrate how espionage indicators show up in different settings—manufacturing floors, research labs, or corporate campuses.

A small tangent worth noting

Security work isn’t just about locks and cameras; it’s about trust. When people understand why they’re reporting and see a fair, measured response, they participate more openly. Sometimes, a simple “Thanks for flagging that” can be more powerful than any high-tech system. Trust is the invisible backbone that makes the reporting process work. And yes, that trust rests on you, the FSO, modeling calm, careful behavior even under pressure.

Putting it all together: your role in a moment like this

If you ever encounter something that feels off, here’s the baseline you can rely on:

• Treat espionage as a legitimate area of concern, not a rumor to be dismissed.

• Collect facts, preserve the scene, and report through the proper channels.

• When in doubt, contact the FBI and let the investigators decide the next steps.

• Support your team with clear procedures, practical training, and calm leadership.

A final thought to keep you grounded

National security doesn’t hinge on a single slip or a heroic last-minute save. It rests on a steady daily discipline: people who notice, people who document, and people who know how to bring the right authorities into the conversation. The FBI is the right partner for espionage-related reports, but your success as an FSO comes from the quiet, persistent work you do every day to keep sensitive information safe and operations running smoothly.

If you’re ever unsure about whether a situation qualifies as espionage, ask yourself this simple question: “Would this be something an investigator would need to know to understand a potential threat?” If the answer is yes, you’ve probably found a signal worth sharing. And if there’s any doubt, remember the portal at tips.fbi.gov and your organization’s security leadership—they’re there to help you navigate the path from concern to action.

In the end, the right agency at the right moment isn’t just a procedural detail. It’s a critical safeguard that protects people, property, and the work you’re guarding every day. You’ve got the training, you’ve got the tools, and you’ve got a clear road map: observe, document, escalate, and involve the FBI when espionage looks like a possibility. That’s how FSOs keep facilities resilient—and that's how good security feels when it’s done right.