Enzoic Navigation
  • Solutions
    • Enzoic Account Takeover Protection
    • Enzoic for Active Directory
    • Enzoic for Active Directory Lite
    • Enzoic Exposure Alerts
    • NIST Password Standards
    • Hospitals & Healthcare Password Policy
  • Tech Docs
    • API – Dev Doc
    • Active Directory – Tech Docs
    • Security Overview
  • FAQ
    • FAQ Overview
    • Active Directory FAQ
  • Resources
    • Get Support
    • What Is Credential Stuffing
    • What Is Account Takeover
    • What is a Cracking Dictionary
    • Intuitive ATO Protection
    • About Strong Passwords
    • Resource Hub
  • Company
    • About
    • Enzoic Blog
    • Threat Intel
    • Contact Us
    • In the News
    • Careers
  • Sign In
  • Get Started
  • Solutions
    • Enzoic Account Takeover Protection
    • Enzoic for Active Directory
    • Enzoic for Active Directory Lite
    • Enzoic Exposure Alerts
    • NIST Password Standards
    • Hospitals & Healthcare Password Policy
  • Tech Docs
    • API – Dev Doc
    • Active Directory – Tech Docs
    • Security Overview
  • FAQ
    • FAQ Overview
    • Active Directory FAQ
  • Resources
    • Get Support
    • What Is Credential Stuffing
    • What Is Account Takeover
    • What is a Cracking Dictionary
    • Intuitive ATO Protection
    • About Strong Passwords
    • Resource Hub
  • Company
    • About
    • Enzoic Blog
    • Threat Intel
    • Contact Us
    • In the News
    • Careers
  • Sign In
  • Get Started
The New DIBBS Password Format

The New DIBBS Password Format Explained

In early September 2019, the DLA Internet Bid Board System (DIBBS) implemented new password requirements in line with the updated Department of Defence (DoD) security requirements. As a portal for contractors to submit quotes and proposals to the Defence Logistics Agency (DLA), DIBBS is home to potentially sensitive information that must be protected with robust cybersecurity measures. The September 2019 update reflects this by introducing new requirements to strengthen security.

Let’s take a look at the new DIBBS password format as well as the reasoning behind any changes. It’s important to note that any attempts we make to explain the logic behind changes to the password rules didn’t come from DIBBS or any other US government agency. Instead, our reasoning is based on current cybersecurity best practices within the industry.

New DIBBS Password Format

1- Your password must be a minimum of 15 characters long and a maximum of 60 characters long. When it comes to passwords, longer is better. Increasingly the length of your password dramatically increases the time it will take to crack it.

2- Your password must contain at least 2 characters from each of the following 4 character classes listed below:

  • English Upper Case Letters: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  • English Lower Case Letters: abcdefghijklmnopqrstuvwxyz
  • Westernized Arabic Numerals: 0123456789
  • Non-alphanumeric (special characters) @ # $ % ^ & + . = !

3- Your password must not have more than 4 Upper and Lower case letters in a row. Additionally, no more than 4 numbers in a row are allowed.

4- The first three characters of the password must be different from each other. For example, “thb” or “abc” would be allowed, but “jjj”, “aab”, or “bab” would not be allowed.

5- The password must not contain more than one special character in a row. For example, “$$” would not be allowed. Repeating characters makes it easier for you to remember the password, but it also makes it easier for a computer to crack it.

6- The password must not begin or end with “!”. Additionally, ampersand (&) cannot be the first special character used in the password. However, it can be the second or subsequent special character used. “!” is one of the first characters on most keyboards so a lot of users will choose this as their first special character. This is known to hackers and therefore inherently weak. “&” is also very commonly used because it is both a special character and a replacement for one of the most used words in the English language.

7- The new password must be different from your last 10 passwords. Reusing passwords dramatically increases the risk of using a password that has been exposed in a data breach and is now known to hackers. Unless you are continually monitoring your passwords by checking them against known exposed passwords or continually checking data breach news, you may be unaware your password has been exposed.

8- Your new password must differ from your previous password by at least 8 characters. This was previously 4 characters. Changing a character from uppercase to lower case or vice versa satisfies the requirement for a change.

  • This requirement is an example of password similarity blocking (blocking new passwords that are too similar to old passwords).
  • People often try to slightly alter their previous password so that it’s just different enough to pass as a new password but remains virtually unchanged to the user.
  • This is common password creation behavior but it leads to poor password security.

9- Passwords are valid for 60 days and then must be changed. It’s advised that users should frequently change their password to reduce the risk of continually using an exposed password.

10- The use of dictionary words from any language is prohibited. This is because password cracking programs that can run through millions of words in a matter of seconds are in widespread use.

11- Passwords should be complex, but also easy to remember. Complexity in this context tends to mean an element of randomness – something that isn’t easy to decipher at a glance and would appear illogical to anyone reading it. It also means that you make good use of all the character sets available to you. Complex passwords are harder for computers to crack because the computer will have to run through many millions of combinations before arriving at the right one. This isn’t the case when you use simple passwords that are all in one case, use repeating character, or only use one type of character class.

  • For example, according to this password checking website, the password “chocolate” would be cracked instantly. However, it would take a computer 8 hours to crack “cHoC0L@tE”. Please note that this example is just to illustrate the reasoning behind the complexity and that “cHoC0L@tE” would not satisfy DIBBS requirements, nor would it be considered a particularly strong password.
  • So, how do you remember a legitimately complex password? The key to this is to use a set of rules that you can follow to always recall the password. DIBBS uses the following examples:
  • Ihl1Cf20#yNi$8# (I have lived in California for 20 years now and is great)
  • Msi5%Y0ld%ni$8# (My Son is 5 years old and is great)
  • You shouldn’t use these examples as your password, but you can use a similar formula to make your own.
  • It’s a good idea to pick a memorable sentence that you’re unlikely to forget.
  • The above examples are personal statements, something personal to you or your life that you can easily cement into your mind.
  • Another example of a personal statement could be something like “Don’t forget, Grandma’s birthday is on September 7th and she wants flowers, chocolate, and a card”, which would become “Df.gBi0S7aSwF.C.AaC.”
  • If you don’t want to use a personal statement, song lyrics or your favorite quote from a book or movie could work well here.

12- The use of personal information in passwords is prohibited. For example, names, telephone numbers, account names, and birthplaces are not allowed. Hackers understand that people often use personal information in passwords because it makes the password easier to remember. Learning this personal information is often the motivation behind phishing attacks. Put simply, unless it’s something ONLY you know, like the name of a pet spider you had when you were a kid that you never told a single soul about, you shouldn’t incorporate it into your password.

13- DIBBS also recommends that you should change passwords with Internet Explorer or Firefox to avoid possible issues.

Conclusion of the new DIBBS Password Format

The new DIBBS password format is attempting to make authentication more secure and while some of the requirements seem onerous, they can make passwords more secure. Beyond just the above password requirements, we would also recommend that screening passwords for exposure would be a logical next step.

Learn more about compromised password screening.

DIBBS

Search

Browse blog categories

  • Account Takeover (19)
  • Active Directory (31)
  • all posts (78)
  • Continuous Password Protection (14)
  • COVID-19 (3)
  • Cracking Dictionaries (2)
  • Credential Screening (15)
  • Cybersecurity (28)
  • Data Breaches (9)
  • EdTech (1)
  • Enzoic Customer (2)
  • Enzoic News (7)
  • Enzoic Recognition and Awards (5)
  • Financial Services Cybersecurity (2)
  • Gaming Cybersecurity (1)
  • GDPR (1)
  • Healthcare Compliance (6)
  • Insider Threats (6)
  • Law Firm Cybersecurity (2)
  • Loyalty and Reward Programs Security (1)
  • NIST 800-63 (19)
  • Password Hygiene (4)
  • Password Tips (30)
  • Regulation and Compliance (3)
  • SMB Cybersecurity (2)

Stay up to date

Research, news, and more right to your inbox

More

  • Learning about strong, but unsafe passwords
  • What is a credential stuffing attack?
  • What is account takeover (ATO) fraud?
  • Eliminating password reuse to prevent ATO fraud
  • Password Strength Meter (Free)
  • Developer Documentation (APIs)

Recent blog posts

  • Pride and Passwords: Top Hacking Methods & How to Prevent Them
  • Cybersecurity and What’s Not Working from Home
  • From Paper to Passwords: Digitizing the Voting Process
  • From NIST Guidelines to Real-World Solutions?
  • [ Free Trial ]
  • Contact Us
  • 1-720-773-4515

Enzoic ©2020 | Privacy Policy | Acceptable Use

Enzoic’s password auditor provides a great baseline for assessing password vulnerability. Get next level of compromised credentials protection and try the full Enzoic for Active Directory at no cost.

Cookies

This website uses cookies to improve your experience. Continue to use the site as normal if you agree to the use of cookies. To find out more about our use of cookies or to opt-out, please see our Privacy Policy.

More Information
This site is for EDUCATIONAL PURPOSES ONLY.
Your password will be sent securely to the Enzoic servers to check if it is compromised. We do not store your password or use it for any other purpose. If you are not comfortable with this, do not enter your real password.
What is this?

Password Check is a free tool that lets you determine not just the strength of a password (how complex it is), but also whether it is known to be compromised. Billions of user passwords have been exposed by hackers on the web and dark web over the years and as a result they are no longer safe to use. So even if your password is very long and complex, and thus very strong, it may still be a bad choice if it appears on this list of compromised passwords. This is what the Password Check tool was designed to tell you and why it is superior to traditional password strength estimators you may find elsewhere on the web.

Why is it needed?

If you are using one of these compromised passwords, it puts you at additional risk, especially if you are using the same password on every site you visit. Cybercriminals rely on the fact that most people reuse the same login credentials on multiple sites.

Why is this secure?

This page, and indeed our entire business, exists to help make passwords more secure, not less. While no Internet-connected system can be guaranteed to be impregnable, we keep the risks to an absolute minimum and firmly believe that the risk of unknowingly using compromised passwords is far greater. Since our database of compromised passwords is far larger than what could be downloaded to the browser, the compromised password check we perform must occur server-side. Thus, it is necessary for us to submit a hashed version of your password to our server. To protect this data from eavesdropping, it is submitted over an SSL connection. The data we pass to our server consists of three unsalted hashes of your password, using the MD5, SHA1, and SHA256 algorithms. While unsalted hashes, especially ones using MD5 and SHA1, are NOT a secure way to store passwords, in this case that isn’t their purpose – SSL is securing the transmitted content, not the hashes. Many of the passwords we find on the web are not plaintext; they are unsalted hashes of the passwords. Since we’re not in the business of cracking password hashes, we need these hashes submitted for more comprehensive lookups. We do not store any of the submitted data. It is not persisted in log files and is kept in memory only long enough to perform the lookup, after which the memory is zeroed out. Our server-side infrastructure is hardened against infiltration using industry standard tools and techniques and is routinely tested and reviewed for soundness.

More…
  • Visit our FAQ to learn more
  • Contact us for press or sales inquiries
  • Add a free password strength meter to your website