← Articles

October 22, 2026

What the Flock Cameras Teach About SSO

Former police officers kept using Flock's camera network after they left the force. Orphaned accounts are the reason, and single sign-on is the fix.

By Treb Ryan

single sign-on offboarding identity management

The Washington Post reported this week that former police officers kept using Flock’s surveillance network long after they left the force.

If you haven’t been following the story, Flock Safety is an Atlanta company that runs more than 120,000 roadside cameras that photograph license plates. Thousands of police departments pay for access, so officers can search where a car has been spotted.

One investigator left a Georgia sheriff’s office in 2021. His Flock login kept working for a few more years. He and other former officers used the access in ways they weren’t authorized to.

Your first reaction might be, “How do you not take someone off the system when they walk out the door?”

Here’s how it usually happens. An organization doesn’t run one system. It runs dozens across a variety of departments, each with its own login and its own admin. Offboarding means keeping track of every single one. Miss one and nobody notices, because a forgotten account looks exactly like a working one.

That’s what happened in another Georgia case. A county police department shared its Flock subscription with the sheriff’s office, and when an officer resigned, nobody told the sheriff’s office to remove her access.

IT has a name for these leftover logins: orphaned accounts. Most of them won’t end in a criminal case. At the very least, they’re an open door for a data breach, and you’re still paying for a seat.

Try this: pull up your offboarding checklist and count how many apps a departing employee touches. Then count how many of those you’d actually remember to shut off.

Isn’t Single Sign-On supposed to be the answer?

The simple solution has existed for over 15 years: single sign-on (SSO). Easy offboarding has been one of the key benefits of SSO since the beginning. Remove a user once, and they’re gone from every system connected to it.

So why doesn’t everyone use it? Because it was designed for enterprises. It’s complicated and expensive. It has only gotten more complicated and expensive since.

Most non-enterprise businesses don’t have the expertise or budget to implement SSO. Not to mention plenty of other organizations, like school districts, nonprofits, and police departments, often don’t have anyone whose job is to think about this at all.

SSO for every organization is the answer

We know the barriers for most organizations adopting SSO. So how do we fix it? Three issues need to be addressed.

  1. Cost. Basic security capabilities should not cost anything. Do you pay extra to have a user name and password for an application?
  2. Easy to use. Free doesn’t help much if you need a chief information security officer to set it up.
  3. Reliable. Even free and easy SSO needs to be as secure and reliable as any offering on the market.

That’s what we built Passless to do. If those three things matter to you, try Passless. Plus, you get SSO, MFA, and passkeys for free, with no per-seat limits and no annual contract, and it’s SOC 2 Type II certified.

Your organization may not run a camera network, but you’re still paying for every seat nobody remembered to remove.

One closing thought

The astute reader will have noticed that shared usernames and passwords were another way people got unauthorized access to Flock. More on that soon.