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>
49 lines
3.3 KiB
Plaintext
49 lines
3.3 KiB
Plaintext
---
|
||
layout: docs
|
||
page_title: Use cases
|
||
description: >-
|
||
Learn how HashiCorp Boundary can help you with zero trust access, multi-cloud access, single-sign on with integrated secrets management, and session monitoring.
|
||
---
|
||
|
||
# Use cases
|
||
|
||
Before understanding use cases, it's useful to know [what Boundary is](/boundary/docs/what-is-boundary). This page lists some concrete use cases for Boundary, but the possible use cases are much broader than what we cover.
|
||
|
||
## Zero trust access
|
||
|
||
Boundary’s access-on-demand workflow securely connects trusted identities to infrastructure services based on granular, admin-defined permission grants. Boundary removes the need to create or store credentials when accessing services. In this way, Boundary can be used to extend or replace many traditional access solutions like VPNs.
|
||
|
||
Traditional access solutions do not employ the Zero-Trust philosophy - meaning they fail to authenticate and authorize users’ access and actions continuously, and often lack granular access controls.
|
||
|
||
## Multi-cloud access
|
||
|
||
Having different access workflows for various infrastructure and identity providers doesn’t scale well for administrators or users. Multi-cloud organizations have a growing need to standardize access through a single workflow. Boundary creates a centralized layer of identity-based authentication and authorization to manage access to the infrastructure, regardless of the platform on which it resides.
|
||
|
||
## Single sign-on with integrated secrets management
|
||
|
||
Boundary enables a single sign-on access model with authentication from trusted identity providers, such as Azure Active Directory, Auth0, and Okta. Once authenticated, users may create sessions with integrated credential management from HashiCorp Vault without the need to re-authenticate.
|
||
|
||
## Session monitoring
|
||
|
||
Boundary provides session monitoring capabilities that give security administrators visibility into user access. Sessions are logged and consumable via the Boundary administrator UI as well as business intelligence (BI) and security information and event management (SIEM) tools.
|
||
|
||
Further, administrators can enable session recording on targets.
|
||
When you enable session recording on a target, a worker records any sessions that access that target from the time the user requests access to when that access is terminated.
|
||
Administrators can view the recordings later using a session player that runs in a browser.
|
||
|
||
## Boundary vs. other software
|
||
|
||
It can be difficult to understand how to compare the different remote access security solutions that are available on the market.
|
||
Is one a replacement for another?
|
||
Are they complementary?
|
||
Refer to the following topics for a more detailed comparison of Boundary to specific technologies:
|
||
|
||
- [Zero trust](/boundary/docs/overview/zero-trust)
|
||
- [Bastion hosts](/boundary/docs/overview/bastion-hosts)
|
||
- [VPNs](/boundary/docs/overview/vpn)
|
||
- [Privileged access management](/boundary/docs/overview/pam)
|
||
- [Software-defined-perimeter](/boundary/docs/overview/sdp)
|
||
- [Secrets management tools](/boundary/docs/overview/secrets-management)
|
||
|
||
The comparisons are philosophical in nature, and are not intended to be oppositional.
|
||
Our goal is to provide readers with a better understanding of how access management solutions overlap with Boundary, and where Boundary does things differently. |