Files
threshold/website/content/docs/overview/vs/zero-trust.mdx
T
58f86936e7 [SPE-6] Boundary vs. other software (#2626)
* [SPE-6] Boundary vs. other software

* Minor edit for word choice

* Update navigation

* Change redundant word in nav

* Fix broken links

* Add anchor link

* Copy edits

* Nest navigation for What is Boundary? section

* Apply batch suggestions from code review

Co-authored-by: Adam Bouhmad <adbouhmad@gmail.com>

* Update intro sentence with new wording

* Split sections out into topics

* changes title of Introduction -> Overview to What is Boundary?

* adds redirects for use-cases and what-is-boundary

Co-authored-by: Adam Bouhmad <adbouhmad@gmail.com>
Co-authored-by: stellarsquall <stellarsquall@protonmail.ch>
2022-11-23 16:18:24 -05:00

19 lines
1.4 KiB
Plaintext

---
layout: docs
page_title: Boundary and Zero Trust
description: Describes how Boundary applies to a Zero Trust security approach
---
# 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.