SecurePass@K: Intrusion-Tolerant Cloud Storage

• SecurePass@K is a client-side, intrusion-tolerant multi-cloud storage system that uses XOR-based secret sharing to ensure information-theoretic confidentiality.
• It integrates a password vault with off-the-shelf cloud services, enabling secure retrieval and storage of secret shares with minimal performance overhead.
• The architecture guarantees file integrity and availability by allowing reconstruction from a threshold of shares even if one cloud is compromised.

SecurePass@K is a client-side, intrusion-tolerant storage system that enables secure and efficient file storage on multiple public cloud platforms, providing confidentiality, integrity, and availability guarantees through a combination of information-theoretic XOR-based secret sharing and single-password authentication. The architecture, as instantiated by the PASSAT system (Satvat et al., 2021), is entirely transparent to cloud servers, requiring no provider cooperation or server-side modifications and leveraging off-the-shelf password managers to protect per-cloud authentication credentials under a single master password.

1. System Architecture and Workflow

SecurePass@K comprises three main components: a client application (PASSAT), a password vault (e.g., LastPass), and multiple cloud storage platforms. The client application integrates a Secret-Sharing Engine ("SecretGen") that implements XOR-based threshold secret sharing, and middleware that interfaces with both the password manager for credential retrieval and cloud platforms for file storage and retrieval. An optional Splitter/Merger module divides large files into manageable chunks.

The password vault securely stores OAuth or platform-specific access tokens for each cloud service, encrypted under the user’s master password. Cloud storage platforms such as Google Drive, Box, and Dropbox each hold a secret share of every protected file.

Workflow Phases:

• Upload ("Store"):

1. User invokes PASSAT, selects file $F$, and provides master password $pw$.
2. Middleware authenticates to the password vault with $pw$ and retrieves cloud-specific access tokens $\{tk_1,\dots,tk_n\}$.
3. Optionally splitting $F$ into chunks, SecretGen generates $(k,n)$-XOR shares for every chunk or block.
4. Middleware authenticates to each cloud using $tk_i$ and uploads share $S_i$ to cloud $S_i$.

• Download ("Retrieve"):

1. PASSAT is launched and $pw$ is entered.
2. Tokens $pw$0 are fetched from the vault.
3. Middleware retrieves any $pw$1 of $pw$2 shares from the corresponding cloud platforms.
4. SecretGen reconstructs $pw$3 from these shares, reassembling any split chunks.

2. XOR-Based Secret Sharing Scheme

PASSAT implements the XOR-based $pw$4 threshold secret sharing scheme of Kurihara et al., providing information-theoretic security and high computational efficiency.

• Notation:
  • Given a file block $pw$5, partitioned as $pw$6, $pw$7 a prime $pw$8.
  • $pw$9 shares $pw$0 are generated, each length $pw$1.
  • Random masks $pw$2, $pw$3.
• Share Generation:

$pw$4

In the $pw$5 instantiation standard in PASSAT, with $pw$6 and blocks $pw$7: - Select random $pw$8, - $pw$9, - $\{tk_1,\dots,tk_n\}$0, - $\{tk_1,\dots,tk_n\}$1.

Any single share is independent of $\{tk_1,\dots,tk_n\}$2; any pair suffices to reconstruct $\{tk_1,\dots,tk_n\}$3 via XOR.

• Reconstruction: Given any $\{tk_1,\dots,tk_n\}$4 of $\{tk_1,\dots,tk_n\}$5 shares $\{tk_1,\dots,tk_n\}$6, $\{tk_1,\dots,tk_n\}$7 is recovered by inverting the XOR pattern:

$\{tk_1,\dots,tk_n\}$8

(up to a fixed, invertible linear transformation defined by the scheme).

• Role of $\{tk_1,\dots,tk_n\}$9: For $F$0, $F$1, SecurePass@K achieves information-theoretic confidentiality (any $F$2 shares reveal no information about $F$3) and tolerates up to $F$4 unavailable or compromised clouds, constituting a balance between confidentiality and availability.

3. Master-Password-Based Authentication Mechanism

All per-cloud OAuth tokens $F$5 are protected within a standard password vault $F$6, encrypted using a symmetric key derived from the master password $F$7 via PBKDF2 or Argon2, and symmetrically encrypted (typically with AES-GCM). This configuration ensures that the user only enters $F$8 into the client, never typing individual cloud credentials into PASSAT.

Authentication Protocol per Platform $F$9:

1. PASSAT requests the access token $(k,n)$0 from $(k,n)$1, supplying $(k,n)$2.
2. The vault decrypts the token and returns $(k,n)$3 to PASSAT.
3. PASSAT uses $(k,n)$4 in an OAuth Bearer header to authenticate to cloud $(k,n)$5.
4. Cloud authorizes upload/download operations.

No further cryptographic transformations are applied to the file shares beyond XOR secret-sharing. Token security is inherited from the vault’s encryption, and its rate-limited unlocking mechanism impedes offline password-guessing.

4. Security Properties and Adversarial Model

SecurePass@K's design targets three main security goals:

• Confidentiality: Any coalition of fewer than $(k,n)$6 clouds obtains no information about $(k,n)$7 (information-theoretic, by XOR sharing).
• Integrity: Any modification of a single share in a set of $(k,n)$8 shares required for reconstruction renders at least one subblock unrecoverable, yielding a corrupted or random-looking output.
• Intrusion Tolerance: The system tolerates up to $(k,n)$9 malicious or unavailable clouds and maintains single-password sign-on.

Adversary Model:

• May control up to $tk_i$0 clouds, obtaining stored shares.
• May acquire the encrypted password vault $tk_i$1 but must guess $tk_i$2 to obtain tokens; password guessing is rate-limited by $tk_i$3 and by cloud API policies.

Security Arguments:

• Confidentiality: The joint distribution of any $tk_i$4 shares is statistically independent of $tk_i$5, ensuring perfect secrecy for sub-threshold coalitions.
• Integrity: Altering any one share for reconstruction causes XOR cancellation failure, producing garbage output. Detection is possible via hash validation or evident randomness.
• Vault Attack: Even if an encrypted token blob is stolen, $tk_i$6 must be guessed (rate-limited). Obtaining $tk_i$7 via $tk_i$8 only allows cloud impersonation; reconstructing $tk_i$9 also requires $S_i$0 shares.

5. Empirical Performance and Resource Utilization

Experimental Environment:

• Client: 8 GB RAM, quad-core 2.8 GHz CPU, Windows 64-bit, 1 Gbps LAN.
• Clouds: Google Drive, Box, Dropbox, via Python SDKs.
• File sizes: 10 KB – 200 MB; share block sizes $S_i$1 bits ($S_i$2).

Measured Quantities:

• Baseline upload/download times per provider (no sharing).
• Secret-sharing CPU time per block, total share/reconstruction time.
• Total end-to-end latency: secret-share/reconstruct + $S_i$3(upload/download).

Key Results:

• Baseline upload time: 10 KB $S_i$4 1.6 s; 200 MB $S_i$5 40 s.
• Baseline download: 10 KB $S_i$6 0.7 s; 200 MB $S_i$7 55 s.
• XOR share/generation per block: single-digit nanoseconds up to $S_i$8 KB.
• Best share time for $S_i$9 KB; best reconstruction time for $S_i$0 KB.
• Overhead vs. baseline: $S_i$15% for files $S_i$2 MB; 10–15% for 10 MB files.
• Splitting 100 MB file into 1 MB pieces adds $S_i$3 s—negligible compared to network latency.

File Size	Upload Overhead	Download Overhead
$S_i$4 1 MB	$S_i$55%	$S_i$65%
10 MB	10–15%	modest
200 MB	network-bound	network-bound

6. Comparison to Related Systems

SecurePass@K/PASSAT contrasts with both baseline and prior defenses for multi-cloud storage confidentiality and availability.

• Baseline (no protection): No confidentiality/integrity, $S_i$7 storage overhead.
• Enhanced Baseline (encryption + replication): Confidentiality, higher CPU cost, tolerance limited to single-cloud failure.
• DepSky: Requires server changes, uses AES and secret-shared keys, $S_i$8 storage, increased computation.
• PPSS: Password-protected secret sharing but dependent on custom server-side password protocol logic.
• HAIL: Provides only integrity and availability with server-side changes, no confidentiality.

Distinct Features of SecurePass@K/PASSAT:

• Server Transparency: Entirely client-side, with no modifications on cloud providers.
• Single-Password SSO: All tokens are unlocked via a single master password in an off-the-shelf vault.
• Efficiency: XOR sharing imposes less than 5% additional overhead relative to direct uploads for typical file sizes.
• Intrusion Tolerance: With $S_i$9, up to any single cloud can be compromised without file exposure or modification.

7. Summary and Significance

SecurePass@K, as realized in the PASSAT framework, tightly integrates an ultra-fast XOR secret-sharing scheme with standard password-vault-based token protection to provide intrusion-tolerant, server-transparent multi-cloud storage hardening. The system delivers information-theoretic confidentiality, robust file integrity, and single-password usability for a practical spectrum of file sizes, all maintained with minimal performance overhead and no dependency on cloud provider modifications. This architecture immediately strengthens the security posture of users’ existing cloud storage accounts against adversaries capable of partial infrastructure compromise, while preserving the prevailing user and provider workflows (Satvat et al., 2021).