One sentence of federal regulation disposes of most of this question. Since 24 February 2021, when the National Industrial Security Program Operating Manual became binding regulation, 32 CFR 117.10(a)(7) has read: “Contractors will not submit requests for determination of eligibility for access to classified information for individuals who are not their employees or consultants.”

No individual application exists. The SF-86 says so in its front matter: questions go to “the office that provided you the form.” Who that office can be is wider than the contractor rule suggests.

What does the regulation say about self-sponsorship?

On the contractor track the company submits, and it must already employ you.

Three provisions of 32 CFR part 117 work together. Paragraph (a)(1)(i) requires the contractor to determine that access is essential to tasks under a classified contract. Paragraph (a)(7) limits who may be put forward, and reaches subcontractor employees too. Paragraph (a)(5) limits volume: requests are held to the minimum needed for operational efficiency and, in the sentence summaries drop, “will not be used to establish a cache of cleared employees.” That sentence kills the speculative-clearing model.

Nor is there a self-service channel. Paragraph (d) requires the electronic SF-86 to be completed in “e-QIP or its successor system” and reviewed by the facility security officer or a designated employee; no source here establishes which system is in production today, so we keep the regulation’s hedge. An FSO sees your submission before any agency does, which is what sponsorship physically consists of; the cognizant security agency adjudicates what arrives.

Is that a government-wide ban?

No, and this is where most write-ups overreach. Part 117 binds contractors, not civil servants and not uniformed members. Any claim about the whole executive branch rests on Executive Order 12968.

The rule limits its own reach. 32 CFR 117.2(b)(1) says it does not “[l]imit in any manner the authority of USG executive branch departments and agencies to grant access … to any individual designated by them,” and puts such grants outside the program. A second boundary sits at 117.10(a)(8): SCI, special access programs, Restricted Data and Formerly Restricted Data go to their own granting authorities.

The government-wide citation is Executive Order 12968, as amended: “Except in agencies where eligibility for access is a mandatory condition of employment, eligibility for access to classified information shall only be requested or granted based on a demonstrated, foreseeable need for access.” That exception is why an intelligence agency can process you as part of hiring and a contractor cannot process a stranger. We quote the 1995 text at 60 FR 40245, untouched by the later amending orders.

Its definitions finish the job. An “applicant” is “a person other than an employee who has received an authorized conditional offer of employment for a position that requires access.” No third category exists. “Employee” runs from agency staff and Armed Forces members to consultants, licensees and grantees, then closes with a catch-all that forbids arguing from absence: “any other category of person who acts for or on behalf of an agency as determined by the appropriate agency head.” Access ends when the need ends, so a posting’s clearance line describes the contract, not the employer.

Can the paperwork start before your first day?

Yes, on two written conditions. That inverts the folklore both ways: no offer, no submission, but also no waiting until day one.

Paragraph 117.10(f) allows submission “prior to the date of employment, provided: (i) A written commitment for employment has been made by the contractor. (ii) The candidate has accepted the offer in writing.” Two signatures, not one; a verbal “we would love to have you” starts nothing.

Paragraph (f)(2) adds that the commitment “must indicate employment will commence within 45 days of the employee being granted eligibility,” at a level letting you perform the contract work. That is a content requirement on the offer document, not a duty on you: section 117.10 attaches no consequence to a start date that slips and does not void your eligibility when day 45 passes. It says nothing about investigation length either. Our piece on time-to-billing keeps the two clocks apart.

Then (f)(3) requires contractors to “comply with the requirements pursuant to paragraph (a)(5) of this section.” The anti-cache limit follows you into the pre-employment route. Submitting early is a scheduling convenience for a real hire, not a side door, and is what a contingent offer on a cleared req is.

Temporary eligibility, still called an interim, changes nothing about who may ask: 117.10(l) reaches applicants, not strangers. See our interim clearance explainer.

Which sponsorship door are you standing at?

Four doors carry most private citizens into classified access. The list is not closed, and only one door is a job board’s inventory.

That last cell is deliberate: the DoD and service-level personnel security manuals refused every automated request, so anything about a recruiting station would be recollection, not sourcing. Ask a recruiter; see eligibility after service.

Four rows are not four doors in total. 117.10(m)(5) puts consultants to a government agency outside the NISP, “processed for determination of eligibility by the GCA”; 32 CFR 117.22 is a separate DHS program for cyber critical-infrastructure partners under Executive Order 13691; SEAD 4 reaches legislative and judicial staff. Read the table as a map of common doors, not an inventory.

Are the exceptions real, or folklore?

Real and sourceable, and none removes the sponsor. They remove the employer. Someone with no federal job and no defense contract can hold classified access if an agency recommends it.

Executive Order 13549 built a program for state, local, tribal and private-sector personnel. Sec. 1.3(a) carries the grant and its cap in one breath: eligibility “shall be determined by a sponsoring agency,” and access “shall not exceed the Secret level, unless the sponsoring agency determines on a case-by-case basis” that more is needed.

“Private sector” is a defined term there, and its opening words are the gate: persons “outside government who are critically involved in ensuring that public and private preparedness and response efforts are integrated as part of the Nation’s Critical Infrastructure or Key Resources (CIKR), including” five limbs. The fifth reaches “other persons not otherwise eligible … pursuant to Executive Order 12829 … determined by the Secretary of Homeland Security to require a personnel security clearance”: a catch-all inside the CIKR class, not a way around it. No critical-infrastructure role, no limb (5). Sec. 4(d)(1) then makes sponsoring agency heads “ensure on a periodic basis that there is a demonstrated, foreseeable need for such access.”

The regulatory limb is DHS’s own rule, not the NISPOM. 6 CFR 7.2(a) applies to “non-contractor personnel inside and outside the Executive Branch” cleared under EO 13549, and 7.2(b) says the part “does not apply to contractors, grantees and other categories of personnel falling under the purview of Executive Order 12829, National Industrial Security Program.” Neither “13549” nor “SLTPS” appears anywhere in 32 CFR part 117. Do not look for this route inside the contractor rule, and do not ask an FSO to open it.

The program is not a dead 2010 artifact, though the evidence is thinner than it looks: Executive Order 14354, signed 29 September 2025, continues its policy advisory committee until 30 September 2027. That renews a committee, not the clearance authority. No participant count or processing time was obtainable from a primary source; DHS pages refuse automated requests. A narrow door of unknown width.

One provision gets misread as a side entrance. EO 12968 Sec. 2.1(b)(3) allows eligibility “where there is a temporary need for access, such as one-time participation in a classified project, provided the investigative standards established under this order have been satisfied,” with a fixed expiration and project-limited access. It sits under a chapeau holding cleared numbers to “the minimum required for the conduct of agency functions,” and it governs the duration and scope of access for someone already an employee or an applicant. It creates no third category and removes no sponsor. Nor is breadth entitlement: SEAD 4 grants eligibility “only when … eligibility is clearly consistent with the national security interests of the United States, and any doubt shall be resolved in favor of national security.”

So what actually works when you have no offer?

Pick the door that matches your situation. We run a cleared job board, so read this accordingly: with no clearance and no offer, our channel is strongest in one specific case.

A cleared job board indexes requisitions, the inventory 117.9(a)(9) lets a contractor advertise while forbidding it to advertise the facility clearance itself. That is the right channel when you already hold eligibility, or when your target is an employer willing to make the written commitment 117.10(f)(1) requires. It is the wrong channel for the other three routes. Whether a given employer will sponsor an uncleared candidate is governed by nothing quoted here: our reading, that sponsorship costs enough to make firms selective, is inference, not sourced fact, and an employer that routinely sponsors strangers would falsify it.

If your route is a designated national security position in the civil service, most vacancies sit on USAJOBS, not a contractor board. Under 5 CFR 1400.101(b) every position “must be evaluated for a position sensitivity designation.” Three honest limits. Part 1400 binds competitive service, convertible excepted-service and career SES positions, but the next sentence lets agencies apply it “to other excepted service positions within the executive branch and contractor positions” too. Its list of sensitive duties is expressly not exhaustive. And nothing in part 1400 says where a job is advertised: the intelligence agencies hire into non-convertible excepted service, which the revised 5 CFR 731.101 carves out by name, and they do not post there. See contract jobs versus federal jobs.

If your route is critical infrastructure, there is no posting: you reach it through the utility, port or transit authority you already work for.

Public Trust is cleared-adjacent work, not a clearance, and its rule changed under most write-ups. OPM’s suitability final rule at 89 FR 102691 revised 5 CFR 731.106 effective 17 January 2025. Paragraph (b) is now mandatory, not a norm: “A position at the high or moderate risk level is designated as a ‘public trust’ position.” Paragraph (a) now reaches every position “in which the occupant performs a service as a contractor employee or as a nonappropriated fund employee.” And the old 14-calendar-day deadline for opening the investigation is gone. The operative text carries no number: an investigation “should be initiated before the individual is appointed …; however, where an agency does not timely initiate the investigation, it must do so as soon as possible, even if the appointment has already occurred.” A 14-day guarantee is a repealed rule. See our guide to Public Trust positions.

Then the question is finding employers who will open it: jobs that sponsor a security clearance, and the employer’s side of the decision.

Frequently Asked Questions

Can I pay for my own clearance investigation?

No, and treat any offer to sell you one as a fraud. Nothing in part 117 or Executive Order 12968 creates a fee-for-service route, and no vendor can stand in for the contractor, the hiring agency or the sponsoring agency that must ask: 117.10(a)(7) bars submission for a non-employee, 117.9(a)(10) bars a firm from applying for its own entity eligibility, and 117.10(d) runs the SF-86 through an employer’s FSO. Anyone selling clearance sponsorship, expediting or “clearance consulting” for a fee is selling something they cannot lawfully deliver.

Can I form a company and sponsor myself?

No. 32 CFR 117.9(a)(10): “A contractor or prospective contractor cannot apply for its own entity eligibility determination.” The next sentence is the useful half: a government customer or a cleared contractor may sponsor an entity “at any point during the contracting or agreement life cycle at which the entity must have access to classified information to participate,” the solicitation phase included. The on-ramp runs through a customer or a prime, never yourself; the cost sits in facility clearance sponsorship.

Can a staffing agency or a subcontractor sponsor me?

Your own employer sponsors you, and 117.10(a)(7) closes by barring requests “for employees of subcontractors.” Two conditions the pitch skips. The firm must already hold entity eligibility, because 117.9(a)(4) says “[n]either the contractor nor its employees will be permitted access to classified information until the CSA has made an entity eligibility determination,” and it cannot cure that by applying for itself. And a consultant is a defined thing: 117.3 requires an individual “under contract, and compensated directly”; a handshake arrangement is not one. Where a real consultancy exists, 117.10(m)(4) treats the consultant as an employee of the using contractor, anti-cache limit included.

Is this legal advice?

No. This summarizes published regulations and executive orders and creates no attorney-client relationship. If your situation turns on a specific determination, a revocation or a dispute over a promised sponsorship, take your own facts to a security clearance attorney.

The one thing to take away

The regulation is not hostile to you. It is indifferent to you, which is more useful: the system is not waiting for a better application. Classified access is a function of a role somebody needs performed, and every route keeps someone else in the position of asking on your behalf. The constant is a sponsor; the variable is who that sponsor can be. Executive Order 13549 pushes it past defense contractors and federal payrolls, as far as the critical-infrastructure role you already hold and no further.

Nothing suggests the contractor rule shifts soon. The last final amendment to part 117 landed 19 August 2021, and a Federal Register query on 22 July 2026 returned zero documents affecting the part since 1 January 2025. The suitability rules around it did move, so check 5 CFR 731 before relying on a date you read anywhere, including here.