We will provide examples of how this can happen, and what you can do to address these. This article is going to go over four areas in which the use of legacy technologies that do not support modern security standards can turn your network into the Titanic. This one example of how the use of legacy technologies can be that well-placed hole. SHA-1 is moving toward obsolescence, and we expect a future update to Windows 10 to disable it by default when Microsoft implements newer technologies in Active Directory. MD5 is so old that it is not used to help secure web browser communications in the current version supported by Microsoft 365, Transport Layer Security (TLS) 1.2. MD5, according to the Internet Engineering Task Force, is so old and insecure that NIST does not recommend it or advertise its usage. According to Microsoft, the use of MD5 allows machines running Windows 2000, Windows XP, or Windows Server 2003 to authenticate to Active Directory Networks. ![]() Vulnerable shops had the MD5 hashing algorithm enabled for communication with previous versions of Windows. The effect of using legacy algorithms was that every password on the network became easily hackable due to lax security. The technology Microsoft uses to verify messages as authentic is based on an older cryptographic hashing algorithm, SHA-1, that NIST has specifically approved for the purpose. The CISA advisory indicated that affected organizations need to remove legacy encryption support for Kerberos, the security technology that underpins Microsoft Active Directory. One of those holes was that all the password hashes on a network were visible to platforms managed by vulnerable versions of their Orion network management software. ![]() It only took one well-placed hole to sink one like the Titanic. ![]() This includes newer secured applications. The goal of this example is to show how accommodating one legacy technology can put an entire network at risk. To illustrate this, we will use the example of Microsoft Active Directory, the authentication technology utilized by most corporate networks, which was also affected by it. The SolarWinds attack was not only an attack on the Software Supply Chain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |