Compliance Posture

Know where each tenant stands against the Essential Eight

T365 checks the Microsoft 365 configuration it has backed up against Essential Eight and ASD Blueprint rules on a schedule, shows the maturity each tenant has reached beside the target you set, and reports what drifted since the last scan.

Essential Eight postureIllustrative — sample data

What you get

Why teams choose Compliance Posture

01

Know your maturity per tenant

See the Essential Eight level each tenant has reached, strategy by strategy, beside the target you set, with the strategies holding it down named.

02

Spot drift before the audit

Each scan is compared with the last, so a setting that slipped out of baseline appears at the next scheduled scan instead of in an assessment report.

03

Hand your assessor a starting point

Essential Eight findings name their mapped ISM controls and show expected and found values, with reports and exports in PDF, Excel, CSV or JSON.

04

Measure against your own standard

Use the supplied ASD Blueprint baseline, or create baselines typed to the Essential Eight, ISM, PSPF or your own rules.

05

Exceptions that stand up later

Accepted risks and disputes carry a justification, an optional end date and an audit log entry.

06

Your tenant is left as it is

Scans read configuration T365 has already backed up. Where a fix can be described, it is shown as a preview for your administrators to apply.

How it works

From connection to evidence

  1. 1

    Capture

    T365’s configuration backup captures your tenant’s policies and settings on its schedule.

  2. 2

    Set targets

    Choose an Essential Eight target for each tenant and the baselines to measure it against.

  3. 3

    Scan

    Scheduled scans check the captured configuration against every rule, daily by default or on demand.

  4. 4

    Compare

    Each scan is compared with the previous one to show what drifted, what improved and what changed.

  5. 5

    Report

    Download maturity reports and export findings for your security adviser or assessor.

In detail

How Compliance Posture works

Essential Eight maturity, tenant by tenant

Each tenant gets an assessed maturity level for each strategy, shown beside the target you set for that tenant: Maturity Level One, Two or Three, with Two as the starting target. Levels are cumulative, so a strategy reaches Maturity Level Two only when its Level One and Level Two checks pass, and the tenant’s overall level is the lowest of the strategies you have turned on.

The strategies holding the overall level down are named, so the conversation starts with what to fix first. A strategy you turn off for a tenant is left out of the result rather than counted as Maturity Level Zero.

Honest about what Microsoft 365 can show

Office macro settings, administrative privileges, multi-factor authentication and regular backups can be measured from Microsoft 365 configuration, and those strategies get a maturity level.

Application control, patching applications, user application hardening and patching operating systems depend partly on endpoint software and patch state that Microsoft 365 configuration does not hold. T365 still runs the checks it can for those four, and labels them as partial coverage instead of giving them a maturity badge, so the dashboard does not claim more than it measured.

Baselines for the standard you answer to

An ASD Blueprint for Secure Cloud baseline is supplied, with rules built from the Blueprint’s published Microsoft 365 configuration. Each rule records the setting it checks, the value the Blueprint expects and the steps to correct it.

You can also create baselines typed to the Essential Eight, the ISM, the PSPF or your own standard, and add or import the rules your agency holds itself to. Every baseline is scanned and drift-reported the same way.

Drift, scan to scan

Each scan is compared with the previous scan of the same baseline, rule by rule and item by item. T365 records what became non-compliant, what became compliant, and where a checked value changed.

Because drift is measured between scans, it is reported on the schedule the scans run, which is daily by default. A setting that slipped out of baseline shows up at the next scheduled scan rather than at the next audit.

Configuration driftIllustrative — sample data

Property Differences2 differences

PropertyExpectedActual
stateenableddisabled
includeRoles[Global Administrator, Security Administrator][Global Administrator]

Exceptions with a reason and an end date

Not every failed check is a defect. A finding can be marked as an accepted risk, disputed, or self-attested as met, each with a written justification. An exception is either enduring or temporary, and a temporary one must carry an expiry date, after which it is shown as expired.

You choose whether an exception counts toward the maturity score, and every exception is written to the audit log, so the reasoning behind a reported level can be checked later.

Evidence your assessor can start from

Essential Eight checks name the ISM controls they are mapped to, and each finding shows the value T365 expected beside the value it found. Maturity reports download as an executive PDF, a detailed PDF or an Excel workbook, scan findings export as CSV or JSON, and assessment history is kept so you can show the trend over time.

T365 does not change your tenant to fix a finding. Where a fix can be described, a remediation preview shows the setting and the value to set it to; your administrators make the change in the Microsoft admin portal, and the next scan records the result.

Who it is for

Built for the people accountable for it

CISOs and IT security advisers

See Essential Eight maturity per tenant against target, and which strategies hold the overall level down.

Microsoft 365 administrators

Find which setting failed, the value expected, and the steps to correct it in the admin portal.

Security assessors

Start from ISM-mapped findings, maturity reports and assessment history instead of a blank spreadsheet.

Managed service providers

Set a target and baselines for each customer tenant and report on each one separately.

Frameworks

The frameworks it helps you evidence

Australian Signals Directorate

Essential Eight

T365 checks Microsoft 365 configuration against Essential Eight rules at Maturity Levels One to Three and reports an assessed level per strategy against your target. The four strategies that depend on endpoint and patch data are shown as partial coverage.

Read the source (opens Australian Signals Directorate in a new tab)

Australian Signals Directorate

Blueprint for Secure Cloud

A Blueprint baseline is supplied, with rules built from the Blueprint’s published Microsoft 365 configuration. Your tenant is scanned against it and drift is reported between scans.

Read the source (opens Australian Signals Directorate in a new tab)

Australian Signals Directorate

Information Security Manual (ISM)

Essential Eight checks name the ISM controls they map to, so a finding points your assessor to the relevant controls. You can also type your own baselines to the ISM.

Read the source (opens Australian Signals Directorate in a new tab)

Attorney-General’s Department

Protective Security Policy Framework (PSPF)

You can type a baseline to the PSPF and add the rules your agency applies to its Microsoft 365 settings; T365 measures them and reports drift. T365 does not supply PSPF rules of its own.

Read the source (opens Attorney-General’s Department in a new tab)

T365 measures, maps and records evidence against these frameworks. Your organisation remains responsible for its own assessment and authorisation decisions.

Questions

What buyers ask us

Which Essential Eight maturity levels does T365 measure?

Maturity Levels One, Two and Three. You set a target per tenant, with Two as the starting target. A strategy reaches a level only when the checks for that level and every level below it pass, and the overall level is the lowest of the strategies you have turned on.

Can it measure all eight strategies from Microsoft 365?

Not fully. Office macro settings, administrative privileges, multi-factor authentication and regular backups are measured from Microsoft 365 configuration. Application control, patching applications, user application hardening and patching operating systems depend partly on endpoint and patch data, so T365 runs the checks it can and labels those strategies as partial coverage.

Does it change my tenant?

No. Scans read the configuration T365 has already backed up. Where a fix can be described, a remediation preview shows the setting and the value to set it to, and your administrators make the change in the Microsoft admin portal. Automatic remediation is not available.

How often does it scan?

Essential Eight assessments run daily by default for each tenant, and you can run one on demand. ASD Blueprint scans run up to once a day by default, after a new configuration backup has completed. Drift is reported scan to scan, not between scans.

Does it use AI?

No. Maturity levels, findings and drift come from rule checks against your captured configuration, not from a language model.

What happens when we accept a risk?

The finding is marked with your justification and, for a temporary exception, an expiry date. You choose whether it counts toward the score, and the decision is written to the audit log.

Evidence: where each claim on this page comes from
  • Cumulative maturity per strategy; overall level is the lowest enabled strategy; partial-coverage strategies

    apps/web/src/lib/compliance/e8-maturity-calculator.ts

  • Target maturity per tenant (ML1 to ML3, ML2 by default) and strategies that can be turned off

    packages/db/src/schema/e8-tenant-config.ts

  • Partial-coverage strategies shown without a maturity badge

    apps/web/src/components/compliance/E8StrategyCard.tsx

  • Essential Eight checks carry mapped ISM control ids

    apps/web/src/lib/compliance/e8-rules-seed.ts

  • Supplied ASD Blueprint baseline built from the published Microsoft 365 configuration

    packages/db/drizzle/0004_seed_asd_blueprint.sql

  • Baselines typed to ASD Blueprint, Essential Eight, ISM, PSPF or custom

    packages/db/src/schema/compliance-baselines.ts

  • Custom rules can be added or imported into a baseline

    apps/web/app/api/compliance/baselines/[id]/rules/import/route.ts

  • Drift found by comparing each scan with the previous one

    packages/compliance/src/drift.ts

  • Blueprint scans scheduled after a new backup, daily by default

    services/scheduler/src/jobs/compliance-scans.ts

  • Essential Eight assessments daily by default

    apps/web/app/api/compliance/essential-eight/[tenantId]/config/route.ts

  • Exceptions with justification, expiry, scoring choice and audit log entry

    apps/web/app/api/compliance/essential-eight/[tenantId]/overrides/route.ts

  • Maturity reports as executive PDF, detailed PDF or Excel

    apps/web/app/api/compliance/essential-eight/[tenantId]/report/route.ts

  • Findings export as CSV or JSON

    apps/web/src/lib/compliance/findings-export.ts

  • Remediation is preview-only; T365 does not write the fix to the tenant

    apps/web/app/api/compliance/remediate/route.ts

Buying for government? We are on the DTA Digital Marketplace.

  • Software
  • Cloud
  • Professional services
  • Labour hire
  • Hardware
How to buy

Ready to Secure Your Microsoft 365?

Start your free 14-day trial or talk to our team about your needs.