OSAM Dual Authorization

Before engaging in an On-orbit Servicing, Assembly, and Manufacturing (OSAM) mission, verification of servicer should be multi-factor authenticated/authorized by both the serviced's ground station and the serviced asset.

Sources

https://attack.mitre.org/mitigations/M1032/

Best Segment for Countermeasure Deployment

Ground Segment and Space Segment

NIST Rev5 Controls

CA-3(6) - Information Exchange | Transfer Authorizations
IA-2(1) - Identification and Authentication (organizational Users) | Multi-factor Authentication to Privileged Accounts
IA-2(2) - Identification and Authentication (organizational Users) | Multi-factor Authentication to Non-privileged Accounts
IA-2(6) - Identification and Authentication (organizational Users) | Access to Accounts — Separate Device

D3FEND

ISO 27001

ID: CM0065

D3FEND Artifacts:

Created: 2022/10/19

Last Modified: 2022/10/19

Techniques Addressed by Countermeasure

here here here here here here here here here

ID		Name	Description
LM-0004		Visiting Vehicle Interface(s)	Threat actors may move to other SVs through visiting vehicle interfaces. When a vehicle docks with a SV, many programs are automatically triggered in order to ensure docking mechanisms are locked. This entails several data points and commands being sent to and from the SV and the visiting vehicle. If a threat actor were to compromise a visiting vehicle, they could target these specific programs in order to send malicious commands to the victim SV once docked.

Space Threats Addressed by Countermeasure

ID	Description