@@ -522,8 +522,6 @@ the following benefits:
522
522
- High performance: Istio authorization (` ALLOW ` and ` DENY ` ) is enforced natively on Envoy.
523
523
- High compatibility: supports gRPC, HTTP, HTTPS and HTTP/2 natively, as well as any plain TCP protocols.
524
524
525
- ### Authorization architecture
526
-
527
525
The authorization policy enforces access control to the inbound traffic in the
528
526
server side Envoy proxy. Each Envoy proxy runs an authorization engine that authorizes requests at
529
527
runtime. When a request comes to the proxy, the authorization engine evaluates
@@ -536,26 +534,16 @@ authorization policies using `.yaml` files.
536
534
caption="Authorization Architecture"
537
535
>}}
538
536
539
- ### Implicit enablement
540
-
541
- You don't need to explicitly enable Istio's authorization features; they are available after installation.
542
- To enforce access control to your workloads, you apply an authorization policy.
543
-
544
- For workloads without authorization policies applied, Istio allows all requests.
545
-
546
- Authorization policies support ` ALLOW ` , ` DENY ` and ` CUSTOM ` actions. You can apply multiple policies, each with a
547
- different action, as needed to secure access to your workloads.
537
+ ### Policy Precedence
548
538
549
- Istio checks for matching policies in layers, in this order: ` CUSTOM ` , ` DENY ` , and then ` ALLOW ` . For each type of action,
550
- Istio first checks if there is a policy with the action applied, and then checks if the request matches the policy's
551
- specification. If a request doesn't match a policy in one of the layers, the check continues to the next layer .
539
+ Authorization features are implicitly enabled. For workloads without authorization policies applied, Istio allows all requests.
540
+ To enforce access control to your workloads, you may apply one or multiple authorization policies with ` ALLOW ` , ` DENY ` and ` CUSTOM ` actions.
541
+ When you apply multiple authorization policies to the same workload, Istio applies them additively .
552
542
553
- The following graph shows the policy precedence in detail:
543
+ Istio checks for matching policies in layers by the order: ` CUSTOM ` , ` DENY ` , ` ALLOW ` . The following graph shows the policy precedence in detail:
554
544
555
545
{{< image width="50%" link="./authz-eval.png" caption="Authorization Policy Precedence">}}
556
546
557
- When you apply multiple authorization policies to the same workload, Istio applies them additively.
558
-
559
547
### Authorization policies
560
548
561
549
To configure an authorization policy, you create an
0 commit comments