Seven Identity Mistakes That Keep SMBs in the Breach Statistics (And How to Fix Each in a Quarter)

Identity security is not just a matter of turning on multifactor authentication. It means knowing who can access what, why they need that access, and whether they should still have it.

A 2026 survey by the National Cybersecurity Alliance and CISA found that 51.1% of surveyed U.S. small and mid-sized businesses required MFA across all key accounts. The same report indicates a 27-percentage-point gap between organizations reporting that they have backups and those reporting that they test them. These are self-reported survey findings, not universal rates, and the public report does not provide enough sampling detail to treat them as representative of every SMB. Read the survey summary and view the full report.

Other widely circulated SMB figures need similar care. SensCy’s 2026 assessment report says 88% of successful attacks involve human error, 50% of assessed SMBs never conduct awareness training, and 33% install critical patches within 48 hours. These figures describe SensCy’s assessment dataset, not all SMBs, and the report does not publish enough transparent sampling or calculation detail to establish population-wide estimates. For broader breach research, Verizon’s 2025 Data Breach Investigations Report analyzed 22,052 incidents, including 12,195 confirmed breaches, and reported human involvement in 60% of breaches. The populations and definitions differ, so these figures are not directly interchangeable.

Use the checklist below to find identity gaps in your own environment. Your own account inventory matters more than any headline percentage.


1. MFA COVERS THE OBVIOUS ACCOUNTS, NOT EVERY PATH IN

Why it matters: Your administrators, email, and remote access may require MFA while an older VPN, a separate SSO portal, a cloud console, or a third-party application remains password-only. Attackers need only one usable path. CISA and the NSA recommend a planned MFA approach that covers accounts and applications consistently, with stronger, phishing-resistant methods prioritized for privileged access.

Check and fix:

  • List all sign-in paths, including legacy applications, VPNs, cloud platforms, and vendor portals.
  • Require MFA everywhere it is supported; document any exception, its owner, and a deadline to resolve it.
  • Prioritize phishing-resistant MFA, such as passkeys or security keys, for administrators and other high-risk accounts.
  • Test recovery and MFA re-enrollment. A weak reset process can undermine a strong login control.

CISA’s MFA guidance explains why MFA matters. For broader access management recommendations, see the CISA/NSA Identity and Access Management best practices.

2. SHARED AND GENERIC ACCOUNTS HAVE NO CLEAR OWNER

Why it matters: When several people use one account (such as “frontdesk,” “admin,” or a shared vendor login) it becomes harder to tell who took an action. And if someone leaves, the account may remain usable with a password they already know.

Check and fix:

  • Find shared, generic, default, and local accounts across devices and applications.
  • Replace shared human logins with named accounts wherever possible.
  • Assign a business owner and purpose to every account that must remain shared.
  • Store unavoidable shared credentials in an approved vault, restrict access, and rotate them when staff or vendors change.

CISA and NSA specifically identify shared, default, and former-employee accounts as risks that are harder to manage and monitor. Their guidance recommends disabling unnecessary accounts and tightly controlling the ones that remain.

3. ADMIN PRIVILEGES ARE ALWAYS ON

Why it matters: A compromised everyday account with permanent administrator rights gives an attacker a much larger opportunity to change systems, access sensitive data, or create persistence. Broad privileges also increase the impact of accidental changes.

Check and fix:

  • Review who has domain, cloud, device, and application administrator roles.
  • Remove privileges that are not required for each person’s current duties.
  • Give administrators separate everyday and administrative accounts.
  • Use just-in-time or time-limited elevation where available; log and review elevated sessions.

Start with a small number of trusted administrators and clearly defined emergency access. Keep emergency accounts protected, monitored, and tested, rather than using them for routine work.

4. OFFBOARDING DOESN’T AUTOMATICALLY REMOVE ACCESS

Why it matters: Access often persists because IT hears about a departure late, or a checklist only covers email and laptops. Former staff, contractors, and vendors may still have active sessions, tokens, app access, or remote credentials.

Check and fix:

  • Make HR or the contract owner responsible for notifying IT of departures and role changes.
  • Disable accounts promptly and revoke sessions, tokens, VPN access, keys, and group memberships.
  • Check third-party applications and vendor accounts, not just the central directory.
  • Record completion and have an owner verify that access is removed.

CISA and NSA recommend managing identity through joiner, mover, and leaver events. In this week’s identity series, see Wednesday’s post on orphaned accounts for a closer look at access that remains after a person or business relationship ends.

5. OAUTH CONSENT HAS SPRAWLED BEYOND YOUR OVERSIGHT

Why it matters: Employees may approve third-party applications that request access to email, files, calendars, or contacts. That permission can persist even after an app is no longer needed. A compromised or untrustworthy application may then access data through a legitimate authorization.

Check and fix:

  • Review connected apps and their granted permissions in your identity platform.
  • Restrict user consent or require administrator approval for sensitive permissions.
  • Check the app’s publisher, business purpose, requested access, and owner before approval.
  • Remove unused or unrecognized grants and schedule recurring reviews.

Do not approve an app simply because it appears in a familiar workflow. Grant only the access required for the business purpose, and make sure someone owns the decision.

6. THE HELP DESK CAN RESET ACCOUNTS WITHOUT PROVING IDENTITY

Why it matters: A password reset, MFA replacement, or recovery-detail change can hand an attacker the keys to an otherwise well-protected account. If support staff rely on information available in public or stolen records, a caller may be able to impersonate an employee.

Check and fix:

  • Create a written identity-verification procedure for resets and MFA changes.
  • Verify high-risk requests using a separate, known contact method, not the phone number or email supplied in the request.
  • Require additional approval for privileged users or unusual recovery requests.
  • Log the request, verification steps, and approver; notify the account owner when recovery details change.

Monday’s post on help-desk resets covers this process in more detail. NIST’s Digital Identity Guidelines also explain why account recovery needs appropriate safeguards.

7. DORMANT ACCOUNTS STAY ENABLED AND UNMONITORED

Why it matters: An enabled account that nobody uses may be overlooked in routine reviews. It might belong to a former employee, contractor, vendor, or old service, and an attacker can test it without raising the same attention as a currently active user.

Check and fix:

  • Identify accounts with no recent sign-in activity across directories and important applications.
  • Confirm each account’s owner, business purpose, and need to remain active.
  • Disable accounts that are no longer needed; review exceptions and service accounts separately.
  • Alert on sign-ins to dormant accounts and unexpected changes to MFA, privileges, or recovery details.

Use an inactivity threshold that fits your business and document exceptions; there is no single cutoff that suits every account type. Review the list regularly so the inventory stays current.


A PRACTICAL QUARTERLY IDENTITY CLEANUP

You do not need to fix everything at once. A mid-size organization can make meaningful progress in a quarter by assigning owners and working in stages:

  • Days 1–30: Find the gaps. Inventory identities, sign-in routes, privileged roles, shared accounts, OAuth grants, and inactive users. Prioritize administrator, email, remote-access, and finance accounts.
  • Days 31–60: Close the highest-risk gaps. Extend MFA, remove unnecessary admin rights, replace shared logins where feasible, and define help-desk verification and offboarding procedures.
  • Days 61–90: Make the controls stick. Automate departure notifications where possible, review dormant accounts and app permissions, and test whether access removal and account recovery work as intended.

Track a few clear measures: MFA coverage for key accounts, the number of standing administrator accounts, time to disable access after a departure, and the number of unknown or ownerless app grants. Review them with leadership, not just once, but on a recurring schedule.

None of these fixes inherently requires an enterprise budget. Some advanced capabilities depend on your platform or licensing, but the most important improvements often start with configuration, clear ownership, and consistent process.

Cenova Cyber helps organizations assess and improve security controls through managed cybersecurity services and vCISO leadership. Contact Cenova Cyber for a free risk assessment and identity review to identify your highest-priority gaps and build a practical plan for the quarter.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top