The break-in that needs no malware.
An attacker with a password never touches a laptop, so the endpoint agent never sees them. Secuno reads every client's Microsoft 365 and Entra ID tenant, watches who signs in from where, and tells you what changed since the last scan.
- AGENTLESS
- READ-ONLY BY DEFAULT
- SIGN-IN SIGNALS EVERY 2 MINUTES
- 08:52Amsterdam, NLThe laptop agrees
- 13:07Utrecht, NLThe laptop agrees
- 03:12Lagos, NGHIGHThe laptop was in Amsterdam nine minutes earlier
A sign-in the user's own laptop contradicts opens a case.
Four detections Secuno raises itself.
Microsoft's own sign-in risk needs Entra ID P2, which Business Premium does not include. Three of these four run without it, on Secuno's own signal poll every two minutes.
How each detection worksThe laptop contradicts the sign-in
A successful sign-in against where the user's own device demonstrably was within fifteen minutes. When the laptop agrees, impossible travel is downgraded instead.
HIGHNot neededA country nobody signs in from
A baseline learned per tenant and per person over fourteen days, with no country list to fill in.
HIGH for the tenant, MEDIUM for the personNot neededA success after failed passwords
Password spray or targeted guessing followed by a sign-in that works. Two narrow rules, so a phone holding last month's password does not fire.
HIGH, CRITICAL if the account itself failed firstNot neededMicrosoft changes its verdict
A risk detection dismissed in Entra resolves its finding here. An account moved to confirmed compromised opens a case within one poll.
Opens a caseNeededThirty-three controls, and an answer for every one.
Every full scan marks 33 controls in eight sections as pass, fail, unknown or not applicable, each with its CIS Microsoft 365 Foundations and CISA SCuBA reference. A clean tenant leaves evidence too.
- 25 pass
- 4 fail
- 3 unknown
- 1 not applicable
Unknown is never a pass
A control whose data could not be read is unknown and names the dataset. A permissions gap that looks like a clean tenant is worse than no answer.
What changed since the last scan
Every scan is compared with the one before it, so you hear about drift in privileged accounts and Conditional Access, not only about what is wrong today.
A number with a frame
Secure Score is set against the industry average and tenants of a similar size, with recommendations ranked by the points still on the table.

Act on the account, from inside the case.
Read-only is the default. A tenant can opt in to account actions. From then on they sit inside the investigation about that account, and an automation rule can run them.
What did they do once they were in?
- The account's inbox rules
- Directory changes: an MFA method added, a consent granted, a role added
- 24 hours of sign-ins
A high rating raises the case to critical. It takes seconds and asks for no access to read mail.
Three actions, one tap each.
- Revoke every session
- Disable the account
- Enable it again
By a person in the case, or by an automation rule that waits for approval.
- OPT-IN
Per tenant, and only on the customer's own app registration, which the customer can remove without asking Secuno.
- REFUSED
Disabling the last Global Administrator, and any case that groups alerts about more than one account.
- RECORDED
Switching it on or off, and every action taken, is written to the audit log.
From mail to sign-ins, graded.
Eight of the finding types. Each can open a risk on its own, with an owner and a due date, and a rescan updates it in place instead of opening a second copy.
Every finding type, and why it is graded that way- Mailbox forwarding to an outside address
- Mail-flow rule copying mail outside the tenant
- Administrator without MFA
- Legacy authentication enabled
- User without MFA
- Mailbox audit logging disabled
- Delegated access to a user mailbox
- Declared break-glass account without a privileged role
The Exchange Online checks behind the mail findings are opt-in per tenant and off by default.
What connecting a tenant involves.
- Does Secuno need write access to my client's tenant?
- Not for monitoring. Posture, controls and sign-in detection use read-only Graph permissions, and nothing is installed in the tenant. The only writes Secuno can make are the account actions described above, each behind a permission the customer grants, and only on a tenant that has opted in through its own app registration. Recommendations still open the relevant Microsoft admin screen rather than claiming to apply a configuration fix.
- Do my client's tenants need Entra ID P2?
- Not for most of this. Three of Secuno's four sign-in detections run without it, and so do most posture checks, which matters because Business Premium includes P1 and not P2. Microsoft's own risky users and risk detections are a P2 dataset, and on a tenant without it that is recorded as a plan limit, not shown as a warning the customer cannot fix.
- Will impossible travel fire every time someone uses a VPN?
- Sign-ins whose location cannot be resolved, or resolves too coarsely, are skipped rather than guessed at. That is the specific case a naive distance check gets wrong, since VPN egress often resolves to a datacentre with no meaningful country attached.
- How is Managed ITDR priced?
- €2.30 per licensed identity per month, excluding VAT, for everything on this page. A licensed identity is an account in the tenant with a Microsoft 365 licence assigned; accounts without a licence are not counted. It is a module on top of the Standard platform. MSPs and MSSPs get partner pricing on request.
Every tenant read. Every sign‑in accounted for.
We will connect a tenant like your clients' and show what Secuno reads, what it raises, and what it would have done at 03:12.