In 2003, the National Institute of Standards and Technology (NIST) stated that strong passwords should consist of upper- and lowercase letters, numbers, and symbols. Recently, however, the institute reversed its stance. Find out why and learn what their new recommendations are for creating strong passwords.

An average business uses over a thousand cloud services. Even if small businesses use just a few dozen apps, securely managing account logins is still a huge hurdle for both users and administrators. Single sign-on (SSO) is an excellent solution to this issue, so let’s dive into how it works.

No matter how valuable your cloud subscriptions are, each new set of login credentials users are forced to create and memorize adds another level of inefficiency. With Single Sign-On (SSO), you can create one user profile that logs you into all your online accounts.

For years, we’ve been told that strong passwords include three things: upper- and lowercase letters, numbers, and symbols. And why wouldn’t we when the National Institute of Standards and Technology (NIST) told us they were the minimum for robust passwords? Here’s why not and how it involves you.

Everyone hates making passwords. From complexity requirements to minimum lengths, each new account brings its own set of headaches. If this problem is reaching a boiling point, Single Sign-On (SSO) solutions can help. They’re secure, easy-to-manage, and do away with the need to manage a long list of usernames and passwords.

A password policy designed for federal agencies must be secure, right? Surprisingly, that hasn’t been the case according to the National Institute of Standards and Technology (NIST). On the hook for the password best practices that we still use today -- the combination of letters, capitalizations, and numbers -- NIST admits that the existing guidelines were misguided.