58f86936e7
* [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>
11 lines
1.0 KiB
Plaintext
11 lines
1.0 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Boundary vs. Software Defined Perimeter
|
|
description: Compares Boundary to using a Software Defined Perimeter solution
|
|
---
|
|
|
|
# Boundary vs. Software Defined Perimeter
|
|
|
|
Software Defined Perimeter (SDP) solutions secure access to applications and infrastructure based on user identity.
|
|
Boundary is fundamentally an SDP solution that takes a zero trust approach to security design for system access; access to services is granted based on the scoped identity and intent of a user.
|
|
Boundary is a scalable proxy that enables identity-based access with multiple layers of security controls including [dynamic credentials](https://developer.hashicorp.com/boundary/tutorials/hcp-administration/hcp-ssh-cred-injection?in=boundary%2Fhcp-administration), [context-based access](https://developer.hashicorp.com/boundary/tutorials/access-management/oidc-idp-groups), [automated service discovery](docs/concepts/service-discovery), and [access auditing](https://developer.hashicorp.com/hcp/docs/boundary/audit-logging) to name a few. |