Prevent
Copies, uploads and unapproved network egress are denied inside the workspace before any data moves. If the dashboard goes quiet, enforcement holds.
CAGE 9FKU4 · DUNS 11-594-0422 · Founded 2021
Government and defense
A virtual SCIF for sensitive data.
Most breaches now begin with valid credentials and one copy command. i4 Zero Exfil closes that last gap, for people with valid credentials and for AI agents alike. Your people and your private AI models work on sensitive data inside your own walls. Attempts to move it out are denied, and your security team is alerted to each one.
Data in use
i4 Zero Exfil uniquely protects data in use.
It fills the gap between encrypted data at rest and encrypted data in transit. Data breaches were already daily news. AI puts a spotlight on the same gap: people and AI agents alike work on data while it is open, decrypted and readable.
At restEncrypted on disk and in backups.
In transitEncrypted on the wire by TLS.
In useOpen, decrypted and readable by anyone holding a valid session, person or AI agent. This is the state i4 Ops guards.
Security
Sovereign AI with provable data security.
Routes out are controlled, attempts raise an alert, and decisions are kept. You get prevention and the evidence to show for it.
Alert
Each attempt raises a real-time alert to your security team, naming the user, workspace, file and destination.
Prove
Requests, approvals, blocks and revokes are chained so any later edit shows. Your auditors get evidence, not assurances.
CMMC and DFARS
The CMMC pause did not pause the requirements.
Third-party CMMC certification is on hold while DoD reviews the program. The obligation behind it stands: contracts with DFARS 252.204-7012 still require the 110 security requirements of NIST SP 800-171 Rev 2, and self-assessments still count toward award.
- In effect
Phase 1 begins
Level 1 and Level 2 self-assessments become a condition of award in new solicitations.
- Paused
Phase 2 suspended
DoD suspends third-party Level 2 certification, due Nov 10, 2026, pending a review of the program.
- In effect
Rev 2 stays the baseline
A DFARS class deviation keeps self-assessments and NIST SP 800-171 Rev 2 under DFARS 252.204-7012.
- Pending
Review findings
DoD's CMMC Reform Task Force recommendations, and a new date for third-party certification.
110Security requirements in NIST SP 800-171 Rev 2, the basis of CMMC Level 2.
72 hoursTo report a cyber incident to DoD under DFARS 252.204-7012.
FY2027DoD's Zero Trust target-level deadline. Its Data pillar names data loss prevention.
Sources: 48 CFR DFARS CMMC rule (effective November 10, 2025); DoD CIO memo suspending Phase 2 (July 13, 2026); DFARS Class Deviation 2026-O0025, Revision 3 (September 3, 2026); NIST SP 800-171 Rev 2; DFARS 252.204-7012; DoD Zero Trust Strategy (November 2022).
The person with access. And the agent with it.
Most of the new tools in this market watch only AI agents. Drawings and specifications can still walk out the ordinary way: a cleared user with valid credentials and one copy command. i4 Ops puts one boundary around both.
Everyday theft by people with access
Emailing drawings to a personal address, uploading a spec to a personal drive, writing a program folder to a USB stick. Each is denied inside the workspace before data moves, and raises an alert naming the user, file and destination.
AI agents and public chatbots
Pasting CUI into a public chatbot, or an AI agent sending data to an outside service. Treated like any other route out: stopped and reported. Private models inside the enclave keep working.
84AI-driven exfiltration exploits stopped in a recent round of our own red-teaming
Red-teamed
We try to take the data ourselves.
We run a suite of exfiltration tests against the platform, and we task AI to take the data too. Attacks that come from AI agents get the same boundary and the same alert as the ones that come from people.
What happens when someone tries to walk out with the drawings.
Pick what an engineer might do with a controlled file. Everyday routes out are blocked and reported. Private AI inside the enclave keeps working.
Dan, Propulsion engineeringCUI enclave
RevC_turbine_assembly.pdfCUI · 214 pages of technical drawings
What does Dan try to do with it?
Pick an action to see what happens.
Security team0 alerts today
- No alerts yet.
Illustrative example. People, programs and data are fictional.
NIST SP 800-171 Rev 2
Mapped to the requirements you are assessed on.
Where i4 Ops can carry a requirement inside the enclave, or produce the evidence for it. CMMC assesses organizations, not products, so your assessor makes the call. We walk through your System Security Plan with you.
| Requirement | What it asks | How i4 Ops helps |
|---|---|---|
| 3.1.3Access control | Control the flow of CUI in accordance with approved authorizations. | Copies, uploads and network routes out are denied by default. Data leaves only through an approved export. |
| 3.1.20Access control | Verify and control/limit connections to and use of external systems. | Uploads to personal cloud drives and pastes into public AI chatbots from the workspace are blocked and reported. |
| 3.1.4Access control | Separate the duties of individuals to reduce the risk of malevolent activity without collusion. | Requesters do not approve their own exports. A second person decides. |
| 3.8.7Media protection | Control the use of removable media on system components. | Writes to USB sticks and removable media from the workspace are blocked and reported. |
| 3.13.1System and communications | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | The workspace boundary is enforced inside each workspace, and each crossing attempt raises an alert. |
| 3.13.6System and communications | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). | Unapproved egress is denied. Approved exports open a temporary window that closes on schedule. |
| 3.3.1Audit and accountability | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | Requests, approvals, blocks and revokes are recorded with the user, workspace, file and destination. |
| 3.3.8Audit and accountability | Protect audit information and audit logging tools from unauthorized access, modification, and deletion. | Records are chained so any later edit shows. |
| 3.6.1Incident response | Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities. | Real-time alerts on each blocked attempt give your team a starting record for detection, analysis and the 72-hour report. |
Requirement text from NIST SP 800-171 Rev 2. This map describes how the platform can support your implementation. It is not a certification, and it does not replace your assessment.
Auditability
A data boundary, and the record behind it.
i4 Ops gives your CUI a data boundary, the kind NIST SP 800-171 asks you to monitor and control. That boundary is the foundation of the event log, from the first upload to the last denied attempt.
Data uploaded
Initial data upload into the protected workspace.
User access
Who opened which workspace and data, and when.
Data modified
Changes to data inside the boundary.
Export approved
Request, second-person approval and the window it opened.
Exfiltration denied
Each unauthorized attempt, with user, file and destination.
Enclave
Built to run as an enclave.
Many contractors keep CUI in a separate enclave so fewer systems fall inside the assessment boundary. i4 Ops gives that enclave a full workspace for the people inside it, and a boundary that holds.
Ask for an enclave briefing- Where it runs
- Infrastructure you control
- Tenancy
- Single, one isolated stack
- Connectivity
- Runs offline once installed
- Sign-in
- Self-hosted
- Agents
- Outbound only, no inbound SSH
- Exports
- Second-person approval, time-boxed
- Audit
- Tamper-evident chain
- Time to deploy
- Minutes, not months
Sovereign AI
AI on CUI, with no vendor in the loop.
Engineers and analysts want AI on the documents they work with, and agency rules keep non-public information out of public AI prompts. Private models inside the enclave do the same work and keep the documents home.
| Question | Public AI tools | Sovereign AI with i4 Ops |
|---|---|---|
| Where prompts and files go | To the vendor's servers | Stay inside your enclave |
| Works with no internet | No | Yes, runs offline once installed |
| Record of each request | Whatever the vendor keeps | In your own audit chain |
| Pasting CUI | Allowed, and invisible to you | Stopped and reported |
Ask questions of your own documents
Chat with contracts, case files and research using private retrieval over your own document stores. Answers come from your files and stay with them.
Summarize and analyze sensitive files
Technical data, program records and financial data can be summarized, compared and explained by a model that keeps them inside your environment.
Build on the real dataset
Data and AI teams train and evaluate models on full production data instead of a sanitized or obfuscated copy, with the same boundary around the base data, the prompts and the results.
How it works
For the people who answer for the data, and the people who use it.
Work on the real dataset instead of a sanitized copy, with the tools you already know.
- Secure data: fuels AI innovation
- AI tools: VS Code, Jupyter and Python
- Local AI: private models, RAG and chat
- Approved Exports in a few clicks
Evidence, not assurances, ready for your System Security Plan and your assessor.
- Denial at the workspace plus real-time alerts
- Two-person export approval
- Tamper-evident audit chain
Know who tried, and what, so your program sees attempts instead of guessing at them.
- Alerts name the user, workspace, file and destination
- Covers people and AI agents
- Supports programs run under NISPOM or agency policy
Project portfolio
Protecting and auditing data that can't walk away.
“What keeps my business data from walking away?”The customer question i4 Ops was founded on, in 2021.
SiSys
A Bay Area fabless semiconductor company uses i4 Ops to protect and audit sensitive ASIC chip design data.
Ramston Capital
A multi-family residential developer and owner uses i4 Ops to protect and audit sensitive resident data.
Questions programs ask.
Is i4 Ops CMMC certified?
CMMC certifies organizations, not software. i4 Ops is designed to help you meet NIST SP 800-171 requirements inside your enclave and to produce the evidence for them. We map it to your System Security Plan with you.
Where does our data live?
On infrastructure you control. Each customer gets one isolated stack with its own sign-in, and nothing needs to leave your environment for the platform to work.
Can our engineers still use AI?
Yes. Private models run inside the enclave, on your hardware. Public AI chatbots are blocked by default, and each attempt to use one is reported.
What does it not protect against?
i4 Ops controls the paths data takes out of a workspace. It does not stop someone photographing a screen, and it does not replace identity hygiene or personnel security. We walk through the threat model on the call.
Brief your security team.
Thirty minutes. We run the exfiltration test live, show private AI working on controlled data, and go through the 800-171 map with you. Need our capability statement? Ask for it in the form.