CUI Handling Statement & Customer Responsibility Matrix
Effective date: September 22, 2026
1. 1. What KollGuard is, in CMMC terms
KollGuard is a readiness and continuous-monitoring tool. It helps a defense contractor attest NIST SP 800-171 requirements, compute an SPRS score, scope an assessment, and export a System Security Plan, POA&M and Shared Responsibility Matrix. It also watches the contractor's vendors against the FedRAMP Marketplace and DFARS flow-down expectations.
KollGuard is not a CUI system and is not inside your CUI boundary:
- KollGuard stores findings, attestations, scores, scope metadata and vendor metadata. It is designed not to store Controlled Unclassified Information (CUI), ITAR/EAR technical data, or classified information, and customers are contractually prohibited from entering it.
- KollGuard is designed not to process, store or transmit CUI on your behalf. Whether the FedRAMP Moderate-equivalency requirement in DFARS 252.204-7012(b)(2)(ii)(D) applies to a service you use is your determination with your assessor and counsel.
- Asset categorization is your determination with your C3PAO. Because KollGuard connects to systems in your environment and performs security-monitoring functions, your assessor may treat it as a Security Protection Asset. This statement describes how KollGuard works so you can make that determination; it is not a scoping decision or legal advice.
KollGuard is not FedRAMP authorized and does not claim to be. Nothing KollGuard produces is a certification, an authorization, or an assessment result. SPRS, the CMMC eCMS and your C3PAO are the systems and parties of record.
2. 2. Guardrails KollGuard enforces
- Free-text fields on the CMMC surfaces (scope inventory, system profile, attestation notes, implementation statements, POA&M entries) reject text carrying CUI marking banners (CUI//, CONTROLLED//, (CUI), NOFORN, FOUO, distribution statements, ITAR/EAR markings).
- Every CMMC input reminds the operator never to paste CUI.
- Scanners are read-only by default (writes such as opening pull requests or applying settings changes happen only when you authorize them) and store findings, not content: no source code or database rows are retained. Documents you upload (for example vendor due-diligence files) are stored and must not contain CUI.
- Evidence is linked by URL to your own systems. Uploaded vendor documents are for vendor due diligence and must not contain CUI.
- All customer data is hosted in the United States (AWS us-east-2 via Supabase), encrypted in transit and at rest, with a hash-chained audit log.
3. 3. Customer Responsibility Matrix
Because KollGuard is outside the CUI boundary, no 800-171 requirement is inherited from KollGuard. The right-hand column describes KollGuard's own platform security so you can risk-manage the tool; the middle column is what stays with you for your CUI environment.
| 800-171 family | You (CUI environment) | KollGuard (platform, outside the boundary) |
|---|---|---|
| AC Access Control | Implement and attest 3.1.x for the enclave. | Role-based access, tenant isolation via row-level security, MFA, SSO/SCIM on Enterprise. |
| AT Awareness & Training | 3.2.x for enclave users. | Staff security training; no customer obligation. |
| AU Audit & Accountability | 3.3.x for the enclave; our audit log can evidence monitoring activities. | Hash-chained, tamper-evident audit log of every tenant action; exportable. |
| CM Configuration Management | 3.4.x, including the asset inventory (our scope inventory is a working copy; your SSP is the record). | Infrastructure as code, reviewed pull requests. |
| IA Identification & Authentication | 3.5.x for the enclave. | Supabase Auth with MFA; tenant-scoped API keys. |
| IR Incident Response | 3.6.x, including the DFARS 7012 72-hour DoD report (your obligation). | Incident notification to affected customers per the Terms; not a 7012 reporting party for your CUI. |
| MA Maintenance | 3.7.x. | Managed platform. |
| MP Media Protection | 3.8.x; CUI never leaves the enclave onto KollGuard. | Not applicable (no CUI media). |
| PE Physical Protection | 3.10.x for your facilities. | Inherited from AWS for our platform; irrelevant to your enclave. |
| PS Personnel Security | 3.9.x. | Background-checked staff; least-privilege production access. |
| RA Risk Assessment | 3.11.x; scan findings and vendor gaps feed your risk assessment. | Continuous vulnerability scanning of the platform. |
| CA Security Assessment | 3.12.x; SSP / POA&M / SRM exports are drafts you own and finalise. | SOC 2-aligned platform controls. |
| SC System & Communications | 3.13.x for the enclave. | TLS 1.2+, encryption at rest, US hosting. |
| SI System & Information Integrity | 3.14.x; findings can evidence flaw-remediation tracking. | Platform patching and monitoring. |
4. 4. Your obligations
- Do not enter CUI into KollGuard: describe systems and controls, link to evidence held in your CUI environment.
- Record KollGuard in your asset inventory and SSP in the category you and your assessor determine, referencing this statement for how the service handles data.
- Treat KollGuard outputs (SSP, POA&M, SRM, SPRS estimate) as drafts to be validated by your Affirming Official and, at Level 2, your C3PAO.
- The DFARS 252.204-7012 incident report and the annual affirmation under 32 CFR 170.22 stay with your Affirming Official; KollGuard only reminds.
5. 5. Contact
Security questions: security@kollitech.com · Trust Center: kollguard.com/security
