Passkeys, FIDO2 and MFA
Select phishing-resistant and other authentication methods for user, device and assurance needs.
Identity security
Protect every route
into the account.
MAITS connects authentication strength, device assurance, risk, session controls, recovery and privileged access into a usable security architecture.
The weakest path matters
A strong primary method is undermined when registration, recovery, emergency access or support processes establish identity with less assurance.
Capability
Design authentication and access policy as one system.
Controls are organised around people, resources, assurance and risk instead of accumulated platform settings.
Conditional Access
Map authentication strength, device state, application sensitivity, location and risk to clear grant and session controls.
Device assurance
Define when managed, compliant or strongly bound devices are required and how exceptions are governed.
Risk-based access
Use supported identity and sign-in risk signals with clear investigation, remediation and false-positive handling.
Registration and recovery
Protect bootstrap, lost-device, help-desk and self-service recovery so trust is re-established deliberately.
Privileged authentication
Apply separate identities, phishing-resistant methods, protected workstations and emergency access to high-value administration.
Engagement outcomes
Make the next decision and delivery step clearer.
Method strategy
Populations and use cases have suitable authentication methods.
Coherent access policy
Conditional Access expresses control intent with fewer unmanaged exceptions.
Resilient journeys
Registration and recovery retain proportionate assurance.
Operational readiness
Monitoring, support and emergency procedures are owned and tested.
Expected outputs
Useful artefacts for the people who must act.
Outputs are agreed for the engagement scope and written for the leaders, architects, engineers, operators and assurance teams who will use them.
Authentication strategyConditional Access designMethod rollout planRecovery designPrivileged authentication modelTest plan
From advice through implementation
Enter at the stage where support is needed.
MAITS can provide one bounded stage or remain involved across design, delivery, validation and capability transfer.
Understand the decision
Clarify the people, systems, obligations, constraints, ownership and outcome involved.
Establish current state
Review evidence, architecture, controls, risk, capability and delivery readiness.
Define the target
Set principles, architecture, policy, operating ownership and a practical change sequence.
Implement the change
Configure, integrate, automate, migrate and roll out alongside accountable teams.
Test the outcome
Review behaviour, evidence, exceptions, recovery, readiness and residual risk.
Transfer capability
Embed knowledge, governance, runbooks, measures and an owned improvement path.
Related capability
Continue with the service that matches the next decision.
Start a conversation
Start with the requirement, risk or decision.
Tell us what needs senior attention and what outcome the organisation needs. We’ll agree an engagement shape around the work.