BRENNEN

Industries / Transport and vehicles / Aerospace and defense / Defense contracting

Software and communications

Armed forces buy software, cloud computing and communications networks from companies, and set the security rules those companies must meet.

7

Milestones achieved, from 1987 to 2025.

2

To watch for: announced, not yet confirmed outside.

2

Open deliverables. Nobody has shipped them.

The road

AchievedWatch forOpen

Achieved

  1. 1987

    Grading how contractors build software

    In November 1986 the Software Engineering Institute (SEI) at Carnegie Mellon University, with help from MITRE, began building a way for the US government to assess the capability of its software contractors. In September 1987 it released a process maturity framework and a maturity questionnaire, and in 1993 it published the Capability Maturity Model for Software, version 1.1, which grades how mature an organization's software process is.

    insights.sei.cmu.edu

    Credit

    Software Engineering Institute; MITRE

  2. 1997

    Ada no longer required

    In the late 1970s and early 1980s the US Department of Defense ran a competition for a new programming language, won by a French team led by Jean Ichbiah, named it Ada, and then required it for major software work. In 1996 a National Research Council board chaired by Barry Boehm advised keeping Ada for warfighting software only, saying that in fields dominated by commercial products Ada was generally less cost-effective than other languages. On 29 April 1997 Emmett Paige Jr., the assistant secretary of defense for command, control, communications and intelligence, ordered the mandate removed, so that each program would choose its language on engineering grounds.

    Lessona single required language costs more where commercial tools have moved on.

    adahome.comnextgov.comadaic.org

    Credit

    Emmett Paige Jr.; National Research Council Computer Science and Telecommunications Board

  3. 2003

    Satellite links bought as service

    In 2003 the UK Ministry of Defence awarded SKYNET 5, its military satellite communications, as a private finance initiative (PFI), a long contract in which a company provides a public service and is paid for the service. The contract went to Paradigm Secure Communications, later part of Airbus Defence and Space. After the PFI ended, a five-year service contract with Team Aurora, led by Babcock with SES, GovSat and Intelsat, took over on 1 March 2024.

    gov.uk

    Credit

    Paradigm Secure Communications (Airbus Defence and Space); UK Ministry of Defence

  4. 2004

    Digital radios, years late

    The UK first aimed to replace its analogue Clansman radios with Bowman digital radios by 1995 and missed. A new competition in 2000 led to General Dynamics UK being appointed in 2001. Bowman entered service in April 2004 with 27 listed shortfalls, and the £2.4 billion program, which paired the radios with battlefield computer systems, had to be recast with £121 million more. It covered some 48,000 radios and 28,000 computer terminals in up to 15,700 vehicles, plus ships and helicopters, and about 75,000 users to train.

    Lessonthe NAO called the 2001 timetable overly ambitious and said such systems need continual development after delivery.

    nao.org.uk

    Credit

    General Dynamics UK; UK Ministry of Defence; National Audit Office

  5. 2017

    Tanker plans leave the whiteboard

    Kessel Run, the US Air Force's in-house software team, rolled out Jigsaw in 2017 at the air operations center at Al Udeid Air Base, Qatar. The program plans air-to-air refueling tanker flights; before it, five or six people spent up to eight hours a day drawing tanker plans on a whiteboard. Air Force officials estimated in 2018 that it saved 400,000 to 500,000 pounds of fuel a week. NATO bought the software in late 2020 and used it in an exercise in 2021.

    airandspaceforces.com

    Credit

    Kessel Run, US Air Force

  6. 2022

    Four clouds instead of one

    The US Department of Defense awarded JEDI, a cloud computing contract worth up to US$10 billion, to Microsoft alone, then abandoned it in July 2021 amid Amazon's claim that the Trump administration had tainted the contest. On 7 December 2022 it picked Amazon, Google, Microsoft and Oracle for the Joint Warfighting Cloud Capability (JWCC), contracts with a shared ceiling of US$9 billion.

    Lessonone winner for a whole department's computing invited a long dispute, and the replacement spread the work across four firms.

    defensenews.com

    Credit

    US Department of Defense

  7. 2025

    Security proof becomes contract condition

    US defense contractors had to put the 110 security requirements of NIST SP 800-171 in place by 31 December 2017, checked only by their own word. The DoD Inspector General and the Defense Contract Management Agency later found that contractors did not consistently do so. Under the Cybersecurity Maturity Model Certification (CMMC) rules, in force from 16 December 2024 and written into contracts from 10 November 2025, a company must hold a current CMMC status, from a self-assessment or an outside assessment, to win contracts that involve federal contract information or controlled unclassified information, two classes of government data that are not secret, with the requirement phased in over three years. DoD estimates 337,968 companies will be covered once fully in place, 229,818 of them small, with 118,289 needing an outside Level 2 certificate.

    Lessona security rule checked only by the supplier's own word was not consistently followed.

    federalregister.govfederalregister.gov

    Credit

    US Department of Defense; NIST

Watch for

  1. One deal for 75 contracts

    The US Army says a 10-year enterprise agreement with Palantir, capped at US$10 billion, folds 15 prime contracts and 60 related contracts into one, removes reseller pass-through fees and sets volume discounts, delivering "significant cost efficiencies". The cap is a ceiling, not money committed.

    Achieved whenGAO, the DoD Inspector General or the Army Audit Agency publishes measured savings against the contracts it replaced; a search in November 2026 found none.

    globalsecurity.orgdefensescoop.com

    Claimed by

    US Army, July 2025

  2. A new UK military satellite

    The UK Ministry of Defence says SKYNET 6A, a communications satellite being built by Airbus Defence and Space UK, is scheduled for launch by SpaceX in 2027, as part of more than £5 billion it plans to invest in SKYNET over ten years.

    Achieved whenthe satellite is launched and the ministry declares its service in use.

    gov.uk

    Claimed by

    UK Ministry of Defence, August 2025

Open

  1. 01

    Score evidence like an assessor

    A public test set of made-up small-company evidence packages (policies, screenshots, configuration exports) covering the 110 requirements of NIST SP 800-171, each requirement marked met or not met by certified CMMC assessors, and a scoreboard showing how often automated tools agree with them.

    The brief
    Credit · unclaimed
  2. 02

    Which primes flow down CMMC

    A public table, refreshed every month, of the supplier terms that large defense prime contractors post on their websites, showing whether each includes the current US defense cybersecurity clauses (DFARS 252.204-7012, -7019, -7020 and the CMMC clause -7021), the clause dates, and how each asks subcontractors to prove their CMMC status.

    The brief
    Credit · unclaimed

Open 01 · the brief

Score evidence like an assessor

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A public test set of made-up small-company evidence packages (policies, screenshots, configuration exports) covering the 110 requirements of NIST SP 800-171, each requirement marked met or not met by certified CMMC assessors, and a scoreboard showing how often automated tools agree with them.

Why it is still open

A May 2026 paper (PACE) tested AI-assisted review of written security policies against NIST SP 800-53, a related federal catalogue, and reached F1 scores of 88.54% and 82.31% on two real policy sets, but it graded policy text, not the mixed evidence an assessor sees, and not against CMMC assessors. Lazarus Alliance, an accredited CMMC assessor, reports from its own 47 Level 2 assessments that 42 needed extra evidence and the average one involved about 1,920 documents and other items. In a February 2026 survey of 17 certified assessors, Logan Therrien and John Hastings found that how much evidence an assessor samples rests mostly on personal judgment and that assessors report inconsistencies between assessments, so even the human baseline is unmeasured. No public set of assessor-scored evidence was found.

arxiv.orglazarusalliance.comarxiv.org

Built with what exists

The public NIST SP 800-171 and 800-171A assessment objectives; a language model that reads documents and screenshots (see the Note "Seven more flagged" on scoring an AI document reviewer against human reviewers); the MIT-licensed scoring engine itsecops-cloud/nist-800-171-sprs-scoring on GitHub; Python.

  1. First step

    Write one made-up 20-person machine shop's evidence for the access-control requirements, with five gaps planted on purpose, and ask one certified assessor to score it.

  2. Done looks like

    30 packages, each scored independently by two certified assessors, with tool-to-assessor agreement (Cohen's kappa) reported for each requirement family beside assessor-to-assessor agreement, and the packages released under an open license.

Open 02 · the brief

Which primes flow down CMMC

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A public table, refreshed every month, of the supplier terms that large defense prime contractors post on their websites, showing whether each includes the current US defense cybersecurity clauses (DFARS 252.204-7012, -7019, -7020 and the CMMC clause -7021), the clause dates, and how each asks subcontractors to prove their CMMC status.

Why it is still open

Primes must pass CMMC requirements down to subcontractors that handle sensitive information and check their status before award, but they have no automated access to subcontractors' records in the Pentagon's Supplier Performance Risk System; subcontractors share screenshots instead. DoD says it does not track subcontractors. GitHub holds clause datasets (a 30-clause DFARS set from Cabrillo Club, BidStride's 959 clauses in JSON) but no comparison of primes' published terms.

hklaw.comfederalregister.gov

Built with what exists

A browser agent such as Browser Use, or plain Python requests, to collect public terms documents (see the Note "Deleting 80% to start over"); pdfplumber or pdftotext; regular expressions for clause numbers and dates; a language model to summarize how each prime asks for proof; USAspending.gov to rank primes by Defense Department obligations.

  1. First step

    Download five primes' published supplier terms and record which of the four clauses each lists, with dates.

  2. Done looks like

    Current terms for 25 primes in one table with clause presence and dates, five of them checked by hand, refreshed monthly for six months with a public change log.