Forum Discussion
how to disable all weak ciphers and tlsv1 in ltm11.5.3 globally
it is not advisable to modify the default ssl profile, however if we would really need to disable all weak ciphers and tlsv1 protocol globally for all virtual servers, please advise beside creating a custom profile, any other solutions which we can consider, beside manually updating all virtual servers one by one. Am I right to say that all weak ciphers are disabled by default for version 11.5.3? Also please advise which firmware version by default tlsv1 is already disabled?
11 Replies
- Hannes_Rapp
Nimbostratus
The default cipher suite in 11.5.3 is already sufficient to comply with current PCI DSS 3.0 requirements. Leaving the paranoid security-guru suggestions aside, there's nothing wrong with using the DEFAULT of 11.5.3 today.
Config related:
Your only sensible option for applying a new global configuration is to create a new clientside SSL profile (i.e. clientssl_custom) which you will then re-use as the
when creating you custom clientssl profiles.Parent Profile- Steve_Sander_31
Nimbostratus
EAV
And: https://devcentral.f5.com/articles/security-sidebar-improving-your-ssl-labs-test-grade
But related for newer versions.
- Hannes_Rapp
Nimbostratus
Updated answer. Enforcement date for 3.1 was postponed (now June 2018)
- Hannes_Rapp_162
Nacreous
The default cipher suite in 11.5.3 is already sufficient to comply with current PCI DSS 3.0 requirements. Leaving the paranoid security-guru suggestions aside, there's nothing wrong with using the DEFAULT of 11.5.3 today.
Config related:
Your only sensible option for applying a new global configuration is to create a new clientside SSL profile (i.e. clientssl_custom) which you will then re-use as the
when creating you custom clientssl profiles.Parent Profile- Steve_Sander_31
Nimbostratus
EAV
And: https://devcentral.f5.com/s/articles/security-sidebar-improving-your-ssl-labs-test-grade
 
But related for newer versions.
 
- Hannes_Rapp_162
Nacreous
Updated answer. Enforcement date for 3.1 was postponed (now June 2018)
- Kevin_Stewart
Employee
None of the firmware versions specifically disable TLSv1.0 by default. As for modifying the default SSL profile, you're definitely correct that it isn't advisable, but certainly doable. An alternative would be to create a new client SSL profile and assign that as the parent (or explicit) SSL profile of each VIP. If that's untenable, and you're also not inclined to scripting, then modifying the default cipher string in the default SSL profile might not be a bad option after all.
Take a look at the following for guidance on what's provided, by default, in client SSL profile ciphers per version:
https://support.f5.com/kb/en-us/solutions/public/13000/100/sol13171.html?sr=51244991
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com