LuxSci

What Are the Implications of the Proposed Changes to the HIPAA Security Rule?

HIPAA Compliant Email

With the recent announcement of proposed changes to the HIPAA Security Rule, by the Office for Civil Rights (OCR), healthcare providers, payers, suppliers, and organizations of all sizes will have to tighten up their cybersecurity practices. In some cases, considerably. 

However, with the announcement being so recent (and there not even yet being a clear timeline for when companies will have to implement the changes), it’s all too easy for organizations to view the proposed amendments as a challenge that’s far off in the future.

However, even at this early stage, the proposed changes to the Security Rule require careful consideration and important conversations. Soon, healthcare companies will have to implement or improve a series of cybersecurity controls designed to better safeguard electronic protected health information (ePHI). 

In light of this, in this post, we’ll discuss some of the most important practical considerations that healthcare organizations will have to contend with to maintain HIPAA compliance when the proposed changes to the Security Rule go through. 

What are the Key Proposed Changes to the HIPAA Security Rule?

First, a refresher on what the proposed changes to the Security Rule are:

  1. More Comprehensive Risk Management: healthcare organizations must conduct more frequent risk assessments to identify, categorize, and mitigate threats to sensitive patient data. 
  2. Stricter Documentation and Evidence Retention Policies: similarly, stronger documentation and record-keeping practices to ensure organizations can demonstrate compliance with security requirements.

    This includes:
  • Maintaining detailed records of how they assess threats and implement safeguard security controls (e.g., encryption policies, access controls, etc).
  • Retaining detailed audit logs of system access, data modifications, and security events, as well as reports from security solutions, such as firewalls and intrusion detection systems all must be securely stored, retained for a defined period, and made available for audits and compliance reviews.
  • By the same token, the proposed updates to the Security Rule may extend how long healthcare organizations must retain logs and other security documentation, allowing auditors to review historical compliance efforts in the event of an investigation.
  1. Mandatory Encryption for All ePHI Transmission: healthcare companies will require end-to-end encryption for emails, messages, and data transfers involving ePHI. Like today, this means that patient data must be encrypted in transit, i.e., from one place to another (when collected in a secure form, sent in an email, etc.), and in storage, i.e., where it will reside.
  2. Stronger User Authentication and Identity Verification Requirements: healthcare providers must implement stronger identity access management IAM safeguards, such as Multi-Factor Authentication (MFA), for employees with access to patient data.
  3. Tighter Third-Party Security Controls: stricter security controls for business associates who have access to the healthcare company’s ePHI. One of the proposed changes to the HIPAA Security Rule is that vendor security audits will be mandatory instead of optional.
  4. Updated Incident Response (IR) and Data Breach Reporting Rules: mandating stricter breach notification timelines for healthcare entities and their business associates, with them being obligated to inform parties affected by a security breach as soon as possible. 

What Are The Practical Implications for Healthcare Companies?

So, what will healthcare companies have to do to comply with HIPAA regulations when the proposed changes to the Security Rule go through? Let’s look at the main practical considerations.

Cybersecurity Solution Deployment and Infrastructure Upgrades 

Many healthcare companies will have to install (and subsequently, maintain) new IT infrastructure and deploy new cybersecurity tools to strengthen their authentication safeguards (e.g., MFA, Zero Trust, etc.) to meet new HIPAA’s heightened cybersecurity standards.

Expanded Vendor and Third-Party Management

As well as having to deploy new cybersecurity solutions, such as HIPAA compliant email services and continuous monitoring tools, healthcare organizations will have to be more diligent in their oversight of their third-party vendors.  

Stricter Auditing and Documentation Requirements

In having to provide more details of their risk management practices and maintain real-time logs, healthcare organizations will have to develop processes, policies, and supporting documentation. 

Staff Training 

Healthcare companies will have to train their staff on the updates of the Security Rule, their implications, how to use the new applications and hardware deployed to harden their security posture, etc. 

Increased Management and Administrative Burden 

Dealing with proposed changes to the Security Rule is going to require all hands on deck. 

Managers and stakeholders are going to make several important strategic decisions; procurement and product managers are going to have to research and purchase new solutions; IT will have to deploy the solutions; and everyone will need to learn how to use them. 

With all this in mind, more will be required from everyone within your organization. Employees will be taken away from their work, which could affect the quality of the service provided to patients and customers. 

That’s why it’s crucial to be prepared…

How Can You Prepare For the Proposed Changes to the Security Rule?

  • Conduct risk assessments: pinpoint vulnerabilities within your IT network and the ePHI contained therein. You should conduct risk assessments annually at the very least – or you upgrade your IT infrastructure. In light of the proposed amendments to the Security Rule, conducting a risk assessment to identify the security gaps in your network against the proposed rule changes is essential.
  • Evaluate your existing email and communication platforms: to accommodate the upcoming changes to the Security Rule, many healthcare companies will need to upgrade to HIPAA compliant email communication solutions, as well as encrypted databases for securely storing ePHI at rest. Deploying an email services solution designed for the healthcare industry from a HIPAA compliant email provider like LuxSci, best ensures compliance with encryption and the other new requirements of the Security Rule.
  • Improve your organization’s incident response planning and documentation processes: develop all the required documentation to track the movement of patient data, and refine your processes for handling security events. This also encompasses training your staff on your new security policies and procedures.
  • Improve your organization’s cybersecurity posture: by implementing end-to-end encryption, network segmentation, zero-trust security infrastructure, data loss protection (DLP) protocols, and other measures that will better protect patient data.
  • Perform vendor due diligence: ensure your third-party service providers meet HIPAA compliance standards and that you have a Business Associate Agreement (BAA) in place with each vendor that can access your ePHI. 

How Luxsci Can Help You Navigate the Proposed Changes to the HIPAA Security Rule

With more than 20 years of experience in delivering best-in-class secure HIPAA compliant marketing solutions for the healthcare industry, LuxSci is a trusted partner for healthcare organizations looking to secure their email and digital communications in line with regulatory standards and the industry’s highest security standards.

LuxSci’s suite of HIPAA-compliant solutions includes:

  • Secure Email: HIPAA compliant email solutions executing highly scalable email campaigns that include PHI – send millions of emails per month.
  • Secure Forms: Securely and efficiently collect and store ePHI without compromising security or compliance – for onboarding new patients and customers and gathering intelligence for personalization.
  • Secure Marketing – proactively reach your patients and customers with HIPAA compliant email marketing campaigns for increased engagement, lead generation and sales.
  • Secure Text Messaging – enable access to ePHI and other sensitive information directly to mobile devices via regular SMS text messages. 

Interested in discovering more about LuxSci can help you get a head start on upgrading your cybersecurity stance to ensure future HIPAA compliance? Contact us today!

Picture of Pete Wermter

Pete Wermter

As a marketing leader with more than 20 years of experience in enterprise software marketing, Pete's career includes a mix of corporate and field marketing roles, stretching from Silicon Valley to the EMEA and APAC regions, with a focus on data protection and optimizing engagement for regulated industries, such as healthcare and financial services. Pete Wermter — LinkedIn

Get in touch

Find The Best Solution For Your Organization

Talk To An Expert & Get A Quote




A member of our staff will reach out to you

Get Your Free E-Book!

LuxSci High Email Deliverability Best Practices Paper

What you’ll learn:

Related Posts

HIPAA compliant email

LuxSci Welcomes Angel Mazariegos as Head of Finance

LuxSci, a leader in secure healthcare communications and HIPAA compliant email, is pleased to announce the appointment of Angel Marie Mazariegos as the company’s new Head of Finance. With over 25 years of experience in financial management, accounting, and human resources, Angel will play a central role in advancing LuxSci’s operational excellence and supporting the company’s rapid growth in 2026 and beyond.

Angel brings a wealth of expertise to LuxSci, having held senior leadership positions at organizations focused on financial services, language and access services for healthcare, and human resources. In these roles, Angel has led multi-department Finance and HR teams, spearheading critical initiatives, including ERP implementations, streamlined employee onboarding, and financial process optimization.

In her role at LuxSci, Angel will oversee all aspects of the company’s finance operations, including budgeting, forecasting and reporting. Additionally, Angel will manage the company’s HR function, ensuring that LuxSci continues to foster a strong, people-driven culture based on its Secure, Trust, Responsible and Smart company values.

“Angel’s blend of financial and HR leadership makes her an invaluable addition to the LuxSci executive team and a real asset for our people,” said Mark Leonard, CEO of LuxSci. “We look forward to working with Angel to build the high-performing teams that will be critical to our future growth and serving the evolving needs of our customers.”

Angel holds dual MBA degrees in Accounting and Human Resource Management from Cappella University, as well as dual BS degrees in Business Administration (Accounting and CIS Business Systems) from California State University, Los Angeles.

“I am honored to join the LuxSci team at such an exciting time for the company,” said Mazariegos. “I look forward to working with the team and helping build on LuxSci’s reputation for excellence and reliability in secure healthcare communications.”

HIPAA Compliant Email

LuxSci Shines in G2 Winter 2026 Reports, Underscoring Commitment to Product Leadership and Trusted Relationships

We’re pleased to announce that LuxSci has been recognized for excellence and leadership for HIPAA compliant email and messaging in the just-released G2 Winter 2026 Reports!

Based on verified customer reviews, LuxSci earned 20 G2 badges as part of the most recent G2 reports, including top honors such as Grid Leader, Highest User Adoption, Best Support, and Best Estimated ROI.

This recognition further validates what we’ve always believed: our customers don’t just choose a great product — they choose a great partner. At LuxSci, we build long-term, trusted relationships with our customers, anchored in product reliability, industry-leading email deliverability and performance, and the best customer support in the business.

Why G2 Matters

G2 is a globally trusted peer‑review platform that aggregates verified user feedback and real‑world usage data to rank software and service providers. G2’s seasonal reports like the Winter 2026 editions shine a spotlight on latest tools and vendors that deliver consistent value and satisfaction to real customers.

Earning 20 badges this quarter signals a strong vote of confidence from our customers and community, helping affirm that LuxSci is a leading, highly adopted secure email solutions provider.

What We Earned in Winter 2026

Among the 20 badges awarded to LuxSci across Email Security, Email Encryption, Email Gateway and HIPAA Compliant Messaging are:

  • Grid Leader
  • Highest User
  • Best Support
  • Best Estimated ROI

This broad range of accolades spanning leadership, adoption, support and return on investment underscores the reliability of our solutions and the trust our customers place in us.

Awards Reflect Our Commitment to Customer Success

Reliable. Winning Grid Leader and Highest User Adoption demonstrates that thousands of users are depending on LuxSci, securely delivering emails to today’s most popular platforms, including Gmail, Apple Mail, Yahoo Mail and AOL, to name a few.

Proven. With Best Estimated ROI, customers are saying that LuxSci delivers tangible results, whether in secure email delivery, regulatory compliance, or operational efficiency.

Long‑Term Trust. Best Support is perhaps the most telling because for us, success isn’t just about features, it’s about being there for our customers every step of the way.

Thank you to all of our customers. We remain committed to your success — today and in the future.

Want to learn more about LuxSci? Reach out and connect with us today!

HIPAA Compliant Email

Here’s What HIPAA Compliant Email Salespeople Don’t Tell You

With email security threats continuously increasing in number and sophistication, as well as healthcare companies requiring secure solutions to communicate with patients and customers, the need for HIPAA compliant email solutions has never been greater. 

However, when looking for the right secure email services provider (ESP), healthcare organizations run the risk of making inaccurate assumptions about HIPAA compliance via what they learn from prospective vendors. This is due to the tendency for sales materials for HIPAA compliant email services, such as web pages or promotional videos, to highlight the strengths of the platform, while downplaying a healthcare company’s own role and responsibilities in securing protected health information (PHI). 

With this firmly in mind, here are six key things that HIPAA compliant email salespeople don’t tell you about securing communications and achieving compliance. 

1. The Shared Responsibility Model

Firstly, HIPAA compliant email salespeople are unlikely to emphasize the idea of shared responsibility when it comes to data security. This is the idea that two entities that share access to data, e.g., a healthcare company and their ESP, have a shared responsibility to preserve the privacy of that data.

In reality, most sales pitches explain the benefits and features of the solution, as opposed to stressing that compliance truly depends on how it’s configured and used. Now, that’s not to say that a salesperson is trying to hide this fact, as they’ll probably allude to training and configuration requirements. But, they’ll be less likely to make light of this and, more broadly, how shared responsibility factors into compliance.

2. A BAA Doesn’t Automatically Make You HIPAA Compliant

A business associate agreement (BAA) is essential for HIPAA compliance, but signing one doesn’t automatically make you compliant. Your organization still has to use the email delivery solution in a way that aligns with HIPAA regulations, which involves proper configuration, training, oversight, and reporting.

The misconception among some healthcare companies that a BAA equals compliance may be perpetuated by the term “HIPAA compliant email services provider”.  This could give some the impression that the vendor is fully HIPAA compliant and, subsequently, in signing a BAA with them, the use of their services is fully compliant.

But, it’s not that simple.

Simply signing a BAA obscures the real effort involved in achieving compliance. There’s no official HIPAA seal of approval, and HIPAA compliant means that the solution is capable of being configured for compliant use, which is a shared responsibility. HIPAA compliant email salespeople are unlikely to volunteer this nuance, especially if their email solution requires considerable configuration or has a steep learning curve to use it securely.

3. Not All Solutions or Features Are HIPAA Compliant

Another key detail often underplayed by vendor sales materials of HIPAA compliant email solutions is that some of their features, or even entire services, aren’t covered by their BAAs, so they can’t be used to handle PHI. 

These tools are referred to as “out of scope” and may include tools capable of integration with the email service, such as analytics or AI capabilities, but they don’t possess the cyber risk mitigation measures that align with HIPAA regulations. Perhaps the main reason for this is that many mass-market email delivery solutions, such as Microsoft 365 or Google Workspace, are designed for companies across all sectors. Consequently, while they can be HIPAA compliant, they weren’t developed from the ground up with the stringent regulatory demands of the healthcare industry in mind.

4. Solutions Are Not HIPAA Compliant “Out of The Box”

HIPAA compliant email salespeople may suggest that compliance is built into their platform, and healthcare organizations can use it to transmit PHI straight away, but this isn’t the case. Healthcare companies must still configure the email platform accordingly, as per the security requirements determined by their risk assessment, e.g., applying the right level of encryption. 

Also, if the email service is difficult to configure for HIPAA compliance or if the vendor’s configuration documentation lacks detail, that presents another obstacle to its compliant use. 

In addition to configuration, healthcare companies also have to implement access management controls and policies, establishing the extent to which each employee can access PHI in respect to their roles and responsibilities. From there, they will have to train their workforce on how to use the HIPAA compliant email solution securely, which may include those tools that fall outside the scope of your BAA with the vendor, and must not be used for the disclosure of patient data.

5. Essential Security Features Cost Extra 

Another more egregious version of an ESP not being HIPAA compliant out of the box is having features required for compliance, such as encryption or audit logging, as premium add-ons and not included in the solution’s base pricing. 

A vendor’s sales materials for its email service might list the necessary safeguards, but underemphasize the fact that only some versions of their platform are truly HIPAA compliant. Consequently, healthcare companies must confirm that the features required for HIPAA compliant email communications are included in the plan they’re purchasing. 

6. The Importance of Staff Training on HIPAA

HIPAA compliant email salespeople are often remiss in stressing the need for additional workforce training alongside the deployment of their platform. A healthcare company’s employees must be trained on how to securely use the email client, how to ID potential threats, and best practices for including PHI in email communications, as well as the regulations tied to HIPAA and data security.

This includes educating users on the differences between regular and secure email, and what they must do to safeguard patient and customer data. Fortunately, secure email solutions from providers like LuxSci enable automated email encryption, and users do not need to take any additional actions to ensure encryption when sending emails.

Additionally, in some cases, employees will need to be trained on which tools or features do not align with HIPAA guidelines and must not be used to process PHI.

LuxSci: Fully HIPAA Compliant – No Hidden Surprises

LuxSci specializes in solutions that enable companies to carry out secure, personalized, and HIPAA compliant email communications and campaigns. With more than 20 years of experience and billions of emails sent for companies including Athenahealth, 1 800 Contacts, Lucerna Health and Rotech Healthcare, we’ve acquired invaluable experience in helping healthcare organizations enhance their engagement efforts, all while adhering to HIPAA regulations. In addition, LuxSci’s secure high-volume and marketing email solutions feature HIPAA-required security controls, including encryption, audit logging, and multi-factor authentication (MFA) by default, not as optional, hidden extras.

Contact us today to learn more about how LuxSci’s secure email solutions can help increase the ROI on your patient and customer outreach efforts, while safeguarding PHI in line with HIPAA requirements.

b2b medical marketing

What Does B2B Marketing Help Healthcare Vendors Accomplish?

B2b medical marketing helps healthcare vendors to explain the practical value of a product to clinical and administrative buyers by presenting clear information that supports decision making across operational and regulatory domains. Buyers respond to communication that describes how a tool fits into routine workflows and how it handles information, and the process depends on steady explanations rather than promotional language.

Early Movement in the Buyer Relationship

The first stage of communication gives prospective buyers a clear sense of what the service does and why it belongs in their setting. Healthcare groups rely on predictable routines and they look for products that support those routines without creating unnecessary strain on staff. When an introduction explains how a tool fits into patient movement, documentation demands, or coordination between departments, readers can place the service into a familiar context. This lowers the cognitive effort required to evaluate whether further consideration is worthwhile and creates a smoother path for later discussions, which is why many vendors treat early stage explanations as the base of effective b2b medical marketing in this environment.

The Influence of Operational Structure

Clinical and administrative environments are shaped by long standing systems, varied software tools, and staff roles that have developed around known constraints. Vendors using b2b medical marketing describe how a product enters this environment so that the buyer can picture the transition from interest to adoption. Extended explanations of onboarding steps, data migration choices, and staff training routines help readers understand how daily operations shift when a new tool is introduced. These explanations allow decision makers to forecast workload changes rather than relying on assumptions, and they reflect the broader goal of b2b medical marketing which is to reduce uncertainty.

Regulatory Considerations in Vendor Communication

Healthcare buyers place great weight on regulatory matters, which is why clear descriptions of data handling are central to this type of communication. Readers look for information about access management, retention practices, audit preparation, and the path information takes through each component of a system. When vendors describe these areas in detail, compliance teams can perform early assessments and avoid long chains of clarification requests. This approach supports efficient internal review because the buyer gains confidence that the vendor maintains structured processes rather than improvised arrangements, and this clarity strengthens the overall impact of b2b medical marketing.

Reliability Expectations Within Clinical Settings

Healthcare settings cannot tolerate uncertainty in the systems that support patient care. B2b medical marketing provides insight into how a vendor manages service interruptions, planned updates, backup routines, and recovery efforts. A description of past events or internal procedures gives readers a sense of how the vendor behaves when conditions are difficult. Buyers place great value on this type of detail because it helps them differentiate between systems that hold up under stress and systems that falter when routine performance is disrupted, and these reliability discussions form a core thread in b2b medical marketing for clinical tools.

Perspectives That Influence Internal Decision Making

Each participant in the purchasing process evaluates a product through a different lens. Financial leaders consider long term spending patterns, clinical managers look for ease of use and effects on staff time, and compliance teams examine information practices. Communication that attends to these perspectives without shifting tone allows the reader to share information across departments with minimal friction. This prevents internal delays because each group can assess the service using information that relates to its role in the organisation, and thoughtful navigation of these viewpoints reinforces the strength of b2b medical marketing across healthcare markets.

The Role of Educational Content in Vendor Outreach

Healthcare groups respond well to educational material that speaks to challenges in clinical settings. Articles and guides that explain regulatory shifts, workflow bottlenecks, or mistakes observed in comparable organisations allow readers to examine their own processes. This form of communication helps buyers understand the vendor’s approach to problem solving and creates familiarity before any formal evaluation begins. Educational content performs well in this field because it demonstrates practical awareness rather than relying on abstract claims, making it a central component of many b2b medical marketing programs.

Use After Adoption

Decision makers frequently look beyond the moment of purchase and seek a clear view of the daily relationship that follows implementation. Communication describing staff support, update patterns, training formats, and communication channels helps buyers picture how the tool will fit into routine operations. Long paragraphs that describe the lived experience of using the service allow internal champions to advocate for the product with fewer unknowns, which supports faster movement through approval stages. This expectation of clarity after adoption aligns with the wider goals of b2b medical marketing which encourage predictable cooperation between vendor and buyer.

Documentation Supporting Review Processes

Healthcare organisations rely heavily on documentation during evaluation. Guides, records, administrative instructions, and explanations of data controls enable teams to examine the product without repeated requests for further detail. B2b medical marketing that introduces these documents early in the conversation reduces internal delays because reviewers can move through their procedures with all necessary information available at the outset. This transparent approach helps build trust between the vendor and the buyer and underscores the value of documentation as a recurring theme within b2b medical marketing.

B2b medical marketing works most effectively when vendors show an accurate grasp of clinical pressures and administrative realities. When communication reflects these conditions and acknowledges the challenges that healthcare groups experience during busy periods, readers gain confidence that the vendor understands the world they operate in. This supports deeper conversations about integration, performance, and long term cooperation across the organisation.

You Might Also Like

LuxSci G2 Spring Reports

LuxSci Earns 22 G2 Spring 2025 Badges, Including “Best Support” and “Best ROI”

We’re excited to share that LuxSci has once again been recognized by G2, the world’s largest and most trusted software marketplace, in its Spring 2025 Reports—this time earning 22 new badges across multiple email security and encryption categories. This recognition reflects not only our unwavering commitment to secure healthcare communications, but also the trust and satisfaction of our valued customers, many of whom have been with us for years.

Among the standout G2 accolades:
🏅 Best Support – A badge that means the world to us, as we pride ourselves on offering the smartest, most responsive support in the HIPAA compliant email and communications industry.
💰 Best Estimated ROI – Demonstrates how LuxSci helps organizations maximize value from their investment in HIPAA compliant email communications – with better results like 98% deliverability.
📈 Momentum Leader – Highlighting the rapid adoption and growing impact of our secure healthcare ommunication solutions across email, text, forms and marketing.

A Spring of Recognition for LuxSci’s Secure Healthcare Communications Suite

This season’s G2 recognition spans our Secure Email, Secure Email Gateway, and Secure Text products, which are part of the LuxSci Secure Healthcare Engagement suite of solutions. These achievements reflect real user feedback, aggregated through verified G2 reviews, and they reinforce our commitment to providing the most flexible, scalable, and secure communication tools tailored for the evolving needs of healthcare organizations.

Whether you’re looking to scale secure high-volume email, build personalized communications and marketing campaigns, or accelerate workflows with multi-channel healthcare journeys, LuxSci delivers best-in-class performance and a proven HIPAA compliant solution for a wide range of healthcare communications use cases.

Why This Matters

In today’s digital healthcare landscape, secure, HIPAA-compliant email and communications are critical. But security alone isn’t enough. Providers, payers, and suppliers also need tools that are high-performing, delivered with expert support, and designed to drive business outcomes—from patient engagement to operational efficiency.

That’s where LuxSci stands out. With more than 20 years of experience, MIT roots, and a singular focus on delivering Secure Healthcare Communications, we offer customers not just software, but a strategic partner in transforming the healthcare journey and keeping patient and customer data secure.

Our recognition by G2 in categories like Support, ROI, and Momentum speaks directly to this value. It also confirms that with LuxSci, you’re not just choosing security and compliance—you’re choosing performance, personalization, and long-term success.

Explore What’s Possible with LuxSci

We invite you to discover how LuxSci can support your organization’s email communications and compliance goals. Contact us to learn more about our HIPAA-compliant solutions for secure email, marketing, forms, and text messaging—and why healthcare organizations like Athenahealth, 1800 Contacts, Rotech Medical Equipment, Delta Dental and Eurofins all use LuxSci as their trusted secure communications partner.

LuxSci Email Deliverability

Webinar: How to Harness HIPAA-Compliant Marketing & Workflows

In today’s connected world with millions of messages bombarding people every second of the day, personalized engagement over digital channels is a requirement for any business – especially in healthcare. However, ensuring that your marketing efforts comply with the Health Insurance Portability and Accountability Act (HIPAA) can be a daunting task that never quite gives you the peace of mind you need. The good news is that you don’t have to lose sleep at night worrying about whether your marketing campaigns are secure and protected from data breaches and outside threats. With the right strategies and solutions, you can create HIPAA-compliant marketing campaigns that not only keep data protected, but also boost lead conversions, improve outcomes, and reduce costs.

Here are some simple but necessary steps to get you off and running with HIPAA-compliant marketing campaigns today:

  1. Understand HIPAA Requirements

Before embarking on any marketing campaign, it’s crucial to have a thorough understanding of HIPAA regulations. HIPAA sets strict guidelines for keeping protected health information (PHI) safe. Ensure your marketing team is well-versed in these regulations to avoid any compliance failures. If you’re not sure, check out this recent LuxSci blog post on understanding encryption requirements for HIPAA-compliant email.

  1. Leverage Automated Data Encryption

Safeguarding protected health information (PHI) is a requirement with HIPAA. Use advanced encryption methods – including dedicated cloud infrastructures and automation that encrypts every email sent with no user intervention required – to secure patient and customer data both in transit and at rest. This ensures that any data shared during marketing campaigns remains confidential and secure from breaches.

  1. Implement Consent Management

Obtaining explicit consent from patients and customers before using their information in marketing campaigns is a also requirement and non-negotiable. Make sure you have a consent management system that records, stores, and manages patient and customer consent effectively and efficiently.

  1. Personalize and Hypersegment Campaigns Using PHI Data

HIPAA does not need to hold you back. In fact, using PHI data can take your email targeting and messages to the next level. Personalized marketing can significantly improve patient and customer engagement and increase your lead conversions. Use PHI data to tailor your marketing messages to the specific needs and preferences of precise segments to ensure content is relevant and valuable – and actionable.

  1. Utilize Encryption for All Healthcare Communications

Communicating with patients and healthcare customers through secure channels is essential for ALL communications, not just those that require HIPAA compliance. Use flexible encrypted email services, secure messaging apps, and patient portals to share sensitive information, and protect yourself from the latest cybersecurity threats at all times.

  1. Monitor, Analyze and Improve Marketing Campaigns

Regularly test, monitor and analyze your marketing campaigns to ensure ongoing HIPAA compliance and the best results, using data on emails delivered, opened, clicked and secured. Take action in real-time to improve segmentation and results based on your latest business needs and deliverability requirements.

Benefits of HIPAA-Compliant Marketing

Implementing HIPAA-compliant marketing strategies offers numerous benefits, including:

  • Improved healthcare experiences – Personalized and secure communications build trust and strengthen relationships with patients and customers.
  • More lead conversions – Hypersegmentation and automation drive higher conversion rates and improve patient and customer engagement.
  • Increased sales opportunities and revenue – Targeted, timely communications and campaigns drive the best results for growing your business.

Call to Action: ‘How-To’ Webinar on HIPAA-Compliant Marketing

Embracing HIPAA-compliant marketing is not just about avoiding penalties; it’s about delivering superior patient and customer experiences – and achieving business success. With HIPAA-compliant marketing, you can create powerful campaigns that protect PHI data, drive lead conversions, and improve patient and customer outcomes.

Are you ready to transform your healthcare marketing strategy – in a HIPAA-compliant way?

Join us for a webinar on How to Harness HIPAA-Compliant Marketing and Workflows, taking place on Tuesday, August 6 at 12:00PM Eastern Time. We’re joining forces with the experts over at Compliancy Group for an informative ‘how-to’ session on the latest best practices, success stories and easy-to-use tools for ensuring compliance across your organization – with a focus on marketing, workflows and automation. This includes:

  • Effectively and efficiently managing compliance across multiple standards
  • How to increase engagement and drive sales with HIPAA-compliant marketing
  • Optimizing workflows with secure forms and automation
  • Includes 2 live demos

Don’t miss it. Sign up today!

Register

HIPAA email laws

How To Overcome Email Encryption Challenges in Healthcare

Encryption is a critical security measure for protecting electronic protected health information (ePHI) included within email communications, and a key technical safeguard under the HIPAA Security Rule. However, despite its efficacy in helping protect sensitive patient data from malicious actors, encryption can be difficult to successfully implement. 

Technical complexity, user resistance, and compatibility issues across different email systems can emerge as persistent problems, leading to frustration, risky workarounds, and, ultimately, increased risk of ePHI exposure and compliance violations. Without thoughtful deployment and support, encryption can become a barrier to successful secure email communication in healthcare, as opposed to a measure that underpins it.

To help you ensure secure, HIPAA compliant email communication, this post discusses the main encryption challenges you’re likely to encounter, how they can diminish your email security posture, and the measures you can take to overcome them. 

What Is Email Encryption?

Before we discuss the most frequent email encryption challenges faced by healthcare organizations, here’s a quick refresher on what email encryption is and why it’s so important for securing sensitive patient data.  

Email encryption is the process of scrambling the content of a message to make it unreadable as it’s sent to recipients or stored in a database. Only the intended recipient, who has the encryption key, can decrypt the email and access the data within. 

Consequently, in the event an encrypted message is intercepted by malicious actors in transit or exfiltrated from a data store during a security breach, they won’t be able to make sense of it. This renders any ePHI included in the message unintelligible and, therefore, worthless, adding another layer of security that preserves patient privacy – and keeps your business safe.

Common Email Encryption Challenges 

Let’s move on to detailing some of the most frequent encryption challenges that must be overcome by healthcare organizations to ensure secure email communication and HIPAA compliance. 

Decrypting Messages Is Too Difficult

The more difficult or drawn out it is for recipients to decrypt their email messages, the more likely they’ll simply go unread or end up deleted. If the decryption process is too cumbersome, which could include requiring a user to log into a separate site (i.e., a web portal), verify their identity multiple times, create a new account, or install additional software, it adds complexity. This can drive users to seek workarounds or cut corners, such as having information sent to them through unsecured channels, which puts your company at risk.  

Similarly, email clients, browsers, and security settings may impact the decryption process, causing compatibility issues that prevent users from accessing their messages. Within a healthcare setting, where timely communication is crucial, such obstacles can disrupt workflows, slow down patient care, and lead to HIPAA compliance violations if users resort to unencrypted alternatives. 

Encryption that Requires Manual Intervention 

Some email encryption tools require users to manually encrypt messages. If users forget to apply encryption or misconfigure settings, sensitive patient data could be exposed, leading to compliance violations and ePHI exfiltration. 

For employees who handle ePHI and need to send encrypted emails, remembering to enable encryption (vs. automated encryption) is an extra step that introduces the risk of human error into the process. To offer a related, and more relatable, example: how many times have you forgotten to include an attachment when sending an email, even when referencing the attachment in the message? It’s all too easily done. In the same way, an inexperienced, tired, or distracted user could simply neglect to turn on or correctly configure encryption before sending an email, putting patient data at risk. 

Increased IT and Administrative Overhead

The two email encryption challenges outlined above contribute to a third overarching difficulty for healthcare organizations: an increased workload for its IT, security and operations teams. 

First of all, IT, security and operations must establish and continuously enforce encryption policies, configuring rules that ensure sensitive patient data is encrypted while non-sensitive, business communication continues to flow unobstructed. Misconfigured policies can cause over-encryption, resulting in user inaccessibility and disruptions, or under-encryption, leading to exposure of ePHI and HIPAA compliance violations.

Second, IT support teams must troubleshoot user issues: namely employees and external recipients who are unfamiliar with encryption protocols and need support in overcoming difficulties in message decryption. These could be caused by compatibility issues between different email clients or systems, expired or missing digital certificates, incorrect key exchanges, or confusion surrounding accessing encrypted messages through portals or attachments.

Lastly, IT and governance teams must keep up-to-date with changing regulatory updates and email security threats. As compliance requirements evolve, healthcare organizations must reassess encryption standards, upgrade outdated protocols, and ensure that their workforce adheres to best practices. Without an adequate strategy and the right systems in place, managing encryption can become a constant drain on IT bandwidth, taking personnel away from other aspects of their work that contribute to patient care. 

Effective Strategies For Email Encryption

Having discussed the most common encryption challenges and how they can impact a company’s email security posture, let’s look at some of the most powerful mitigation strategies, which will improve the email encryption experience for both senders and recipients.

Balance Security With Ease of Use

To overcome the challenges of user inaccessibility, human error, and excessive administrative overhead, healthcare organizations must balance the ease of use of their encryption solutions with the level of security they provide. 

While opting for the most secure encryption protocols intuitively seems like the best option, extra security often comes at the expense of usability, which can render the encryption irrelevant if users decide to circumvent it altogether, as outlined earlier. Instead, it’s essential to evaluate the sensitivity of message content and select a corresponding level of encryption. 

Moving onto practical technical examples, Transport Layer Security (TLS) is a widely used email encryption standard, thanks to its ease of implementation and use, i.e., once activated, no further action is required by the user to encrypt the message content. However, TLS only encrypts ePHI in transit, i.e., when being sent to recipients, which may prove insufficient for highly sensitive patient data.

In contrast, encryption protocols such as Secure/Multipurpose Internet Mail Extensions (S/MIME),  AES-256 and Pretty Good Privacy (PGP) provide more comprehensive encryption, safeguarding the ePHI contained in email communications both in transit and at rest, i.e., when stored in a database. Now, while this makes them more effective at securing patient data and achieving HIPAA compliance, these standards are more complicated to implement and to use than TLS encryption. 

S/MIME requires users to obtain and install digital certificates from a Certificate Authority (CA), which verifies their respective identities and provides the public key for encryption. Consequently, both the sender and recipient must have valid certificates; if either party’s certificate is revoked or expires, they won’t be able to encrypt or decrypt the message, respectively.

With PGP, meanwhile, users must manually generate and exchange public/private keys. This offers greater flexibility than S/MIME but requires careful key management, which can be confusing for non-technical users. If a recipient doesn’t have the sender’s public key, they won’t be able to decrypt the message. Additionally, both S/MIME and PGP require a public key infrastructure (PKI), which can add considerable administrative overhead, particularly in regards to the management of certificates, public keys, and user credentials. 

Accounting for this, healthcare organizations can balance security with accessibility by employing a tiered encryption strategy: using TLS for lower-risk communication while opting for S/MIME or PGP for more sensitive communications.  

Enable Automatic Encryption 

Subsequently, the challenge of balancing security with accessibility can be remediated by deploying an email delivery platform that not only removes the need for manual user intervention but also automatically applies the appropriate encryption standard based on message content and delivery conditions. Rather than relying on users to choose the correct method—or worse, bypass encryption altogether—modern email solutions like LuxSci can intelligently enforce encryption without affecting the user experience.

Many healthcare companies rely on TLS encryption because it eliminates the need for encryption keys or certificates, additional log-ins, etc. For this reason, it’s often referred to as  ‘invisible encryption’ for its lack of effect on the user experience. 

However, to be most effective, both the sender’s and recipient’s email servers must support enforced TLS (i.e., TLS 1.2 and above). In the event the recipient’s email server doesn’t support TLS, the email message will be delivered unencrypted or fail to send altogether, depending on the server configurations. Additionally, once the email is delivered to the recipient’s inbox, unless the recipient’s email infrastructure encrypts messages at rest, it will be stored in an unencrypted format. 

Consequently, while TLS is ideal for email messaging that doesn’t contain highly sensitive ePHI, it’s insufficient for all healthcare communication. To ensure the secure and HIPAA compliant inclusion of patient data in emails, healthcare organizations should opt for an email solution that supports automated, policy-based encryption, which can upgrade to S/MIME or PGP when necessary. This offers the combined benefits of optimal ePHI security, minimal administrative burden, and removing the need for staff intervention.

Invest in Employee Education

While a flexible encryption policy and deploying email solutions that support automation will go a long way towards overcoming email encryption challenges, these efforts can still be undermined if users aren’t sufficiently educated on their benefits and use. For this reason, it’s crucial that healthcare companies take the time to educate their employees on both the how and why of email encryption.  

Even the most advanced encryption systems can fail if employees don’t understand how to use them properly, as well as what to look out for in their day-to-day email use. Some aspects of email encryption, such as recognizing secure message formats or troubleshooting delivery issues, may still require user awareness. With this in mind, employee training programs should focus on recognizing when additional encryption measures are necessary, how to ask for assistance, the dangers of unsecured channels, and how to report suspicious activity in addition to the practical aspects of using your email delivery platform. 

Overcome Email Encryption Challenges with LuxSci

LuxSci is a leader in secure healthcare communication, offering HIPAA compliant solutions that empower organizations to connect with patients securely and effectively. With over 20 years of expertise, we’ve facilitated the delivery of billions of encrypted emails for healthcare providers, payers, and suppliers.

Luxsci’s proprietary SecureLine encryption technology is specially designed to help healthcare organizations overcome frequent encryption challenges and better ensure HIPAA compliance with powerful, flexible encryption capabilities. Its features include: 

  • Comprehensive email encryption: ensuring the encryption of patient data in transit and at rest. 
  • Automated encryption: “set it and forget it” email encryption guarantees security and HIPAA compliance – with no action required on the part of users once configured. 
  • Flexible encryption: dynamically determining the optimal level of email encryption, as per the recipient’s security posture, job role and supported encryption methods. This makes sure messages are delivered securely while maintaining HIPAA compliance.

Ready to take your healthcare email engagement to the next level? Contact LuxSci today!

encrypted email transmission

Is the Email Encrypted? How to Tell if an Email is Transmitted Using TLS

SMTP TLS encryption is popular because it provides adequate data protection without creating a complicated user experience for email recipients. Sometimes, though, the experience is too seamless, and recipients may wonder if the message was protected at all.

Luckily, there is a way to tell if an email was encrypted using TLS. To see if a message was sent securely, we can look at the raw headers of the email. However, it requires some knowledge and experience to understand the text. It is actually easier to tell if a recipient’s server supports TLS than to tell if a particular message was securely transmitted.

To analyze a message for transmission security, we will look at an example email message sent from Hotmail to LuxSci. We will explain what to look for when decoding the message headers and how to tell if the email was transmitted using TLS encryption.

An Example Email Message

First, we must understand how an email message typically travels through several machines on its way from the sender to the recipient. Roughly speaking:

  1. The sender’s computer talks to the sender’s email or WebMail server to upload the message.
  2. The sender’s email or WebMail server then talks to the recipient’s inbound email server and transmits the message to them.
  3. Finally, the recipient downloads the message from their email server.

It is step 2 that people are most concerned about when trying to understand if their email message is transmitted securely. They usually assume or check that everything is secure and OK at the two ends. Indeed, most users who need to can take steps to ensure that they are using SSL-enabled WebMail or POP/IMAP/SMTP/Exchange services so that steps 1 and 3 are secure. The intermediate step, where the email is transmitted between two different providers, is where messages may be sent insecurely.

To determine if the message was transmitted securely between the sender’s and recipient’s servers (over TLS), we need to extract the “Received” header lines from the received email message. If you look at the source of the email message, the lines at the top start with “Received.” Let’s look at an example message from a Hotmail user below. The email addresses, IPs, and other information are obviously fake.

LuxSci:

The Outlook email was sent to a LuxSci user. The Received headers appear in reverse chronological order, starting with the server that touched the message last. Therefore, in this example, we see the LuxSci servers first.

Received: from abc.luxsci.com ([1.1.1.1])
	by def.luxsci.com (8.14.4/8.13.8) with ESMTP id r7JEfLgH003867
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <user-xyz@def.luxsci.com>; Mon, 19 Aug 2019 10:41:21 -0400
Received: from abc.luxsci.com (localhost.localdomain [127.0.0.1])
	by abc.luxsci.com (8.14.4/8.13.8) with ESMTP id r7JEfK0Z030182
	for <user-xyz@def.luxsci.com>; Mon, 19 Aug 2019 09:41:20 -0500
Received: (from mail@localhost)
	by abc.luxsci.com (8.14.4/8.13.8/Submit) id r7JEfKXD030178
	for user-xyz@def.luxsci.com; Mon, 19 Aug 2019 09:41:20 -0500
Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [2.2.2.2])
	by abc.luxsci.com (8.14.4/8.13.8) with ESMTP id r7JEfIkK030002
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <someone@luxsci.net>; Mon, 19 Aug 2019 09:41:19 -0500

Proofpoint:

LuxSci uses an email filtering service, Proofpoint. Messages reach Proofpoint’s servers before being delivered to LuxSci. Here’s what their servers report about the email transmission:

Received: from unknown [65.54.190.216] (EHLO bay0-omc4-s14.bay0.hotmail.com)
	by dispatch1-us1.ppe-hosted.com.ppe-hosted.com
        (envelope-from <someone@hotmail.com>);
	Mon, 19 Aug 2019 08:41:18 -0600 (MDT)

Outlook:

And finally, here’s what we see from Oultook’s server.

Received: from BAY403-EAS373 ([65.54.190.199]) by bay0-omc4-s14.bay0.outlook.com
       with Microsoft SMTPSVC(6.0.3790.4675); 
       Mon, 19 Aug 2019 07:41:19 -0700

How to Use Received Message Headers to Tell if the Email is Encrypted

The message headers contain information that can help us determine if an email is encrypted. Here are a few helpful notes to help you decode the text:

  1. We said this above, but the message headers appear in reverse chronological order. The first one listed shows the last server that touched the message; the last one is the first server that touched it (typically the sending server).
  2. Each Received line documents what a server did and when.
  3. There are three sets of servers involved in this example: one machine at Hotmail, one machine at Proofpoint, where our Premium Email Filtering takes place, and some machines at LuxSci, where final acceptance of the message and subsequent delivery happened.

Presumably, the processing of email within each provider is secure. The place to be concerned about is the hand-offs between Hotmail and Proofpoint and between Proofpoint and LuxSci, as these are the big hops across the internet between providers.

In the line where LuxSci accepts the message from Proofpoint, we see:

(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)

This section, typical of most email servers running “sendmail” with TLS support, indicates that the message was encrypted during transport with TLS using 256-bit AES encryption. (“Verify=not” means that LuxSci did not ask Proofpoint for a second SSL client certificate to verify itself, as that is not usually needed or required for SMTP TLS to work correctly). Also, “TLSv1/SSLv3” is a tag that means that “Some version of SSL or TLS was used;” it does not mean that it was SSL v3 or TLS v1.0. It could have been TLS v1.2 or TLS v1.3.

So, the hop between Proofpoint and LuxSci was locked down and secure. What about the hop between Hotmail and Proofpoint? The Proofpoint server’s Received line makes no note of security at all! This means that the email message was probably not encrypted during this step.

Hotmail either did not support opportunistic TLS encryption for outbound emails, or Proofpoint did not support receipt of messages over TLS, and thus, TLS could not be used. With additional context, you can know which server supports TLS and which does not.

In this case, we know that Proofpoint supports inbound TLS encryption. In fact, from another example message where LuxSci sent a message to Proofpoint, we see the Received line:

Received: from unknown [44.44.44.44] (EHLO wgh.luxsci.com)
	by dispatch1-us1.ppe-hosted.com.ppe-hosted.com
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	with ESMTP id b-022.p01c11m003.ppe-hosted.com
        (envelope-from <from@domain.com>);
	Mon, 02 Feb 2009 19:28:27 -0700 (MST)

The red text makes it clear that the message was indeed encrypted. Based on the additional context, we can deduce that the Hotmail sending server did not securely transmit the email using TLS.

How To Tell if an Email is Encrypted With TLS

  1. When analyzing your message headers, consider the following items to determine if the email is encrypted:
    1. The receiving server will log what kind of encryption, if any, was used in receiving the message in the headers.
    2. Different email servers use different formats and syntax to display the encryption used. Look for keywords like “SSL,” “TLS,” and “Encryption,” which will signify this information.
    3. Not all servers will record the use of encryption. While LuxSci has always logged encryption use, not every email service provider does. It is possible to use TLS encryption and not log it. Sometimes, there is no way to tell from the headers if a message is encrypted if it is not logged.
    4. Messages passed between servers at the same provider do not necessarily need TLS encryption to be secure. For example, LuxSci has back-channel private network connections between many servers so that information can be securely passed between them without SMTP TLS. So, the lack of TLS usage between two servers does not mean the transmission between them was “insecure.” You may also see multiple received lines listing the same server: the server passes the message between different processes within itself. This communication also does not need to be TLS encrypted.
    5. If you are a LuxSci customer, you can view online email delivery reports to see if TLS was used for any particular message. We record the kind of encryption in the delivery reports, so it’s easy to see which emails were encrypted.

How can you Ensure Emails Are Securely Transmitted?

With some servers not recording TLS in message headers, how can you determine if a message was transmitted securely from sender to recipient?

To answer this question accurately, you must understand the properties, servers, and networks involved. It may be easy to determine that the message was transmitted securely if included in the header information. However, the absence of information does not necessarily mean the message was insecurely transmitted. You can only know this if you know what each system’s servers record.

In our example of a message from Hotmail to LuxSci, you need to know that:

  1. Proofpoint and LuxSci will always log the use of TLS in the headers. We can infer that the Hotmail to Proofpoint transmission was not secure as nothing was recorded there.
  2. The transmission of messages within LuxSci’s infrastructure is secure due to private back channel transmissions. So, even though there is no mention of TLS in every Received line after LuxSci accepts the message from Proofpoint (in this example), transferring the messages between servers in LuxSci is as secure as using TLS. Also, the same server can add multiple received lines as it talks to itself. Generally, these hand-offs on the same server will not use TLS, as there is no need. In the LuxSci example, we see this as “abc.luxsci.com” adds several headers.
  3. We don’t know anything about Hotmail’s email servers, so we don’t know how secure the initial transmissions within their network are. However, since we know they did not securely transmit the message to Proofpoint, we are not confident that the transmissions and processing within Hotmail (which may have gone unrecorded) were secure.

Was the email message sent and received using encryption?

We skipped steps 1 and 3 and focused on step 2 – the transmission between servers. Steps 1 and 3 are equally, if not more, necessary. Why? Because eavesdropping on the internet between ISPs is less of a problem than eavesdropping near the sender and recipient (i.e., in their workplace or local wireless hotspot). So, it’s essential to ensure messages are sent securely and received securely. This means:

  • Sending: Use SMTP over SSL or TLS when sending messages from an email client or use WebMail over a secure connection (HTTPS).
  • Receiving: Ensure your POP or IMAP connection is secured via SSL or TLS. If using WebMail to read your email, be sure it is over a secure connection (HTTPS).
  • WebMail: There is generally no record in the email headers to indicate if a message sent using WebMail was transmitted from the end-user to WebMail over a secure connection (SSL/HTTPS).

You can typically control one side and ensure it is secure; you can’t control the other without taking extra steps. So, what can you do to ensure your message is secure even if it might not be transmitted with encryption or if the recipient tries to access it insecurely?

You could use end-to-end email encryption (like PGP or S/MIME, which are included in SecureLine) or a secure web portal that doesn’t require the recipient to install or set up anything to get your secure email message. These methods meet HIPAA and other regulatory compliance requirements for secure data transmission and provide complete confidence that the message will be sent and received securely.

LuxSci’s SecureLine offers flexible encryption options, including TLS, secure web portal, PGP, and S/MIME. Its dynamic capabilities can determine what types of encryption the recipient’s server supports to ensure your emails are always sent securely. Contact our team today to learn more about how to secure your emails.