Hackers attempt to enter and exploit network systems, particularly for organizations or people that work with sensitive data. Cyberattacks are extremely harmful to covered entities (CEs) tasked with safeguarding patients’ protected health information ( PHI).
RELATED: Understanding and Implementing HIPAA Rules
To combat cyberattacks, in the mid-1990s Netscape developed Secure Socket Layer (SSL) protocol to provide extra security for Internet users. Such protocols encrypt data through a variety of methods to keep communication between two parties secure.
RELATED: Free SSL Security Testing for HIPAA Compliance
As an SSL descendent, Transport Layer Security (TLS), addresses problems with SSL by providing extra layers of protection. Moreover, the TLS protocol encrypts every type of Internet traffic, including web, email, and Usenet.
RELATED: Why TLS Encryption is Essential to Safeguard Email
Over time, cyberattackers have discovered holes (i.e. areas to breach) in past encryption protocols. This is why several updates have been created and released. TLS 1.3 is the newest, most secure version to date. And this is also why NSA’s guidance is critical:
Obsolete configurations provide adversaries access to sensitive operational traffic using a variety of techniques, such as passive decryption and modification of traffic through man-in-the-middle attacks.
RELATED: What is A Man-in-The-Middle (MITM) Attack?
Continued use of vulnerable protocols not only increases cyberattack risk but also provides a false sense of security. If you think you are secure then you won’t fix possible problems.
Networks and systems that use deprecated forms of [TLS] and [SSL] for traffic sessions are at risk of sensitive data exposure and decryption.Therefore, the guidance delineates the required critical steps to ensure up-to-date TLS configurations. Users can find accompanying tools on the NSA’s GitHub. First, users must employ network monitoring systems to detect obsolete encryption protocols. These are SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.1. RELATED: How to Check for TLS to Secure Your Email Second, for TLS 1.2 sessions, users should run further checks that identify outdated cipher suites. Finally, for TLS 1.2 and TLS 1.3 sessions with recommended cipher suites, users should employ monitoring systems to find weak key exchange methods. All protocols, cipher suites, and key exchange methods must meet the standards communicated in the Committee on National Security Systems Policy 15. If these checks reveal issues and/or unmet standards, users must reconfigure TLS sessions. The guidance ends by stating users should design network monitoring systems to automatically send alerts about and possibly block weak TLS traffic. Such alerts provide immediate detection so that users know when communication may not be secure. By following these steps and standards, companies can protect their Internet communication methods and use only the best protection afforded to them by encryption protocols.
According to U.S. HIPAA legislation, CEs must use strong cybersecurity measures to protect PHI from a breach and possible HIPAA violation. Paubox provides HIPAA compliant email solutions that protect patients’ PHI. One of the main features of Paubox security is our up-to-date TLS protocols. We only accept TLS 1.2 or higher connections from our customers. Furthermore, we offer TLS 1.3 email encryption for all three of our solutions:
The best part of choosing Paubox is that our tough cybersecurity measures have no impact on user behavior. Our products are perfect for CEs when they need to email PHI safely and securely, with no extra steps, portals, and logins. Along with our stringent access controls and HITRUST CSF certification, you can always guarantee that your healthcare organization and patients are cybersafe with Paubox.