> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/release-notes/look-ahead-planned-updates-on-prisma-cloud/look-ahead-secure-the-infrastructure.md).

# Look Ahead Updates to Secure the Infrastructure

Learn more about planned Prisma Cloud updates.

Read this section to learn about what is planned in the 26.12.1 CSPM Platform, Agentless Container Host, Agentless Host Security, CIEM, Data Security, and CDEM releases.

The Look Ahead announcements are for an upcoming release and is not a cumulative list of all announcements.

The details and functionalities listed below are a preview and the actual release date is subject to change.

There are currently no API ingestions or Policy Updates planned for the 26.12.1 release.

See also:

* [Change in Behavior](#change-in-behavior)
* [Deprecation Notices](#deprecation-notices)

### Change in Behavior

#### TLS 1.2 Support

Starting with the Prisma Cloud 26.12.1 release, weak CBC (Cipher Block Chaining) ciphers will no longer be supported as part of TLS 1.2 level encryption. CBC ciphers are considered weak and vulnerable to attacks.\
\
**Impact**: TLS 1.3 is fully supported and customers are urged to use TLS 1.3 supported software to connect to Prisma Cloud.

### Deprecation Notices

| **Deprecated Endpoints**                                                                        | **Deprecated** | **Sunset** | **Replacement Endpoints**                                                                                                                                                                                                          |
| ----------------------------------------------------------------------------------------------- | -------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Deprecation of alerts/job endpoint**                                                          | 26.10.1        | -          | To improve reliability, system stability, and performance, all alert extraction workflows are transitioning to the **v2/alert** API.                                                                                               |
| <mark style="background-color:orange;">**Deprecation of End Timestamp in Config Search**</mark> | -              | -          | The end timestamp in the date selector for Config Search will soon be deprecated after which it will be ignored for all existing RQLs. You will only need to choose a start timestamp without having to specify the end timestamp. |


---

# 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://docs.prismacloud.io/release-notes/look-ahead-planned-updates-on-prisma-cloud/look-ahead-secure-the-infrastructure.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.