password policy for business - abstract dark theme illustration

Password Policy for Business: A Practical Guide for South African SMBs

A modern password policy for business should prioritize length and usability over arbitrary complexity requirements. For most South African SMBs, the goal is to stop the common habits that lead to breaches: using “Password123”, reusing the same secret across five different apps, or writing passwords on sticky notes. The most effective policies focus on long passphrases, the use of password managers, and the total removal of forced periodic rotations. When a policy is too strict, employees find workarounds that create more risk than the policy was meant to solve. The objective is to create a system that is easy to follow but difficult for an attacker to crack.

What should a modern password policy for business include?

The shift in security standards from NIST and Microsoft reflects a hard truth: humans are bad at creating random strings of characters. When forced to use a symbol, a number, and a capital letter every 90 days, people usually just change “Summer2024!” to “Autumn2024!”. This predictable pattern is a gift to attackers using credential stuffing tools.

A current policy focuses on length. A 16-character passphrase made of four random words is significantly harder to crack than an 8-character “complex” password. Length provides more entropy, which is the primary defense against brute-force attacks. Along with length, a modern policy includes screening against known breach corpora. If a user chooses a password that has already appeared in a public leak, the system should reject it immediately.

Practical guidance: Set a minimum length of 14 characters. Do not require special characters or numbers if it encourages users to follow predictable patterns. Use a tool that checks passwords against a list of commonly leaked secrets.

Why the 90-day rotation rule is a security risk

For decades, IT managers have forced users to change passwords every three months. This rule made sense in 2003 when most attacks were slow and manual. Today, it is a liability. Forced rotation leads to “password cycling,” where users make tiny, predictable changes to their existing password. This doesn’t increase security; it just creates frustration.

Furthermore, frequent changes increase the likelihood that employees will write their passwords down or store them in unencrypted text files on their desktops. This creates a massive vulnerability that can be exploited through phishing attacks on South African businesses, where an attacker gains access to a machine and finds a “passwords.txt” file.

The current gold standard is to only require a password change when there is evidence of a compromise. If the password is long, unique, and protected by a second factor, there is no technical reason to change it on a calendar basis.

Practical guidance: Remove mandatory periodic expiration from your Active Directory or Google Workspace settings. Switch to a “change on compromise” model.

The role of password managers in the SMB workplace

Asking employees to remember twenty different 16-character passphrases is a recipe for failure. The only way to ensure a password policy is actually followed is to provide the tools to make it possible. A business-grade password manager is not an optional luxury; it is a core security requirement.

Password managers allow employees to generate truly random secrets and store them in an encrypted vault. This eliminates the need for memory-based shortcuts. For SMBs, this also solves the problem of onboarding and offboarding. When an employee leaves, you can revoke their access to the shared vault immediately rather than spending a weekend changing passwords on every shared service.

CISA recommends that businesses provide a company-wide password manager to make best practices easier to adopt. By removing the cognitive load of remembering passwords, you remove the incentive to reuse them.

Practical guidance: Deploy a managed password manager like Bitwarden or 1Password. Provide training on how to use the browser extension to fill credentials automatically.

How shared passwords sink South African SMBs

Many small businesses in South Africa still use shared logins for things like social media accounts, accounting software, or industry portals. This is a critical failure in accountability and security. When five people use the same “admin” password, you cannot tell who performed a specific action, and you cannot revoke access for one person without disrupting everyone else.

From a legal perspective, this creates a nightmare for POPIA compliance. If a data breach occurs, you need to be able to audit exactly who accessed the data. Shared passwords make a clean audit trail impossible. If that shared password is leaked, the entire business is exposed because there is no segmentation of access.

To fix this, every user must have their own unique identity. If a service only allows one login, use a password manager with secure sharing capabilities. This allows the team to access the account without actually knowing the master password, and access can be pulled back instantly.

Practical guidance: Audit all your company accounts. Replace shared logins with individual user accounts wherever possible. For legacy systems, use a vault to manage the shared secret.

The necessity of a strong second factor

No matter how long or complex a password is, it can still be stolen via a phishing site or a keylogger. This is why a password policy is only half of the equation. The most important addition to any business security stack is multi-factor authentication for businesses.

MFA turns the password into just one of several requirements for entry. Even if an attacker steals a 20-character passphrase, they still cannot enter the account without the second factor, such as a TOTP code from an app or a hardware key. This provides a massive safety net that protects the business from the inevitable human error of a leaked credential.

When combined with endpoint security for South African SMBs and a locked-down network security strategy, MFA becomes the final wall that stops a credential leak from becoming a full-scale ransomware event.

Practical guidance: Enable MFA on every single account that supports it, starting with email and financial tools. Prioritize app-based authenticators over SMS.

How to roll out a new policy without causing a revolt

Security policies often fail because they are delivered as a list of restrictions. To get buy-in from your team, you must present the new policy as a way to make their lives easier. If you tell them they no longer have to change their password every 90 days, they will be much more willing to accept a 14-character minimum length.

The rollout should follow a logical order:

  • First, deploy the password manager. Give employees a week to set up their vaults before enforcing new rules.
  • Second, introduce the new length requirements. Allow them to update their passwords at their own pace over a two-week window.
  • Third, disable the forced rotation. This is the “carrot” that makes the other changes palatable.
  • Finally, mandate MFA across all critical systems.

Microsoft guidance suggests that removing character-composition requirements and mandatory rotations significantly reduces user friction without compromising security. Focus on the tools and the length, and the users will follow.

Practical guidance: Hold a 15-minute demo to show how the password manager works. Explain the “why” behind the change, specifically mentioning the risk of predictable patterns.

For the underlying guidance, the NIST password guidance in SP 800-63B and CISA password and MFA advice both point the same direction: longer passphrases, screened against known breaches, kept in a password manager, backed by MFA.

Frequently Asked Questions

Is a 12-character password enough for a business?

While 12 characters is a decent baseline, 14 to 16 characters is the modern recommendation for businesses. The extra length provides exponential increases in protection against brute-force attacks. If you use a password manager, there is no reason not to use longer, more secure passphrases.

Should we still require symbols and numbers?

No. Current NIST and Microsoft guidance suggests that requiring symbols often leads to predictable substitutions, like replacing ‘a’ with ‘@’. This doesn’t actually confuse modern cracking tools. Focus on length instead. A long string of random words is more secure than a short, complex one.

What is the best way to handle passwords for shared accounts?

Avoid shared accounts entirely if possible. If you must use one, store the credential in a business password manager. This allows you to share access with specific team members without them needing to write the password down or share it via insecure channels like WhatsApp.

Does POPIA require a specific password policy?

POPIA does not dictate specific character counts, but it requires “appropriate, reasonable technical and organisational measures” to prevent unauthorized access. A weak password policy that allows reuse and shared logins would likely be seen as a failure to meet these requirements during an audit.

Should we use SMS for MFA codes?

SMS is better than nothing, but it is vulnerable to SIM swapping attacks. For a professional business policy, move toward app-based authenticators or hardware keys. These are more secure and more reliable, especially for employees who may travel or change phone numbers.

Building a sustainable password policy for business is about balancing security with human behavior. When you stop fighting your employees with outdated rules and instead provide them with the tools to succeed, your overall risk profile drops. Start with length, deploy a manager, and kill the rotation cycle to secure your business for the long term.

See what hackers can see about your business

Get your free security scan

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *