LuxSci

Healthcare Email Threat Readiness Strategies

Best Secure Email Hosting

Are you up to date on the latest email security threats?

In this post, we share details from our just-released Email Cyber Threat Readiness Report, exploring the most effective ways to strengthen your healthcare organization’s email cyber threat readiness in 2025.

Let’s go!

Conduct Regular Risk Assessments 

To strengthen your company’s email security posture, you must first identify vulnerabilities in your infrastructure that malicious actors could exploit. Frequent risk assessments will highlight the security gaps in your email infrastructure and allow you to implement the appropriate strategies to mitigate threats.

A comprehensive email risk assessment should include:

  • Assessment of email encryption practices.
  • Review of email authentication protocols, i.e., SPF, DKIM, DMARC.
  • Evaluation of access control policies and practices.
  • Assessment of malware detection capabilities.
  • Audit of third-party integrations.
  • Testing of employee email threat awareness through simulated attacks to determine threat readiness and training needs.
  • Review of incident response and business continuity plans, especially, in this case, in regard to email-based threats.

A risk assessment may also involve the use of vulnerability scanning tools, which scan your email infrastructure looking for conditions that match those stored in a database of known security flaws, or Common Vulnerabilities and Exposures (CVEs). Alternatively, healthcare companies often employ the services of ethical, or ‘white hat’, hackers who carry out penetration tests, in which they purposely attempt to breach your email security measures to pinpoint its flaws.

​​Implement Email Authentication Protocols

As touched on above, enabling and correctly configuring the right email authentication protocols is an essential mitigation measure against phishing and BEC attacks, domain spoofing and impersonation, and other increasingly common email threats. Just as importantly, it allows recipient email servers to verify that a message is authentic and originated from your servers, which reduces the risk of your domain being blacklisted and your emails being directed to spam folders instead of the intended recipient’s inbox.

The three main email authentication protocols are:

  • DomainKeys Identified Mail (DKIM): adds a cryptographic signature to outgoing emails, allowing the recipient’s server to verify that the email was not altered in transit. 
  • Sender Policy Framework (SPF): allows domain owners to specify which servers are authorized to send emails on their behalf, mitigating domain spoofing and other forms of impersonation.
  • Domain-based Message Authentication, Reporting & Conformance (DMARC): builds on SPF and DKIM by establishing policies for handling unauthorized emails. It instructs the recipient email server to monitor, quarantine, or reject emails that fail authentication checks. 

Establish Robust Access Control Policies

Implementing comprehensive access control policies reduces the chances of ePHI exposure by restricting its access to individuals authorized to handle it. Additionally, access privileges shouldn’t be equal and should be granted based on the employee’s job requirements, i.e., role-based access control (RBAC).

Zero Trust Architecture (ZTA), in contrast, is a rapidly emerging, and more secure, alternative to RBAC. ZTA’s core principles are “least privilege”, i.e., only granting the minimum necessary access rights, and “never trust, always verify”, i.e., continually asking for the user to confirm their identity as the conditions of their session change, e.g., their location, the resources they request access to, etc. 

Enable User Authentication Measures

Because a user’s login credentials can be compromised, through a phishing attack or session hijacking, for instance, access control, though vital, only protects ePHI to an extent. Subsequently, you must require a user to prove their identity, through a variety of authentication measures – with a common method being multi-factor authentication (MFA).

Recommended by HIPAA, MFA requires users to verify their identity in two or more ways, which could include:

  • Something they know (e.g., one-time password (OTP), security questions)
  • Something they have (e.g., a keycard or security token)
  • Something they are (i.e., biometrics: retinal scans, fingerprints, etc.). 

What’s more, it’s important to note that the need to enable MFA will be emphasized to a greater degree when the proposed changes to the HIPAA Security Rule go into effect in late 2025.

Identify and Manage Supply Chain Risk

While on the subject of access control, one of the most significant security concerns faced by healthcare organizations is that several third-party organizations, such as vendors and supply chain partners, have access to the patient data under their care to various degrees. As a result, cybercriminals don’t have to breach your email security measures to access ePHI – they could get their hands on your patients’ data through your vendors.

Consequently, third-party risk management must be a fundamental part of every healthcare organization‘s email threat mitigation strategy.  This requires you to ensure that each vendor you work with has strong email security measures in place. In light of this, a HIPAA requirement is to have a business associate agreement (BAA) in place with each third party, or business associate, so you both formally establish your responsibilities in securing ePHI. 

Set Up Encryption for Data In Transit and At Rest

Encrypting the patient data contained in email communication is a HIPAA regulation, as it prevents its exposure in the event of its interception by a cybercriminal. You should encrypt ePHI both in transit, i.e., when being included in emails, and at rest, i.e., when stored in a database.

Encryption standards sufficient for HIPAA compliance include:

  • TLS (1.2 +): a commonly-used encryption protocol that secures email in transit; popular due to being ‘invisible’, i.e., simple to use.
  • AES-256: a powerful encryption standard primarily used to safeguard stored data, e.g., emails stored in databases or archives.
  • PGP: uses public and private key pairs to encrypt and digitally sign emails for end-to-end security.
  • S/MIME: encrypts and signs emails using digital certificates issued by trusted authorities.

Develop a Patch Management Strategy

One of the most common means of infiltrating company networks, or attack vectors, is exploiting known security vulnerabilities in applications and hardware. Vendors release updates and patches to fix these vulnerabilities, so it’s crucial to establish a routine for regularly updating and patching email delivery platforms and the systems and infrastructure that underpin them.


Additionally, vendors periodically stop supporting particular versions of their applications or hardware, leaving them more susceptible to security breaches. With this in mind, you must track which elements of your IT ecosystem are nearing their end-of-support (EOS) date and replace them with suitable, HIPAA-compliant alternatives.

Implement Continuous Monitoring Protocols

Continuously monitoring your IT infrastructure is crucial for remaining aware of suspicious activity in your email traffic and potential security breaches. Without continuous monitoring, cybercriminals have a prime opportunity to infiltrate your network between periodic risk assessments. 

Worse, they can remain undetected for longer periods, allowing them to move laterally within your network and access your most critical data and systems. Conversely, continuous monitoring solutions employ anomaly detection to identify suspicious behavior, unusual login locations, etc. 

Develop Business Continuity and Disaster Recovery Plans

The unfortunate combination of organizations being so reliant upon email communication, email threats being so prevalent, and the healthcare sector being a consistent target for cyber attacks makes a data breach a near inevitability rather than a mere possibility. 

Consequently, it’s imperative to develop business continuity and disaster recovery protocols so you can resume normal operations as soon as possible in the event of a cyber attack. An essential part of a disaster recovery plan is making regular data backups, minimizing the impact on the service provided to patients and customers.

Implement Email Threat Awareness Training for Employees

Healthcare organizations must invest in email threat awareness training for their employees, so they can recognize the variety of email-based cyber attacks they’re likely to face and can play a role in their mitigation.

Email threat awareness training should include:

  • The different email-based cyber threats (e.g., phishing), how they work, and how to avoid them, including AI-powered threats.
  • Who to inform of suspicious activity, i.e., incident response procedures.
  • Your disaster recovery protocols.
  • Cyber attack simulations, e.g., a phishing attack or malware download.

While educating your employees will increase their email threat readiness, failing to equip them with the knowledge and skills to recognize email-based attacks could undermine your other mitigation efforts. 

Download LuxSci’s Email Cyber Threat Readiness Report

To gain further insight into the most effective email threat readiness strategies and how to better defend your healthcare organization from the ever-evolving threat landscape, download your copy of LuxSci’s Email Cyber Threat Readiness Report for 2025

You’ll also learn about the top email threats facing healthcare organizations in 2025, as well as how the upcoming changes to the HIPAA Security Rule may further impact your company’s cybersecurity and compliance strategies.

Grab your copy of the report here and reach out to us today if you want to learn more.

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

Most Popular LuxSci Blog Posts of 2025

As we close out 2025, healthcare communicators, IT and compliance leaders, and digital marketers face an ever-changing landscape of security threats, regulatory updates, and technology innovations. At LuxSci, we’re committed to helping you with continuous updates and guidance on the future of secure healthcare communications.

In case you missed it, or need a refresh, below are some of our most popular blog posts from 2025. Enjoy!

1. Improve Email Engagement and Marketing Results with Automated Workflows

Automated workflows are transforming how healthcare organizations engage patients and customers — enabling dynamic, event-driven campaigns that easily scale your outreach and keep you HIPAA compliant. In this post, we introduce LuxSci’s Automated Workflows capability for our Secure Marketing healthcare solution. Learn how sequence-based journeys can personalize outreach and optimize engagement with behavior-based triggers that improve campaign performance — without sacrificing data security.

Read the full post: LuxSci Enhances Secure Marketing with Automated Workflows

2. Healthcare Email Threat Readiness Strategies

Email remains a frontline channel for healthcare communications, and a prime target for cyber threats and criminals. This deep-dive into email threat readiness strategies covers essential practices like continuous monitoring, business continuity planning, and workforce training to mitigate email-borne security risks. Whether you’re responsible for clinical systems, marketing, or enterprise IT, this post provides a strategic playbook to strengthen your defenses, while maximizing your results.

Read the full post: Healthcare Email Threat Readiness Strategies

3. HIPAA Compliant Email — 20 Tips in 20 Minutes

For practical guidance you can apply right now, this on-demand webinar distills 20 key tips for HIPAA-compliant email across technical, legal, and operational domains. Whether you’re refining your infrastructure, improving deliverability, or modernizing your data security posture in 2026, this resource is a time-efficient way to elevate your compliance and security.

Read the post and watch the webinar on demand: HIPAA Compliant Email: 20 Tips in 20 Minutes

4. Is SendGrid HIPAA-Compliant? What You Should Know

Choosing the right email provider matters, especially when Protected Health Information (PHI) is at stake. In this post, we examine SendGrid’s capabilities in the context of HIPAA compliance, outline what it takes to send PHI securely, and offer guidance on evaluating third-party services for secure healthcare email and communication needs.

Read the full post: Is SendGrid HIPAA-Compliant?

5. LuxSci Shines in G2 Winter 2026 Reports

Customer feedback matters to LuxSci. In this post, we share the most recent news about LuxSci’s performance in the G2 Winter 2026 Reports, where we earned 20 badges across categories like Email Security, Encryption, Gateway, and HIPAA-Compliant Messaging. These reviews reflect not just product excellence, but trust from real users, which we work hard to build every day!

Read the full post: LuxSci Shines in G2 Winter 2026 Reports

Looking Ahead to 2026

We look forward to providing more information and insights on secure healthcare communications in the coming year, including the latest on HIPAA compliant email, PHI security, healthcare marketing, threat readiness, and personalized engagement. In the meantime, if you’re not already, follow us on LinkedIn below, and we’ll see you here in 2026!

Follow LuxSci on LinkedIn

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.

You Might Also Like

AES-256 Maximal Security

Enhanced Security: AES-256 Encryption for SSL and TLS

AES-256 EncryptionSSL and TLS play critical roles in securing data transmission over the internet, and AES-256 is integral in their most secure configurations. The original standard was known as Secure Sockets Layer (SSL). Although it was replaced by Transport Layer Security (TLS), many in the industry still refer to TLS by its predecessor’s acronym. While TLS can be relied on for securing information at a high level—such as US Government TOP SECRET data—improper or outdated implementations of the standard may not provide much security.

Variations in which cipher is used in TLS impact how secure TLS ultimately is. Some ciphers are fast but insecure, while others are slower, require a greater amount of computational resources, and can provide a higher degree of security. Weaker ciphers—such as the early export-grade ciphers—still exist, but they should no longer be used.

The Advanced Encryption Standard (AES) is an encryption specification that succeeded the Data Encryption Standard (DES). AES was standardized in 2001 after a five-year review and is currently one of the most popular algorithms used in symmetric-key cryptography. It is often seen as the gold standard symmetric-key encryption technique, with many security-conscious organizations requiring employees to use AES-256 for all communications. It is also used prominently in TLS. (more…)

Is AWS IAM HIPAA Compliant

Is AWS IAM HIPAA Compliant?

AWS Identity and Access Management (IAM) can be part of a HIPAA-compliant AWS environment when properly configured and used to control access to HIPAA-eligible services covered under Amazon’s Business Associate Agreement (BAA). IAM itself provides the access control mechanisms necessary for protecting healthcare data, but doesn’t automatically create HIPAA compliance. Healthcare organizations must implement appropriate IAM policies, permission boundaries, and monitoring to become HIPAA compliant.

Access Control Management

AWS IAM manages access permissions for AWS resources through users, groups, and roles with various policies. Healthcare organizations use IAM to restrict who can access AWS services that store or process protected health information. This service helps fulfill the HIPAA Security Rule requirements for access management and authorization controls. IAM enables detailed permissions that follow the principle of least privilege, giving users only the access they need to perform their jobs. While IAM provides these security capabilities, healthcare organizations remain responsible for configuring them properly to be HIPAA compliant.

Configuration Steps

Healthcare organizations must implement particular IAM configurations to support HIPAA compliance. Multi-factor authentication adds an extra verification layer beyond passwords for accounts accessing patient data. Permission boundaries limit maximum privileges that can be granted to users or roles. IAM policies should restrict access based on job functions and responsibilities. Regular access reviews verify that permissions remain appropriate as staff roles change. Password policies enforce complexity requirements and regular rotation. Organizations typically document these configuration decisions as part of their overall security planning to demonstrate efforts to become HIPAA compliant.

Audit Trail Implementation

HIPAA requires tracking who accesses protected health information and when this access occurs. AWS IAM integrates with CloudTrail to log all user activities and API calls. These logs create audit trails showing who performed what actions within AWS services that manage healthcare data. Organizations must configure appropriate log retention periods based on their compliance requirements. Monitoring tools should alert security teams about suspicious activities like failed login attempts or unusual access patterns. This monitoring capability helps organizations identify potential security issues and respond promptly to maintain HIPAA compliance.

Complementary AWS Security Services

IAM works with other AWS services to create a complete HIPAA compliance environment. AWS Organizations helps manage multiple accounts with centralized policy control for healthcare environments. AWS Key Management Service (KMS) handles encryption keys that protect healthcare data. AWS Secrets Manager securely stores database credentials and API keys. AWS Control Tower provides guardrails that enforce security policies across multiple accounts. Healthcare organizations often implement these services together to create thorough security architectures. This integrated approach helps maintain consistent controls across all systems handling protected health information.

Permission Management Approaches

Effective IAM policy management forms an essential part of maintaining HIPAA compliance. Organizations should document their IAM policy creation and review processes. Templates for common healthcare roles help maintain consistency when creating new accounts. Regular policy reviews identify and remove unnecessary permissions. Automated tools can validate that policies align with security standards and best practices. Changes to IAM permissions should follow change management procedures with appropriate approvals. These practices help organizations maintain proper access controls throughout their AWS environment.

BAA HIPAA Compliant Requirements

AWS offers a Business Associate Agreement (BAA) that applies to specific HIPAA-eligible AWS services used to store, process, or transmit protected health information. AWS Identity and Access Management (IAM) itself does not store or process ePHI, but is used to control access to HIPAA-eligible services covered under the BAA. Healthcare organizations must execute the AWS BAA before storing any patient data in HIPAA-eligible AWS services. While IAM plays a critical role in enforcing access controls, organizations remain responsible for properly configuring and managing IAM as part of their overall HIPAA compliance program.

replying to an email

Are Replies to Encrypted Emails also Secure?

Sending HIPAA-compliant emails is easy when you use an encryption solution like LuxSci. But what happens when someone replies to an encrypted message? Are the replies also secure? This is primarily a concern when using SMTP TLS as a secure means of email delivery. 

This article will explain how messages are sent securely, how replies behave, and whether they are secure and compliant. At the end, we provide some recommendations for how to balance security and usability. 

(more…)

biggest email threats

Know the Biggest Email Threats Facing Healthcare Right Now

Due to its near-universal adoption, speed, and cost-effectiveness, email remains one of the most common communication channels in healthcare. Consequently, it’s one of the most frequent targets for cyber attacks, as malicious actors are acutely aware of the vast amounts of sensitive data contained in messages – and standard email communication’s inherent vulnerabilities.

In light of this, healthcare organizations must remain aware of the evolving email threat landscape, and implement effective strategies to protect the electronic protected health information (ePHI) included in email messages. Failing to properly secure email communications jeopardizes patient data privacy, which can disrupt operations, result in costly HIPAA compliance violations, and, most importantly, compromise the quality of their patients’ healthcare provision.

With all this in mind, this post details the biggest email threats faced by healthcare organizations today, with the greatest potential to cause your business or practice harm by compromising patient and company data. You can also get our 2025 report on the latest email threats, which includes strategies on how to overcome them.

Ransomware Attacks

Ransomware is a type of malware that encrypts, corrupts, or deletes a healthcare organization’s data or critical systems, and enables the cybercriminals that deployed it to demand a payment (i.e., a ransom) for their restoration. Healthcare personnel can unwittingly download ransomware onto their devices by opening a malicious email attachment or clicking on a link contained in an email.

In recent years, ransomware has emerged as the email security threat with the most significant financial impact. In 2024, for instance, there were over 180 confirmed ransomware attacks with an average paid ransom of nearly $1 million. 

Email Client Misconfiguration

While a healthcare organization may implement email security controls, many fail to know the security gaps of their current email service provider (ESP) or understand the value of a HIPAA compliant email platform, leaving data vulnerable to email threats, such as unauthorized access and ePHI exposure, and also, subsequently, a greater risk of compliance violations and reputation damage.

Common types of email misconfiguration include:

  • Lack of enforced TLS encryption: resulting in emails being transmitted in plaintext, rendering the patient data they contain readable by cybercriminals in the event of interception during transit.
  • Improper SPF/DKIM/DMARC setup: failure to configure or align these email authentication protocols correctly gives malicious actors greater latitude to successfully spoof trusted domains.
  • Disabled or lax user authentication: a lack of authentication measures, such as multi-factor authentication (MFA), increases the risk of unauthorized access and ePHI exposure.
  • Misconfigured secure email gateways: incorrect rules or filtering policies can allow phishing emails through or block legitimate messages.
  • Outdated or unsupported email client software: simply neglecting to download and apply the latest updates or patches from the email client’s vendor can leave vulnerabilities, which are well-known to cybercriminals, exposed to attack.

Social Engineering Attacks

A social engineering attack involves a malicious actor deceiving or convincing healthcare employees into granting unauthorized access or exposing patient data. Relying on psychological manipulation, social engineering attacks exploit a person’s trust, urgency, fear, or curiosity, and encompass an assortment of threats, including phishing and business email compromise (BEC) attacks, which are covered in greater depth below.

Phishing

As mentioned above, phishing is a type of social engineering attack, but they are so widespread that it warrants its own mention. Phishing sees malicious actors impersonating legitimate companies, or their employees, to trick victims into revealing sensitive patient data. 

Subsequently, healthcare organizations can be subjected to several different types of phishing attacks, which include:

  • General phishing: otherwise known as bulk phishing or simply ‘phishing’, these are broad, generic attacks where emails are sent to large numbers of recipients, impersonating trusted entities to steal credentials or deliver malware. 
  • Spear phishing: more targeted attacks that involve personalized phishing emails crafted for a specific healthcare organization or individual. These require more research on the part of malicious actors and typically use relevant insider details gleaned from their reconnaissance for additional credibility.
  • Whaling: a form of spear phishing that specifically targets healthcare executives or other high-level employees. 
  • Clone phishing:  when a cybercriminal duplicates a legitimate email that was previously received by the target, replacing links or attachments with malicious ones.
  • Credential phishing: also known as ‘pharming’, this involves emails that link to fake login pages designed to capture healthcare employees’ usernames and passwords under the guise of frequently used legitimate services.

Domain Impersonation and Spoofing

This category of threat revolves around making malicious messages appear legitimate, which can allow them to bypass basic email security checks. As alluded to above, these attacks exploit weaknesses in email client misconfigurations to trick the recipient, typically to expose and exfiltrate patient data, steal employee credentials, or distribute malware.

Domain spoofing email threats involve altering the “From” address in an email header to make it appear to be from a legitimate domain. If a healthcare organization fails to properly configure authentication protocols like SPF, DKIM, and DMARC, there’s a greater risk of their email servers failing to flag malicious messages and allowing them to land in users’ inboxes.

Domain impersonation, on the other hand, requires cybercriminals to register a domain that closely resembles a legitimate one. This may involve typosquatting, e.g., using “paypa1.com” instead of “paypal.com”. Alternatively, a hacker may utilize a homograph attack, which substitutes visually similar characters, e.g., from different character sets, such as Cyrillic. Malicious actors will then send emails from these fraudulent domains, which often have the ability to bypass basic email filters because they aren’t exact matches for blacklisted domains. Worse still, such emails can appear authentic to users, particularly if the attacker puts in the effort to accurately mimic the branding, formatting, and tone used by the legitimate entity they’re attempting to impersonate. 

Insider Email Threats

In addition to external parties, employees within a healthcare organization can pose email threats to the security of its PHI. On one hand, insider threats can be intentional, involving disgruntled employees or third-party personnel abusing their access privileges to steal or corrupt patient data. Alternatively, they could be the result of mere human error or negligence, stemming from ignorance, or even fatigue.

What’s more, insider threats have been exacerbated by the rise of remote and flexible conditions since the onset of the COVID-19 pandemic, which has created more complex IT infrastructures that are more difficult to manage and control.  

Business Email Compromise (BEC) Attacks

A BEC attack is a highly targeted type of social engineering attack in which cybercriminals gain access to, or copy, a legitimate email account to impersonate a known and trusted individual within an organization. BEC attacks typically require extensive research on the targeted healthcare company and rely less on malicious links or attachments, unlike phishing, which can make them difficult to detect.

Due to the high volume of emails transmitted within the healthcare industry, and the sensitive nature of PHI often included in communications to patients and between organizations, the healthcare industry is a consistent target of BEC attacks.

BEC attacks come in several forms, such as:

  • Account compromise: hijacking a real employee’s account and sending fraudulent messages.
  • Executive fraud: impersonating high-ranking personnel to request urgent financial transactions or access to sensitive data.
  • Invoice fraud: pretending to be a vendor asking for the payment of a fraudulent invoice into an account under their control.

Supply Chain Risk

Healthcare organizations increasingly rely on third-party vendors, including cloud service providers, software vendors, and billing or payment providers to serve their patients and customers. They constantly communicate with their supply chain partners via email, with some messages containing sensitive patient data; moreover, some of these organizations will have various levels of access to the PHI under their care.

Consequently, undetected vulnerabilities or lax security practices within your supply chain network could serve as entry points for email threats and malicious action. For instance, cybercriminals can compromise the email servers of a healthcare company’s third-party vendor or partner, and then send fraudulent emails from their domains to deploy malware or extract patient data.

Another, somewhat harrowing, way to understand supply chain risk is that while your organization may have a robust email security posture, in reality, it’s only as strong as that of your weakest third-party vendor’s security controls.

Download LuxSci’s Email Cyber Threat Readiness Report

To gain further insight into the biggest email threats to healthcare companies in 2025, including increasingly prevalent AI threats, download your copy of LuxSci’s Email Cyber Threat Readiness Report

You’ll also learn about the upcoming changes to the HIPAA Security Rule and how it’s set to impact your organization going forward, and the most effective strategies for strengthening your email security posture.

Grab your copy of the report here and begin the journey to strengthening your company’s email threat readiness today.