Ashlee M Boyer
e6be6431b2
* Adding docs-content-check-legacy-links-format workflow * Adding test-link-rewrites workflow * Migrating links to new format
11 lines
930 B
Plaintext
11 lines
930 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 service discovery](/boundary/docs/concepts/service-discovery), and [access auditing](/hcp/docs/boundary/audit-logging) to name a few. |