Documentation (architecture) — Firezone

Cited by

Facts read from this source

• Definition Report an error

  “At its core, Firezone is a secure remote access platform that connects users to computing resources.”

• Osi layer Report an error

  “Firezone operates at layer 3 of the OSI model.”

• Protocols covered Report an error

  “This means it can secure any resource that can be accessed over IP, include TCP, UDP, and HTTP-based services, similar to traditional VPNs.”

• Open source Report an error

  “Open source: All source code is available for anyone to audit on GitHub.”

• Scalability Report an error

  “Scalable: Firezone was designed to be horizontally scalable from the start. Simply deploy more Gateways to handle more traffic.”

• Built on wireguard Report an error

  “Secure: Firezone is built on WireGuard®, a fast, provably-secure VPN protocol. Firezone further builds on this security with ephemeral encryption keys and firewall hole-punching to limit your exposed attack surface.”

• Policy engine Report an error

  “Easy to manage: No firewall configuration or complex ACLs are required. Firezone's Policy Engine makes access easy to manage and audit at scale.”

• Zero trust Report an error

  “Zero trust architecture: Firezone follows what's commonly known as a Zero Trust security model. This means all users and devices are untrusted by default and must be authenticated and authorized continuously before accessing each protected Resource.”

• Nist reference Report an error

  “Firezone's architecture draws heavily from The National Institute of Standards and Technology (NIST)'s published guidelines on zero trust architecture.”

• Identity providers Report an error

  “Firezone integrates with virtually any identity provider to authenticate your users in a secure and standards-compliant way.”

• Resource scope Report an error

  “These resources can be anything from a private web application or database to public SaaS apps and even entire subnets. Firezone makes no assumptions about what you want to secure access to.”

3 facts read from this page are not shown because they could not be confirmed on the page as captured.

Scores citing this record

• The DevOps Engineer Access model & connectivity
• The DevOps Engineer Identity, access policy & device posture
• The DevOps Engineer Architecture, reliability & security assurance
• The IT Lead Access model & connectivity
• The IT Lead Architecture, reliability & security assurance
• The MSP Technician Access model & connectivity
• The MSP Technician Identity, access policy & device posture
• The MSP Technician Architecture, reliability & security assurance
• The Operations Manager Access model & connectivity
• The Operations Manager Identity, access policy & device posture
• The Operations Manager Architecture, reliability & security assurance
• The Information Security Officer Access model & connectivity
• The Information Security Officer Identity, access policy & device posture
• The Information Security Officer Architecture, reliability & security assurance
• The Skeptic Access model & connectivity
• The Skeptic Architecture, reliability & security assurance