> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/networking/appsec-ali-33.md).

# Alibaba Cloud Cypher Policy is not secured misconfiguration detected in code

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_ALI\_33                            |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | ALIBABA\_CLOUD                             |
| Severity               | LOW                                        |
| Framework              | Terraform                                  |

## Impact

This rule ensures that Alibaba Cloud SLB (Server Load Balancer) TLS cipher policies are secure. Specifically, it ensures that only secure versions of TLS (Transport Layer Security) are used by disallowing the use of TLSv1.0 and TLSv1.1. Using outdated TLS versions presents security vulnerabilities that can be exploited, compromising the security of data in transit.

Failing to enforce secure TLS versions can result in insecure connections, leaving data susceptible to interception and decryption by attackers.

## How to Fix

*Resource:* alicloud\_slb\_tls\_cipher\_policy

* *Attribute:* tls\_versions

To mitigate this issue, ensure that the `tls_versions` attribute in the `alicloud_slb_tls_cipher_policy` resource does not include `TLSv1.0` or `TLSv1.1`.

## Example: \[source,go]

resource "alicloud\_slb\_tls\_cipher\_policy" "example" { ...

* tls\_versions = \["TLSv1.1"]
* tls\_versions = \["TLSv1.2", "TLSv1.3"] }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/networking/appsec-ali-33.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.