Security that keeps tech data controlled, the ops floor fenced, launch kits ready.Security that keeps techdatacontrolledtheopsfloorfencedlaunchkitsready
Corporate IT and export-control discipline for teams building, launching and operating hardware in orbit.
Space and satellite IT
Your data is export-controlled before it's finished
A space company is part hardware shop, part software company and part operator, often all under one roof with a small IT budget. Technical data starts controlled the moment someone draws a bracket, and mission ops can't tolerate a stray laptop on the wrong network. Here's how that pressure plays out, where it fails, and what we build.
01 · The pressure
Design reviews, test campaigns and a manifest slot
In a single week, engineers push a design review package through Teamcenter, the flight software team merges builds in GitLab, the test team runs thermal vacuum at an outside facility and mission ops rehearses commanding with simulated telemetry in COSMOS. Program managers trade documents with a NASA or DoD customer and a launch provider. Lose access to controlled data for days, or have a foreign national see it without authorization, and you risk the launch slot and the contract.
- Controlled technical data in every program
- Customers with contract security clauses
- Launch dates set months in advance
Ansys STKOpenC3 COSMOSMATLAB and SimulinkSiemens NXSiemens TeamcenterGitLabJiraMicrosoft 365 GCC High
02 · How it breaks
A shared drive with no citizenship check
Controlled drawings sit on a commercial cloud drive that every employee and intern can browse, including foreign persons not covered by a license. An engineer emails an interface document to a launch provider's personal address. A mission ops workstation doubles as someone's daily email machine, so a phishing link lands one hop from the ground segment. Contractors at a test facility plug unknown laptops into the test network. And nobody can say which systems fall under the NASA or DFARS clause in the contract.
- No access control by export authorization
- Ops workstations used for everyday email
- Unknown laptops on test facility networks
Ansys STKOpenC3 COSMOSMATLAB and SimulinkSiemens NXSiemens TeamcenterGitLabJiraMicrosoft 365 GCC High
03 · What we change
An enclave for controlled data and a fenced ops floor
We build a controlled-data enclave, often in Microsoft 365 GCC High, where access is granted only to people your export compliance lead has approved. Engineering workstations get device management, encryption and data loss rules that flag controlled markings. Mission ops gets dedicated workstations on a separate network with no email or browsing, and remote access only through MFA jump hosts. Launch and test kits ship preconfigured. We coordinate with your ops engineers on anything inside ground station or flight equipment.
- Access tied to export authorization status
- Dedicated, offline-from-email ops workstations
- Preconfigured kits for launch and test sites
Ansys STKOpenC3 COSMOSMATLAB and SimulinkSiemens NXSiemens TeamcenterGitLabJiraMicrosoft 365 GCC High
04 · The after
Contract reviews and launch campaigns without panic
When a prime or NASA contracting officer asks how you meet the security clause in your contract, you hand over a system security plan that matches reality. Your export compliance lead can show who has access to controlled data and why. Engineers and ops staff fly out to a launch site with laptops that already work on the campaign network. And a phishing email that gets clicked stays an office problem, nowhere near the ground segment.
- A security plan that matches the systems
- Proof of who sees controlled data and why
- Phishing kept away from mission operations
Ansys STKOpenC3 COSMOSMATLAB and SimulinkSiemens NXSiemens TeamcenterGitLabJiraMicrosoft 365 GCC High