Perry Chaffee

∙

The Password Apocalypse Is Coming

The Password Apocalypse Is Coming

Perry Chaffee

∙

The Password Apocalypse Is Coming

The Password Apocalypse Is Coming

Perry Chaffee

∙

The Password Apocalypse Is Coming

The Password Apocalypse Is Coming

Human-readable credentials, usernames, passwords, and the personal details behind them, are becoming impossible to trust as machines get better at faking humans and humans keep leaving their data scattered across decades of breaches. The fix isn't a stronger password or a second factor bolted on top. It's removing human-readable credentials from identity and access management entirely.

Why Machines Make This Worse

In a 1950 paper titled "Computing Machinery and Intelligence," Alan Turing proposed a test of artificial intelligence that's remained highly influential ever since. One human evaluator communicates with two entities, one human and one machine, through text alone. If the evaluator can't tell which is which, the machine is said to have passed.

A robot named Sophia, who once said she would destroy all humans, was given citizenship a few years back. Remarkable as "she" is, Sophia would be unlikely to pass as human in person. But the Turing test doesn't require in-person interaction. It happens through the same channels most people use every day: email, social media, messaging apps.

With virtual machines, automation, and deep learning, we're getting dangerously close to that threshold. A Terminator-style machine war is unlikely any time soon, but we are on the verge of something else: an apocalypse for passwords, usernames, and every other human-readable credential (HRC) organizations rely on for identification and access.

Organizations that use HRCs as the basis of their identity and access management are putting both their users and themselves at risk of phishing, spoofing, social engineering, and a long list of other problems. It's bad enough that people can already fool other people by pretending to be someone they're not. When virtual machines and automation scale that same tactic, it gets far more efficient, and far more effective.

Why Usernames and Passwords Have to Go

Businesses treat passwords and usernames as a cheap, convenient way to manage users. For the end user, they're inconvenient, and in today's threat environment, they're obsolete.

Technology connects people at an unprecedented scale, socially, professionally, financially, but almost entirely through self-asserted identity. Self-assertion is an invitation to either tell the truth or lie, and it's built on "something you know": usernames and passwords, but also every other human-readable credential, your name, birthday, contact information, Social Security number, passport number, driver's license number. Someone asserting their identity honestly provides real credentials. Someone exploiting the system's inherent weakness provides fake or stolen ones, and there's no structural difference between the two at the point of login.

From a user's perspective, a service that asks for more information feels more secure, and one that asks for less feels less secure. Logging into Instagram for cat photos might take just a username and password. Logging into your bank account takes more. In reality, neither is actually secure. Your money isn't meaningfully better defended than your cat photos, and remembering a growing pile of different passwords and other human-readable credentials isn't doing you any favors either.

The Breaches We Know About, and the Ones We Don't

For most people, logging in just means filling in blanks with information that's often already accessible to other people, whether they realize it or not. Prior breaches have flooded the darker corners of the internet with massive sets of credentials. Some of these we know about. Others, most likely, we don't.

Breach

What happened

Time to full disclosure

U.S. Office of Personnel Management

More than 21 million federal employees and servicemembers affected

Took more than a year for the intrusion to be noticed

Equifax

Affected 147.9 million consumers after the estimate was revised twice (from an initial 143 million)

Over a month between discovery and public disclosure

Yahoo

All user accounts eventually confirmed compromised, not just the subset first announced

Took over four years for the full scope to be admitted

What else is being breached right now that won't surface for months or years? It's a known unknown.

You might get warned to change your password after a breach, but you're very unlikely to change every other piece of personally identifying information tied to that breach, that would be impractical, often impossible. Worse, the same convenience that makes password resets easy for you also makes it easy for an attacker who already has your other information to temporarily lock you out and take over your account.

Why Human-Readable Credentials Keep Causing Problems

Websites relying on a username and password for login expose users to phishing, spoofing, keylogging, man-in-the-middle and man-in-the-browser attacks, password guessing, password cracking, shoulder surfing, social engineering, and more. Combine those vectors with virtual machines, automation, and AI, and the problem compounds.

So far, breaches have largely been treated like a lottery. Most companies weigh the probability of getting hacked against the severity of the fallout, invest minimally in following industry standards, and cover themselves with cybersecurity insurance. That approach pushes as much of the impact as possible onto users, and it tends to invest more in the PR response than in actual prevention. Preventative effort is usually limited to compliance, which is less about reducing risk and more about being able to say you tried after something goes wrong.

Equifax is a clear example. Its practices were largely compliance-focused, and its initial response to the breach was to delay notification for over a month, during which window several executives sold company stock, a timing issue that drew regulatory scrutiny afterward. The response to permanently compromising this data, for life, was a temporary offer of free credit monitoring that would later convert to a paid service.

Government hasn't done much to break this cycle either, even awarding an IRS fraud-prevention contract to Equifax after the breach. A real paradigm shift away from human-readable credentials as the foundation of identity and access management will likely take public pressure on government, paired with government leadership to drive the transition. That's one area where government involvement actually matters: your birth certificate, Social Security number, driver's license, and passport are all government-issued, and while each is built on the same flawed HRC foundation, the free market alone has little power to fix that. Since current policy lets businesses externalize most of the risk onto their users, businesses have little incentive to fix it either.

Until government identity providers implement something like a secure universal identity (SUID) system, breaches like OPM, Yahoo, and Equifax will keep happening.

Why 2FA and MFA Are a Band-Aid, Not a Fix

Adding a second factor is itself an admission that the first factor, the password, is inadequate. If that's true, the better question is why keep using the first factor at all, rather than replace it.

Traditional 2FA and MFA are inconvenient additions to a fundamentally obsolete identity and access management system, and they're still not fully secure. They're less a solution than a sign that organizations are choosing to treat symptoms instead of resolving the actual problem.

Augmenting HRCs with additional factors is a bit like going from a gas car to an electric one by way of a hybrid. The hybrid still carries the gas engine's downsides, just slightly reduced, while adding the new burdens of an electric engine and battery system on top. Building cars with both isn't the ideal end state, and neither is bolting MFA onto a system still rooted in usernames and passwords. It's more secure than nothing, and it's also more friction, more inconvenience, and nowhere near the real destination.

Why Biometrics Aren't the Whole Answer

Biometrics often get treated as the future of identity, but you can learn to fake a fingerprint from a YouTube tutorial in a few minutes, and security researchers have demonstrated unlocking an iPhone X with a crafted mask. Voice recognition and iris scanners carry their own risks too. We also leave our DNA in places we never intend to, which is exactly what forensic investigators rely on to solve crimes. Compared to securing your DNA, a sticky note with a password on it is arguably easier to control. Biometrics can add real value as a verification step after identity is established, but they shouldn't be the first or only step in the process.

The better foundation is a system built on math and cryptography: layered, mutual, bidirectional authentication using something you have that contains something no human could ever simply "know," running on a zero-trust architecture that compartmentalizes and segregates data across secure distributed storage, so that when no one's actively using the data (protected by client-side and end-to-end encryption), it doesn't exist in a form that can be stolen.

The Evidence Is Already Overwhelming

Verizon's Data Breach Investigations Report has found that more than 81% of breaches result from weak or compromised credentials. In each of those cases, someone managed to "know" the credentials of a trusted employee and used that knowledge to reach sensitive systems. Eliminating human-readable credentials addresses that entire category of risk directly.

The other half of the problem is data storage architecture itself. If a system lets one individual access the full data set, or even a large part of it, there's a meaningful risk that, given enough time, the wrong person eventually gets that access too, whether their credentials are quietly compromised or their loyalty shifts. Edward Snowden and Chelsea Manning both went through more rigorous background vetting than the average IT professional at an average company, and both still leaked vast amounts of sensitive information. Whatever you think of either individual, their actions make the same point: any architecture that lets humans access large data sets this way should assume that, eventually, the wrong humans will too.

Why Companies Keep Doing This Anyway

Companies keep using obsolete identity and access management because we let them. As consumers, most of us don't know enough to demand better security and better convenience, not through feedback and support channels, and not through government.

Many people also assume this is simply an unsolvable problem we're stuck with. Others worry about a government-run SUID system based on an incomplete picture of what it would actually mean, and let an understandable but outsized concern crowd out a broader view of the value such a system could deliver to consumers, businesses, and government alike.

A properly implemented SUID system would protect privacy rights more effectively than today's methods, meaningfully reduce data breaches and identity theft, and give government no new insight into people's private activity. It would simply help manage information already collected, more securely and far more conveniently than the status quo does now.

FAQ

What is a "human-readable credential" (HRC)?
Any identifying information a person can read, say, or type: usernames, passwords, birthdays, Social Security numbers, driver's license numbers, and similar details. If a human can know it, it can be guessed, phished, or stolen, which is the core vulnerability this article describes.

Why doesn't two-factor or multi-factor authentication solve the problem?
Because it still relies on the same flawed first factor, a password, underneath it. Adding a second factor on top treats the symptom (an easily compromised password) without removing the credential that caused the exposure in the first place.

How many people were actually affected by the Equifax breach?
Equifax's own disclosures put the final count at 147.9 million U.S. consumers, revised upward twice from an initial estimate of 143 million.

Are biometrics a secure replacement for passwords?
On their own, no. Fingerprints can be replicated, facial recognition has been fooled with crafted masks, and biometric data like DNA is left behind in places people don't control. Biometrics work best as an added verification step, not as the sole or first factor in identity.

What does Verizon's research say about credential-based breaches?
Verizon's Data Breach Investigations Report has found that more than 81% of breaches stem from weak or compromised credentials, making human-readable credentials the dominant vulnerability behind modern breaches.

Human-readable credentials, usernames, passwords, and the personal details behind them, are becoming impossible to trust as machines get better at faking humans and humans keep leaving their data scattered across decades of breaches. The fix isn't a stronger password or a second factor bolted on top. It's removing human-readable credentials from identity and access management entirely.

Why Machines Make This Worse

In a 1950 paper titled "Computing Machinery and Intelligence," Alan Turing proposed a test of artificial intelligence that's remained highly influential ever since. One human evaluator communicates with two entities, one human and one machine, through text alone. If the evaluator can't tell which is which, the machine is said to have passed.

A robot named Sophia, who once said she would destroy all humans, was given citizenship a few years back. Remarkable as "she" is, Sophia would be unlikely to pass as human in person. But the Turing test doesn't require in-person interaction. It happens through the same channels most people use every day: email, social media, messaging apps.

With virtual machines, automation, and deep learning, we're getting dangerously close to that threshold. A Terminator-style machine war is unlikely any time soon, but we are on the verge of something else: an apocalypse for passwords, usernames, and every other human-readable credential (HRC) organizations rely on for identification and access.

Organizations that use HRCs as the basis of their identity and access management are putting both their users and themselves at risk of phishing, spoofing, social engineering, and a long list of other problems. It's bad enough that people can already fool other people by pretending to be someone they're not. When virtual machines and automation scale that same tactic, it gets far more efficient, and far more effective.

Why Usernames and Passwords Have to Go

Businesses treat passwords and usernames as a cheap, convenient way to manage users. For the end user, they're inconvenient, and in today's threat environment, they're obsolete.

Technology connects people at an unprecedented scale, socially, professionally, financially, but almost entirely through self-asserted identity. Self-assertion is an invitation to either tell the truth or lie, and it's built on "something you know": usernames and passwords, but also every other human-readable credential, your name, birthday, contact information, Social Security number, passport number, driver's license number. Someone asserting their identity honestly provides real credentials. Someone exploiting the system's inherent weakness provides fake or stolen ones, and there's no structural difference between the two at the point of login.

From a user's perspective, a service that asks for more information feels more secure, and one that asks for less feels less secure. Logging into Instagram for cat photos might take just a username and password. Logging into your bank account takes more. In reality, neither is actually secure. Your money isn't meaningfully better defended than your cat photos, and remembering a growing pile of different passwords and other human-readable credentials isn't doing you any favors either.

The Breaches We Know About, and the Ones We Don't

For most people, logging in just means filling in blanks with information that's often already accessible to other people, whether they realize it or not. Prior breaches have flooded the darker corners of the internet with massive sets of credentials. Some of these we know about. Others, most likely, we don't.

Breach

What happened

Time to full disclosure

U.S. Office of Personnel Management

More than 21 million federal employees and servicemembers affected

Took more than a year for the intrusion to be noticed

Equifax

Affected 147.9 million consumers after the estimate was revised twice (from an initial 143 million)

Over a month between discovery and public disclosure

Yahoo

All user accounts eventually confirmed compromised, not just the subset first announced

Took over four years for the full scope to be admitted

What else is being breached right now that won't surface for months or years? It's a known unknown.

You might get warned to change your password after a breach, but you're very unlikely to change every other piece of personally identifying information tied to that breach, that would be impractical, often impossible. Worse, the same convenience that makes password resets easy for you also makes it easy for an attacker who already has your other information to temporarily lock you out and take over your account.

Why Human-Readable Credentials Keep Causing Problems

Websites relying on a username and password for login expose users to phishing, spoofing, keylogging, man-in-the-middle and man-in-the-browser attacks, password guessing, password cracking, shoulder surfing, social engineering, and more. Combine those vectors with virtual machines, automation, and AI, and the problem compounds.

So far, breaches have largely been treated like a lottery. Most companies weigh the probability of getting hacked against the severity of the fallout, invest minimally in following industry standards, and cover themselves with cybersecurity insurance. That approach pushes as much of the impact as possible onto users, and it tends to invest more in the PR response than in actual prevention. Preventative effort is usually limited to compliance, which is less about reducing risk and more about being able to say you tried after something goes wrong.

Equifax is a clear example. Its practices were largely compliance-focused, and its initial response to the breach was to delay notification for over a month, during which window several executives sold company stock, a timing issue that drew regulatory scrutiny afterward. The response to permanently compromising this data, for life, was a temporary offer of free credit monitoring that would later convert to a paid service.

Government hasn't done much to break this cycle either, even awarding an IRS fraud-prevention contract to Equifax after the breach. A real paradigm shift away from human-readable credentials as the foundation of identity and access management will likely take public pressure on government, paired with government leadership to drive the transition. That's one area where government involvement actually matters: your birth certificate, Social Security number, driver's license, and passport are all government-issued, and while each is built on the same flawed HRC foundation, the free market alone has little power to fix that. Since current policy lets businesses externalize most of the risk onto their users, businesses have little incentive to fix it either.

Until government identity providers implement something like a secure universal identity (SUID) system, breaches like OPM, Yahoo, and Equifax will keep happening.

Why 2FA and MFA Are a Band-Aid, Not a Fix

Adding a second factor is itself an admission that the first factor, the password, is inadequate. If that's true, the better question is why keep using the first factor at all, rather than replace it.

Traditional 2FA and MFA are inconvenient additions to a fundamentally obsolete identity and access management system, and they're still not fully secure. They're less a solution than a sign that organizations are choosing to treat symptoms instead of resolving the actual problem.

Augmenting HRCs with additional factors is a bit like going from a gas car to an electric one by way of a hybrid. The hybrid still carries the gas engine's downsides, just slightly reduced, while adding the new burdens of an electric engine and battery system on top. Building cars with both isn't the ideal end state, and neither is bolting MFA onto a system still rooted in usernames and passwords. It's more secure than nothing, and it's also more friction, more inconvenience, and nowhere near the real destination.

Why Biometrics Aren't the Whole Answer

Biometrics often get treated as the future of identity, but you can learn to fake a fingerprint from a YouTube tutorial in a few minutes, and security researchers have demonstrated unlocking an iPhone X with a crafted mask. Voice recognition and iris scanners carry their own risks too. We also leave our DNA in places we never intend to, which is exactly what forensic investigators rely on to solve crimes. Compared to securing your DNA, a sticky note with a password on it is arguably easier to control. Biometrics can add real value as a verification step after identity is established, but they shouldn't be the first or only step in the process.

The better foundation is a system built on math and cryptography: layered, mutual, bidirectional authentication using something you have that contains something no human could ever simply "know," running on a zero-trust architecture that compartmentalizes and segregates data across secure distributed storage, so that when no one's actively using the data (protected by client-side and end-to-end encryption), it doesn't exist in a form that can be stolen.

The Evidence Is Already Overwhelming

Verizon's Data Breach Investigations Report has found that more than 81% of breaches result from weak or compromised credentials. In each of those cases, someone managed to "know" the credentials of a trusted employee and used that knowledge to reach sensitive systems. Eliminating human-readable credentials addresses that entire category of risk directly.

The other half of the problem is data storage architecture itself. If a system lets one individual access the full data set, or even a large part of it, there's a meaningful risk that, given enough time, the wrong person eventually gets that access too, whether their credentials are quietly compromised or their loyalty shifts. Edward Snowden and Chelsea Manning both went through more rigorous background vetting than the average IT professional at an average company, and both still leaked vast amounts of sensitive information. Whatever you think of either individual, their actions make the same point: any architecture that lets humans access large data sets this way should assume that, eventually, the wrong humans will too.

Why Companies Keep Doing This Anyway

Companies keep using obsolete identity and access management because we let them. As consumers, most of us don't know enough to demand better security and better convenience, not through feedback and support channels, and not through government.

Many people also assume this is simply an unsolvable problem we're stuck with. Others worry about a government-run SUID system based on an incomplete picture of what it would actually mean, and let an understandable but outsized concern crowd out a broader view of the value such a system could deliver to consumers, businesses, and government alike.

A properly implemented SUID system would protect privacy rights more effectively than today's methods, meaningfully reduce data breaches and identity theft, and give government no new insight into people's private activity. It would simply help manage information already collected, more securely and far more conveniently than the status quo does now.

FAQ

What is a "human-readable credential" (HRC)?
Any identifying information a person can read, say, or type: usernames, passwords, birthdays, Social Security numbers, driver's license numbers, and similar details. If a human can know it, it can be guessed, phished, or stolen, which is the core vulnerability this article describes.

Why doesn't two-factor or multi-factor authentication solve the problem?
Because it still relies on the same flawed first factor, a password, underneath it. Adding a second factor on top treats the symptom (an easily compromised password) without removing the credential that caused the exposure in the first place.

How many people were actually affected by the Equifax breach?
Equifax's own disclosures put the final count at 147.9 million U.S. consumers, revised upward twice from an initial estimate of 143 million.

Are biometrics a secure replacement for passwords?
On their own, no. Fingerprints can be replicated, facial recognition has been fooled with crafted masks, and biometric data like DNA is left behind in places people don't control. Biometrics work best as an added verification step, not as the sole or first factor in identity.

What does Verizon's research say about credential-based breaches?
Verizon's Data Breach Investigations Report has found that more than 81% of breaches stem from weak or compromised credentials, making human-readable credentials the dominant vulnerability behind modern breaches.

Human-readable credentials, usernames, passwords, and the personal details behind them, are becoming impossible to trust as machines get better at faking humans and humans keep leaving their data scattered across decades of breaches. The fix isn't a stronger password or a second factor bolted on top. It's removing human-readable credentials from identity and access management entirely.

Why Machines Make This Worse

In a 1950 paper titled "Computing Machinery and Intelligence," Alan Turing proposed a test of artificial intelligence that's remained highly influential ever since. One human evaluator communicates with two entities, one human and one machine, through text alone. If the evaluator can't tell which is which, the machine is said to have passed.

A robot named Sophia, who once said she would destroy all humans, was given citizenship a few years back. Remarkable as "she" is, Sophia would be unlikely to pass as human in person. But the Turing test doesn't require in-person interaction. It happens through the same channels most people use every day: email, social media, messaging apps.

With virtual machines, automation, and deep learning, we're getting dangerously close to that threshold. A Terminator-style machine war is unlikely any time soon, but we are on the verge of something else: an apocalypse for passwords, usernames, and every other human-readable credential (HRC) organizations rely on for identification and access.

Organizations that use HRCs as the basis of their identity and access management are putting both their users and themselves at risk of phishing, spoofing, social engineering, and a long list of other problems. It's bad enough that people can already fool other people by pretending to be someone they're not. When virtual machines and automation scale that same tactic, it gets far more efficient, and far more effective.

Why Usernames and Passwords Have to Go

Businesses treat passwords and usernames as a cheap, convenient way to manage users. For the end user, they're inconvenient, and in today's threat environment, they're obsolete.

Technology connects people at an unprecedented scale, socially, professionally, financially, but almost entirely through self-asserted identity. Self-assertion is an invitation to either tell the truth or lie, and it's built on "something you know": usernames and passwords, but also every other human-readable credential, your name, birthday, contact information, Social Security number, passport number, driver's license number. Someone asserting their identity honestly provides real credentials. Someone exploiting the system's inherent weakness provides fake or stolen ones, and there's no structural difference between the two at the point of login.

From a user's perspective, a service that asks for more information feels more secure, and one that asks for less feels less secure. Logging into Instagram for cat photos might take just a username and password. Logging into your bank account takes more. In reality, neither is actually secure. Your money isn't meaningfully better defended than your cat photos, and remembering a growing pile of different passwords and other human-readable credentials isn't doing you any favors either.

The Breaches We Know About, and the Ones We Don't

For most people, logging in just means filling in blanks with information that's often already accessible to other people, whether they realize it or not. Prior breaches have flooded the darker corners of the internet with massive sets of credentials. Some of these we know about. Others, most likely, we don't.

Breach

What happened

Time to full disclosure

U.S. Office of Personnel Management

More than 21 million federal employees and servicemembers affected

Took more than a year for the intrusion to be noticed

Equifax

Affected 147.9 million consumers after the estimate was revised twice (from an initial 143 million)

Over a month between discovery and public disclosure

Yahoo

All user accounts eventually confirmed compromised, not just the subset first announced

Took over four years for the full scope to be admitted

What else is being breached right now that won't surface for months or years? It's a known unknown.

You might get warned to change your password after a breach, but you're very unlikely to change every other piece of personally identifying information tied to that breach, that would be impractical, often impossible. Worse, the same convenience that makes password resets easy for you also makes it easy for an attacker who already has your other information to temporarily lock you out and take over your account.

Why Human-Readable Credentials Keep Causing Problems

Websites relying on a username and password for login expose users to phishing, spoofing, keylogging, man-in-the-middle and man-in-the-browser attacks, password guessing, password cracking, shoulder surfing, social engineering, and more. Combine those vectors with virtual machines, automation, and AI, and the problem compounds.

So far, breaches have largely been treated like a lottery. Most companies weigh the probability of getting hacked against the severity of the fallout, invest minimally in following industry standards, and cover themselves with cybersecurity insurance. That approach pushes as much of the impact as possible onto users, and it tends to invest more in the PR response than in actual prevention. Preventative effort is usually limited to compliance, which is less about reducing risk and more about being able to say you tried after something goes wrong.

Equifax is a clear example. Its practices were largely compliance-focused, and its initial response to the breach was to delay notification for over a month, during which window several executives sold company stock, a timing issue that drew regulatory scrutiny afterward. The response to permanently compromising this data, for life, was a temporary offer of free credit monitoring that would later convert to a paid service.

Government hasn't done much to break this cycle either, even awarding an IRS fraud-prevention contract to Equifax after the breach. A real paradigm shift away from human-readable credentials as the foundation of identity and access management will likely take public pressure on government, paired with government leadership to drive the transition. That's one area where government involvement actually matters: your birth certificate, Social Security number, driver's license, and passport are all government-issued, and while each is built on the same flawed HRC foundation, the free market alone has little power to fix that. Since current policy lets businesses externalize most of the risk onto their users, businesses have little incentive to fix it either.

Until government identity providers implement something like a secure universal identity (SUID) system, breaches like OPM, Yahoo, and Equifax will keep happening.

Why 2FA and MFA Are a Band-Aid, Not a Fix

Adding a second factor is itself an admission that the first factor, the password, is inadequate. If that's true, the better question is why keep using the first factor at all, rather than replace it.

Traditional 2FA and MFA are inconvenient additions to a fundamentally obsolete identity and access management system, and they're still not fully secure. They're less a solution than a sign that organizations are choosing to treat symptoms instead of resolving the actual problem.

Augmenting HRCs with additional factors is a bit like going from a gas car to an electric one by way of a hybrid. The hybrid still carries the gas engine's downsides, just slightly reduced, while adding the new burdens of an electric engine and battery system on top. Building cars with both isn't the ideal end state, and neither is bolting MFA onto a system still rooted in usernames and passwords. It's more secure than nothing, and it's also more friction, more inconvenience, and nowhere near the real destination.

Why Biometrics Aren't the Whole Answer

Biometrics often get treated as the future of identity, but you can learn to fake a fingerprint from a YouTube tutorial in a few minutes, and security researchers have demonstrated unlocking an iPhone X with a crafted mask. Voice recognition and iris scanners carry their own risks too. We also leave our DNA in places we never intend to, which is exactly what forensic investigators rely on to solve crimes. Compared to securing your DNA, a sticky note with a password on it is arguably easier to control. Biometrics can add real value as a verification step after identity is established, but they shouldn't be the first or only step in the process.

The better foundation is a system built on math and cryptography: layered, mutual, bidirectional authentication using something you have that contains something no human could ever simply "know," running on a zero-trust architecture that compartmentalizes and segregates data across secure distributed storage, so that when no one's actively using the data (protected by client-side and end-to-end encryption), it doesn't exist in a form that can be stolen.

The Evidence Is Already Overwhelming

Verizon's Data Breach Investigations Report has found that more than 81% of breaches result from weak or compromised credentials. In each of those cases, someone managed to "know" the credentials of a trusted employee and used that knowledge to reach sensitive systems. Eliminating human-readable credentials addresses that entire category of risk directly.

The other half of the problem is data storage architecture itself. If a system lets one individual access the full data set, or even a large part of it, there's a meaningful risk that, given enough time, the wrong person eventually gets that access too, whether their credentials are quietly compromised or their loyalty shifts. Edward Snowden and Chelsea Manning both went through more rigorous background vetting than the average IT professional at an average company, and both still leaked vast amounts of sensitive information. Whatever you think of either individual, their actions make the same point: any architecture that lets humans access large data sets this way should assume that, eventually, the wrong humans will too.

Why Companies Keep Doing This Anyway

Companies keep using obsolete identity and access management because we let them. As consumers, most of us don't know enough to demand better security and better convenience, not through feedback and support channels, and not through government.

Many people also assume this is simply an unsolvable problem we're stuck with. Others worry about a government-run SUID system based on an incomplete picture of what it would actually mean, and let an understandable but outsized concern crowd out a broader view of the value such a system could deliver to consumers, businesses, and government alike.

A properly implemented SUID system would protect privacy rights more effectively than today's methods, meaningfully reduce data breaches and identity theft, and give government no new insight into people's private activity. It would simply help manage information already collected, more securely and far more conveniently than the status quo does now.

FAQ

What is a "human-readable credential" (HRC)?
Any identifying information a person can read, say, or type: usernames, passwords, birthdays, Social Security numbers, driver's license numbers, and similar details. If a human can know it, it can be guessed, phished, or stolen, which is the core vulnerability this article describes.

Why doesn't two-factor or multi-factor authentication solve the problem?
Because it still relies on the same flawed first factor, a password, underneath it. Adding a second factor on top treats the symptom (an easily compromised password) without removing the credential that caused the exposure in the first place.

How many people were actually affected by the Equifax breach?
Equifax's own disclosures put the final count at 147.9 million U.S. consumers, revised upward twice from an initial estimate of 143 million.

Are biometrics a secure replacement for passwords?
On their own, no. Fingerprints can be replicated, facial recognition has been fooled with crafted masks, and biometric data like DNA is left behind in places people don't control. Biometrics work best as an added verification step, not as the sole or first factor in identity.

What does Verizon's research say about credential-based breaches?
Verizon's Data Breach Investigations Report has found that more than 81% of breaches stem from weak or compromised credentials, making human-readable credentials the dominant vulnerability behind modern breaches.

Get WWPass

Download the WWPass Key app and test authentication without a username or password.

© 2026 World Wide Pass — WWPass

Get WWPass

Download the WWPass Key app and test authentication without a username or password.

© 2026 World Wide Pass — WWPass

Get WWPass

Download the WWPass Key app and test authentication without a username or password.

© 2026 World Wide Pass — WWPass