Skip to main content

TL;DR

If your business is sharing passwords through text, email, Slack, chat, spreadsheets, or phone calls, you do not have password management.

You have a risk hiding in plain sight.

Most small businesses do this because it feels fast. Someone needs access, someone sends the login, and everyone moves on. The problem is that nobody really knows where that password went, who still has it, or what happens when that employee, contractor, or vendor leaves.

There is a safer way.

A password manager, individual user access, multi-factor authentication, and a simple access review process can reduce a lot of unnecessary risk without turning your company into an IT department.

This is small business password security without the tech jargon.

Watch on YouTube -> LINK HERE

Your Password Is Not a Security Strategy

Password sharing is everywhere in small business

Let’s be honest.

Small businesses share passwords constantly.

Maybe the website login gets sent through a text.

Then the CRM password gets dropped into Slack.

A vendor receives social media credentials by email.

Later, someone reads a password over the phone because “it is faster.”

Eventually, those shortcuts turn into a spreadsheet full of business logins. Called something like “Company Passwords,” which is both convenient and terrifying.

It is common.

It is also risky.

The issue is not only that the password might be weak. The bigger issue is that access becomes messy. Once a password gets copied into chat, email, text, or a spreadsheet, you lose control of where it goes next.

That creates a simple but serious question:

Who actually has access to your business right now?

For a lot of owners, the honest answer is:

“I think I know.”

That is not a strategy.

The problem is not just weak passwords

Weak passwords are bad.

Shared passwords are worse.

A weak password is one problem. A shared password creates multiple problems at once.

Here is what usually happens:

  • The same login gets used by multiple people
  • The password gets sent through chat, text, or email
  • Nobody remembers who received it
  • A contractor leaves, but nobody changes the password
  • A former employee still knows the login
  • The login gets reused across multiple tools
  • Everyone uses the admin account because creating users feels annoying
  • No one knows which accounts have multi-factor authentication turned on

That is how a small convenience turns into a real business risk.

NIST, one of the top cybersecurity standards bodies, specifically calls out credential sharing as a problem. It notes that users are responsible for protecting authentication secrets and not disclosing them to others, and that technical controls are often poor at detecting or preventing intentional sharing.

Translation:

If your team keeps sharing passwords, the system probably will not save you from yourselves.

Why sharing passwords through chat, email, and text is risky

Most password sharing feels harmless in the moment.

It usually sounds like this:

“Can you send me the login real quick?”

So someone sends it.

Done.

Except now the password might live in:

  • A text thread
  • A Slack message
  • An email inbox
  • A screenshot
  • A forwarded message
  • A vendor’s phone
  • A contractor’s notes
  • A former employee’s chat history

That is the part owners underestimate.

You cannot revoke a screenshot.

You cannot unsend a password that was forwarded.

You cannot easily audit every place that password has been copied.

LastPass, one of the major password management platforms, warns against sharing passwords by text or email and notes that traditional methods like texts, calls, and emails can be intercepted, overheard, forwarded, or shared without good controls.

The risk is not always some dramatic hacker scene.

Sometimes the risk is boring.

Someone gets access they should not have.

Someone keeps access after they leave.

Someone uses an old shared password months later.

Someone’s email account gets compromised, and now your business logins are sitting in the inbox waiting to be found.

Boring risk still counts.

Credentials are a real attack path

This is not theoretical.

Verizon’s Data Breach Investigations Report is one of the most widely referenced cybersecurity reports. Its 2026 report notes that common breach causes include the human element, social engineering, phishing, stolen credentials, and vulnerability exploitation. It also recommends multi-factor authentication as one way businesses can block unauthorized access.

That matters because most small business owners think cybersecurity starts with firewalls, servers, and complicated tools.

A lot of the time, it starts with a login.

A real-world example: Uber’s 2022 security update said an attacker likely purchased a contractor’s corporate password after the contractor’s personal device had been infected with malware. The attacker then repeatedly attempted to log in until the contractor accepted a multi-factor authentication prompt, which gave the attacker access to internal tools. Uber’s response included blocking compromised accounts, requiring password resets, rotating keys, and strengthening MFA policies.

Another example: Microsoft’s analysis of the DEV-0537, also known as LAPSUS$, activity group described attackers using tactics like buying credentials and session tokens, paying employees or suppliers for credentials or MFA approval, and searching collaboration tools like Teams and Slack for exposed credentials.

That last part should get every owner’s attention.

Attackers know that companies share sensitive information inside workplace tools.

So if your team has passwords sitting in Slack, chat, email, or old docs, that is not just messy.

It is searchable risk.

There is a safer way to share access

The goal is not to make work harder.

The goal is to stop treating passwords like office supplies.

A better approach is to use a business password manager and share access through that system instead of sending raw credentials through messages.

Tools like LastPass, Bitwarden, 1Password, and others have business features that let teams share access in a more controlled way.

For example, LastPass describes secure password sharing that can let someone access a login without seeing the plain text password. It also allows businesses to manage access by employee, contractor, team, or project, and revoke access when someone leaves.

That is a big improvement over:

“I think we texted that password to the old contractor last year.”

Bitwarden uses shared collections and permission levels so organizations can group passwords and control which members or groups have access to specific items. Bitwarden also offers access reporting for enterprise organizations, which helps show who has access to what.

1Password allows secure item sharing with links that can expire and can be limited to specific people. Its business features also include shared vaults and permissions for managing team access.

Here is the plain-English version:

A password manager gives you a cleaner way to share access, track access, and remove access.

That is the whole game.

Important note: hidden does not always mean impossible to access

This part matters.

Some password managers offer features where a user can use a password without seeing the actual credential. That is helpful.

But do not confuse that with magic.

Bitwarden, for example, specifically warns that hidden passwords limit access but do not fully prevent it. Hidden passwords should still be treated as shared credentials.

So the point is not:

“Nobody could ever get this password.”

The point is:

“We are no longer blasting passwords through chat, email, and text with zero control.”

That is still a major improvement.

A password manager helps you:

  • Stop sending raw passwords
  • Organize access by role or team
  • Remove access faster
  • Avoid mystery logins
  • Reduce password reuse
  • Keep passwords out of chat history
  • Make offboarding cleaner
  • Build a basic access record

Perfect security is not the goal.

Better control is the goal.

What small businesses should do instead

You do not need to overhaul everything overnight.

Start with the obvious stuff.

1. Pick one company password manager

Do not let every employee pick their own system.

Choose one company-approved password manager and use it consistently.

Good options to evaluate include:

  • LastPass
  • Bitwarden
  • 1Password
  • Keeper
  • Dashlane

The specific tool matters less than the discipline around using it.

If passwords are still living in Slack, email, text, and spreadsheets, the tool is not the real problem yet.

The habit is.


2. Stop sharing passwords through messages

This is the first rule.

No passwords in:

  • Text messages
  • Slack messages
  • Email
  • Shared docs
  • Spreadsheets
  • Screenshots
  • Phone calls unless absolutely unavoidable

If someone needs access, share it through the password manager or create their own user account inside the tool.

The cleaner question is not:

“Who needs the password?”

The cleaner question is:

“What level of access does this person actually need?”

That shift matters.


3. Use individual accounts whenever possible

Shared logins are common because they feel easy.

But individual user accounts are almost always cleaner.

For example, instead of five people using one admin login, create five users with the right permissions.

That way, when someone leaves, you remove their account.

You do not have to change the password and then tell everyone the new one.

Individual accounts also make it easier to see who did what, who changed what, and who still has access.

That matters when something breaks.

It matters even more when something goes wrong.


4. Turn on multi-factor authentication

Passwords alone are not enough.

NIST says passwords are not phishing-resistant, which means a password by itself can still be stolen or tricked out of someone.

Multi-factor authentication, often called MFA or 2FA, adds another step. That might be an authenticator app, security key, passkey, or another approved method.

NIST describes higher assurance authentication as requiring proof of possession and control of two distinct authentication factors.

Plain English:

A password should not be the only thing standing between your business and a bad day.

Turn on MFA for your most important accounts first:

  • Email
  • Website admin
  • Domain registrar
  • Hosting
  • Banking
  • Payroll
  • Accounting
  • CRM
  • Payment processors
  • Password manager admin account

Also, do not share MFA codes.

Microsoft specifically recommends not allowing employees to share credentials or MFA factors.

That includes the classic:

“Can you send me the code real quick?”

No.

That code exists to prove the right person is logging in.

If the code is being passed around, the control is being bypassed.


5. Use stronger password rules, but do not overcomplicate it

The old advice was to create weird passwords with symbols, capital letters, and random substitutions.

That created nonsense like:

Summer2024! or Anystreet<last 4 of your business phone number>!

That is not a strong strategy.

NIST’s current guidance focuses on longer passwords, checking against compromised or commonly used passwords, avoiding forced periodic password changes unless there is evidence of compromise, and not relying on old-school composition rules.

For small businesses, the practical version is simple:

  • Use long, unique passwords
  • Do not reuse passwords
  • Let the password manager generate them
  • Turn on MFA
  • Change passwords when someone leaves or when access is uncertain
  • Change passwords immediately if they were shared through unsafe channels

Do not make your team invent passwords.

That is how you get bad passwords.

Let the password manager do the boring work.


Start with your highest-risk accounts

Not every login carries the same risk.

Start with the accounts that could hurt the business the most if they were accessed by the wrong person.

High-priority accounts to review first

  • Email admin account
  • Google Workspace or Microsoft 365 admin
  • Website admin
  • Website hosting
  • Domain registrar
  • DNS
  • Banking
  • Payroll
  • Accounting software
  • CRM
  • Payment processor
  • Social media accounts
  • Ad accounts
  • File storage
  • Password manager admin account

If you only have time to do one thing this week, review these accounts.

Ask:

  • Who has access?
  • Is MFA turned on?
  • Are people using individual accounts?
  • Are old employees or contractors still listed?
  • Is the password saved in a password manager?
  • Has this password ever been shared through text, Slack, email, or a spreadsheet?

If the answer is yes, clean it up.


The contractor problem nobody wants to talk about

Contractors are not the problem.

Messy access is the problem.

Small businesses often bring in contractors for websites, marketing, bookkeeping, admin help, CRM work, automation, design, ads, or IT support.

That is normal.

But here is where it gets risky:

  • The contractor gets the main admin login
  • The password gets sent through email
  • Nobody documents what they received
  • The project ends
  • Nobody removes access
  • The same password keeps getting reused
  • Months later, nobody knows what that person can still access

That is not a contractor issue.

That is an access management issue.

The better process is simple:

  1. Create a user account when possible
  2. Give the lowest access level needed
  3. Share passwords only through the password manager when needed
  4. Document what access was granted
  5. Set a reminder to review access
  6. Remove access when the project ends
  7. Change any shared passwords if needed

This does not need to be complicated.

It just needs to be intentional.


The owner test

Here is a quick test.

Can you answer these questions right now?

  • Who has access to your website?
  • Who has access to your email admin account?
  • Who has access to your domain registrar?
  • Who has access to your payment processor?
  • Which contractors still have logins?
  • Which former employees still know shared passwords?
  • Where are your passwords stored?
  • Are any passwords sitting in Slack, text messages, email, or spreadsheets?
  • Which critical accounts have MFA turned on?
  • Can you remove someone’s access in under 10 minutes?

If you cannot answer those questions, you do not have a password strategy.

You have memory.

And memory is not a security system.


What a simple access review looks like

You do not need a 40-page cybersecurity policy to get started.

Run a simple access review once per quarter.

Here is the basic version:

Step 1: List your critical tools

Start with email, website, domain, hosting, banking, payroll, accounting, CRM, payment tools, social media, ads, and file storage.

Step 2: List who has access

Write down employees, contractors, vendors, and admin users.

Step 3: Remove people who no longer need access

Be ruthless here.

Access should match current need, not historical convenience.

Step 4: Turn on MFA for critical accounts

Start with email, finance, website, domain, and password manager accounts.

Step 5: Move shared credentials into a password manager

Stop sending passwords manually.

Step 6: Change passwords that were shared unsafely

If a critical password was sent by text, email, Slack, or a spreadsheet, assume it has traveled farther than you think.

Change it.

Step 7: Set a recurring reminder

Do this quarterly.

Put it on the calendar.

No drama. Just maintenance.


This is not about being paranoid

Small business owners do not need more fear.

They need cleaner systems.

Password security is not about pretending every company needs an enterprise cybersecurity department.

It is about basic business hygiene.

You lock your office.

You control bank access.

You do not give every employee the same key to every room.

Your digital access should work the same way.

The problem is that small businesses often grow faster than their internal controls. Password sharing starts as a quick fix, then quietly becomes the company standard.

That is where the risk builds.

Not because people are careless.

Because the business never created a better way.


Final thought

Your password is not a security strategy.

Your strategy is how you create, share, protect, review, and remove access.

If your team is still sharing usernames and passwords through text, Slack, email, spreadsheets, or phone calls, start there.

Pick a password manager.

Turn on MFA.

Move passwords out of messages.

Create individual accounts where possible.

Review who has access.

Remove people who no longer need it.

You do not need to make this complicated.

You just need to stop letting convenience make security decisions for you.

Not sure who still has access to your business tools?

Start with a basic access review. It is one of the easiest ways to reduce risk, clean up your tech stack, and stop relying on memory to protect your business.

I help business owners reduce the quiet tech risks that build up over time, especially shared passwords, messy access, and old logins nobody remembers to clean up. Reach out if you want help reviewing who has access to what before a small shortcut turns into a bigger problem.

Contact us:
info@ascentoperationsgroup.com
843-310-1851
Drop us a note!

AOG