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.