Skip to content
Compliant · Managed CUI & ITAR Enclave

Service teams kept attaching regulated files to the CRM, so the CRM was made to hand them to the enclave

A global additive-manufacturing equipment maker. Outcome verified

The problem

A global additive-manufacturing equipment maker had export-controlled technical data in a commercial file-sharing service, in the CRM where service teams attached customer files, and on engineers' workstations. Leadership wanted all of it inside the compliant cloud environment without slowing the teams that relied on those workflows. The CRM could not be made compliant, and much of the content was CAD files that labeling tools do not recognize.

Why it mattered

Holding export-controlled data in non-compliant systems is a violation in itself, the company was already under regulatory scrutiny, and every uncontrolled copy widened the exposure.

What we did

Vizius rebuilt the file store inside the compliant environment to mirror the layout people knew, then intercepted the workflows rather than the users. Files attached in the CRM are relayed automatically into the compliant repository, and labels are inherited from location so users rarely choose. For CAD and other unsupported file types, Vizius automated labeling and encryption.

What changed

At the close of the second labeling phase, loss-prevention rules were enforced across email, chat, file shares and devices, unlabeled content leaving the environment was blocked by default, and CAD files were covered. Adoption was not measured.

  • Manufacturing
  • Large company
  • ITAR/EAR
  • NIST 800-171

Sound familiar?

  • Our ITAR files are in the CRM and on desktops
  • Our labeling tool can't handle CAD files
  • Users won't label things, so DLP is useless
How we did it

Managed CUI & ITAR Enclave

"Who keeps the enclave in shape after the build team leaves?"

We run the enclave day to day: device reconciliation, application vetting, user training, changes and audit-ready records.