You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
link:https://www.redhat.com/en/topics/security/what-is-zero-trust[Zero trust] is an approach to designing security architectures based on the premise that every interaction begins in an untrusted state.
28
-
The Layered Zero Trust pattern describes how to implement a zero trust architecture in a {rh-ocp} environment.
29
-
The pattern identifies specific transactions between an actor and a resource within the environment.
30
-
For these transactions, you can identify the context and implement policy enforcement.
27
+
link:https://www.redhat.com/en/topics/security/what-is-zero-trust[Zero trust] is an approach to security architecture based on the idea that every interaction starts in an untrusted state.
28
+
The Layered Zero Trust pattern shows how to implement zero trust in a {rh-ocp} environment.
29
+
The pattern identifies specific transactions between an actor and a resource.
30
+
For these transactions, you can determine the context and enforce policies.
31
31
32
-
Because of the breadth and diversity of possible interactions between components in {ocp}, this pattern is presented as a set of abstract, stackable layers.
32
+
Because of the breadth and diversity of possible interactions between components in {rh-ocp}, this pattern is presented as a set of abstract, stackable layers.
33
33
These layers provide the prerequisite capabilities that are needed to implement appropriate enforcement points.
34
-
For each instance, this pattern describes the associated actors, transactions, and the zero trust policy that you can implement within the platform. To provide context for users, this pattern uses relevant business use cases and traces them to the associated implementation components.
34
+
For each instance, this pattern describes the associated actors, transactions, and the zero-trust policy that you can implement within the platform.
35
+
To provide context for users, this pattern uses relevant business use cases and traces them to the associated implementation components.
35
36
36
37
Use case::
37
38
The pattern addresses the shortcomings of traditional cybersecurity methods, such as defensive hardening and reactive detection.
@@ -85,20 +86,20 @@ The pattern consists of the following key components:
85
86
[id="sidecar-pattern"]
86
87
==== Sidecar pattern
87
88
88
-
The sidecar pattern is a deployment model where a separate container or process, called a sidecar, runs alongside a main application to handle auxiliary tasks.
89
-
In an {ocp} environment, this is simplified through the use of pods, which ensure the sidecar and main application share the same lifecycle.
90
-
This approach is highly beneficial for Zero Trust architectures because it allows for the centralized enforcement of security policies, such as authentication, authorization, traffic encryption (mTLS), rate limiting, auditing, and logging, without requiring developers to build this logic into every microservice.
89
+
The sidecar pattern is a deployment model where a separate container or process, known as a sidecar, runs alongside the main application to handle auxiliary tasks.
90
+
In an {ocp} environment, pods simplify this by ensuring the sidecar and main application share the same lifecycle.
91
+
This approach benefits Zero Trust architectures by enabling centralized enforcement of security policies such as authentication, authorization, traffic encryption (mTLS), rate limiting, auditing, and logging, without requiring developers to add this logic to every microservice.
91
92
It separates concerns, simplifies development, and allows security policies to be updated independently of the main application.
92
93
93
-
While sidecars are often criticized for adding complexity and resource usage, the text argues these are often misconceptions:
94
+
While sidecars are often criticized for adding complexity and resource usage, these are often misconceptions:
94
95
95
96
* *Complexity*: Sidecars simplify the main application by offloading tasks, and modern platforms, such as {ocp}, are designed to manage them efficiently.
96
97
* *Resource Usage*: The resource cost of a sidecar is often minimal compared to the additional CPU and memory required to integrate security logic into every application.
97
98
* *Debugging*: Sidecars can simplify debugging by isolating logs and metrics from the main application, making it easier to pinpoint the source of a policy failure.
98
99
99
-
The Layered Zero Trust pattern makes extensive use of the sidecar approach to achieve its goals by offloading critical security functions from the main application.
100
-
This provides significant benefits by centralizing policy enforcement, simplifying development, and separating security concerns.
101
-
The specific sidecar patterns used in this approach handle tasks, such as, authentication and authorization, traffic encryption, rate limiting, and auditing and logging.
100
+
The Layered Zero Trust pattern uses the sidecar approach to offload critical security functions from the main application.
101
+
This centralizes policy enforcement, simplifies development, and separates security concerns.
102
+
The sidecar patterns in this approach handle tasks such as authentication and authorization, traffic encryption, rate limiting, and auditing and logging.
0 commit comments