Monity 1.24/30/2023 ![]() Platform-specific guidance Platform/Language Otherwise you may miss the added security of the newer standards and possibly experience problems if TLS 1.2 is ever deprecated in favor of those newer standards. ![]() Allowing the agent to automatically detect, negotiate, and take advantage of future security standards is preferable. We recommend you do NOT explicit set your agent to only use TLS 1.2 unless absolutely necessary. Once Azure drops legacy support, if your agents can't communicate over at least TLS 1.2 you won't be able to send data to Azure Monitor Logs. The PCI Security Standards Council has set a deadline of Jto disable older versions of TLS/SSL and upgrade to more secure protocols. Older versions of TLS/Secure Sockets Layer (SSL) have been found to be vulnerable and while they still currently work to allow backwards compatibility, they are not recommended, and the industry is quickly moving to abandon support for these older protocols. To ensure the security of data in transit to Azure Monitor, we strongly encourage you to configure the agent to use at least Transport Layer Security (TLS) 1.2. ![]() ![]() The information in this article is specific to Azure Monitor Logs and supplements the information on Azure Trust Center.Īzure Monitor Logs manages your cloud-based data securely using:Ĭontact us with any questions, suggestions, or issues about any of the following information, including our security policies at Azure support options. This article explains how Azure Monitor collects, processes, and secures log data, and describes security features you can use to further secure your Azure Monitor environment. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |