DoD subcontract with CUI: what to collect from the subcontractor
For a DoD subcontract where the sub will process, store or transmit controlled unclassified information: eligibility and screening first, then the CMMC status, the SPRS score and the signed representations to have on file before award.
The list is the "DoD subcontract with CUI" requirement template as Watch ships it, read on November 15, 2026. General information, not legal advice.
What the template covers
A subcontract that handles controlled unclassified information: eligible, screened, CMMC Level 2 (Self) at least, affirmed in the last year (DFARS 252.204-7021, 32 CFR 170.23(a)(2)), an SPRS score, the DFARS 252.204-7012 safeguarding and incident-reporting questionnaire signed, insured. If the prime contract requires Level 2 (C3PAO), link the "CMMC Level 2 (C3PAO)" set too.
9 items: 4 answered from public records once you confirm which registration is the supplier's, 5 asked of the supplier. Each is marked critical or warning, which is the severity of the finding an unmet item raises in Watch.
The checklist
1. Active SAM.gov registration
Critical · Public record- What counts
- Registered, active, and not past its expiry date. A UEI on its own, without a registration, doesn't meet it.
- Why it is on the list
- An agency generally can't make an award to a company whose registration isn't active. The FAR asks registration of offerors and prime contractors rather than of subs, so for a sub this is a choice your subcontract or policy makes. Plenty of primes make it, because it gives them a public record to check. Guide: SAM.gov registration expiry: catching it before it lapses.
- Where the answer comes from
- SAM.gov's public monthly entity extract. Every registration fact carries the extract's date, and a change made mid-month shows on SAM.gov first. About this source
2. No exclusions
Critical · Public record- What counts
- No active exclusion on the registration and no confirmed exclusion match.
- Why it is on the list
- FAR 52.209-6 limits subcontracting with parties that are debarred, suspended or proposed for debarment, above the threshold in FAR 9.405-2(b). An exclusion can be added on any day, so a check from onboarding isn't the same as a check before award. Guide: FAR 52.209-6: subcontracting with excluded parties.
- Where the answer comes from
- SAM.gov's daily public exclusions extract. A record that carries the supplier's UEI or CAGE is linked to it; one that only resembles its name is shown as "possible, confirm" until a person decides. About this source
3. No screening-list match
Critical · Public record- What counts
- No confirmed match on the Consolidated Screening List (OFAC, BIS, State).
- Why it is on the list
- The Consolidated Screening List puts the export-control and sanctions lists of Treasury (OFAC), Commerce (BIS) and State into one file. They are separate from SAM.gov exclusions, and they apply to a transaction whether or not any federal money is involved. Guide: Checking suppliers against the Consolidated Screening List.
- Where the answer comes from
- The trade.gov Consolidated Screening List, loaded daily. A screening hit is matched by name and always shown as "possible, confirm" for a person to decide. About this source
4. CMMC Level 2 (Self) or higher
Critical · From the supplier- What counts
- A current CMMC status at Level 2 (Self) or higher: inside its validity, a conditional status inside its 180 days, affirmed in the last year.
- Why it is on the list
- Paragraph (f) of DFARS 252.204-7021 has the prime, before awarding a subcontract that will process, store or transmit FCI or CUI, make sure the sub has a current CMMC certificate or status at the level appropriate for the information flowed down to it. The template cites DFARS 252.204-7021, 32 CFR 170.23(a)(2). Guide: CMMC flow-down to subcontractors (DFARS 252.204-7021).
- Where the answer comes from
- The supplier: an attestation through the portal, a document it sends, or a status you record yourself. Watch doesn't assess anyone.
5. SPRS score 0 or higher
Warning · From the supplier- What counts
- A NIST SP 800-171 score of 0 or higher, under three years old. The template asks only that a score is on file and isn't below zero. Raise the minimum on your own requirement set if your contract asks for more.
- Why it is on the list
- In practice, CMMC flow-down means holding each sub's SPRS score for NIST SP 800-171 with the date it was posted, next to its CMMC status. Guide: CMMC flow-down to subcontractors (DFARS 252.204-7021).
- Where the answer comes from
- The supplier, with the date the score was posted to SPRS: through the portal, a document it sends, or a score you record yourself.
6. Section 889 representation (covered telecommunications) signed
Warning · From the supplier- What counts
- The supplier signed the "Section 889 representation (covered telecommunications)" questionnaire through the portal in the last year.
- Why it is on the list
- FAR 52.204-25(e) puts the prohibition in all subcontracts, commercial ones included, with no dollar threshold. The representations are provisions for offerors and don't flow down; primes commonly ask subs for one anyway, because it is the practical way to reach the reasonable inquiry behind their own answer. The template cites FAR 52.204-24, -25 and -26. Guide: Section 889 for subcontractors: clauses, numbers and flow-down.
- Where the answer comes from
- The supplier, signed through the portal. The item asks for a signature from the last year.
7. Cybersecurity: DFARS 252.204-7012 safeguarding and incident reporting signed
Warning · From the supplier- What counts
- The supplier signed the "Cybersecurity: DFARS 252.204-7012 safeguarding and incident reporting" questionnaire through the portal in the last year.
- Why it is on the list
- DFARS 252.204-7012 flows down to subcontracts that involve covered defense information or operationally critical support. The questionnaire covers the security requirements, the cloud services the supplier uses, and how it would report a cyber incident. The template cites DFARS 252.204-7012.
- Where the answer comes from
- The supplier, signed through the portal. The item asks for a signature from the last year.
8. Certificate of insurance on file
Warning · From the supplier- What counts
- A certificate of insurance on file that hasn't expired. One with no expiry date doesn't lapse by itself.
- Why it is on the list
- Paperwork you ask of the supplier and keep current. The item stops being met when the document on file expires.
- Where the answer comes from
- The supplier, through a one-time link or the supplier portal. Documents are stored with their issue and expiry dates, with reminders before they expire.
9. No delinquent federal debt
Warning · Public record- What counts
- The registration's debt-offset flag is not set.
- Why it is on the list
- A SAM.gov registration says whether the company has delinquent federal debt. The item reads that flag, so you hear about it rather than find it later.
- Where the answer comes from
- The delinquent federal debt flag on the supplier's SAM.gov registration.
What the supplier is asked
The supplier answers through its portal and signs. These are the questions as it sees them; some appear only after an earlier answer.
Section 889 representation (covered telecommunications)
Section 889 of the FY2019 NDAA (FAR 52.204-24, -25 and -26) prohibits covered telecommunications equipment and services: Huawei, ZTE, Hytera, Hikvision and Dahua, and their subsidiaries and affiliates.
- Does the company provide covered telecommunications equipment or services as a part of its offered products or services in the performance of any contract, subcontract or other contractual instrument? (FAR 52.204-26(c)(1))
- After a reasonable inquiry, does the company use covered telecommunications equipment or services, or any equipment, system or service that uses them? (FAR 52.204-26(c)(2))
- Did the company make a reasonable inquiry (a review of the information it holds, not an audit) before answering?
- Does the company flow FAR 52.204-25 down to its own subcontracts that may involve covered telecommunications?
What the signature says: I am authorized to make this representation for the company. It is true and complete to the best of my knowledge after a reasonable inquiry, and the company will report promptly under FAR 52.204-25(d) if it identifies covered telecommunications equipment or services during performance.
Cybersecurity: DFARS 252.204-7012 safeguarding and incident reporting
For subcontracts that involve covered defense information or operationally critical support. DFARS 252.204-7012 flows down to you: these questions cover the security requirements, the cloud services you use, and how you would report a cyber incident. Your CMMC status and SPRS score are asked separately.
- Will the company's information systems process, store or transmit covered defense information under this subcontract?
- Has the company implemented the NIST SP 800-171 security requirements on the systems that handle it? (DFARS 252.204-7012(b)(2))
- Which revision of NIST SP 800-171 does the company implement?
- Does the company have a current system security plan that describes the system boundary and how each requirement is met? (NIST SP 800-171 requirement 3.12.4)
- Has the company asked the DoD CIO, through the Contracting Officer, to vary from any NIST SP 800-171 requirement? (DFARS 252.204-7012(b)(2)(ii)(B))
- Does the company use an external cloud service to store, process or transmit covered defense information?
- Which cloud services (provider and offering)?
- Does each of them meet security requirements equivalent to the FedRAMP Moderate baseline, and the incident reporting, malicious software, media preservation, access and damage assessment terms of DFARS 252.204-7012(c) to (g)? (DFARS 252.204-7012(b)(2)(ii)(D))
- Does an external service provider (for example a managed IT or security provider) run or have access to the systems that handle covered defense information?
- Which provider, and what do they do?
- Can the company report a cyber incident to DoD at https://dibnet.dod.mil within 72 hours of discovering it? (DFARS 252.204-7012(c)(1))
- Does the company hold a DoD-approved medium assurance certificate, which DIBNet requires to file a report? (DFARS 252.204-7012(c)(3))
- Will the company submit malicious software it finds in connection with a reported incident to the DoD Cyber Crime Center, as DoD instructs? (DFARS 252.204-7012(d))
- Will the company preserve images of the affected systems and the relevant monitoring and packet-capture data for at least 90 days after reporting an incident? (DFARS 252.204-7012(e))
- When reporting an incident to DoD, will the company give us the incident report number DoD assigns, as soon as practicable, and tell us when it asks the Contracting Officer for a variance? (DFARS 252.204-7012(m)(2))
- Has the company reported a cyber incident to DoD under DFARS 252.204-7012 in the last 12 months?
- Does the company include DFARS 252.204-7012 in its own subcontracts that involve covered defense information or operationally critical support? (DFARS 252.204-7012(m)(1))
What the signature says: I am authorized to answer for the company, and these answers are true and complete to the best of my knowledge. The company will tell the customer promptly if any of them changes, and will report cyber incidents as DFARS 252.204-7012 requires.
What stays with you
- The written disclosure
- FAR 52.209-6(c) asks the sub to say in writing whether it or its principals are excluded. Watch's sanctions declaration isn't worded as that disclosure, so use your own form and keep the signed copy on the supplier. See the pre-award screening checklist.
- People
- Watch loads business entities only. If your concern is a named person, check SAM.gov directly. See where the data comes from.
- Changes made this month
- Registration facts come from SAM.gov's public monthly extract, so a renewal made at SAM.gov shows in Watch after the next monthly file. Confirm at SAM.gov when the date matters. See how fresh each source is.
- The assessment itself
- Watch doesn't assess anyone and isn't a CUI system: it keeps the status your subs give you next to their public record. Don't upload CUI to it. See the CMMC flow-down guide.
- Inspection and reporting
- Watch doesn't inspect anyone's network or find covered equipment. It holds what your subs tell you, dated and signed. The questionnaire cites the 52.204 numbers, so if your contract carries 52.240-91, attach your own wording. Reports to the government stay with you. See the Section 889 guide.
- Your contract
- Which checks an award needs depends on the prime contract, the subcontract's value and what the sub will touch. Treat this as the list to start from and read the clauses in your own contract. See which checks depend on the award.
Holding suppliers to it in Watch
Start a requirement set from the "DoD subcontract with CUI" template and edit any item. Then:
- Attach the set to a list, to a tag (such as one contract number), or to a single supplier.
- The matrix shows every supplier it covers against every item: met, unmet, needs review, or expiring.
- Each unmet item raises a "Requirement not met" finding on that supplier, and clears itself when the evidence arrives.
- Send a portal request from a supplier's page and Watch fills it with exactly the items that supplier is missing.
Keeping the record by hand instead? The free subcontractor screening log has the columns a check needs: Excel or CSV.
Try it on your own suppliers
14-day trial, no card. Up to 25 suppliers. Paste UEIs, upload a list or type one sentence, then start a requirement set from this template.