Use Cases

Where GFAE applies

GFAE addresses environments where physical location, registered hardware, and authorised time are legitimate cryptographic security constraints, not aspirational policy controls. Each page describes technical applicability only; no deployed instances are claimed.

Illustrative satellite ground station at night representing a physically bounded operational site.

Operational context

Ground station boundary, Time-bound command access

Defence & Military

Threat context

Forward operating bases handle classified intelligence on equipment that may be captured or relocated. Stolen credentials and cloned devices cannot be reliably revoked in disconnected environments.

GFAE fit

Location-bound key derivation means classified data cannot be decrypted outside the approved physical perimeter, regardless of credential theft.

Explore use case

Space & Satellite

Threat context

Ground station operations involve narrow contact windows and high-value telemetry. Unauthorised access to command-and-control channels poses mission-critical risk.

GFAE fit

Ground station polygon binding and contact-window time constraints ensure command authority can only be exercised from the correct site during the correct window.

Explore use case

NHS & Healthcare

Threat context

Clinical records accessed from outside approved facilities represent a GDPR Article 25 failure mode. Staff credentials are valid globally; the physical facility boundary is not enforced cryptographically.

GFAE fit

Hospital building polygon binding and shift-based time windows constrain key derivation to approved clinical environments, aligning with privacy-by-design principles.

Explore use case

Critical Infrastructure

Threat context

SCADA and industrial control systems require operator access that should be physically constrained to approved control rooms. Remote maintenance windows are frequently abused attack vectors.

GFAE fit

Key derivation restricted to approved control-room polygons, with maintenance-window time constraints that expire automatically.

Explore use case

Enterprise & Regulated Sectors

Threat context

Cloud region labels are administrative metadata, not cryptographic constraints. Sensitive legal, financial, and compliance documents remain accessible from any jurisdiction once credentials are valid.

GFAE fit

Geographic polygon and approved-office binding enforce data residency as a cryptographic constraint rather than a policy assertion.

Explore use case

Scope note. All sector pages describe technical applicability of the GFAE architecture to known security problems in those sectors. GFAE has not been deployed in any operational environment. No sector-specific regulatory approval, certification, or procurement endorsement is claimed. GNSS-based geofencing introduces dependencies on signal availability and physical-layer integrity that are described honestly within each sector page.