Dan Heath
3f4cd53d16
* docs: Update headings for new style rule * docs: Fix headings - Get started * docs: Fix headings - Install * docs: Fix headings - Concepts * docs: Fix typos * docs: Fix headings - Configuration * docs: Fix headings - Operations * docs: Fix headings - Troubleshoot * docs: Fix headings - Clients and Develop * docs: Fix headings - HCP and ENT * docs: Fix headings - Release notes * docs: Fix typos * docs: Fix capitalization in TOC
11 lines
924 B
Plaintext
11 lines
924 B
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](/boundary/tutorials/hcp-administration/hcp-ssh-cred-injection), [context-based access](/boundary/tutorials/access-management/oidc-idp-groups), [automated host discovery](/boundary/docs/concepts/host-discovery), and [access auditing](/hcp/docs/boundary/audit-logging) to name a few. |