Written for the officer who signs the approval.
CONOPS | MOS (Manufacturing Operating System) is designed for and deployed in ITAR-controlled environments. This page states where data lives, who can see it, how access and history are enforced, what the service connects to, and which frameworks the deployment is built to live under.
You own the tenant, the subscription, the database and the files
There is no CONOPS-hosted environment. The service runs in your Azure Government subscription or on your server; the database is your Azure SQL or SQL Server 2022; files are in your SharePoint Online; mail moves through your Exchange Online. CONOPS holds no copy.
- Azure Government and GCC High, or your own premises. Nothing in commercial cloud regions.
- No vendor telemetry, no usage analytics leaving your environment.
- Backups follow your retention policy on your platform.
- At termination you keep everything; there is nothing to export back from us.
- Application
- Your VM or server
- Database
- Your Azure SQL (Azure Government) or SQL Server 2022
- Files
- Your SharePoint Online (GCC High)
- Identity
- Your Entra ID (.us endpoints)
- Your Exchange Online
- CONOPS holds
- Nothing
Entra ID single sign-on, six roles, one permission grid
Users sign in with your Entra ID on login.microsoftonline.us. Conditional access, MFA and device policies are yours and apply unchanged. There are no local passwords.
Six seeded roles map to a data-driven permission grid your administrator can read on one screen. Roles are site-scoped; corporate users receive a read-only cross-site role.
- Tenant Admin: configuration, sites, users, modules per site
- Site Admin: departments, workcenters, categories, SLAs, templates for one site
- Manager: full read and write on the modules enabled for their site
- Contributor: create and update records and tasks they own or are queued
- Kiosk: submit only, from a shared terminal
- Corporate Read Only: every site, no edits
| Permission | Tenant Admin | Site Admin | Manager | Contributor | Read Only |
|---|---|---|---|---|---|
| Configure sites and modules | Yes | Own site | |||
| Manage users and roles | Yes | Own site | |||
| Edit workflow templates | Yes | Yes | Yes | ||
| Create and edit records | Yes | Yes | Yes | Own / queued | |
| Read all sites | Yes | Yes | |||
| Export ledger | Yes | Own site | Yes |
Enforced in SQL with session context, not only in the UI
Every site-scoped row carries a site id. A security policy in the database filters reads and blocks writes based on the session context the service sets at sign-in. A query that bypasses the application still cannot see another site's rows.
- Filter and block predicates on every site-scoped table
- Session context set per request from the signed-in identity
- Corporate read-only role is a policy, not an exception in code
- Verify reports confirm policy coverage after every migration
| Table | Site column | Filter | Block | State |
|---|---|---|---|---|
| app.Record | SiteId | Yes | Yes | Pass |
| app.WorkflowInstance | SiteId | Yes | Yes | Pass |
| app.ProjectTask | SiteId | Yes | Yes | Pass |
| dw.Backlog | SiteId | Yes | n/a (read) | Pass |
History you read, not history you reconstruct
SharePoint Online, in your tenant
- Attachments are written to a SharePoint site you own via Graph API on graph.microsoft.us
- SharePoint versioning, Microsoft Defender scanning and your retention labels apply
- The application stores references, never file bodies, in the database
- For air-gapped on-premises sites, a file-share option is scoped as a service
Outbox out, shared mailbox in, no inbound webhooks
- Notifications queue in an outbox table and send through Exchange Online in your tenant
- Inbound replies are read by polling a shared mailbox you own; no internet-facing endpoint listens for mail
- Message bodies on records are subject to the same Row-Level Security
Two outbound destinations, both yours
The service makes no outbound calls except Microsoft Graph and SMTP in your tenant. There is no telemetry, no license check and no update beacon to CONOPS.
- HTTPS only, your certificate, behind a private endpoint or IIS
- ERP access is a linked server from your SQL Server, read only
- Remote support is screen-share only; no data leaves the customer environment
| Destination | Purpose | Direction |
|---|---|---|
| graph.microsoft.us | SharePoint attachments | Outbound |
| smtp.office365.us | Notifications | Outbound |
| login.microsoftonline.us | Sign-in (browser) | Outbound |
| Your ERP server | Linked server, nightly | Internal, read |
Pinned dependencies, published on request
The open-source dependency list with pinned versions is part of the security package. Releases are built from a tagged commit; the migration manifest names every script in order; verify reports prove the result before go-live.
US persons only, for any role with data access
Consulting and support staff who can touch customer data are US persons under a background-check policy. Remote sessions are screen-share only, with your people driving. The exact wording of the staffing statement is confirmed with counsel before launch.
Built to live under CMMC 2.0 Level 2 and NIST SP 800-171
The deployment supports your control implementation; it is not certified against these frameworks and does not claim to be. A control-mapping worksheet in the security package maps each practice family to what the platform provides, what Microsoft provides and what remains yours.
| NIST SP 800-171 family | What the platform provides | What stays with you |
|---|---|---|
| Access Control (3.1) | Entra ID SSO, six roles, permission grid, Row-Level Security in SQL, corporate read-only | Conditional access, MFA, account lifecycle |
| Audit and Accountability (3.3) | Temporal history, append-only ledger, activity log | Log retention and review cadence |
| Configuration Management (3.4) | Ordered migration manifest, idempotent scripts, verify reports, pinned dependencies | Change board, server baseline |
| Identification and Authentication (3.5) | No local credentials; identity from your tenant | Entra ID policies |
| Media Protection (3.8) | Files only in SharePoint Online; references, not bodies, in the database | Retention labels, Defender policies |
| System and Communications Protection (3.13) | HTTPS only; egress limited to Graph and SMTP in your tenant; private endpoint or IIS | Network segmentation, certificates |
| System and Information Integrity (3.14) | Defender scanning on attachments; verify reports after migrations | Patch management for servers |
DFARS 252.204-7012 is referenced as the clause the deployment is built to live under. The full worksheet, with every family, is in the security package.
What we say about ITAR, and what we do not
There is no such thing as ITAR certification for software, and CONOPS does not claim one. CONOPS | MOS is designed for and deployed in ITAR-controlled environments. Specifically: the buyer owns the tenant and the data; the architecture keeps technical data inside Microsoft 365 Government (GCC High) or on the buyer's premises; consulting staff who touch customer data are US persons; remote support is screen-share only, with no data leaving the customer environment.
CMMC 2.0 Level 2, NIST SP 800-171 and DFARS 252.204-7012 are the frameworks the deployment is built to live under, never frameworks CONOPS | MOS itself is certified against.
Counsel reviews this page and the site footer before launch. Security questions: security@conopsusa.com.
Request the security package.
Architecture description, the control-mapping worksheet, the pinned dependency list and the staffing statement, sent to a work email within one business day.