Colour theme
Book a consultation

Reviewing protection for business logins

Find gaps in business account protection, check privileged access and sign-in coverage, and make sure someone can investigate suspicious activity.

An illustration of a masked figure on a phone screen holding up a website login form.

Business accounts extend beyond email. Your domain registrar, accounting service, remote support tools and customer systems may have independent sign-ins, recovery methods and administrators.

A protection review should find out which accounts exist, which controls apply and who responds when something looks wrong. Use the MFA-method guide to choose stronger authentication. This review checks whether the protection reaches the accounts your business relies on.

Find the sign-ins outside your central system

List important services and their owners. Record how people sign in, who can administer them, the enforced authentication requirement and the recovery route. Include supplier-managed accounts, emergency access and accounts used by integrations.

For each service connected to central single sign-on, check whether a separate local password or recovery link can still bypass that route. Keep necessary exceptions documented with an owner and a review date. Single sign-on centralizes access, but other ways into an application can stay open.

Check dormant users, former staff and shared accounts against the business owner. Follow the cloud-access audit for old access that may have been missed.

Close password and authentication gaps

Use a unique password for each service that still needs one. The business’s password manager can help staff generate, store and retrieve them. Protect its own sign-in and practise recovery. The Cyber Centre’s password-manager guidance covers those safeguards.

Require the supported stronger authentication for the service, and test the requirement. Registering an authenticator doesn’t mean every account or application requires it. Ordinary typed codes and push approvals can still be phished.

The Cyber Centre’s phishing-resistant MFA guidance recommends methods that resist phishing relays. Confirm service and device support, exceptions and recovery before changing enforcement. A biometric unlock on the device doesn’t make the rest of a remote application’s sign-in phishing-resistant.

Reduce the reach of administrator accounts

Give administrators separate accounts for privileged work and ordinary email or browsing. Review permanent administrative roles, supplier access and the accounts that can reset other people’s credentials.

Grant only the access needed. Where the platform supports it, evaluate temporary elevation with approval and an expiry. Test that access ends as intended. Keep a controlled recovery route so a failed policy or lost credential doesn’t lock the business out.

The Cyber Centre’s administrative-privilege guidance explains account separation and limiting privileges. Don’t assume a role-management feature is available or licensed in every product.

Make suspicious activity someone’s responsibility

Decide who receives sign-in alerts, when they review them and whom they can contact for investigation. Check that someone can still be reached during holidays and outside normal working hours, within the support arrangements you have.

Microsoft Entra sign-in logs distinguish interactive users, non-interactive users, service principals and managed identities. Review the categories relevant to your systems. A dashboard for staff sign-ins doesn’t cover every integration, and Entra logs don’t cover independent third-party logins.

Look into an unfamiliar location or time, but don’t assume the account is compromised. Network routing, VPN use and legitimate background activity can affect the evidence. Confirm logging retention, permissions and alert capabilities for the products you’re using.

Use a safe test to check alert delivery and the handoff. Avoid collecting unnecessary personal browsing information during an account-security review.

Practise containment and recovery

Write down how to reach the administrator through an independent channel, restrict a suspected account and preserve relevant logs. Test the procedure using a designated test account.

Containment may require resetting credentials, revoking sessions, checking new authentication methods, reviewing app permissions and investigating the device. A password change alone may leave other access working. The email-recovery guide and browser-session guide explain those separate checks.

Finish the review with named owners for each gap and a date to verify the fix. Talk to us if you need help checking account coverage, administrative access and alert handoffs.


Featured Image Credit