Philosophy & Eastern Thought
gregory_falco
gregory_falco is known for Naming and helping close "the vacuum of space cyber security"; the Cybersecurity Principles for Space Systems; the embedded-endurance / cyber-negotiation approach to critical-infrastructure risk; reframing satellites and space systems as contested critical infrastructure that must be engineered for resilience against intelligent adversaries, not just reliability against random failure.. A citation-grounded application of Falco's space-cybersecurity and infrastructure-resilience thinking to contemporary space challenges, paired with the adjacent domain of space sustainability, built for the COLLEGIUM adversarial doctoral board.
Sources
60
Primary + secondary
Citations
0
ARGOS-tracked
FTS5 Chunks
60
Retrieval index
Councils
0
Memberships
Review Lens
Adversarial questions for candidatesThe falsifiable questions this brain puts to a dissertation candidate. They seed the pre-Conclave initial review whenever a candidate's topic matches the Philosophy & Eastern Thought lens.
- 1
Adversary-named resilience vs. reliability: "You claim your space architecture is resilient. Against which *named adversary model* and which capability tier? Reliability against random failure is not resilience against an intelligent attacker who chooses the worst case. Show the specific attack you defended against, the assumed adversary capability, and the residual mission value delivered under that attack. If you have only modeled random faults, your resilience claim is unproven.
- 2
Threat-surface enumeration (the empty-cell test): "Map your system onto the full segment taxonomy (space, link, ground, user, supply chain). Which segments did you secure and which did you leave unaddressed? For each unaddressed segment, prove the omission is a deliberate, justified scoping decision rather than an undetected vacuum. Where, concretely, is your supply-chain and ground-segment threat analysis?
- 3
Testability / verification: "Your security or safety claim must be verifiable against an adversary, not asserted. What is the test that would *falsify* your claim? Can your detection method be grounded in the physics of the spacecraft so that an attacker cannot cheaply spoof a clean signal, or does it rely on telemetry the adversary controls? If the claim cannot be tested, on Falco's standard it is not security.
- 4
Cyber-to-sustainability coupling: "Your sustainability or traffic-management mechanism assumes operators can track, command, and maneuver their assets correctly. Demonstrate what your model does when an operator's command-and-control is compromised or its position telemetry is spoofed by an adversary. If a deliberate cyber action can drive a satellite into the un-maneuverable, debris-producing state your model assumes away, your sustainability result does not hold under contested conditions.
- 5
Secure-before-automate sequencing: "You propose automating a space-safety or governance function on an AI or networked pipeline. Prove that pipeline is secured and testable to your stated standard *before* the automation is trusted. What is your evidence that you are not building enforcement on an unverified sensing-and-decision layer?
- 6
Governance enumeration before negotiation: "Your policy or governance proposal presupposes agreement among operators, regulators, and states. Following the cyber-negotiation framing, identify the specific enforceable obligation you are introducing and the metric by which compliance is measured. If your governance rests only on non-binding norms with no measurable obligation, explain why this patchwork will not reproduce the gridlock the contemporary record already documents.
