Three moves, one direction: DoD is trying to lower the barriers to entry

Three things moving in GovCon this week that cleared contractors and staffing firms should be watching.

๐Ÿญ. ๐—ฃ๐—ฒ๐—ป๐˜๐—ฎ๐—ด๐—ผ๐—ปโ€™๐˜€ ๐—บ๐—ผ๐—ฏ๐—ถ๐—น๐—ฒ ๐—ฆ๐—–๐—œ๐—™ ๐—ณ๐—น๐—ฒ๐—ฒ๐˜: DoDโ€™s new โ€œSecure Space Networkโ€ will deploy about 50 mobile SCIFs across military bases, tech accelerators, and other mission-relevant locations nationwide. It builds on the Bridge Programโ€™s four shared facilities (Pittsburgh included) and nine privately owned SCIFs planned for Austin, San Francisco, Boston, Charleston, Chicago, Cleveland, Louisville, and New York. For years, the biggest gatekeeping capable small businesses out of classified work wasnโ€™t talent or technology; it was a locked door. If this scales, it changes who gets to compete, not just who gets to win. Watching: how fast these get accredited, and whether โ€œmission-relevant locationsโ€ means somewhere your team can actually get to.

๐Ÿฎ. ๐——๐—œ๐—ฆ๐—”โ€™๐˜€ ๐—ฐ๐—ผ๐—บ๐—ฏ๐—ฎ๐˜๐—ฎ๐—ป๐˜ ๐—ฐ๐—ผ๐—บ๐—บ๐—ฎ๐—ป๐—ฑ ๐—บ๐—ถ๐—ด๐—ฟ๐—ฎ๐˜๐—ถ๐—ผ๐—ป: 11 combatant commands. 231,000 users. 200 sites worldwide. One deadline: September 30, 2028. Thatโ€™s the scale of DISAโ€™s push to move every combatant commandโ€™s IT onto DoDNet, and industry is now asking a pointed question: Is this real market research, or are requirements being written narrow enough to justify handing the work sole-source again? This came after GDIT protested DISA adding the combatant commands to Leidosโ€™s Defense Enclave Services contract without competing it. GAO dismissed the protest only after DISA agreed to redo its market research and acquisition approach. Since then, DISA has issued two sources-sought notices in quick succession, and sources are openly questioning whether the agency is rushing rather than actually reconsidering. Every combatant command runs different systems and has different operational needs. Thatโ€™s not a detail you route around with a fast timeline. Worth watching if youโ€™re on the identity, ICAM, zero trust, or infrastructure-as-code side of things.

๐Ÿฏ. ๐—œ๐—ป๐—ฑ๐˜‚๐˜€๐˜๐—ฟ๐˜† ๐—ฝ๐˜‚๐˜€๐—ต๐—ฒ๐˜€ ๐——๐—–๐—ฆ๐—” ๐—ผ๐—ป ๐—ฐ๐—ผ๐—ป๐˜๐—ถ๐—ป๐˜‚๐—ผ๐˜‚๐˜€ ๐˜ƒ๐—ฒ๐˜๐˜๐—ถ๐—ป๐—ด ๐—ฑ๐—ฎ๐˜๐—ฎ: Cleared industry just told DCSA, in a public meeting, that continuous vetting has a visibility problem. At the September 2 NISPPAC meeting, ManTechโ€™s LaToya Coleman asked DCSA directly for more data on how CV alerts get resolved and how long itโ€™s actually taking. The concern isnโ€™t the concept; itโ€™s the black box. Contractors are seeing cleared people sidelined by alerts with no clear adjudication timeline, and that turns into real delays getting people onto contracts. This lands right as DCSA discontinued periodic reinvestigation requests at the end of June, making CV the primary model going forward, and as the same approach extends to non-sensitive public trust employees. A system that flags people faster only helps if it also resolves them faster. If you staff cleared talent, an unresolved alert on a candidate youโ€™re trying to start is a staffing problem before itโ€™s a policy problem.

Same underlying theme across all three: the department is moving to lower barriers and modernize faster, and in each case, industry is right to press on execution before taking the win for granted.

Sources: Pentagon plans fleet of portable SCIFs | Federal News Network

1 Like

The CV issue in #3 is huge for recruiters right now. Discontinuing periodic reinvestigations makes sense on paper, but turning continuous vetting into an opaque red-light system freezes revenue for staffing firms. A candidate with an unexplained alert is functionally un-billable until DCSA creates a real-time resolution workflow.

1 Like

Absolutely. The challenge isnโ€™t continuous vetting itself; itโ€™s the lack of visibility into what happens after an alert is triggered. When candidates canโ€™t get clear timelines for resolution, contractors are left managing staffing gaps, delayed starts, and revenue impacts. Greater transparency would benefit both security and mission readiness.