Dan HeathandRobin Beck
5ce6515156
* docs: IA reorganization * docs: Updates * docs: Updates * docs: Fix links * docs: Updates * docs: Fix a typo * docs: Fix client agent topic * docs: Update Client Agent nav * docs: Fix conflict * docs: Fix a typo in Client Agent docs (#5853) * docs: Fix client agent topic * docs: Updates * docs: Updates * docs: Updates * docs: Updates * docs: Fixes get started and operations links * docs: Update nav * docs: Partials * docs: Unix partials * docs: Worker partials * docs: Updates * docs: Update workers and targets * docs: Updates * docs: Updates * docs: Fixes link * docs: Updates after sync review * docs: Updates from review feedback * docs: Move worker filter examples * docs: Fix links * docs: Updates for filters based on working session * docs: Fixes broken links * docs: Add links to other filter topics * docs: Update list intro * docs: Adds link * docs: Fixes redirects * docs: Fixes redirects * docs: Deleted mysql page from TOC * docs: Add versioned redirect * docs: Adds versioned redirects * docs: Adds versioned redirects * docs: Update redirects * docs: Update redirects * docs: Redirect fixes * docs: Update redirect format * docs: Fix a typo * docs: Fixes redirects * docs: Fixes redirect * docs: Adds links out to client agent troubleshooting * uses /etc/boundary.d/ as recommended installation directory (#6003) * docs: Updates legacy io links * docs: Fixes redirects * docs: Fix redirect * docs: Restoring deleted file --------- Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
20 lines
1.5 KiB
Plaintext
20 lines
1.5 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Boundary and zero trust
|
|
description: >-
|
|
Learn how Boundary enables a zero trust approach to security in which all access transactions are authenticated and authorized based on trusted identity.
|
|
---
|
|
|
|
# Boundary and zero trust
|
|
|
|
Malware lands on the machine of an engineer working for an HVAC vendor.
|
|
Credentials are harvested, and many of them belong to external clients.
|
|
The attackers use the vendor's system as an entry point into the large corporations they service.
|
|
They move laterally throughout the client's network, eventually using the vendor's admin credentials to access a point-of-sale system that contains PII (personally identifiable information), and the credit card information of millions of customers.
|
|
|
|
Zero trust was born out of the concept that people should have only the necessary levels of access to do their jobs, and all access transactions should be authenticated and authorized based on a trusted identity.
|
|
Zero trust is not a specific solution or class of solutions, it's a design philosophy for how access to digital systems should be secured.
|
|
Embracing a zero trust mindset assists an organization in reducing their attack surface.
|
|
|
|
You can use Boundary and other HashiCorp tools such as Vault and Consul to create a zero trust access model for infrastructure endpoints in which all transactions are authenticated, authorized, and audited.
|
|
Boundary focuses on giving developers a consistent workflow for zero trust access to their infrastructure, wherever it resides. |