Frequently Asked Questions

Understanding the FileBridge Zero-Trust Access Gateway.

Security & Credentials

What is a "Zero-Trust Access Gateway"?

In traditional FTP, you "trust" anyone who has the password. In a Zero-Trust model, we assume the environment is compromised. Our gateway acts as a middle-layer that verifies every single identity request before allowing a command to reach your legacy server. We never share the root password with the end user.

How does Credential Isolation work?

When you add a server to FileBridge, we encrypt its credentials using hardware-backed AES-256-GCM keys. Your team members log in with their own verified identities. Our gateway handles the server handshake on their behalf. The team member never sees, manages, or handles your raw server credentials.

Is my data stored on FileBridge servers?

No. We use a "Zero-Buffer" architecture. We act as a streaming proxy. Bytes pass through our gateway's memory in real-time and are piped directly to your browser—they are never written to our disks.

Managed Operations

How does the compliance audit work?

Legacy FTP servers often lack granular logging of "who" did "what". Because every action in FileBridge is identity-bound, we generate an immutable audit trail that tracks every list, preview, and download back to a specific verified user.

What are the different roles?

• Viewer: Can browse directories and see previews.
• Auditor: Viewer + Can download files locally.
• Editor: Auditor + Can perform write operations (Upload, Mkdir).
• Manager: Full control, including deletion and team management.

Advanced Features

Does it support SSH keys?

Currently, FileBridge supports standard password authentication for FTP, FTPS, and SFTP. Support for SSH Private Key isolation is on our roadmap for the next enterprise update.

Can I revoke access instantly?

Yes. As the gateway owner, you can revoke a team member's access or change their role instantly from the dashboard. The next request they make will be rejected by our Identity-Aware Proxy.