Skip to content

Commit b2c4dd1

Browse files
committed
refactor istio.io security page Authz part
1 parent 679c600 commit b2c4dd1

File tree

1 file changed

+5
-17
lines changed
  • content/en/docs/concepts/security

1 file changed

+5
-17
lines changed

content/en/docs/concepts/security/index.md

Lines changed: 5 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -522,8 +522,6 @@ the following benefits:
522522
- High performance: Istio authorization (`ALLOW` and `DENY`) is enforced natively on Envoy.
523523
- High compatibility: supports gRPC, HTTP, HTTPS and HTTP/2 natively, as well as any plain TCP protocols.
524524

525-
### Authorization architecture
526-
527525
The authorization policy enforces access control to the inbound traffic in the
528526
server side Envoy proxy. Each Envoy proxy runs an authorization engine that authorizes requests at
529527
runtime. When a request comes to the proxy, the authorization engine evaluates
@@ -536,26 +534,16 @@ authorization policies using `.yaml` files.
536534
caption="Authorization Architecture"
537535
>}}
538536

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
548538

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.
552542

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:
554544

555545
{{< image width="50%" link="./authz-eval.png" caption="Authorization Policy Precedence">}}
556546

557-
When you apply multiple authorization policies to the same workload, Istio applies them additively.
558-
559547
### Authorization policies
560548

561549
To configure an authorization policy, you create an

0 commit comments

Comments
 (0)