Your stack is the evidence.
Connect Microsoft 365, Google Workspace, AWS, GitHub, Okta and thirteen more - read-only, in minutes. Assura sweeps your live environment every day and turns each passing check into verified evidence inside your assessments, so your posture is proven, not promised.
A short call about your organisation, then a full demo if it fits - no obligation.
Eighteen connectors. One picture of your posture.
Identity, cloud, code, devices, people and network - each connector adds read-only checks that sharpen the same score.
More on the way - request any connector from inside the app and we build to demand.
From first connection to verified evidence.
Connect read-only
Approve an OAuth consent or paste a scoped, read-only credential. Assura stores it encrypted, never gets write access, and you can revoke it from the provider at any time.
Checks sweep daily
Checks run the moment you connect, again whenever you ask, and automatically every day: MFA, admin counts, branch protection, endpoint coverage, public exposure and more.
Evidence lands in scores
Each passing check becomes verified evidence against the controls it proves. Live checks carry more weight than documents, and documents more than self-attestation.
Drift raises its hand
When a check flips from pass to fail you get a Slack or Teams alert, a task in the Action Centre, and the nightly agent chases it into your morning briefing.
Read-only by design.
A monitoring connector is only worth having if it cannot make anything worse. Every Assura connector authenticates with the minimum scopes needed to read your environment - and nothing that could ever change it.
- Scoped tokens with read-only permissions, checked at connect time
- Credentials encrypted at rest, never shown again once saved
- Revoke from the provider at any time - Assura degrades gracefully
- No agent to install, nothing running inside your network
Checks become evidence, not chores.
Screenshots age the moment you take them. Assura's checks land directly in your assessments as verified evidence: when a control is scored, a live pass from your own environment counts for more than any document - and every score shows exactly what backed it.
- Passing checks attach to the controls they prove, automatically
- Confidence-ranked: live check, then document, then self-attested
- Provenance on every score, so nothing is taken on faith
- One connection strengthens every framework it maps to
Drift gets caught - then chased.
Passing once is easy; staying passed is the job. Assura alerts on the transition - the moment a check that was green goes red - so your channel only speaks when something actually changed, and every wobble leaves a trace in the check's history.
- Slack and Teams posture alerts, only on failure transitions
- Check history on every connector, so you can see the wobble
- The nightly agent opens remediation tasks and writes your morning briefing
- Connectors that go quiet for 48 hours show amber, never a stale green
What the checks actually look at.
Every connector brings its own read-only checks. Together they cover the questions an auditor, an insurer or a buyer will ask first.
- MFA coverage across every user
- Admin counts and privilege separation
- Legacy sign-in protocols blocked
- Root and privileged account MFA
- Publicly exposed storage and services
- Audit logging switched on, and kept on
- Branch protection on default branches
- Organisation-wide two-factor enforcement
- Open vulnerabilities by severity
- Disk encryption and screen lock
- OS and patch currency across the fleet
- EDR sensor coverage, device by device
- Staff roster synced straight from HR
- Leavers offboarded automatically
- Background screening status
- Device authorisation on your network
- On-call cover for incident response
- Monitoring and alert hygiene
Asked and answered.
Is the access really read-only?
Yes. Every connector authenticates with the minimum read scopes the checks need - never write access. Credentials are stored encrypted, and you can revoke them from the provider's own console at any time; Assura simply marks the connector as disconnected.
How often do the checks run?
On connect, on demand whenever you press run, and automatically every day. The nightly agent then reviews the results, opens tasks for anything that regressed, and summarises it all in your morning briefing.
What happens when a check fails?
You get a Slack or Teams alert the moment a previously passing check fails - not a daily repeat of everything that is already red. A remediation task lands in the Action Centre, the score's provenance updates, and the check's history keeps the record.
Do I need to connect everything?
No. Start with your identity suite - Microsoft 365 or Google Workspace - and you'll have a live posture in seconds. Each additional connector widens the coverage and strengthens the evidence behind your scores, but every one is optional.
Does this replace the assessment?
It feeds it. The checks verify what can be observed from your stack; the assessment covers the rest - policies, process, governance. Where a check proves a control, your answer arrives pre-supported by live evidence.