FSO Support for a Non-Possessing Facility: What Still Must Be Managed

Posted by Ashley Jones

FSO training for non-possessing facilities prepares you to manage a security program even when classified information stays at customer sites. DCSA calls these access-elsewhere facilities. Personnel records, briefings, reporting, visits, insider threat, and self-inspection remain part of the work; the absence of onsite storage changes the program’s scope.

Key takeaways

  • Access elsewhere still requires oversight: identify where employees work and how their security records stay current.
  • Training follows the duties: use the non-possessing curriculum and confirm applicable requirements with the oversight office.
  • Self-inspection remains required: inspect the actual program and document corrective action.
  • Records use different channels: a facility profile update does not substitute for a changed-condition package.
For employers
Hiring cleared professionals?
Post your cleared req where security-cleared candidates already search.

Post a Cleared Job

For job seekers
Holding a clearance?
Browse cleared roles from employers hiring right now.

Browse Cleared Jobs

What does access elsewhere change about the FSO’s work?

It changes where classified information is handled and which safeguards apply at the company’s location. It does not erase the contractor’s security obligations. DCSA’s NAESOC description identifies access-elsewhere facilities as cleared facilities that do not store classified information onsite.

The NAESOC overview is a useful starting point for an assigned facility’s oversight arrangements. Confirm the company’s actual assignment rather than assuming every non-possessing facility uses that office. A distributed workforce still needs an identified security contact at its employer.

The contractor’s protection responsibility extends to government locations under 32 CFR 117.7(a). For you as an FSO candidate, the useful interview question is where employees access classified information and how the company coordinates with those host sites. Ask about the current program before proposing a staffing model.

Program area Work that remains Boundary to confirm
Personnel security Eligibility, access, nondisclosure, and status records Government eligibility decisions versus contractor access administration
Training and reporting Briefings, refreshers, debriefings, reporting procedures Who delivers each briefing and keeps the evidence
Contracts and visits Security requirements and host coordination Which site controls the work and the visit
Oversight Insider threat, self-inspection, corrective action, updates FSO, insider threat official, and management responsibilities
Onsite safeguarding Confirm the facility’s approved scope Do not treat a non-possessing designation as storage approval

Which FSO training fits a non-possessing facility?

CDSE offers FSO Orientation for Non-Possessing Facilities, IS020.CU. The regulatory training requirement depends on the contractor’s involvement with classified information and the cognizant security agency’s direction. Under 32 CFR 117.12(d), contractor FSOs complete required training within six months of appointment.

The current CDSE curriculum page includes personnel and facility clearances, reporting, visits, education, and self-inspection. It requires the courses and associated exams to be completed in STEPP for curriculum credit. Use the live list when planning your training instead of an old brochure’s course count.

A completion certificate is evidence of learning. Pair it with an explanation of how you would maintain a roster, verify a briefing record, or follow up a self-inspection finding. The broader FSO requirements discussion supplies appointment context; the access-elsewhere role needs particular attention to coordination across customer sites.

What personnel and access records still need attention?

The contractor must maintain accurate eligibility and access records in the designated system. Government authorities determine eligibility; the contractor establishes the work-related access need and administers access within the rule’s conditions. Non-possessing status does not collapse those separate decisions into a customer badge request.

Under 32 CFR 117.10(a)(1)(iii), access depends on need-to-know, an appropriate favorable government eligibility determination, and a signed nondisclosure agreement, within the contractor’s authorized level. Paragraph (a)(3) addresses record accuracy. Those conditions remain relevant when the employee works elsewhere.

Ask how the employer reconciles hiring, assignment changes, and departures with its security records. A useful working roster would connect an employee to the supporting contract, host site, required briefings, and responsible security contacts. That is an organizational aid, not a replacement for the official record or a determination made by the government.

For an interview example, describe how you found and resolved a mismatch without revealing personal information. Explain who authorized the correction and how you confirmed completion. Avoid presenting an FSO’s administrative work as an adjudicative decision.

Ask about the handoff from recruiting to security. Who tells the FSO that an accepted candidate’s proposed assignment has changed, and who confirms the employee has actually arrived at the customer site? Walking through that sequence can reveal whether the role has reliable inputs or depends on chasing information after a start date has already been discussed.

Which briefings continue when employees work elsewhere?

Initial briefings, recurring education, applicable special briefings, and termination debriefings still need an owner. The contractor provides an initial briefing before access, recurring security education every 12 months, and documented debriefings when the conditions in 32 CFR 117.12(l) apply.

The training and briefings rule also addresses insider threat awareness and role-specific training. Plan around actual access and duties. An employee assigned to a customer location should know which briefing comes from the employer and which site-specific instruction comes from the host.

Special access categories need their own review. NAESOC’s resources explain that NATO, COMSEC, or CNWDI briefing requests need a valid contract security specification supporting the access requirement. Ask the responsible office which category and procedure apply before assuming that a general orientation satisfies a particular assignment.

Keep a completion record that can survive an employee transfer or an FSO handoff. In practical terms, ask where evidence lives, who follows up missing training, and how departures trigger debriefing. Repeatedly forwarding a training link is not evidence that a person completed the required activity.

When evaluating a collateral-duty role, request time to perform this follow-up as well as time to deliver training. Compare the proposed workload with the distribution of employees, customer sites, contract changes, and unresolved records. A small office can still have complicated coordination needs; ask management which other duties take priority when deadlines collide.

How should reporting and insider threat work across sites?

Employees need a clear route to their employer’s security program even when their supervisor or customer is elsewhere. The contractor must establish internal reporting procedures. Reports then follow the applicable government channel; the FSO should not assume that telling a host-site contact completes every employer obligation.

32 CFR 117.8(a)(2) and (c)(1) address internal procedures and adverse information. The adverse-information provision excludes rumor or innuendo and states that termination of employment does not remove the reporting requirement. It also specifies coordination when the employee is assigned to a government location.

The insider threat program remains the contractor’s responsibility under 32 CFR 117.7(d). If the Insider Threat Program Senior Official is a different person, paragraph (b)(4)(i) requires the FSO to be an integral member. Clarify how security, human resources, and other authorized participants exchange relevant information while following applicable privacy requirements.

Use an interview scenario rather than asking to see sensitive case files. For example, ask how an offsite employee would reach the program, who would assess the reporting channel, and how the team would track follow-up. Keep the distinction between receiving information and deciding its security significance.

What connects contracts, visits, and customer-site requirements?

The connection is the actual classified work requirement. Match employees and visits to the relevant contract security instructions and host procedures. The company’s non-possessing status does not establish what an employee may access at another location or authorize classified work at the company’s own office.

Use the DD 254 explanation to organize questions about the contract’s security requirements. For classified subcontracts, 32 CFR 117.17(a)(1) makes the prime responsible for communicating appropriate requirements. Determine which organization supplies updates and who checks that the working version reflects the assignment.

32 CFR 117.16(a)(5)(iii) says employees at government installations follow host requirements while the contractor retains security oversight of long-term visitors. Ask how visit authorization, changed assignments, and departure notifications are coordinated between the employer and host.

What should the self-inspection and facility updates cover?

Inspect the security program that actually exists: personnel, contracts, visits, training, reporting, insider threat, and management follow-through. Contractors conduct a formal self-inspection at least annually. The report records findings and resolution; the Senior Management Official provides the separate written certification required by 32 CFR 117.7(h)(2)(iii).

The NAESOC resources page identifies applicable checklists and submission guidance. Retain the formal report until after the next government security review, as required by paragraph (h)(2)(ii). An empty safe does not establish that access records or reporting procedures are effective.

Keep updates distinct. DCSA says facility profile updates can cover contracts, program assets, and security contacts, while facility-clearance changed conditions must not be submitted as profile updates. Its NAESOC page states that Entity Vetting assumed processing of changed-condition packages effective October 1, 2026.

For an assigned facility, confirm the current communication channel and package instructions on DCSA’s pages. The NISPOM rule overview can help frame the program review, but direct interpretations and case-specific questions to the cognizant security office.

For your own handoff notes, pair each open issue with its responsible person, next action, and evidence needed for closure. Ask management to explain how overdue items are escalated. That discussion helps you assess whether the advertised FSO role includes enough authority and support to carry out its stated responsibilities.

ClearedJobs.NET connects cleared talent with the employers who need it.
Whether you are hiring for a cleared req or holding a clearance and looking, start here.

Post a Cleared JobBrowse Cleared Jobs

Frequently Asked Questions

Does non-possessing mean the company has no FSO duties?

No. Access-elsewhere facilities still manage a security program covering people and classified work performed elsewhere. Assess the actual assignments, training, reporting, records, and oversight responsibilities rather than using onsite storage as the measure of workload.

Can the customer handle all employee briefings?

Delivery arrangements need to be confirmed. The contractor remains responsible for required training, and the rule specifically addresses employees dispatched elsewhere. Establish who delivers each briefing and how the employer obtains completion evidence.

Is every non-possessing facility assigned to NAESOC?

Confirm the facility’s oversight assignment. NAESOC’s resources describe oversight for select access-elsewhere companies and explain that assigned companies receive assistance from the team rather than an individually assigned industrial security representative.

How should I prepare for an access-elsewhere FSO interview?

Bring a sanitized example of resolving a records, training, or inspection issue. Before the interview, make a responsibility checklist covering the employer, host sites, FSO, insider threat official, and management; use it to identify the program handoffs you need explained.

Author

  • Ashley Jones is ClearedJobs.Net's blog Editor and a cleared job search expert, dedicated to helping security-cleared job seekers and employers navigate job search and recruitment challenges. With in-depth experience assisting cleared job seekers and transitioning military personnel at in-person and virtual Cleared Job Fairs and military base hiring events, Ashley has a deep understanding of the unique needs of the cleared community. She is also the Editor of ClearedJobs.Net's job search podcast, Security Cleared Jobs: Who's Hiring & How.

    View all posts

Comment

Notify me of updates to this conversation

Author

  • Ashley Jones is ClearedJobs.Net's blog Editor and a cleared job search expert, dedicated to helping security-cleared job seekers and employers navigate job search and recruitment challenges. With in-depth experience assisting cleared job seekers and transitioning military personnel at in-person and virtual Cleared Job Fairs and military base hiring events, Ashley has a deep understanding of the unique needs of the cleared community. She is also the Editor of ClearedJobs.Net's job search podcast, Security Cleared Jobs: Who's Hiring & How.

    View all posts
This entry was posted on Thursday, November 12, 2026 9:12 am