EXEMPLE : entreprise et chiffres inventés. Ce document montre la forme exacte du rapport livré, ce n’est pas un audit réel.
Les 5 lectures du même audit : Pour le dirigeant · Pour le RSSI · Pour l'informaticien · Pour le DPO / la conformité · Pour l'assureur / le donneur d'ordre
SYAGA Audit
Third-party attestation report
Without seeing your data · Ref. SYAGA-DEMO-QUESTIONNAIRE-0001
Microsoft 365 posture findingDated and verifiable document
Entity audited
Entreprise Démonstration (exemple, non client) (tenant d3m0a1b2-c3d4-4e5f-8a9b-0c1d2e3f4a5b)
Audit date
17 juillet 2026
Issuer
SYAGA CONSULTING · SIREN 518 489 471
Verifiable in
your own Microsoft audit logs · syaga.eu
The verdict, before the evidence file

Four structural weaknesses expose your insurability for Microsoft 365.

Your 85 gaps are not 85 problems: they come down to four root causes. Address them in order and you neutralize the bulk of the risk with focused effort, without redoing everything.

Insurability posture
70/100
To be strengthened
sound foundations, but some flaws remain open

One proof, three readers. This file is designed to be presented to a cyber insurer (underwriting format), to a principal contractor requiring proof of your posture (supply chain trickle-down, NIS2 Art. 21 - shareable version), and to a statutory auditor or external auditor. Every finding below is verifiable in your own Microsoft logs: enforceable, not declarative.

195
Compliant controls
4
Root causes weighing on insurability
85
Non-conformities found to date
What is provable today

195 compliant control(s) out of 280 assessed controls - the verifiable baseline that can already be presented to an insurer, point by point, with supporting evidence. Posture rated C, without flattery, based solely on assessed items.

What exposes your file

85 non-conformity(ies) found and 63 unmeasured control(s) remain an exposure not covered by enforceable proof: as long as the root causes below are not addressed, this exposure cannot be attested.

I

Configuration hardening

34 grouped gap(s) - Configuration & compliance
The exposure: an unhardened baseline silently widens the attack surface, with no visible alert.
Today: On this theme, the following compliance requirements are not met: S'assurer que les comptes prioritaires bénéficient des paramètres prédéfinis de protection stricte (Strict protection) ; S'assurer que la synchronisation OneDrive est restreinte pour les appareils non gérés ; Seuls les utilisateurs ayant le rôle Présentateur sont autorisés à présenter dans les réunions Teams ; Les comptes d'accès d'urgence (break-glass) ne doivent pas être bloqués.
What the audit found: Sensibiliser les utilisateurs aux bonnes pratiques élémentaires (hameçonnage, gestion des mots de passe, MFA, signalement) par des campagnes récurrentes et des simulations ; mesure principalement organisationnelle. Appliquer le preset de protection Strict aux comptes prioritaires pour leur garantir le niveau de filtrage le plus élevé. Bloquer la synchronisation OneDrive depuis les appareils non gérés via une politique d'accès conditionnel (AllowLimitedAccess) limitant l'accès au web sans téléchargement/synchronisation.
Effort MediumImpact Moderate
II

Identity and access

31 grouped gap(s) - Identity & access
The exposure: account takeover is the most common entry point for an attack; it is the only theme where a limited effort closes an entire class of risks at once.
Today: On this theme, the following compliance requirements are not met: S'assurer que l'authentification multifacteur est activée pour tous les utilisateurs ; La MFA DOIT être imposée pour tous les utilisateurs ; S'assurer que le flux de consentement administrateur est activé ; S'assurer que tous les utilisateurs membres sont 'compatibles MFA' (MFA capable).
What the audit found: Le MFA doit être exigé pour l'ensemble des utilisateurs via une politique d'accès conditionnel afin de bloquer la grande majorité des attaques par compromission d'identité. Activer le flux de consentement administrateur dans Entra ID pour qu'une demande d'accès bloquée côté utilisateur soit routée vers un réviseur plutôt que simplement rejetée sans suite. Au moins deux comptes d'accès d'urgence (break-glass) cloud-only en *.onmicrosoft.com, exclus des politiques CA bloquantes, doivent être définis pour éviter un verrouillage total de l'administration.
Effort LowImpact Major
III

Monitoring and logging

14 grouped gap(s) - Detection & monitoring
The exposure: without active detection or complete logs, an attack can succeed without being blocked, spotted in time, or proven afterward: a direct handicap in the event of an incident, a regulatory inspection, or an insurance claim.
Today: On this theme, the following compliance requirements are not met: L'action pour le spam à haut niveau de confiance (High Confidence Spam) est définie sur Mettre le message en quarantaine ; Les liens sûrs (Safe Links) ne sont pas contournés ; L'action en cas d'usurpation de domaine (Domain Impersonation) est définie sur déplacer vers la quarantaine ; L'action en cas d'usurpation d'identité d'utilisateur (User impersonation) est définie sur déplacer vers la quarantaine.
What the audit found: Inclure tous les utilisateurs dans la protection Defender for Office 365 via le preset de sécurité Standard ou Strict. Configurer la politique Anti-courrier indésirable (anti-spam) pour appliquer le réglage cible : « Durée de rétention en quarantaine portée à 30 jours ». Configurer la politique Anti-hameçonnage pour appliquer le réglage cible : « Mise en quarantaine des messages détectés comme hameçonnage ».
Effort LowImpact High
IV

Data exposure

6 grouped gap(s) - Data & exposure
The exposure: data leaving the company without a safeguard is the most common leak vector, and the most costly in both reputational and regulatory terms.
Today: On this theme, the following compliance requirements are not met: S'assurer que les stratégies d'étiquettes de confidentialité Information Protection sont publiées ; S'assurer que le partage de contenu OneDrive est restreint ; Une solution de prevention des pertes de données (DLP) DOIT être utilisée ; L'action de la politique personnalisée DEVRAIT être configurée pour bloquer le partage d'informations sensibles avec tout le monde.
What the audit found: Publier au moins une politique d'étiquettes de sensibilité (sensitivity labels) auprès des utilisateurs ou groupes cibles, afin de permettre la classification et la protection des documents selon leur niveau de confidentialité. Restreindre le partage de contenu OneDrive au niveau le plus restrictif approprié (au plus 'Invités existants'), sachant qu'OneDrive peut être plus restrictif que SharePoint mais jamais plus permissif. Mettre en place une solution de prévention des pertes de données (DLP) couvrant Exchange Online.
Effort MediumImpact High

Non-conformities weighing on insurability

Actual findings related to root causes
BenchmarkControl pointSeverity
M365SEC:2.4.2M365SAT, Monkey365MEx 2.4.2 - Priority accounts do not have 'Strict protection' presets appliedHigh
M365SEC:7.3.2M365SAT, Monkey365MSp 7.3.2 - OneDrive for Business sync from unmanaged devices is not blockedHigh
MT.1037MaesterOnly users with Presenter role are allowed to present in Teams meetingsHigh
MT.1034MaesterMT.1034.$($EmergencyAccessUsers.IndexOf($_)): Emergency access users should not be blocked ($($_.userPrincipalName))To be remediated
M365SEC:5.2.2.2M365SAT, Monkey365MAz 5.2.2.2 - MultiFactor Authentication (MFA) is not enabled for all users non-administrative rolesCritical
CISA:MS.AAD.3.2Maester, ScubaGearIf phishing-resistant MFA has not been enforced, an alternative MFA method SHALL be enforced for all users.Critical
M365SEC:5.1.5.2M365SAT, Maester, Monkey365CISMAz 5.1.5.2 - User consent to apps accessing company data on their behalf is allowed!High
M365SEC:5.2.3.4M365SAT, Monkey365MAz 5.2.3.4 - Not all member users are 'MFA capable'High
ORCA.140MaesterHigh Confidence Spam action set to Quarantine message.High
ORCA.189.2MaesterSafe Links is not bypassed.High

Blind spots: not covered by enforceable proof until measured

63 unmeasured control(s) in the catalog
BenchmarkControl pointStatus
M365SEC:1.3.5M365SAT, Maester, Monkey365MOff 1.3.5 - Internal phishing protection for Forms is disabledNot measured
M365SEC:2.4.1M365SAT, Monkey365MEx 2.4.1 - Priority account protection is not enabled and configured!Not measured
M365SEC:3.2.1M365SAT, Monkey365MEx 3.2.1 - DLP Policy is not enabled!Not measured
M365SEC:7.2.7M365SAT, Maester, Monkey365MSp 7.2.7 - Ensure link sharing is not restricted in SharePoint and OneDrive!Not measured
CISA:MS.AAD.4.1Maester, ScubaGearSecurity logs SHALL be sent to the agency's security operations center for monitoring.Not measured
M365SEC:6.2.1M365SAT, Monkey365MEx 6.2.1 - Forms of mail forwarding are not blocked and/or not disabledNot measured
CISA:MS.EXO.13.1Maester, ScubaGearMailbox auditing SHALL be enabled.Not measured
M365SEC:4.2Monkey365Devices enrollment personal devices not blockedNot measured
M365SEC:7.2.11Maester, Monkey365Ensure the SharePoint default sharing link permission is setNot measured
MT.1027MaesterNo Service Principal with Client Secret and permanent role assignment on Control Plane.Not measured
The order in which to build the insurability file
First
Baseline configuration. The strongest risk-eliminated / effort ratio. Until this is done, the rest protects a house whose door remains open.
Then
Identity. Once the first lever is secured, we reduce the surface through which the risk materializes.
Then
Monitoring. What remains is to anchor these gains over time: governance, regular reviews and retained evidence, so the posture holds over time and not just on audit day.
Being consolidated
Remaining underlying projects. external exposure: to be consolidated once the top-of-list priorities are held.

What this trajectory avoids

Interruption. a hijacked account that paralyzes operations.
Leak. customer data leaving without a trace.
Non-compliance. an enforceable GDPR or NIS2 gap during an inspection.
Insurance refusal. a claim not covered for lack of evidence.

The 195 compliant controls, one by one

You do not have to take our word for a total. Each line below carries its reference and the public framework that grounds it: your insurer, your client or your statutory auditor can check them one by one in your own Microsoft logs.
BenchmarkControl pointSeverity
ANSSI R13ANSSI/NIS2 ANSSI R13ANSSI R13Compliant
ANSSI R14ANSSI/NIS2 ANSSI R14ANSSI R14Compliant
ANSSI R16ANSSI/NIS2 ANSSI R16ANSSI R16Compliant
ANSSI R24ANSSI/NIS2 ANSSI R24ANSSI R24Compliant
ANSSI R29ANSSI/NIS2 ANSSI R29ANSSI R29Compliant
ANSSI R36ANSSI/NIS2 ANSSI R36ANSSI R36Compliant
ANSSI R5ANSSI/NIS2 ANSSI R5ANSSI R5Compliant
ANSSI R8ANSSI/NIS2 ANSSI R8ANSSI R8Compliant
M365SEC:5.1.1.1M365SAT CISMAz5111CISMAz 5.1.1.1 - The Security Defaults are enabled on Azure Active Directory TenantCompliant
M365SEC:6.1.4M365SAT CISMEx614MEx 6.1.4 - Des boîtes aux lettres portent-elles 'AuditBypassEnabled', qui les exclut du journal d'audit ?Compliant
CISA:MS.EXO.10.1Maester CISA.MS.EXO.10.1Emails SHALL be scanned for malware.Compliant
CISA:MS.EXO.10.2Maester CISA.MS.EXO.10.2Emails identified as containing malware SHALL be quarantined or dropped.Compliant
CISA:MS.EXO.10.3Maester CISA.MS.EXO.10.3Email scanning SHALL be capable of reviewing emails after delivery.Compliant
CISA:MS.EXO.11.1Maester CISA.MS.EXO.11.1Impersonation protection checks SHOULD be used.Compliant
CISA:MS.EXO.11.2Maester CISA.MS.EXO.11.2User warnings, comparable to the user safety tips included with EOP, SHOULD be displayed.Compliant
CISA:MS.EXO.11.3Maester CISA.MS.EXO.11.3The phishing protection solution SHOULD include an AI-based phishing detection tool comparable to EOP Mailbox Intelligence.Compliant
CISA:MS.EXO.12.1Maester CISA.MS.EXO.12.1IP allow lists SHOULD NOT be created.Compliant
CISA:MS.EXO.14.1Maester CISA.MS.EXO.14.1A spam filter SHALL be enabled.Compliant
CISA:MS.EXO.14.2Maester CISA.MS.EXO.14.2Spam and high confidence spam SHALL be moved to either the junk email folder or the quarantine folder.Compliant
CISA:MS.EXO.14.3Maester CISA.MS.EXO.14.3Allowed domains SHALL NOT be added to inbound anti-spam protection policies.Compliant
CISA:MS.EXO.15.1Maester CISA.MS.EXO.15.1URL comparison with a block-list SHOULD be enabled.Compliant
CISA:MS.EXO.15.2Maester CISA.MS.EXO.15.2Direct download links SHOULD be scanned for malware.Compliant
CISA:MS.EXO.15.3Maester CISA.MS.EXO.15.3User click tracking SHOULD be enabled.Compliant
CISA:MS.EXO.16.1Maester CISA.MS.EXO.16.1Alerts SHALL be enabled.Compliant
CISA:MS.EXO.16.2Maester CISA.MS.EXO.16.2Alerts SHOULD be sent to a monitored address or incorporated into a security information and event management (SIEM) system.Compliant
CISA:MS.EXO.17.1Maester CISA.MS.EXO.17.1Microsoft Purview Audit (Standard) logging SHALL be enabled.Compliant
CISA:MS.EXO.2.1Maester CISA.MS.EXO.2.1A list of approved IP addresses for sending mail SHALL be maintained.Compliant
EIDSCA.AF01Maester EIDSCA.AF01Authentication method - FIDO2 security key - State.Compliant
EIDSCA.AF02Maester EIDSCA.AF02Authentication Method - FIDO2 security key - Allow self-service set up.Compliant
EIDSCA.AF03Maester EIDSCA.AF03Authentication method - FIDO2 security key - Enforce attestation.Compliant
EIDSCA.AF04Maester EIDSCA.AF04Authentication method - FIDO2 security key - Enforce key restrictions.Compliant
EIDSCA.AF05Maester EIDSCA.AF05Authentication method - FIDO2 security key - Restricted.Compliant
EIDSCA.AF06Maester EIDSCA.AF06Authentication Method - FIDO2 security key - Restrict specific keys.Compliant
EIDSCA.AG01Maester EIDSCA.AG01Authentication method - General settings - Manage migration.Compliant
EIDSCA.AG02Maester EIDSCA.AG02Authentication method - General settings - Report suspicious activity - State.Compliant
EIDSCA.AM01Maester EIDSCA.AM01Authentication method - Microsoft Authenticator - State.Compliant
EIDSCA.AM02Maester EIDSCA.AM02Authentication method - Microsoft Authenticator - Allow use of Microsoft Authenticator OTP.Compliant
EIDSCA.AM03Maester EIDSCA.AM03Authentication Method - Microsoft Authenticator - Require number matching for push notifications.Compliant
EIDSCA.AM04Maester EIDSCA.AM04Authentication Method - Microsoft Authenticator - Included users/groups of number matching for push notifications.Compliant
EIDSCA.AM06Maester EIDSCA.AM06Authentication Method - Microsoft Authenticator - Show application name in push and passwordless notifications.Compliant
EIDSCA.AM07Maester EIDSCA.AM07Authentication method - Microsoft Authenticator - Users and groups included for showing the application name in push and passwordless notifications.Compliant
EIDSCA.AM09Maester EIDSCA.AM09Authentication Method - Microsoft Authenticator - Show geographic location in push and passwordless notifications.Compliant
EIDSCA.AM10Maester EIDSCA.AM10Authentication method - Microsoft Authenticator - Users and groups included for showing the geographic location in push and passwordless notifications.Compliant
EIDSCA.AP01Maester EIDSCA.AP01Default authorization settings - Self-service password reset enabled for administrators.Compliant
EIDSCA.AP04Maester EIDSCA.AP04Default Authorization Settings - Guest invite restrictions.Compliant
EIDSCA.AP06Maester EIDSCA.AP06Default Authorization Settings - User can join the tenant by email validation.Compliant
EIDSCA.AP08Maester EIDSCA.AP08Default authorization settings - User consent policy assigned for applications.Compliant
EIDSCA.AP10Maester EIDSCA.AP10Default Authorization Settings - Default User Role Permissions - Allowed to create Apps.Compliant
EIDSCA.AS04Maester EIDSCA.AS04Authentication Method - SMS - Use for sign-in.Compliant
EIDSCA.AT01Maester EIDSCA.AT01Authentication method - Temporary Access Pass - State.Compliant
EIDSCA.AT02Maester EIDSCA.AT02Authentication method - Temporary Access Pass - One-time use.Compliant
EIDSCA.AV01Maester EIDSCA.AV01Authentication method - Voice call - State.Compliant
EIDSCA.CP01Maester EIDSCA.CP01Default settings - Consent policy settings - Group owner consent for apps accessing data.Compliant
EIDSCA.CP03Maester EIDSCA.CP03Default Settings - Consent Policy Settings - Block user consent for risky apps.Compliant
EIDSCA.PR02Maester EIDSCA.PR02Default Settings - Password Rule Settings - Password Protection - Enable password protection on Windows Server Active Directory.Compliant
EIDSCA.PR03Maester EIDSCA.PR03Default settings - Password rule settings - Enforce custom list.Compliant
EIDSCA.PR05Maester EIDSCA.PR05Default Settings - Password Rule Settings - Smart Lockout - Lockout duration in seconds.Compliant
EIDSCA.PR06Maester EIDSCA.PR06Default settings - Password rule settings - Smart Lockout - Lockout threshold.Compliant
EIDSCA.ST08Maester EIDSCA.ST08Default Settings - Classification and M365 Groups - M365 groups - Allow Guests to become Group Owner.Compliant
EIDSCA.ST09Maester EIDSCA.ST09Default settings - Classification and M365 groups - M365 groups - Allow guests to access group content.Compliant
M365SEC:1.1.1Maester M365.1.1.1MOff 1.1.1 - Ensure Administrative accounts are separate and cloud-onlyCompliant
M365SEC:1.1.3Maester M365.1.1.3Ensure that between two and four global admins are designatedCompliant
M365SEC:1.3.1Maester M365.1.3.1Ensure the 'Password expiration policy' is set to 'Set passwords to never expire (recommended)'Compliant
M365SEC:1.3.3Maester M365.1.3.3Ensure 'External sharing' of calendars is not availableCompliant
M365SEC:1.3.4Maester M365.1.3.4MOff 1.3.4 - User owned apps and services are not restrictedCompliant
M365SEC:2.1.1Maester M365.2.1.1Ensure Safe Links for Office Applications is Enabled (Only Checks Default Policy)Compliant
M365SEC:2.1.11Maester M365.2.1.11Ensure comprehensive attachment filtering is appliedCompliant
M365SEC:2.1.2Maester M365.2.1.2Ensure the Common Attachment Types Filter is enabled (Only Checks Default Policy)Compliant
M365SEC:2.1.3Maester M365.2.1.3Ensure notifications for internal users sending malware is Enabled (Only Checks Default Policy)Compliant
M365SEC:2.1.4Maester M365.2.1.4Ensure Safe Attachments policy is enabled (Only Checks Default Policy)Compliant
M365SEC:2.1.5Maester M365.2.1.5Ensure Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is EnabledCompliant
M365SEC:2.1.6Maester M365.2.1.6Ensure Exchange Online Spam Policies are set to notify administrators (Only Checks Default Policy)Compliant
M365SEC:2.1.7Maester M365.2.1.7Ensure that an anti-phishing policy has been created (Only Checks Default Policy)Compliant
M365SEC:3.1.1Maester M365.3.1.1MEx 3.1.1 - Microsoft 365 audit log search is Disabled!Compliant
M365SEC:4.1Maester M365.4.1Ensure devices without a compliance policy are markedCompliant
M365SEC:5.1.2.2Maester M365.5.1.2.2MAz 5.1.2.2 - Third party integrated applications are allowed!Compliant
M365SEC:5.1.5.1Maester M365.5.1.5.1Ensure user consent to apps accessing company data on their behalf is not allowedCompliant
M365SEC:5.1.6.2Maester M365.5.1.6.2Ensure that guest user access is restrictedCompliant
M365SEC:5.2.3.5Maester M365.5.2.3.5Ensure weak authentication methods are disabledCompliant
M365SEC:7.2.2Maester M365.7.2.2MSp 7.2.2 - SharePoint and OneDrive integration with Azure AD B2B is not enabled!Compliant
M365SEC:7.2.5Maester M365.7.2.5Ensure that SharePoint guest users cannot share items they donCompliant
M365SEC:7.2.9Maester M365.7.2.9MSp 7.2.9 - Guest access to a site or OneDrive does not expire automaticallyCompliant
M365SEC:7.3.1Maester M365.7.3.1MSp 7.3.1 - Office 365 SharePoint infected files are NOT disallowed for downloadCompliant
M365SEC:8.4.1Maester M365.8.4.1Ensure all or a majority of third-party and custom apps are blockedCompliant
M365SEC:8.6.1Maester M365.8.6.1Ensure users can report security concerns in Teams to internal destinationCompliant
MT.1003Maester MT.1003At least one Conditional Access policy is configured with All Apps.Compliant
MT.1004Maester MT.1004At least one Conditional Access policy is configured with All Apps and All Users.Compliant
MT.1006Maester MT.1006At least one Conditional Access policy is configured to require MFA for administrators.Compliant
MT.1007Maester MT.1007At least one Conditional Access policy is configured to require MFA for all users.Compliant
MT.1008Maester MT.1008At least one Conditional Access policy is configured to require MFA for Azure management.Compliant
MT.1009Maester MT.1009At least one Conditional Access policy is configured to block other legacy authentication.Compliant
MT.1010Maester MT.1010At least one Conditional Access policy is configured to block legacy authentication for Exchange ActiveSync.Compliant
MT.1011Maester MT.1011At least one Conditional Access policy is configured to secure security info registration only from a trusted location.Compliant
MT.1014Maester MT.1014At least one Conditional Access policy is configured to require compliant or Entra hybrid joined devices for administrators.Compliant
MT.1015Maester MT.1015At least one Conditional Access policy is configured to block access from unknown or unsupported device platforms.Compliant
MT.1016Maester MT.1016At least one Conditional Access policy is configured to require MFA for guest access.Compliant
MT.1020Maester MT.1020All Conditional Access policies are configured to exclude directory synchronisation accounts, or do not target them.Compliant
MT.1022Maester MT.1022MT.1022Compliant
MT.1025Maester MT.1025No external user with permanent role assignment on Control Plane.Compliant
MT.1026Maester MT.1026No hybrid user with permanent role assignment on Control Plane.Compliant
MT.1031Maester MT.1031Control Plane privileged roles are managed by PIM only.Compliant
MT.1032Maester MT.1032A limited number of Global Administrators is assigned.Compliant
MT.1044Maester MT.1044Ensure modern authentication for Exchange Online is enabledCompliant
MT.1045Maester MT.1045Only guest users should be admitted automatically to Teams meetingsCompliant
MT.1050Maester MT.1050Applications with high-risk permissions having a direct path to Global Administrator.Compliant
MT.1051Maester MT.1051Applications with high-risk permissions having an indirect path to Global Administrator.Compliant
MT.1052Maester MT.1052At least one Conditional Access policy targets the Device Code authentication flow.Compliant
MT.1061Maester MT.1061The device registration MFA control conflicts with Conditional Access policies.Compliant
MT.1066Maester MT.1066Conditional Access policies should not include or exclude deleted users, groups or roles.Compliant
MT.1071Maester MT.1071At least one Conditional Access policy explicitly includes Azure DevOps.Compliant
MT.1072Maester MT.1072Conditional Access policies should not use the deprecated Approved Client App grant.Compliant
MT.1075Maester MT.1075Third-party Entra applications should have explicitly assigned users rather than All Users.Compliant
MT.1105Maester MT.1105The MDM authority should be set to Microsoft IntuneCompliant
ORCA.101Maester ORCA.101Bulk is marked as spam.Compliant
ORCA.102Maester ORCA.102Advanced Spam filter options are turned off.Compliant
ORCA.104Maester ORCA.104High Confidence Phish action set to Quarantine message.Compliant
ORCA.108.1Maester ORCA.108.1DNS Records have been set up to support DKIM.Compliant
ORCA.109Maester ORCA.109Senders are not unsafely allow listed.Compliant
ORCA.111Maester ORCA.111Anti-phishing policy exists and EnableUnauthenticatedSender is true.Compliant
ORCA.112Maester ORCA.112Anti-spoofing protection action is configured to Move message to the recipients' Junk Email folders in Anti-phishing policy.Compliant
ORCA.118.1Maester ORCA.118.1Domains are not unsafely allow listed in anti-spam policies.Compliant
ORCA.118.3Maester ORCA.118.3Your own domains are not unsafely allow listed in anti-spam policies.Compliant
ORCA.121Maester ORCA.121A supported filter policy action is in use.Compliant
ORCA.124Maester ORCA.124Safe Attachments unknown malware response is set to block messages.Compliant
ORCA.139Maester ORCA.139The spam action is set to move the message to the Junk Email folder or to quarantine.Compliant
ORCA.141Maester ORCA.141Bulk action set to Move message to Junk Email Folder.Compliant
ORCA.143Maester ORCA.143Safety Tips are enabled.Compliant
ORCA.158Maester ORCA.158Safe Attachments is enabled for SharePoint and Teams.Compliant
ORCA.180Maester ORCA.180Anti-phishing policy exists and EnableSpoofIntelligence is true.Compliant
ORCA.221Maester ORCA.221Mailbox Intelligence is enabled in anti-phishing policies.Compliant
ORCA.225Maester ORCA.225Safe Documents is enabled for Office clients.Compliant
ORCA.226Maester ORCA.226Every domain has a Safe Links policy applied to it.Compliant
ORCA.227Maester ORCA.227Every domain has a Safe Attachments policy applied to it.Compliant
ORCA.228Maester ORCA.228No trusted senders in Anti-phishing policy.Compliant
ORCA.229Maester ORCA.229No trusted domains in Anti-phishing policy.Compliant
ORCA.230Maester ORCA.230Each domain has a Anti-phishing policy applied to it, or the default policy is being used.Compliant
ORCA.231Maester ORCA.231Each domain has a anti-spam policy applied to it, or the default policy is being used.Compliant
ORCA.232Maester ORCA.232Each domain has a malware filter policy applied to it, or the default policy is being used.Compliant
ORCA.234Maester ORCA.234Click through is disabled for Safe Documents.Compliant
ORCA.236Maester ORCA.236Safe Links is enabled for emails.Compliant
ORCA.237Maester ORCA.237Safe Links is enabled for teams messages.Compliant
ORCA.238Maester ORCA.238Safe Links is enabled for office documents.Compliant
ORCA.240Maester ORCA.240Outlook is configured to display external tags for external emails.Compliant
ORCA.242Maester ORCA.242The significant protection alerts responsible for AIR activity are enabled.Compliant
ORCA.244Maester ORCA.244Policies are configured to honour the DMARC policy of sending domains.Compliant
M365SEC:5.2.2.3Monkey365 eid-cap-block-legacy-authentication-not-enabledMAz 5.2.2.3 - No Conditional Access policies to block legacy authenticationCompliant
M365SEC:5.2.2.4Monkey365 eid-cap-lack-sign-in-frequency-browser-persistent-sessionMAz 5.2.2.4 - Ensure Sign-in frequency is enabled and browser sessions are not persistent for Administrative usersCompliant
M365SEC:5.2.2.12Monkey365 eid-device-code-sign-in-flow-not-enabledEid device code sign in flow not enabledCompliant
M365SEC:5.2.2.1Monkey365 eid-ensure-mfa-for-high-privileged-users-missing-capMAz 5.2.2.1 - MultiFactor Authentication (MFA) is not enabled for all users in administrative rolesCompliant
M365SEC:5.2.2.5Monkey365 eid-ensure-phishing-resistant-mfa-for-high-privileged-users-missing-capMAz 5.2.2.5 - Phishing-resistant MFA strength must be required for AdministratorsCompliant
M365SEC:5.1.6.3Monkey365 eid-guest-invite-restriction-disabledEid guest invite restriction disabledCompliant
M365SEC:5.2.3.1Monkey365 eid-microsoft-authenticator-lack-mfa-fatigue-protectionMAz 5.2.3.1 - Microsoft Authenticator is not configured to protect against MFA fatigueCompliant
M365SEC:5.1.8.1Monkey365 eid-password-hash-sync-disabledMAz 5.1.8.1 - Password Synchronization DisabledCompliant
M365SEC:5.2.2.9Monkey365 eid-require-device-compliant-all-apps-missing-capEid require device compliant all apps missing capCompliant
M365SEC:5.2.2.10Monkey365 eid-require-device-compliant-to-register-security-info-missing-capEid require device compliant to register security info missing capCompliant
M365SEC:5.1.6.1Monkey365 eid-restrict-collaboration-specific-domains-disabledMAz 5.1.6.1 - Collaboration invitations are not sent to allowed domains onlyCompliant
M365SEC:5.2.2.11Monkey365 eid-sign-in-frequency-intune-enrollment-missing-capEid sign in frequency intune enrollment missing capCompliant
M365SEC:5.2.4.1Monkey365 eid-sspr-enabled-set-to-allMAz 5.2.4.1 - Self Service Password Reset is not set to be enabled for all usersCompliant
M365SEC:6.1.3Monkey365 exchange-audit-bypass-enabledExchange audit bypass enabledCompliant
M365SEC:6.1.1Monkey365 exchange-audit-enabled-globallyMEx 6.1.1 - Mailbox auditing is not Enabled for all usersCompliant
M365SEC:6.2.3Monkey365 exchange-external-email-sender-configuredMEx 6.2.3 - Email from external senders cannot be identifiedCompliant
M365SEC:6.5.1Monkey365 exchange-modern-authentication-disabledExchange modern authentication disabledCompliant
M365SEC:2.1.14Monkey365 exhange-inbound-anti-spam-policies-allowed-domainsMEx 2.1.14 - No comprehensive attachment filtering is applied!Compliant
M365SEC:7.2.8Monkey365 sharepoint-external-sharing-not-restricted-by-security-groupMSp 7.2.8 - Ensure external sharing is restricted by security group!Compliant
M365SEC:7.2.1Monkey365 sharepoint-modern-authentication-requiredSharePoint modern authentication requiredCompliant
M365SEC:8.5.1Monkey365 teams-anonymous-users-cant-join-meetingCISM Tm 8.5.1 - Anonymous users can join a meetingCompliant
CISA:MS.AAD.1.1ScubaGear MS.AAD.1.1v1Legacy authentication SHALL be blocked.Compliant
CISA:MS.AAD.3.1ScubaGear MS.AAD.3.1v1Phishing-resistant MFA SHALL be enforced for all users.Compliant
CISA:MS.AAD.3.3ScubaGear MS.AAD.3.3v2If Microsoft Authenticator is enabled, it SHALL be configured to show login context information.Compliant
CISA:MS.AAD.3.4ScubaGear MS.AAD.3.4v1The Authentication Methods Manage Migration feature SHALL be set to Migration Complete.Compliant
CISA:MS.AAD.3.6ScubaGear MS.AAD.3.6v1Phishing-resistant MFA SHALL be required for highly privileged roles.Compliant
CISA:MS.AAD.3.7ScubaGear MS.AAD.3.7v1Managed devices SHOULD be required for authentication.Compliant
CISA:MS.AAD.3.8ScubaGear MS.AAD.3.8v1Managed Devices SHOULD be required to register MFA.Compliant
CISA:MS.AAD.3.9ScubaGear MS.AAD.3.9v1Device code authentication SHOULD be blocked.Compliant
CISA:MS.AAD.5.1ScubaGear MS.AAD.5.1v1Only administrators SHALL be allowed to register applications.Compliant
CISA:MS.AAD.5.2ScubaGear MS.AAD.5.2v1Only administrators SHALL be allowed to consent to applications.Compliant
CISA:MS.AAD.6.1ScubaGear MS.AAD.6.1v1User passwords SHALL NOT expire.Compliant
CISA:MS.AAD.7.1ScubaGear MS.AAD.7.1v1A minimum of two users and a maximum of eight users SHALL be provisioned with the Global Administrator role.Compliant
CISA:MS.AAD.7.2ScubaGear MS.AAD.7.2v1Privileged users SHALL be provisioned with finer-grained roles instead of Global Administrator.Compliant
CISA:MS.AAD.7.4ScubaGear MS.AAD.7.4v1Permanent active role assignments SHALL NOT be allowed for highly privileged roles.Compliant
CISA:MS.AAD.8.1ScubaGear MS.AAD.8.1v1Guest users SHOULD have limited or restricted access to Microsoft Entra ID directory objects.Compliant
CISA:MS.AAD.8.2ScubaGear MS.AAD.8.2v1Only users with the Guest Inviter role SHOULD be able to invite guest users.Compliant
CISA:MS.AAD.8.3ScubaGear MS.AAD.8.3v1Guest invites SHOULD only be allowed to specific external domains that have been authorized by the agency for legitimate business purposes.Compliant
CISA:MS.DEFENDER.2.2ScubaGear MS.DEFENDER.2.2v1Domain impersonation protection SHOULD be enabled for agency-owned domains in standard and strict policies.Compliant
CISA:MS.DEFENDER.2.3ScubaGear MS.DEFENDER.2.3v1Domain impersonation protection SHOULD be added for key suppliers and partners in standard and strict policies.Compliant
CISA:MS.DEFENDER.3.1ScubaGear MS.DEFENDER.3.1v1Safe attachments SHOULD be enabled for SharePoint, OneDrive, and Microsoft Teams.Compliant
CISA:MS.DEFENDER.5.1ScubaGear MS.DEFENDER.5.1v1Alerts required by Exchange Online baseline SHALL be enabled at minimum.Compliant
CISA:MS.DEFENDER.5.2ScubaGear MS.DEFENDER.5.2v1Alerts SHOULD be sent to a monitored address or incorporated into SIEM.Compliant
CISA:MS.DEFENDER.6.1ScubaGear MS.DEFENDER.6.1v1Unified Audit logging SHALL be enabled.Compliant
CISA:MS.EXO.1.1ScubaGear MS.EXO.1.1v2Automatic forwarding to external domains SHALL be disabled.Compliant
CISA:MS.EXO.6.1ScubaGear MS.EXO.6.1v1Contact folders SHALL NOT be shared with all domains.Compliant
CISA:MS.EXO.6.2ScubaGear MS.EXO.6.2v1Calendar details SHALL NOT be shared with all domains.Compliant
CISA:MS.EXO.7.1ScubaGear MS.EXO.7.1v1External sender warnings SHALL be implemented.Compliant
CISA:MS.SHAREPOINT.1.3ScubaGear MS.SHAREPOINT.1.3v1External sharing SHALL be restricted to approved external domains and/or users in approved security groups per interagency collaboration needs.Compliant
CISA:MS.TEAMS.1.3ScubaGear MS.TEAMS.1.3v1Anonymous users and dial-in callers SHOULD NOT be admitted automatically.Compliant

Verifiable proof is the argument. This diagnostic has never seen your data: only configuration settings were read, never personal content. Every finding above is verifiable in your own Microsoft logs, and therefore enforceable - whether the reader is an insurer, a principal contractor auditing you, or a statutory auditor.

Method & proof
Direct reading, zero-knowledge
Microsoft 365 configuration read via the Graph API (directory, Exchange, Teams, SharePoint, Purview): no data (e-mail, file) is read, only settings are. No data retention beyond the production of the report.
Cross-referenced frameworks
M365 security baselineCISA SCuBAMaesterMonkey365M365SATSYAGA controls
Baseline reformulated by SYAGA from the open-source checkers, cross-referenced with the CISA SCuBA baseline.
Scope assessed
280
controls assessed against the SYAGA catalog
420 = 280 decided + 44 under assisted coverage + 63 not measured + 24 non applicables (licence) + 6 declarative (organisational) + 3 en lecture seule
SYAGA CONSULTING attests that the technical findings above result from a direct reading of the audited tenant's configuration on the stated date, following the described zero-knowledge method, and without retaining any data beyond the production of this report. The declarative organisational points (governance, awareness, physical security) fall under your own attestation: you confirm them, SYAGA does not measure them. This split - SYAGA for what is measured, you for what is declared - is what makes the file valuable: dated, verifiable proof of accountability, admissible to an insurer or a principal.
Reference: SYAGA-DEMO-QUESTIONNAIRE-0001
Score = contrôles conformes / contrôles tranchés (conformes + non conformes), sans pondération ; les contrôles non collectés et non applicables sont exclus du score.
Optional SharePoint add-on (3 control(s))
Complément optionnel : Microsoft ne propose pas de mode lecture seule pour ces réglages SharePoint par site - y accéder exige un droit d'écriture (limite Microsoft, pas la nôtre). Désactivé par défaut, disponible en option de votre côté, et hors score tant que non activé.
These controls count as NEITHER compliant, NOR non-compliant, NOR uncollected: they remain out of the score until you enable the add-on (at your initiative, on your side, never on ours).
Not applicable: feature not present on the tenant (24 control(s))
These controls do not apply to your tenant: the relevant feature (Microsoft Entra ID P2 / Governance license, or a product like Copilot, Sentinel, Defender for Endpoint, Power Platform...) is not present. There is therefore nothing to measure: this is neither a failure nor a blind spot.
These controls count as NEITHER compliant NOR non-compliant: this is an observation, not a failure. We do not encourage you to buy an additional license: the security objective targeted can often be achieved otherwise (configuration, internal procedure, or a third-party tool sometimes free and less costly). They would become measurable again if the resource were present on your tenant.
6 point(s) de vigilance organisationnels
These requirements (physical security, network segmentation, awareness, governance) belong to the organisation and are NOT measurable by a read-only Microsoft 365 scan. They are reported separately, outside the score and outside the gap count: to be checked by an internal review.
SYAGA Audit · published by SYAGA CONSULTINGVerifiable audit, never a certification