Export-controlled information
Apply customer-approved handling requirements for ITAR or EAR information where applicable. Industry membership or a government-cloud label alone never establishes the classification or authorization.
Aerospace & Defense Security & Compliance
Controls begin with an approved boundary.
Operate sensitive, unclassified cloud and AI workloads with a clearly defined scope for users, information, services and evidence. Or assess the cloud environments you already run, without mistaking a technical assessment for regulatory approval.
The customer defines what is permitted.
Authorized customer authorities determine workload classification, programs, approved people, permitted activities, export authorizations and contractual obligations. Liminaid is designed to translate those requirements into technical control profiles, operating boundaries, repeatable checks and evidence for the agreed scope.
CUI and cybersecurity safeguards
Map applicable requirements, including NIST SP 800-171 and relevant DFARS/CMMC expectations, to observable technical checks and evidence. A passing check does not confer CMMC status or replace an assessment.
Program-specific boundaries
Connect requirements to approved programs, identities, networks, applications, AI paths and access decisions. Keep unapproved and unknown conditions distinct from verified results.
Cloud qualification is specific, not automatic.
Liminaid designs offerings across AWS GovCloud, Azure Government and qualified Google Cloud configurations. Eligibility must be reviewed by provider, region, service, deployment configuration, processing path, workload profile and operating responsibilities. Not every feature, service or cloud region is available or suitable for every boundary.
Assessing an existing environment does not authorize it to hold controlled information. Identifying that an environment has gaps can be the starting point for improvement.
Understand who can act, what is visible, and where evidence lives.
Connector and access authority
Standalone Assurance begins with customer-approved, scoped connectors and read-only observation by default. Changes require separately granted permissions and approval procedures.
AI and information paths
Govern approved sources, retrieval, model execution, agent tools, outputs and logs. Model and telemetry processing must fit the customer's agreed workload and information-handling arrangements.
Evidence and coverage
Record control definitions, observations, investigations, approvals, test results and verified outcomes. Coverage can be measured, limited, unavailable or unknown where required telemetry is missing.
Technical assurance is not certification.
Technical evaluations can help identify configuration, access and operational problems and keep evidence current. They do not make legal export-control decisions, approve the processing of controlled information or certify complete compliance. Customers, qualified assessors and other authorized parties retain their respective responsibilities.
Assess existing infrastructureExplore Cloud & AIDiscuss your requirements
