| CCC.LB.CP01 | Static Load Balancing | The service can employ load balancing algorithms that follow fixed rules, such as round robin, independent of the current server state. | 1 |
| CCC.LB.CP02 | Dynamic Load Balancing | The service can employ load balancing algorithms that consider the current state of servers before distributing traffic, adjusting the distribution in real time based on server health, resource utilization, and traffic conditions. | 1 |
| CCC.LB.CP03 | Layer 7 Routing | The service can distribute incoming traffic based on application layer (OSI layer 7) information. Some of the supported protocols on layer 7 are HTTP/2, HTTP/3, HTTPS, gRPC, and WebSockets. | 3 |
| CCC.LB.CP04 | Layer 4 Routing | The service can distribute incoming traffic based on transport layer (OSI layer 4) information, using the combination of IP addresses and TCP/UDP ports rather than inspecting the content of the packets. | 1 |
| CCC.LB.CP05 | URL-Based Routing | The service can direct incoming requests to different backend resources based on the content of the request URL. | 1 |
| CCC.LB.CP06 | HTTP Header-Based Routing | The service can direct incoming requests to different backend resources based on the values of HTTP headers. | 1 |
| CCC.LB.CP07 | WebSocket Support | The service can proxy WebSocket connections between clients and backend targets. | 1 |
| CCC.LB.CP08 | Dual-stack Load Balancing | The service can accept traffic originating from both IPv4 and IPv6 clients on the same frontend. | 1 |
| CCC.LB.CP11 | SSL/TLS Termination | The service can decrypt SSL or TLS encrypted traffic at the load balancer rather than at the backend servers, offloading the decryption task from the backend servers. | 3 |
| CCC.LB.CP12 | Target Health Checks | The service automatically performs continuous health checks on backend targets by checking the response to an HTTP request, a TCP connection, or another application-specific parameter. | 1 |
| CCC.LB.CP13 | Health Checks-based Target Removal | The service automatically removes a backend target from its list of available targets when a health check detects that the target is unhealthy, so that traffic is no longer routed to that target. | 1 |
| CCC.LB.CP15 | Session Affinity | The service may be configured to pass subsequent requests from an initial client to the same backend target. | 1 |
| CCC.LB.CP16 | URL Redirects | The service can redirect incoming traffic to a different URL or location. | 1 |
| CCC.LB.CP17 | URL Rewrites | The service can rewrite URL paths before forwarding requests to backend services. | 1 |
| CCC.LB.CP18 | Custom Response | The service can return specific HTTP responses directly to the client under defined conditions, including custom error responses, without forwarding the request to a backend target. | 1 |
| CCC.LB.CP19 | Request and Response Header Transformations | The service can modify HTTP headers of both incoming requests and outgoing responses. | 2 |
| CCC.LB.CP20 | Traffic Splitting / Weighted Routing | The service can distribute incoming traffic across multiple backend resources based on predefined weights or percentages, for example for canary, A/B, blue-green, or gradual traffic migration deployments. | 1 |
| CCC.LB.CP23 | Web Application Firewall Integration | The service can integrate with a web application firewall so that only legitimate traffic reaches backend servers, blocking malicious requests. | 2 |
| CCC.LB.CP24 | Configurable TLS Policy | The service may be configured with a TLS policy that sets the minimum protocol version and the permitted cipher suites negotiated with clients. | 1 |
| CCC.LB.CP25 | Backend Re-encryption | The service can re-encrypt traffic to backend targets after terminating TLS at the load balancer, so that data stays encrypted end to end. | 1 |
| CCC.LB.CP26 | Mutual TLS Client Authentication | The service may be configured to require and validate client certificates during the TLS handshake, rejecting connections from clients that do not present a certificate issued by a trusted authority. | 1 |