Identity and Access Management

5 Password Policies to Up Your Security

Complex passwords can save users from being hacked—any IT admin will tell you that. Plus, countless studies and articles on password security have been published about why password policies are vital to online security. Increasing the length of passwords, adding complexity to them and never reusing passwords more than once … these are three examples of smart password policies every person and company should use. After all, stronger passwords contribute to users being safer online. And if users are safer online, then your organization is safer, too. However, your organization’s password policies must be adhered to and enforced for them to protect you from security breaches and hacks.

Password Policies to Enforce for Greater Online Security

Password policy enforcement generally refers to a number of different items, including the following five best practices:

  • Length of Password – Perhaps the strongest correlation with password strength is the length of the password. As computers have become more advanced, the amount of time it takes to hack a password has become significantly less. In fact, a password that worked a couple of years ago is a weak password today. Increasing your password length will keep your user’s devices more secure. Many IT admins now advise that passwords be a minimum of 12 characters, but we suggest increasing that to an 18-character minimum.
  • Alphanumeric Characters – Requiring upper and lowercase characters and numbers greatly increases the complexity of the password. Alphanumeric characters also increase the potential combinations of passwords, making it even more difficult for a password, and thus a device or account, to be hacked.
  • Special Characters – To increase the level of password complexity, require special characters in all passwords. This password policy alone adds another 32 characters that can be utilized to strengthen passwords. In combination with alphanumeric characters, each character in a password could have 94 different choices. Better yet, make that password have 18 characters and you have 1.78e119 number of combinations. Word to the wise: It’s more secure to have long passwords with many different character choices rather than just long passwords that contain only letters.
  • Password Aging – If your organization is required to age passwords after, say, 90 days, then you’ll want to leverage this enforcement capability and have all users update their passwords every three months. There is some debate in the security community if password aging does, in fact, increase security, but we’ll leave that debate for a different blog post. As a general rule of thumb: Updating passwords to at least the same length and complexity after a set timeframe can only help to increase online security.
  • Password Lockout – Another security mechanism that we advise adopting is the password lockout. That is, to lock a user out of his or her account after too many incorrect attempts to log in. The password lockout helps prevent hackers from brute-forcing their way into users’ accounts.

Even in today’s cloud-operating and multi-device world, many IT organizations only leverage password policies if they are under compliance requirements to do so. But enforcing complex passwords by using the best practices listed above is the only way to guarantee your organization is safe from security breaches.

Of course, you must decide where to enforce the above password policies that require everyone within your organization to use complex passwords. Ideally, there is an automated central system that enforces passwords across your entire infrastructure, including your endpoint devices, servers, applications and networks. A system like this, a directory system, would take the manual work out of enforcing password policies. Modern directory-as-a-service platforms offer the ability to enforce password policies across all devices, applications and your company’s network infrastructure.

Greg Keller

Greg Keller

Before becoming the Chief Strategy Officer, Greg Keller previously served as the Chief Product Officer at JumpCloud for over four years, helping create and bring the first cloud directory service to market. Keller co-founded BlipSnips (acquired by Atigeo, Inc.), an early-stage software development company and a graduate of the Techstars accelerator program in 2010. Keller is a career product visionary and executive management leader with over two decades of product management, marketing, and operations experience ranging from startups to global organizations.

Recent Posts

Valkey is Rapidly Overtaking Redis

Redis is taking it in the chops, as both maintainers and customers move to the Valkey Redis fork.

11 hours ago

GitLab Adds AI Chat Interface to Increase DevOps Productivity

GitLab Duo Chat is a natural language interface which helps generate code, create tests and access code summarizations.

16 hours ago

The Role of AI in Securing Software and Data Supply Chains

Expect attacks on the open source software supply chain to accelerate, with attackers automating attacks in common open source software…

21 hours ago

Exploring Low/No-Code Platforms, GenAI, Copilots and Code Generators

The emergence of low/no-code platforms is challenging traditional notions of coding expertise. Gone are the days when coding was an…

2 days ago

Datadog DevSecOps Report Shines Spotlight on Java Security Issues

Datadog today published a State of DevSecOps report that finds 90% of Java services running in a production environment are…

2 days ago

OpenSSF warns of Open Source Social Engineering Threats

Linux dodged a bullet. If the XZ exploit had gone undiscovered for only a few more weeks, millions of Linux…

3 days ago