Avatar of seven45
seven45
 asked on

sweet32 bug pci compliance

Hi,
We keep failing the pci compliance.   have already disabled the recommended ciphers and protocols except for TLS 1.0 (but i believe it breaks RDP when disabled on the SBS2011 server).
we're failing the following:
443 TCP WWW service:  SSL 64 bit block size cipher suites supported. and Medium Strenght cipher suites supported.

Dont want to use the cryptoIIS tool as I'm not certain if it'll break other things in an SBS 2011 environment.   I'm trying to do one of the following as a mitigation solution (that i need your help on).    Can anyone give me steps to applying one of the mitigation factors below?

Mitigations Against SWEET32
The authors of the paper recommend three main ways to dealing with SWEET32 attack:
All web servers should be configured to prefer 128-bit (or higher) ciphers.
3DES should be offered by web browsers as fallback-only, even if the servers prefer 3DES over AES for encrypted connections.
TLS libraries should limit the length of TLS sessions with a 64-bit cipher.
SBS* ciphers* pci compliance

Avatar of undefined
Last Comment
btan

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
btan

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
btan

As per advice given.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck