Skip to main content

LevelBlue + SentinelOne: Global Partnership to Deliver AI-Powered Managed Security Operations and Incident Response. Learn More

LevelBlue + SentinelOne: Global Partnership to Deliver AI-Powered Managed Security Operations and Incident Response. Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
PGA of America Partnership
Secure What's Next
LevelBlue Security Operations Platforms
Security Colony
Partners
SentinelOne
Advancing integrated, intelligence‑driven security operations
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Partner Portal
Loading...
Loading...

HOWTO: Enabling Strong TLS for .NET

Expand / Collapse


This article applies to:

  • MailMarshal SPE 4.X - Systems with TLS 1.0 disabled
  • Marshal Reporting Console - email TLS

Question:

  • How do I enable use of TLS 1.1 and 1.2 by .NET components in SPE 4.X?
  • How do I fix TLS related errors connecting from SPE to the SEG Array Manager?
  • How do I update the TLS version used for email connectivity in MRC?

Procedure:

To allow use of "Strong" TLS (1.1 and 1.2) by .NET, you must enable system settings and .NET specific settings on affected systems.

  • For SPE this is the Marshal Interface Agent server.
  • For MRC this is the server where the software is installed.

This article covers .NET specific settings.

Update the following Registry entries (see also the attached Powershell script):

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001

Notes:

  • SPE 5.X and above uses newer versions of .NET and does not require these settings.
  • The SchUseStrongCrypto setting allows .NET to use TLS 1.1 and TLS 1.2. 
  • The SystemDefaultTlsVersions setting allows .NET to use the OS configuration.
  • For further information see Microsoft documentation.
  • These settings apply immediately. System or service restart is not required.


To contact LevelBlue about this article or to request support:


Rate this Article:
     

Attachments


strongcrypto.zip strongcrypto.zip (332 bytes, 941 views)

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.