How Developers got Password Security so Wrong


Both in our real lives, and online, there are times where we need to authenticate ourselves - where we need to confirm we are who we say we are. This can be done using three things:
- Something you know
- Something you have
- Something you are
Passwords are an example of something you know; they were introduced in 1961 for computer authentication for a time-share computer in MIT. Shortly afterwards, a PhD researcher breached this system (by being able to simply download a list of unencrypted passwords) and used the time allocated to others on the computer.
As time has gone on; developers have continued to store passwords insecurely, and users have continued to set them weakly. Despite this, no viable alternative has been created for password security. To date, no system has been created that retains all the benefits that passwords offer as researchers have rarely considered real world constraints[1]. For example; when using fingerprints for authentication, engineers often forget that there is a sizable percentage of the population that do not have usable fingerprints or hardware upgrade costs.
Cracking Passwords
In the 1970s, people started thinking about how to better store passwords and cryptographic hashing started to Continue reading
The startup’s revenue grew 181 percent in 2017 over the previous year.
Public safety groups may benefit from slicing functionality.
EOLO built a custom SDN routing appliance for deployment at radio towers.
It added integrations with Xirrus WiFi and enhanced its automated cloud connectivity.

In this SDxCentral eBook, Making Networks Secure, we look at some of the key security strategies that are being used to protect networks in this new virtualized world.