Skip to content

Pass-through and shared responsibility

This page is for security reviewers and procurement teams. It states our posture plainly, says what the customer owns, says what we provide, and summarizes how we handle data.

GovConHouse holds:

  • No CMMC certification at any level.
  • No FedRAMP authorization at any impact level.
  • No SOC 2 report.
  • No authorization to operate and no third-party assessment.
  • No SPRS score of its own.

We do not claim, imply or display any of these. We will update this page the day one is granted and not before. See Certifications.

Pass-through means the customer’s obligation stays the customer’s. No certification, score or control passes from GovConHouse to the customer. Our tools help a customer prepare, store and track its own records. The customer reviews them. The customer’s senior official signs and submits.

GovConHouse does not sign anything and does not submit to SPRS or to the Department of Defense. The platform has no connection that sends anything to a government system.

Item Customer GovConHouse
CMMC obligations and assessment Owns Provides tracking and drafts
Deciding a control is met Owns Does not verify
Evidence, and its truth Owns Stores and links it
SPRS score reported to the Government Owns and submits Calculates a figure for the customer to check
Affirmation Senior official signs Generates a letter to review
System Security Plan and POA&M content Owns and validates Drafts from the customer’s data
Flow-down to subcontractors Owns Does not pass obligations down for the customer
Incident reporting to the Government Owns Does not report for the customer
Deciding whether data is CUI Owns Does not decide
FedRAMP authorization n/a Holds none. No control is inherited from us
Our own platform security Reviews it Operates it. See Security practices

CMMC and SPRS are self-reporting. The customer makes the statement to the government. FedRAMP covers a cloud product, so it applies to whoever runs the software that holds federal data. GovConHouse holds no FedRAMP authorization. Authorizations held by our hosting providers do not transfer to GovConHouse and do not reach a customer through GovConHouse.

During the pilot these tools are switched off for customer accounts. Where enabled for an account:

  • Control tracking against NIST SP 800-171, with evidence linked to each control.
  • An SPRS score calculation using the published DoD method, with the arithmetic shown.
  • Drafts of an affirmation letter, a System Security Plan, a Plan of Action and Milestones and an evidence index. Each generated affirmation letter carries a note that the customer must review it, that an authorized senior official must sign it, and that the customer submits it.
  • An append-only audit trail. See Audit trail.

Every output is a draft. The platform records what the customer enters and does not verify it.

Topic Summary Detail
What we hold Public federal procurement data from public sources, plus customer-entered records Data processing
Controlled information Customers must not upload Controlled Unclassified Information at this time See below
Tenant separation The application scopes data to each customer’s organization. GovConHouse staff with administrator access can view customer data for support, and the access is logged Data isolation
Audit records Append-only. Each record is chained to the one before it so alteration can be detected Audit trail
Government submissions Never automatic. The customer submits Above
AI processing Draft output only, reviewed by a person AI human review
Who processes data Our hosting and service providers Subprocessors
Where United States compute Data residency
Retention and deletion See the retention page and your agreement Data retention
Incident notice to customers Set by the Data Processing Agreement Ask your account contact for the current agreement

Do not upload Controlled Unclassified Information to GovConHouse at this time. Our hosting has not been assessed for it. DFARS 252.204-7012 sets requirements for systems that store, process or transmit covered defense information. The customer decides what is CUI under its contract. Files that are not CUI are fine.

The pilot must not hold CUI. Field encryption is off and is not offered as a control today, so do not count on encryption at rest for anything you upload. The customer owns CUI handling.

Terms, a Data Processing Agreement and further addenda for regulated use are available from your account contact. They govern, and this page does not replace them.

32 CFR Part 170, FAR 52.204-21, DFARS 252.204-7012, 7019, 7020 and 7021, and NIST SP 800-171. Read the current text of each.