Client access

Use the right workspace for the information.

Portal access is issued individually after onboarding. Solstice separates ordinary business documents from controlled information so the handling method can match the contract and data requirements.

Before sending anything: Do not email or submit classified information, CUI, passwords, security keys, export-controlled data, vulnerability details, or sensitive system information. Solstice will confirm an approved exchange method first.

Secure uploads coming soon

Standard Client Portal

The secure upload portal is coming soon. When it launches, it will support ordinary engagement materials that are not classified, CUI, export controlled, credential data, or sensitive vulnerability information.

Proposals, invoices, schedules, and approved questionnaires
Non-controlled policies, drafts, and project documents
Individual access issued after identity and engagement confirmation

Request launch notification

Uploads are not active yet. Do not attach documents to the notification request.

Controlled path by approval only

CUI Capable Workspace

This path is configured separately when an engagement may involve CUI, ITAR or other contract-controlled information. It is not an upload destination until the required environment is approved and activated.

Contract and data-category requirements confirmed first
Approved cloud boundary and access controls documented
Separate identities, MFA, retention, logging, and offboarding

Discuss controlled access

A compliant product alone does not make an engagement compliant; configuration, contracts, people, procedures, and the full system boundary matter.

Controlled workspace activation

CUI access is provisioned deliberately.

The controlled path remains separate from the public website and standard portal. Activation occurs only after the engagement requirements and approved handling boundary are documented.

01Classify

Confirm whether the information is ordinary business data, FCI, CUI, ITAR, or another controlled category.

02Map requirements

Identify contract clauses, customer direction, residency, retention, and access requirements.

03Approve the boundary

Select and configure the appropriate environment before any controlled information is exchanged.

04Provision access

Issue named accounts, enforce MFA, verify permissions, and document onboarding and offboarding.

Not sure which path applies? Start with a consultation. Describe the requirement at a high level without including sensitive details.

Book a consultation