Cloud Based Identity Management Services: How to Enforce MFA
A practical rollout for Dallas-Fort Worth firms with 10 to 50 users: inventory accounts, retire shared logins, enforce MFA, cut admin rights and keep emergency access that works.
Cloud based identity management services decide who can reach your applications and what they can do once inside. For a Dallas-Fort Worth firm with 10 to 50 users, the rollout starts with individual accounts, enforced multi-factor authentication and fewer admin privileges, not another software purchase.
If your insurer wants proof of MFA while staff still share a VPN password, fix the shared access first. Then test access policies before enforcing them. A policy that locks out every administrator creates another recovery problem.
First, list every account that can sign in
Build the inventory before changing settings. Record each account, who owns it and the systems it can access. Include local accounts on laptops, not just the names in your cloud directory.
- Export users from your identity system and local accounts from company computers. Combine them into one inventory.
- Mark accounts with cloud or local admin rights. Confirm that each holder still needs that access.
- Identify shared credentials, including the VPN password and any “front desk” login.
- Check applications with separate sign-ins, such as payroll. Your central directory may not show them.
Date the inventory. Disable forgotten accounts after checking ownership and preserving any records the organization needs.
Remove shared logins before you enforce anything else
Replace the shared VPN password with an account for each person. MFA on a shared login does not establish which person used it. Changing its password does not solve that accountability problem.
- Create individual accounts with only the access each person needs. Do not copy excessive permissions from the shared account.
- Move staff in groups and confirm that their individual sign-ins work.
- Disable the shared login after the cutover. Record the retirement date.
- Revoke former employees’ access, including active sessions where the platform supports it.
Check service accounts separately. A scanner or application may need a nonhuman identity, but that is not a reason to let staff keep using shared credentials.
Turn on MFA for every account, the owner included
Require multi-factor authentication for every person who signs in, including the owner and office-only staff. Document emergency access separately. An undocumented exception is an access path you cannot defend during a review.
- Start with administrators, then extend enforcement to all staff.
- Use an authenticator app with number matching as a practical default. Use phishing-resistant hardware security keys for privileged accounts where supported.
- Register a backup method so a lost phone does not become an improvised security exception.
- Review enrollment and enforcement separately. Registering a method does not prove that every sign-in requires it.
Some applications and machine accounts cannot use interactive MFA. Identify them explicitly and apply supported controls rather than reporting blanket coverage you do not have.
Choosing methods people can use on a bad day
Number matching makes an accidental approval harder than a bare “approve” button. It does not make a push prompt phishing-resistant. Tell staff to reject and report prompts they did not initiate.
Text codes are a fallback, not the preferred control. They depend on cellular service and are vulnerable to interception. Hardware keys avoid that dependency, but staff still need a tested recovery method if a key is lost.
What MFA does not finish
MFA reduces the risk from a stolen password. It does not stop every attack or remove an attacker’s existing session. Access control must also limit what an authenticated account can reach.
How do you cut admin rights without breaking software?
Find the applications that need elevated permissions before removing local admin rights. Test them on one computer first. Rushing this step can interrupt work without fixing the underlying permissions problem.
- Run each business application as a standard user and record failures or elevation prompts.
- Determine whether the fix is a supported installation change or a controlled elevation method. Do not grant broad admin rights to fix one application.
- Test normal work and the application’s update process.
- Remove unnecessary admin rights in groups, with a documented rollback procedure.
Find the apps that need elevation first
Daily email does not require local admin rights. Older business software may write to protected folders or run an updater that requests elevation. Ask the software vendor for a supported standard-user configuration before changing folder permissions.
For an architecture firm running Revit, test the actual application workflow, including required add-ins. Opening the program once is not a complete test.
Give admins a separate account
Keep daily email accounts separate from privileged accounts. Administrators should use elevation only for work that requires it. This limits the privileges available to malicious code running under the daily account; it does not make that computer immune to compromise.
What a conditional access baseline looks like
Conditional access evaluates a sign-in against rules, such as whether the device is managed. Where your platform supports these controls, start with a baseline you can test and enforce.
- Require MFA for all users, with separately controlled emergency access.
- Block legacy authentication that cannot enforce MFA.
- Require managed devices for privileged access.
- Flag unexpected sign-ins for investigation.
Location alone is weak evidence. Hotel Wi-Fi and mobile networks can produce unfamiliar locations. Review the account and device context before treating a location alert as proof of an attack.
Staff working outside Texas sit under the same policy
A remote employee does not need weaker authentication because they work outside Texas. Apply the same baseline to your Fort Worth office and out-of-state staff. Test remote access before enforcement so travel does not become the excuse for a permanent bypass.
Why a travel exception becomes a permanent hole
An exception without an expiry date is permanent until someone remembers it. Record who approved it and when it must end. Remove the exception when the trip ends, rather than waiting for the next insurance questionnaire.
Keep a way back in that no policy can lock out
Maintain at least two emergency, or break-glass, admin accounts. Configure them according to your identity platform’s recovery guidance so a faulty access policy cannot block every administrator. Emergency access is not an excuse for weak authentication.
- Create dedicated emergency accounts that do not depend on an employee’s daily mailbox.
- Exclude them from policies that could cause a complete administrative lockout, following the platform’s guidance.
- Protect their credentials offline, with access restricted to authorized people.
- Test access on a documented schedule and investigate any use outside a planned test.
North Texas storms and winter ice can interrupt power or connectivity. An emergency account cannot restore an internet connection. Recovery instructions must identify how authorized staff will reach the identity platform during an office outage.
How do you avoid lockouts during rollout?
Use report-only mode, where available, for one to two weeks before enforcement. Read which legitimate sign-ins would fail. Then pilot with two or three staff members whose work includes remote access or other likely trouble spots.
- Review report-only results daily, including failed sign-ins.
- Resolve unexpected blocks without excluding an entire department.
- Confirm the pilot covers normal work, not just a successful login.
- Expand to one department, then the rest of the firm. Make changes on a weekday morning.
- Stop and investigate any unexplained administrator sign-in before adding more policies.
For Thanksgiving and year-end closures in 2026, finish changes early enough to observe normal work before staff leave. Otherwise, schedule enforcement for January. Record escalation contacts and recovery steps before the closure, not after someone loses access.
Preserve relevant sign-in logs before changing a suspicious account’s settings. Tightening policies is not a substitute for investigating possible compromise.
What evidence should you keep for the insurer?
Keep dated exports showing actual enforcement, not just purchased licenses or enrolled users. Your policy and insurer’s questions determine the evidence required. Capture the starting position and the final configuration, with records of material changes between them.
- Active accounts and whether MFA is enforced for each one, with last-sign-in records where the platform keeps them.
- Cloud and local administrators, with approval for their access.
- Conditional access settings and their exclusions.
- Emergency-access test results and shared-login retirement dates.
Our identity and access control work includes enforced MFA, administrative privilege reduction and conditional access baselines within security-controlled IT operations. For your DFW organization’s next step, bring the account inventory and current exclusions to a 30-minute security discussion.
Frequently asked questions
Will MFA slow down everyone's daily logins?
MFA adds a verification step when your sign-in policy requires it, not necessarily every time someone opens an application. The frequency depends on session settings and risk controls. Test those settings with staff before enforcement rather than weakening MFA to suppress prompts.
Can we keep the shared VPN password while we roll out MFA?
Keep it only for a controlled cutover while individual accounts are tested, then disable it. MFA does not make a shared login attributable to one person. Do not claim individual MFA coverage while that shared access remains available.
Do staff working outside Texas need a different policy?
Apply the same security baseline to remote and office staff. Test legitimate remote sign-ins before enforcing location restrictions. Any necessary exception should have an approver and an expiry date.
How many break-glass accounts do we need, and where do their passwords go?
Maintain at least two dedicated emergency administrator accounts so one failure does not remove your recovery path. Protect their credentials offline and configure authentication according to your platform’s emergency-access guidance. Test them on a documented schedule and investigate unplanned use.
What does an insurer usually want to see?
Expect questions about who can sign in and whether MFA is enforced. Keep dated exports and policy settings, including exclusions, to support your answers. Check the insurer’s actual requirements rather than assuming a standard evidence package satisfies every policy.
Total 360 Technology provides security-controlled IT operations and cybersecurity for businesses in the Dallas-Fort Worth area with 10 to 50 users. We focus on enforced safeguards, proactive risk management, and 24x7 managed detection and response rather than traditional reactive IT support.
Serving Dallas, Fort Worth, Napa, Sonoma.
More from the blog
6 min read
Small Business Cyber Security Checklist: 10 Controls to Test
A cyber security checklist should prove that controls work, not just that they exist. This one covers ten checks a 10-to-50-user office can run before a holiday closure.
Read article7 min read
Cyber Security Tech Companies in Dallas: Which Type Fits You
Product vendors, managed service providers and operations partners are different buys with different duties. This guide shows what each leaves on your desk and what to check before you sign.
Read article10 min read
Data Breach 2026: How Long Intruders Stay Undetected
The 2026 breach cases that matter to a 10-to-50-user firm turn on how long intruders stay undetected, with two questions to ask your IT provider this month.
Read article