Documenting a Suspicious Approach While Abroad
Record a suspicious overseas approach, preserve existing messages, and contact security with facts about what was asked and shared.
Updated October 26, 2026
Security Clearance
If someone abroad presses you for protected work information, disengage safely, record the request, and contact your designated security point of contact. Before foreign travel, DoD personnel and contractors should confirm the reporting channel that applies to them. During a suspicious approach, use that channel promptly rather than waiting to identify the person’s employer or motive.
Key takeaways
- Safety comes first: leave the exchange without confronting or testing the person.
- Capture the request: record what was asked, what you said, and what information or access you provided.
- Keep existing evidence: preserve messages without continuing the conversation to collect more.
- Report uncertainty honestly: distinguish what you observed from what you suspect.
What should you do during a suspicious approach?
End the exchange as safely as circumstances allow and follow the emergency arrangements established for your trip if you need immediate help. Gathering evidence is secondary to your safety. You do not need to challenge the person, announce a suspicion, or keep talking to make your account more complete.
A short response can close an ordinary conversation: “I cannot discuss those work details.” Avoid explaining the boundary by naming a protected program, describing your access, or identifying colleagues who could answer instead. Move away when it is safe to do so.
Consider a hypothetical conference encounter. Someone you have just met asks for an internal document and offers to move the discussion to a private messaging service. Your useful account is the request, the proposed channel, and your response. You do not need to discover whether the person was acting for an intelligence service before raising the concern.
In its 2024 company travel security guidance, the National Counterintelligence and Security Center advises travelers experiencing suspicious approaches to notify a U.S.-based colleague as soon as possible. That general advice supports early contact; it does not replace your organization’s designated security reporting process.
If there is an immediate threat, use the emergency instructions and local assistance appropriate to your situation. Avoid trying to resolve a safety problem through a lengthy written report. Once you are safe, provide your security contact with what you know and how you can be reached.
What should DoD personnel confirm before foreign travel?
Confirm who receives an incident report, how to reach that office while abroad, and which communication methods are approved. Your status and organization determine the applicable process. A general pre-travel training search does not establish the instructions for every DoD employee, service member, contractor, or job seeker.
Keep the contact details somewhere you can access without searching an unfamiliar message or link. Ask how urgent concerns should be handled outside normal office hours and what to do if your usual contact is unavailable. Those details belong in your trip preparation alongside the itinerary.
Use travel preparation considerations for clearance holders to organize your questions for security. Confirm the actual requirements with that office rather than treating an older briefing or another employer’s instructions as your own.
If the encounter has already happened and you lack a saved number, use an independently known organizational contact to find the designated security office. A contact offered by the person who approached you is not a reliable route for reporting concerns about that same encounter.
What facts should you write down?
Record the setting, sequence, request, response, information shared, and any continuing contact. Use exact words only when you remember them accurately or have a message. Mark an approximate time, uncertain spelling, or incomplete recollection plainly. A useful report can contain unknowns.
Write the account when safe, while your memory is fresh. Include the local date and time, the time zone if known, the location, and why you were there. Explain how the conversation began and what caused your concern, rather than opening with a conclusion about espionage.
Identify the person by the information actually available to you: the name they gave, a visible affiliation, or an existing account address. Distinguish a claimed affiliation from one independently confirmed. If you never learned a name or nationality, say so; guessing makes the record less accurate.
Describe both sides of the exchange. What did they ask? Did they request a file, an introduction, a future meeting, or access to a device? What did you answer, send, show, or permit? If no material was shared, state that without assuming it makes the approach unreportable.
SEAD 3, effective June 12, 2017, establishes reporting duties for covered individuals with classified access or sensitive positions. Its Appendix A, item 13, identifies incident dates, people, contact method, information sought, and surrounding circumstances among the data to provide when available and applicable.
Use the following comparison to keep your notes factual. These are sample writing choices, not findings about a real person or a mandatory reporting form.
| Instead of a conclusion | Record an observation | Preserve the uncertainty |
|---|---|---|
| They were an intelligence officer | They asked for an internal document | Their actual affiliation is unknown |
| They knew everything about my job | They named my employer and asked about my duties | I do not know how they obtained that information |
| My phone was compromised | My phone was out of my possession | I cannot confirm whether anyone accessed it |
| Nothing happened because I refused | They made the request; I declined | Security can assess the attempted approach |
How should you preserve messages without extending the exchange?
Keep the messages and other material you already have, using your organization’s handling instructions. Ask security how to transfer them through an approved channel. Avoid replying, opening unfamiliar attachments, or arranging another meeting simply to obtain more evidence.
Note where the original material exists: the email account, messaging platform, device, or paper document. Keep the surrounding conversation available rather than selecting only the most alarming sentence. A cropped image may leave out context that the reviewer needs.
Tell security if a message might disappear or if you are unsure how to preserve it. Ask for handling instructions promptly. Do not let uncertainty about the best evidence format delay an initial notification that an approach occurred.
If you suspect a device was accessed, describe the observable event and seek instructions from the designated security or information security team. Avoid experimenting with unknown files or trying to prove compromise yourself. Record any action you have already taken so the receiving team has an accurate starting point.
Keep the incident out of public posts and job-search discussions. If your concern involves protected material, ask how to provide the details securely; an ordinary email or personal note-taking service should not become a new place to reproduce that material.
Who should receive your report?
Use the security office or other recipient designated by your organization. For DoD contractors, DCSA identifies the company Facility Security Officer as the self-reporting contact. If you work directly for an agency or service, follow its security reporting instructions and ask for routing help when needed.
DCSA’s self-reporting guidance distinguishes contacts by employment status and notes that agency procedures can differ. A message to a colleague can help you reach the right office, but confirm that the designated office has received the concern.
An initial notification can be brief: “I am abroad and want to report an approach involving a request for work information. I am currently safe. Please confirm receipt and the approved method for providing my account and existing messages.” Include a safe way to contact you and indicate if further contact is expected.
Keep a record of when you reported, which office received it, and the instructions you were given. If you cannot reach the usual recipient, follow the alternate contact or escalation process established for your trip. Do not invent a deadline from an unrelated travel-reporting rule.
How do you separate concern from speculation?
Describe the behavior that concerned you, then label your interpretation as a concern rather than a fact. Security professionals can assess affiliation, significance, and next steps. Your role is to supply an accurate account, including what you do not know.
SEAD 3 separately addresses unofficial contact with a known or suspected foreign intelligence entity and, for its specified access and position categories, attempts to obtain classified information or information whose disclosure is specifically prohibited by law. An unsuccessful request can still matter. At the same time, its casual-public-contact exception is qualified by other reporting duties; nationality alone does not establish a suspicious approach.
Questions about ordinary foreign-contact reporting concern the relationship and applicable requirements. A specific attempt to obtain protected information deserves its own factual description. Explain the request rather than using the person’s accent, appearance, or presumed citizenship as evidence of intent.
Keep any routine trip reporting separate enough that the suspicious event remains easy to identify. When reviewing foreign travel reporting procedures, ask your security office how an immediate incident notification connects with the later travel report. Filing an itinerary should not be assumed to have conveyed an encounter that was never described.
Frequently Asked Questions
Must I prove the person works for a foreign intelligence service?
No proof of employment is needed to raise a concern with your security contact. State the request, circumstances, and basis for any suspicion. Mark the person’s affiliation unknown if you cannot verify it, and let the authorized office assess the event.
Should I wait until I return home?
Use your designated reporting channel promptly. NCSC’s company travel guidance recommends notifying a U.S.-based colleague as soon as possible about a suspicious approach. Ask your security contact how to complete the incident report and any later travel reporting through the appropriate channels.
What if I already answered a question?
Report what you actually said or shared without reconstructing protected content in an unapproved channel. Explain where any original material exists and ask how to provide details securely. Avoid minimizing the exchange or assuming that sharing information determines a clearance outcome.
What if my account is incomplete?
Send the known facts and identify the gaps. You can correct or supplement the record through the receiving office. Once safe, contact your designated security point of contact with the request, location, approximate time, your response, and a safe way to reach you.