Defense contractors run their business development on Salesforce for the same reasons everyone else does: it tracks pipeline, manages accounts, and keeps sales and program teams working from one system. The complication shows up the moment that CRM starts holding information tied to a defense program. At that point, a standard commercial setup is no longer enough, and treating it as though it were is how contractors end up in front of an auditor with no good answers.
This is not a reason to avoid Salesforce for defense work. It is a reason to configure it deliberately, with the platform treated as a real piece of your compliance boundary rather than just a sales tool.
Key Takeaways
- CUI is unclassified, but mishandling it can still cost you a contract, not just a failed audit.
- A default Salesforce org is not built to hold CUI. Getting there takes intentional setup, not a checkbox.
- NIST SP 800-171 and CMMC work together: one sets the technical bar, the other checks whether you actually cleared it.
- Salesforce Government Cloud gives you an authorized foundation, but everything built on top of it is still yours to secure.
- Most compliance failures trace back to configuration choices, not the platform itself: open permissions, missing audit trails, and unvetted integrations.
What Is Controlled Unclassified Information (CUI)?
CUI is information the government creates, or that a contractor creates on the government’s behalf, that needs protection even though it is not classified. It sits below Secret or Top Secret, but exposing it can still hurt national security or give competitors an unfair edge, so federal law and policy require it to be safeguarded and shared only with authorized people.

For defense contractors, CUI shows up more often than most teams expect. It includes engineering drawings, manufacturing specifications, contract line-item detail, program schedules, and technical data restricted under the International Traffic in Arms Regulations (ITAR). All of that can land inside a CRM through a proposal attachment, a program status update, or an email thread synced into a record.
Losing control of CUI is not just a paperwork problem. It can jeopardize military readiness, trigger contract penalties, and put future Department of Defense awards at risk.
Why Using Salesforce with CUI Requires Special Considerations
Commercial cloud platforms are built for speed and easy collaboration. Sharing rules, mobile caching, email sync, and global search all make daily work faster, and all of them create ways for sensitive records to end up visible to people who should never see them.
Understanding who is responsible for what starts with the shared responsibility model. Salesforce secures the data centers, the underlying infrastructure, and the operating environment. Your organization is responsible for everything built on top of that: who has access, how data is classified, and how encryption keys are managed. Neither side covers the other’s half.
Federal regulators are not lenient about that line. Defense contracts require prompt breach reporting and verifiable safeguards for any cloud system touching CUI. Under the Department of Justice’s Civil Cyber-Fraud Initiative, contractors that misrepresent their compliance status or store defense data in an unauthorized environment have faced False Claims Act enforcement, some resulting in multi-million dollar settlements.
Key Compliance Frameworks You Need to Know
Two frameworks come up constantly in defense compliance conversations, and they are often confused for each other. They are not interchangeable. Each answers a different question.
NIST SP 800-171
NIST SP 800-171 is the technical rulebook for protecting CUI on non-federal systems. It is required by the contract clause DFARS 252.204-7012 and spans 110 individual controls across 14 categories, covering things like access restrictions, session limits, multi-factor authentication, encryption, and activity logging.
When this standard gets applied to Salesforce, it means checking specific, concrete things: Who can log in, and how are they verified? How long does a session stay open before it locks? Is sensitive data encrypted, and is every access to it logged? Every system that touches CUI has to meet each of these requirements, or have an approved workaround in its place.
CMMC (Cybersecurity Maturity Model Certification)
CMMC is the Department of Defense’s program for verifying that contractors are actually doing what NIST SP 800-171 requires, not just claiming to. Level 1 covers basic hygiene for Federal Contract Information through self-assessment. Level 2, the one that matters for CUI, maps directly onto the same 110 controls in NIST SP 800-171.
NIST SP 800-171
- What it is
- The technical rulebook for protecting CUI on non-federal systems.
- Where it comes from
- Required by the contract clause DFARS 252.204-7012.
- Scope
- 110 individual controls across 14 categories, covering access restrictions, session limits, multi-factor authentication, encryption, and activity logging.
- Applied to Salesforce
-
- Who can log in, and how are they verified?
- How long does a session stay open before it locks?
- Is sensitive data encrypted?
- Is every access to it logged?
CMMC (Cybersecurity Maturity Model Certification)
- What it is
- The Department of Defense’s program for verifying that contractors are actually doing what NIST SP 800-171 requires, not just claiming to.
- Levels
-
Level 1Basic hygiene for Federal Contract Information, through self-assessment.Level 2The one that matters for CUI. It maps directly onto the same 110 controls in NIST SP 800-171.
Depending on the contract, meeting Level 2 means either a self-assessment your company signs and submits, or an independent review by a Certified Third-Party Assessment Organization (C3PAO). Third-party certification was set to become the default in November 2026, but that step was suspended in July 2026 pending a Department of War review. Self-assessments remain a condition of award on applicable contracts. If you want the full picture of how FedRAMP and CMMC fit together and where the CMMC rollout stands right now, we broke that down in detail here.
Can Salesforce Be Used for CUI?
Yes, but only with the right environment and the right configuration behind it. A standard commercial Salesforce org is built for open collaboration, not compliance boundaries, and using one to store CUI creates exposure that a compliance review will catch.
Salesforce Government Cloud and Government Cloud Plus are built differently. They keep data within U.S. borders, restrict system administration to screened domestic personnel, and carry authorizations up to FedRAMP High (Government Cloud Plus) and Department of Defense Impact Level 5 (Government Cloud Plus Defense tier). That means the physical and network-level security is already handled, so your team can focus on the configuration layer above it. We go deeper on which data types push you toward Government Cloud, and how spillage actually happens, in our earlier look at secure data management for Salesforce Government Cloud.
Best Practices for Securing CUI in Salesforce
-
Start by identifying which fields, objects, and attachments actually hold sensitive defense information. On our projects, it most often turns up in attachments and synced email. From there, apply least privilege: give people access only to what their role requires, using permission sets and sharing rules rather than broad, organization-wide visibility. Pair that with multi-factor authentication, IP restrictions, and automatic session timeouts to close the door on unauthorized logins.
-
CUI has to be encrypted using FIPS 140-validated methods, both while it is stored and while it is moving across a network. Salesforce Shield’s Platform Encryption covers this inside the application, protecting standard fields, custom fields, search indexes, and file attachments at rest, though encrypted fields lose some filtering and sorting, so test automation first. Using your own managed encryption keys, rather than relying solely on Salesforce’s defaults, keeps that cryptographic control in your hands.
-
NIST SP 800-171 expects real accountability: knowing who touched what, and when. Standard field history tracking only shows you what changed, not who viewed or exported a record, which is not enough on its own. Salesforce Shield’s Event Monitoring closes that gap by logging views, searches, queries, and exports, and feeding that activity into a security monitoring tool where unusual behavior can actually be caught. Field Audit Trail preserves that history so it holds up years later, when an assessor asks for it.
-
Most defense contractors connect Salesforce to other systems: ERP platforms, email, engineering tools. Each of those connections is a potential exit point for CUI if it is not deliberately managed. In the orgs we review, AppExchange apps and email plugins are the most common culprits: they can quietly move records into servers that were never accredited to hold them. Every integration exchanging CUI should run over secured APIs with mutual TLS and properly scoped OAuth tokens, and every new connection should be checked against the question of where the data is actually going.
Common Mistakes Defense Contractors Make
The failures we see most often are not exotic. They are the same handful of gaps, repeated across different organizations:
- Assuming the platform is compliant by default. Salesforce provides the tools. Configuring them correctly is on you.
- Giving too many people too much access. Broad, convenient permissions are the fastest way to turn one compromised account into a wide exposure.
- Skipping activity monitoring. Without logs of who accessed what, there is no way to prove compliance during an assessment, and no way to catch a problem early.
- Leaving integrations unmanaged. Unreviewed connectors and email sync tools can pull CUI outside your compliance boundary without anyone noticing, and can quietly widen the scope of a CMMC assessment in the process.
When to Consider a GovCloud or Specialized Setup
Whether you need Government Cloud, or the higher Government Cloud Plus Defense tier (for contractors supporting a DoD mission owner's IL4 or IL5 data), depends on your specific contracts. If an award includes DFARS 252.204-7012 or requires CMMC Level 2, a dedicated government environment is the more defensible path. These environments provide logical separation, run on domestically screened infrastructure, and align with ITAR requirements.
Yes, that means separate licensing, priced as a percentage of your Salesforce spend, and a real migration effort. Weighed against the cost of a failed assessment, False Claims Act exposure, corrective action plans, or a lost contract, that investment is the cheaper problem to have.
How Vectr Solutions Supports Secure Salesforce for Defense Contractors
This is the kind of work we do every day. Vectr Solutions builds and supports Salesforce environments for contractors operating under exactly these requirements, where business development, program execution, and engineering teams need to move fast without stepping outside federal security standards.
When an aerospace and defense manufacturer building unmanned aerial systems needed a secure, compliant environment to manage business development across both commercial and government segments, we built them a FedRAMP-aligned Salesforce Government Cloud instance, staffed exclusively by U.S. citizen resources. That build included Salesforce Shield for compliance monitoring, MFA and SSO enforcement, a secured Outlook integration, and pipeline dashboards the team could actually trust, giving them one centralized, audit-ready source of truth for a business that had never had one.
We help contractors with the full path:
-
Step 1
Map
Where CUI lives today
-
Step 2
Design
Least-privilege permission structures
-
Step 3
Deploy
Shield encryption and Event Monitoring
-
Ongoing
Govern
Habits that keep the environment compliant long after setup is done
If you are trying to figure out where your own org stands, our Salesforce Advisory and Governance team is a good place to start that conversation.
Build a Secure, Compliant Salesforce Environment
Handling CUI in Salesforce takes more than a default setup. It takes a deliberate, compliance-first approach built by people who understand what a defense contractor's environment actually needs to hold up under review.
If you are preparing for a CMMC assessment or rethinking how your CRM handles sensitive program data, talk to a Vectr Solutions expert about what a secure environment would look like for your team.