MAITS — Securing what mattersIAM Health Check

Identity, access & cloud security

Specialist depth.
One connected identity system.

MAITS helps New Zealand organisations resolve difficult identity, access and cloud security problems — from strategy and architecture through implementation guidance and assurance.

Discuss your identity environment
Start with the control problem

Technology matters, but only after the trust boundary, access decision and operating responsibility are clear.

Capability map

Follow identity from source to trust decision.

MAITS spans identity, authentication, context, authorisation, provisioning, governance and assurance — with every hand-off designed as part of one control system.

01Identity
02Authentication
03Access
04Governance
05Credentials
06Trust

Identity platform

Modernise directories and Microsoft identity without losing architectural control.

01

Microsoft Entra

Tenant architecture, authentication, Conditional Access, governance, External ID, applications and workload identity.

Explore Microsoft Entra
02

Hybrid identity

Active Directory, Entra Connect, Cloud Sync, source authority, authentication, writeback and Exchange identity dependencies.

Explore Hybrid identity

Access, governance & integration

Make access deliberate throughout its lifecycle.

Cloud & digital trust

Extend governed identity into workloads and organisational relationships.

09

DiligenceID

Issue, hold and verify reusable digital evidence across people, organisations and trust boundaries.

Explore DiligenceID

Technical capability

Architecture depth across the identity estate.

The technology is organised around the control outcome it supports, not presented as an undifferentiated product list.

DIRECTORIES

Identity foundation

Active Directory · Microsoft Entra ID · hybrid directories · tenant and forest architecture

SYNCHRONISATION

Identity flow

Entra Connect · Cloud Sync · attribute mapping · source authority · supported writeback

AUTHENTICATION

Strong establishment

OIDC · SAML · FIDO2 · passkeys · Windows Hello for Business · MFA

PROVISIONING

Application lifecycle

SCIM · Microsoft Graph · REST APIs · custom connectors · reconciliation

ACCESS

Policy & authorisation

Conditional Access · RBAC · ABAC patterns · groups · application roles · claims

GOVERNANCE

Control & evidence

PIM · entitlement management · access reviews · lifecycle workflows · SoD

CUSTOMER IDENTITY

External journeys

External ID · B2B · federation · registration · recovery · B2C migration

DIGITAL TRUST

Portable evidence

DiligenceID · Verified ID integration · credentials · authority · consent

How MAITS engages

Advisory that survives implementation.

The starting point may be a risk, platform, migration or difficult decision. The method keeps the control objective visible from discovery through to operation.

01 / CURRENT STATE

See the whole identity system

Map the people, platforms, applications, dependencies, ownership and material control gaps.

02 / TARGET STATE

Define what good means

Set the intended trust boundaries, access decisions, architecture and governance outcomes.

03 / DELIVERY PATH

Sequence practical change

Prioritise work around risk, dependencies and the organisation’s capacity to implement and operate it.

04 / ASSURANCE

Keep decisions intact

Review design and implementation so that important controls do not disappear between architecture and production.

Engagements can focus on architecture, a specific platform or migration, implementation assurance, or a structured IAM Health Check. Scope is agreed around the organisation’s environment and priorities.

Start a conversation

Find the right starting point.

Bring the identity risk, migration deadline or architecture decision. We’ll help turn it into a practical scope.

Discuss your identity environment Request an IAM Health Check