dotnet / dotnet/announcements

Transport Layer Security (TLS) best practices with the .NET Framework article published

Open
#63 0 comments 0 reactions 0 assignees View on GitHub
.NET Framework Documentation Security
Dominant language
No language data
Stars
1.4k
Forks
53
PR merge metrics
No merged PRs in 30d

Description

# Transport Layer Security (TLS) best practices with the .NET Framework article published

A new article was published that discusses the Transport Layer Security (TLS) best practices for .NET Framework applications at https://docs.microsoft.com/dotnet/framework/network-programming/tls.

To ensure .NET Framework applications remain secure, the TLS version should **not** be hardcoded. .NET Framework applications should use the TLS version the operating system (OS) supports.

The (TLS) best practices article targets developers who are:
* Directly using the System.Net APIs (for example, `System.Net.Http.HttpClient` and `System.Net.Security.SslStream`).
* Directly using WCF clients and services using the `System.ServiceModel` namespace.
* Using [Azure Cloud Services](https://azure.microsoft.com/services/cloud-services/) Web and Worker roles to host and run your application. See the [Azure Cloud Services](https://docs.microsoft.com/dotnet/framework/network-programming/tls#azure-cloud-services) section.

The article explains how to enable the strongest security available for the version of the .NET Framework that your app targets and runs on.

The section [Audit your code and make code changes](https://docs.microsoft.com/dotnet/framework/network-programming/tls#audit-your-code-and-make-code-changes) covers auditing and updating your code.

## Discussion

Please share your thoughts and have any discussions with us at:

dotnet/docs#4675

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.