Updated 2025: Looking for a Business Associate Agreement? Download our FREE template

TotalHIPAA Logo

Password Guidelines Updated by NIST

Summary:

The National Institute of Standards and Technology (NIST) has updated its password guidelines in accordance with new research. The U.S. government requires its agencies to follow these guidelines, and many other organizations would benefit from implementing these rules as well. These practices represent a reasonable standard and will help you keep confidential information safe and […]

The National Institute of Standards and Technology (NIST) has updated its password guidelines in accordance with new research. The U.S. government requires its agencies to follow these guidelines, and many other organizations would benefit from implementing these rules as well.

These practices represent a reasonable standard and will help you keep confidential information safe and protect against breaches.¹

NIST is a federal agency that promotes U.S. innovation and industry by advancing the nation’s technology and information security infrastructure.² Following these updated guidelines can help you improve your password security practices and increase staff efficiency. Next, we’ll take you through recommended practices from the new guidelines and how to comply with them.

Increase password length

Length is a critical component of strong passwords. Longer passwords are statistically less likely to be cracked. Because of this, NIST now requires a minimum length of eight characters for user-generated passwords and six characters for those that are generated by a machine. To ensure greater security for more sensitive accounts, NIST says you should set the maximum password length at 64 characters.³

Allow special characters and spaces

Another way of increasing security levels is to allow the use of special characters in passwords. NIST now requires systems to permit passwords that contain special characters, even emojis and spaces. The new guidelines prohibit sequential (ex: 1234) or repeating (ex: aaaa) characters and dictionary words.³

Permit users to paste text

The guidelines encourage the use of automated systems for added security. Password fields must now allow users to paste text using a device’s copy and paste feature. This affords users the opportunity to use password managers, which can greatly increase security.

Stored passwords must also be hashed and salted (security measures similar to encryption). These are security measures that help to safeguard passwords that are in storage. If put into effect, hackers won’t be able to read your password data even if they manage to steal it.³

Outlaw password hints

Password hints are one example of an added security measure that can actually undermine password security. It’s only too common for users to set hints that make it very easy to determine the password. This defeats the purpose of having a password in the first place.

To prevent this, NIST has completely outlawed the use of password hints. Knowledge-based authentication (KBA) questions like “What street did you grow up on?” are also no longer permitted. The answers to these are too easily found over the internet, and can easily lead to a breach.³

Remove periodic password change requirements

Recent studies have shown that company policies that require frequent password changes are counterproductive to good password security. NIST recommends removing this requirement, which should increase usability and make password security more user-friendly.

Many industries have had a frequent password change standard in place for years, so it may take some time before this new standard is commonly observed. But for those who found the previous standard to be unnecessary, this may come as a welcome change.¹

Reduce complexity

NIST recommends minimizing password complexity requirements, like the necessary inclusion of upper case letters, symbols, and numbers. As with frequent password change policies, these requirements can result in passwords that decrease usability and hamper employee efficiency. Reducing password complexity can be another great step on the road to better security practices that employees find easier to manage.¹

Screen new passwords against commonly used or compromised passwords

A commonly held security practice is screening your users’ passwords against lists of commonly held passwords and known compromised passwords. NIST recommends you utilize software that can check proposed passwords against previously held or exposed passwords. This will protect against the hacking practice of trying known passwords in new settings.¹

Our HIPAA compliance services help ensure that your business follows the basic HIPAA rules and guidelines to protect sensitive patient information. Our team of experts is dedicated to providing affordable rates and personalized solutions to help you become HIPAA compliant. We understand that navigating the complex requirements of HIPAA can be challenging, which is why we offer a comprehensive range of services to meet your unique needs. From risk assessments to employee training, we have the tools and expertise necessary to help your business achieve and maintain HIPAA compliance. Contact us today to learn more about how we can help you protect your patients, your employees, and your business.

Sources

  1. New password guidelines from the US federal government via NIST
  2. NIST Special Publication 800-63B
  3. The New NIST Guidelines

Sharing is caring!

Looking for a Business Associate Agreement?

Download our free template to get started on your path toward HIPAA compliance.

Download Now

Want to stay informed?

Join our community, stay ahead of the curve on HIPAA compliance and receive free expert guidance.

Related Posts

Why do we need to test our Disaster Recovery Plan every year?

Why do we need to test our Disaster Recovery Plan every year?

Even if your internal software and servers remain perfectly static, the infrastructure, vendor updates, and cyber threats around them are constantly shifting. Waiting 2 or 3 years to test your backup systems leaves you vulnerable. This post breaks down the four external factors that degrade an untested playbook, explores HIPAA compliance mandates under NIST SP 800-66, and provides a granular, step-by-step example of what a compliant disaster recovery blueprint actually looks like.

How to Maintain HIPAA Compliance in Public Cloud Environments

How to Maintain HIPAA Compliance in Public Cloud Environments

Storing ePHI in the public cloud offers scalability but requires a strict “Shared Responsibility” approach. To remain HIPAA compliant, organizations must go beyond basic Business Associate Agreements (BAAs). The implementation of AES-256 encryption, multi-factor authentication (MFA), and microsegmentation are now required. This guide outlines the essential steps to securing your cloud infrastructure while meeting the latest HHS and OCR standards.

How to Stay HIPAA Compliant with Audit Logs

How to Stay HIPAA Compliant with Audit Logs

HIPAA audit logs are a mandatory technical safeguard under the HIPAA Security Rule, designed to track and record system activity across your network. To ensure complete compliance, organizations must actively maintain and routinely review these logs to detect unauthorized access to electronic protected health information (ePHI). This guide covers federal hipaa audit log requirements, the essential six-year hipaa audit log retention rules, best practices for tracking digital and physical data access, and how utilizing a structured hipaa audit log template protects your organization from catastrophic data breaches and costly federal penalties.

Save & Share Cart
Your Shopping Cart will be saved and you'll be given a link. You, or anyone with the link, can use it to retrieve your Cart at any time.
Back Save & Share Cart
Your Shopping Cart will be saved with Product pictures and information, and Cart Totals. Then send it to yourself, or a friend, with a link to retrieve it at any time.
Your cart email sent successfully :)