One-Time Foreign National Encounters vs. Ongoing Reportable Contact
Compare casual encounters with recurring foreign-national contact, personal-information exchange, suspected intelligence contact and exploitation attempts.
Updated October 26, 2026
Security Clearance
A one-time encounter with a foreign national is not automatically reportable under DCSA’s cleared-industry SEAD 3 guidance. Limited or casual public contact generally is not reportable unless another reporting rule applies. The answer changes when contact is expected to recur, a close relationship develops, nonpublic personal information is exchanged, foreign intelligence involvement is suspected, or someone tries to exploit your covered position.
Key takeaways
- Casual can remain casual: a brief public encounter is not the same as a continuing relationship.
- A developing acquaintanceship matters: contact that recurs or is expected to recur can change how personal-information exchange is assessed.
- Content matters: friendly public conversation differs from sharing information of an intimate or nonpublic nature.
- Threat indicators override the casual label: suspected intelligence contact or an exploitation attempt belongs in a separate reporting category.
- Your program controls the channel: use the reporting instructions and security contact assigned to you.
Is a one-time encounter with a foreign national reportable?
For contractor personnel covered by DCSA’s DoD NISP guidance, limited or casual public contact is not reportable by itself, absent another SEAD 3 requirement. “One time” is not the end of the analysis, though. The setting, what was exchanged, whether another meeting is expected, and whether anything was suspicious all count.
The current DCSA NISPOM Rule FAQ on SEAD 3 gives the limited-or-casual public-contact answer. That page implements reporting for covered contractor personnel under the National Industrial Security Program and DoD security cognizance. It is not a universal script for every military member, federal civilian, intelligence program, or special-access environment.
Your department, agency, customer, or program can provide additional procedures. Official-duty contacts can also be governed by agency instructions. Use the DCSA comparison to understand the factors, then follow the channel that actually binds your position.
First confirm the person is a foreign national. DCSA says SEAD 3 defines one as anyone who is not a U.S. citizen or a U.S. national, so a U.S. citizen with dual citizenship is not a foreign national and does not need to be reported as a foreign contact. The exception DCSA names is a spouse, civil-union or domestic partner, or cohabitant, whom people with TS or “Q” eligibility report regardless of citizenship. A green card holder is still a foreign national for this purpose; that contact is reportable when the relationship meets the SEAD 3 criteria.
Nationality alone does not turn every greeting into a report. Nor does meeting in public permanently settle the issue. A public encounter can develop into a recurring relationship, and a brief exchange can contain suspicious requests that trigger a different rule.
What separates limited contact from an ongoing reportable relationship?
Duration is only one factor. DCSA describes a continuing relationship with a known foreign national as reportable when it involves bonds of affection, intimate contact, personal obligation, or qualifying exchange of personal information. In-person, telephone, letter, social-media, and online contact can all maintain it.
| Fact pattern | Likely category under DCSA industry guidance | Next step |
|---|---|---|
| Brief public greeting with no expected follow-up | Limited or casual public contact | Check for another reporting requirement |
| Names exchanged and another meeting planned | Possible recurring contact if an acquaintanceship is developing; content becomes important | Apply personal-information and relationship criteria |
| Dating or intimate contact | Potential continuing relationship involving intimate contact or affection | Contact the designated security office |
| Repeated online messages with nonpublic personal details | Potential recurring personal-information contact | Preserve facts and seek reporting guidance |
| Suspected intelligence approach or exploitation | Separate reportable security category | Report through the required channel |
An isolated conversation about the venue or weather stays at the public-contact end. A relationship that develops affection, obligation, intimacy, or a pattern of private disclosures moves toward the continuing-contact criteria.
Message count is a poor threshold. One long conversation can establish an expectation of follow-up; many impersonal work emails may remain official professional interaction. Judge the relationship and the information, then ask the security office when the result is unclear.
Why can an expected second meeting change the answer?
In DCSA’s reporting exercise, contact counts as recurring when it is re-occurring or expected to re-occur “due to the development of an acquaintanceship that extends beyond typical public interaction.” A planned second meeting can be a sign of that, but the question is whether an acquaintanceship is developing, so weigh the setting and the relationship, not just the calendar. You must still assess the other criteria; expected recurrence alone does not prove that qualifying personal information was exchanged.
The FAQ describes three combined facts for that route: you know the person’s name and nationality, you shared personal information that is not reasonably expected to be public or willingly released publicly, and the contact recurs or is expected to recur.
That recurrence element is DCSA’s reading for contractors. SEAD 3’s own text lists “any contact with a foreign national that involves the exchange of personal information” and lets heads of agencies or their designees provide specific guidance and examples of updated reporting situations, with contact during official duties set by the agency. If you are a federal employee or Service member, ask your security office which standard applies instead of relying on the recurrence limiter.
A business card exchanged for an ordinary work purpose is different from a private discussion of your finances, family stress, employment vulnerabilities, travel routines, or clearance-related circumstances. DCSA’s exercise excludes ordinary information used for a generally available legal commercial transaction, personable rather than personal social exchange, and employer-related information shared to advance a work matter from its personal-information meaning.
Those exclusions have edges. The commercial-transaction exclusion also does not cover established business relationships or contracted activity. A unique offer, targeted invitation, probing follow-up, or effort to move a work contact into private channels may change the context. If the contact feels tailored to your access, employer, or personal pressure point, treat that as a security question instead of forcing it into the casual-contact exception.
When is personal-information exchange worth immediate review?
Review the contact when nonpublic details could identify, profile, pressure, or target you and the relationship is recurring or expected to continue. Name and nationality must also be known for the specific DCSA personal-information criteria. Suspicious conduct can create a separate reason to report even when that test is incomplete.
DCSA’s FAQ defines relevant personal information broadly enough to include identifying data and details about family, friends, employment, or finances. The key limitation is that the information is not reasonably expected to be publicly accessible or something you would willingly release publicly.
Public professional biography is not automatically private merely because a foreign national read it. A direct message about debt pressure, marital conflict, internal duties, travel patterns, or access may be different. Record what was actually asked and answered.
Close and continuing contact on the SF-86 is a question of questionnaire disclosure. That is related but not identical to continuing reporting under SEAD 3. Apply the correct instrument and instructions to the correct event.
Why is suspected foreign intelligence contact a different category?
Unofficial contact with someone known or suspected to be associated with a foreign intelligence entity is separately reportable under the DCSA exercise. It asks about one or more interactions, so a single approach can qualify. A recurring relationship is not required for that branch.
The official DCSA contact-and-relationship exercise also says that an attempt by anyone to obtain illegal or unauthorized access to classified information, or to compromise or exploit you because of your covered position, must be reported to the FSO regardless of the person’s nationality or relationship to you.
Focus on observable facts. Note unusual questions, requests, offered benefits, pressure, secrecy, efforts to bypass official channels, or requests for introductions. Leave investigating and accusing to the security and counterintelligence professionals. Preserve communications and report through the security or counterintelligence route in your instructions.
How do common conference, travel, dating, and online examples compare?
At a conference, a brief exchange in a public session with no private information or planned follow-up may remain casual. A later invitation to a private meeting, questions about nonpublic work, or a planned ongoing exchange changes the analysis. Official work contact may also be subject to employer or agency procedures.
During travel, a one-time encounter can matter under travel reporting even if it never becomes a relationship. SEAD 3 Appendix A includes unplanned contacts with foreign governments, companies, or citizens and the reason for contact among post-travel data elements, along with unusual or suspicious occurrences of possible security or counterintelligence significance. Follow the travel briefing you received.
Dating commonly creates repeat contact and may involve affection, intimacy, or nonpublic personal details. Assess it early rather than waiting for a label such as “serious.” The broader SEAD 3 foreign-contact reporting overview explains the ongoing obligation.
Online, a single unsolicited reaction to a public post may remain a one-time public interaction. Repeated direct messages, movement to encrypted or private channels, personal probing, or an expectation of meeting can change that. How contact began does not exempt a relationship maintained online.
What five questions should you ask before deciding not to report?
Before the five questions, confirm the person is a foreign national; in DCSA’s exercise the suspected-foreign-intelligence question comes before the citizenship question, so that one applies either way. Then ask: Was the interaction truly limited and public? Is contact recurring or expected to recur? Did the relationship involve affection, intimacy, or personal obligation? Was nonpublic personal information exchanged? Did anything suggest intelligence affiliation, targeting, unauthorized access, compromise, or exploitation?
A “yes” to the last question calls for a report under the separate security category. A combination of recurrence with relationship or personal-information factors points toward the continuing foreign-contact criteria. When the answer is uncertain, ask your security office.
The questions above are a shortcut built from the DCSA criteria. They do not replace the DCSA exercise or your agency’s procedure; run the official decision aid in sequence if it applies to you. DCSA expressly limits that aid to contractor personnel with classified-access eligibility under the NISP and DoD cognizance.
What should you record after asking your FSO?
For a DoD contractor, DCSA directs unofficial foreign-contact reports to the company Facility Security Officer. Its FAQ identifies date and time, purpose, the foreign national’s name and affiliation, and the nature of contact as core report information. Other populations should use their assigned security channel. DCSA’s FAQ also says that failing to report unofficial foreign contact, for contractors under DoD security cognizance, could result in disciplinary action up to and including loss of the security clearance.
Keep a factual note of what you reported, when, through which approved channel, and what guidance you received. Classified or unnecessarily sensitive material stays out of a personal log. Preserve original messages only as policy permits and ask the FSO how to transmit them.
After an initial report, DCSA says updates on continuing unofficial association are required when a significant change in the nature of contact meets the criteria. Routine repetition is not automatically a new narrative. A new intimate dimension, personal obligation, sensitive exchange, suspicious request, or other material change deserves review.
Your note also makes reporting qualifying foreign contacts easier to do accurately, because it preserves the original facts. If the contact is unresolved now, send the FSO the date, setting, participants, expected follow-up, information exchanged, and any suspicious feature before memory fades.
Frequently Asked Questions
Is every conversation with a foreign national reportable?
No under DCSA’s DoD cleared-industry guidance. Limited or casual public contact is not reportable absent another SEAD 3 requirement. Agency, program, official-duty, travel, or threat-reporting rules can still apply.
Does a planned second meeting automatically require a report?
Not by itself under DCSA’s personal-information criteria for contractors. Expected recurrence is one factor; assess name and nationality, the type of information exchanged, the relationship, and any separate suspicious or exploitation concern. Federal employees and Service members should ask their agency which standard applies.
Does online contact count as continuing contact?
It can. DCSA says a continuing relationship may be maintained through social media or online communication, as well as meetings, calls, or letters. The nature of the relationship controls, not the platform.
What if I do not know whether the person is linked to foreign intelligence?
Record the observable reasons for concern and contact your FSO or assigned security office. DCSA’s exercise sends an “I don’t know” answer on suspected foreign-intelligence association to the FSO for guidance; it does not endorse willful ignorance.
Must I report every later message after the relationship was reported?
DCSA says updates on a reported continuing unofficial association occur when a significant change meets the criteria. Follow your FSO’s instructions for what constitutes a significant change in your program.