An account may be compromised
Unfamiliar sign-ins, unexpected authentication activity or an account behaving differently.
Expert help when something is wrong
Suspect a compromised account or business email compromise?
Get help understanding what happened and taking the next steps. Our engineers investigate available evidence, assess potential impact and carry out agreed containment and recovery actions.
Incident enquiries: European and US business hours.

Recognise the situation?
A suspected incident can leave your team unsure what to trust or where to start. Tell us what you have noticed; we will help define the investigation and response scope.
Unfamiliar sign-ins, unexpected authentication activity or an account behaving differently.
A changed payment instruction, a customer reporting fraud or messages sent without the user's knowledge.
Unexpected mailbox forwarding, inbox rules, delegation or application access.
Unusual downloads, external sharing or concerns about exposure in SharePoint and OneDrive.
A clear response, with you in control
Discuss the suspected incident, affected accounts and immediate business concerns. Agree the scope, access and authorised actions.
Review available evidence and assess impact. Where needed, an engineer carries out agreed containment alongside the investigation, rather than waiting for a final report.
Support agreed recovery actions, document findings and explain remaining risks. Give your team prioritised recommendations for the next steps.
The response depends on your environment and the evidence available. Missing logs are recorded as visibility gaps, not treated as proof that no incident occurred.
What your team takes away
Expert-reviewed findings from the private Cleverina Microsoft 365 Security Investigation platform.
An executive summary of findings, affected scope, confidence and important limitations.
A technical investigation report with source-linked findings, a timeline and relevant indicators.
A record of agreed response actions, remaining risks and prioritised recommendations.
Investigation coverage
We agree relevant sources before collection and explain what each source can — and cannot — establish.
Collection focuses on metadata, configuration and audit activity. Collectors do not read email bodies or attachments, or download document contents.
Review available Microsoft Entra sign-in records, authentication details, IP addresses, devices and risk signals. Additional non-interactive user, service principal and managed identity streams depend on supported Microsoft beta APIs and approved access.
Examine forwarding, inbox rules (including hidden rules where available), delegation and available audit events. Message-trace metadata can help establish the sequence of communications. Collectors do not read email bodies or attachments.
Review available application and service principal information, consent grants and permissions. Findings help an engineer assess suspicious or excessive access; a permission alone does not establish malicious use.
Review available access, download, change, deletion and sharing events, including guest and Anyone-link activity. Correlate eligible events with earlier risky sign-ins. Permission snapshots cover selected files or folders, not a complete tenant-wide effective-access audit. Collectors do not download document contents.
Bring available Entra ID Protection signals, Microsoft Defender alerts and incidents, Secure Score, organisation details and licence information into the case. Availability depends on licensing, provisioning, permissions and retained data.
Organise source-linked findings, relevant indicators, timestamps and the analyst's decisions. Distinguish current settings, historical events, investigation leads and confirmed conclusions. Evidence hashing supports integrity checks; it does not constitute immutable storage or a legal certification.
Start a conversation
You do not need to prepare a technical report. A short description of the concern is enough to start the discussion.
European and US business hours
contact@cleverina.comBefore we begin
Our engineers can perform separately agreed containment and recovery actions. We confirm scope, permissions and approval before making changes. The investigation platform collects and analyses evidence; it does not autonomously remediate your environment.
We define the Microsoft permissions and operator roles needed for the agreed sources. Consent alone does not provide every log or historical record: licensing, service configuration and retention also affect coverage. Collection is read-oriented; Purview collection may create audit search jobs.
This is an engineer-led service supported by the private Cleverina Microsoft 365 Security Investigation platform. Its current analysis uses deterministic rules, with specialist review. Customer evidence is not sent to external AI inference services by the platform.
We handle incident enquiries during European and US business hours. Availability, scope, fees and next steps are confirmed directly. Submitting a request does not confirm that response work has started. Delivery time depends on the evidence available and the investigation required.