← XSSG / HOME

SECURITY / PROOF OVER PROMISES

No magic.
Just measurable controls.

The first person promising an unhackable server is asking you to suspend your judgment. We would rather show the evidence and the remaining tests.

The line we will not cross

No product is unhackable, and no measured configuration test proves protection from every threat. XSSG reports tested controls, not immunity. We see security as a continuing engineering process of limiting exposure, controlling necessary interactions and measuring what changes.

Verified in live guided runs

A beta16 operator log showed Mac-to-Linux key-only SSH login, an encrypted USB vault created and restored, a recovered-key login passing independently, active UFW rules for the requested SSH sources, effective SSH password authentication disabled, and protected transaction confirmation. This is evidence of one tested path, not certification of every platform or every adversarial condition.

Not yet independently verified

  • Actual lockout followed by timed rollback recovery when the controller cannot reconnect.
  • A real VPN-source SSH connection and a negative test from a prohibited source.
  • Independent password-authentication rejection attempts across relevant SSH account/source contexts.
  • Power-loss or mid-write USB interruption, media compatibility matrix, and key-rotation on physical hardware.
  • Publisher-signed release authenticity and an independent security code audit.
  • Future FIDO2 hardware-backed enrollment and recovery workflows.

Threat separation and layers

The Open Source Security Testing Methodology Manual informs the philosophy of measuring actual controls. XSSG seeks to avoid exposing an SSH service to unnecessary source networks, require key-based access, ensure the recovery asset is separately protected, and verify the intended configuration. This is an independent implementation philosophy, not ISECOM accreditation.

Disclosure and responsible evaluation

Review the operator manual and seven-step model before running a privileged transaction. Evaluate in a staging environment first; use a working server console and preserve existing backups. Feedback and coordinated vulnerability reporting should be directed through XERXES SI’s official contact channel until a dedicated policy is published.

XSSG measures what it can verify. The beta does not guarantee an unhackable host, and planned features are not advertised as shipping.

Keep exploring

The encrypted vault · The recovery-first method · Operational manual · Q&A · Tools that complement XSSG · The wider XERXES SI story

The connection. The safeguards. The way back.

XSSG stages SSH public-key authentication and reviews source-network access before changing the firewall. It verifies a separately restored recovery login and prepares an independent rollback so an unproven change need not be treated as permanent. Release checksums support byte-integrity verification; they are not publisher signatures. No system can promise recovery from all network failures.

Explore the six technical verification layers →