Cloud and SaaS
Microsoft 365 Assessment
Assess tenant identity, application permissions and collaboration controls. Findings address account compromise, business email fraud and unintended disclosure arising from excessive sharing or delegated authority.
01 / Overview
Assessment objectives and control obligations
Microsoft 365 review examines effective tenant protection across Entra ID, conditional access, authentication methods, legacy protocols and recovery. Service-principal permissions and consent grants are assessed independently of interactive-user login controls. Licence dependencies and exclusions are recorded against the capabilities actually available in the tenant.
Representative Exchange, Teams and SharePoint resources establish delegated authority, forwarding and external-sharing behaviour. Audit retention and revocation evidence inform compromise investigation and account containment. Findings distinguish excessive current access from historical misuse, minimising inspection of message content and unrelated personal information.
02 / Technical analysis
Failure mechanisms and security implications
Application permissions may survive independently of a user’s interactive session. Strong login protection does not resolve excessive sharing or consent. We assess the authority granted and how it is revoked.
03 / Scope
Technical coverage and authorisation boundaries
Coverage is agreed in writing before testing begins. The rows below describe what this service normally examines. Exclusions, testing windows and escalation contacts are recorded in the rules of engagement.
- Identity and applications
- Privileged roles, conditional access, consent and token authority.
- Mail and collaboration
- Forwarding, rules, guests and external sharing.
- Audit and revocation
- Log availability, retention and session or application removal.
- Supporting tools
- Environment-appropriate instrumentation may include ScubaGear, Microsoft Graph API, Entra ID, PowerShell, Maester. Selection follows the investigative objective, compatibility requirements and approved operating constraints. Automated output requires corroboration against implementation evidence or observed execution before classification as a substantiated finding.
04 / Methodology
Investigation and validation methodology
Control review evaluates design adequacy and operating effectiveness against an explicit baseline. Sampling rationale, implementation evidence, exceptions and analytical limitations are retained to support traceable conclusions and proportionate remediation.
01
Objectives and evidence plan
Preparation
We agree the questions, applicable references and evidence sources, and authorise any sampling or active validation before collection.
02
Reconcile tenant policy
Identify enforced controls, exceptions and available evidence.
03
Check representative access
Verify sharing and permission outcomes with controlled resources.
04
Priorities and handover
Review completion
Factual reconciliation precedes delivery of a risk-treatment roadmap identifying accountable owners, implementation dependencies and measurable verification criteria.
05 / Assessment options
Access models and evidential confidence
Supplied access determines investigative reach, validation depth and evidential confidence. The proposal records the access model, supporting material and unresolved coverage limitations; no model implies unrestricted authority or exhaustive verification.
- Black box
- Testing starts without supplied credentials or internal design material. External exposure is examined, while authenticated workflows may remain inaccessible.
- Grey box
- Representative accounts and selected design information support direct comparison of roles, tenants and sensitive workflows.
- White box
- Source, configuration and design evidence support root cause analysis. Runtime and access limitations are still recorded.
06 / Deliverables
Decision-support and verification deliverables
Deliverables distinguish what was observed, what was concluded and where the evidence stops. The agreed scope states which evidence, review sessions and retesting are included.
Executive summary
The summary explains the demonstrated exposure, the business functions affected and the treatment decisions required, including material uncertainty.
Technical findings
Each confirmed issue records the affected assets, prerequisites, reproduction evidence and a specific remediation. Technical severity is presented separately from business priority.
Coverage and limitations
The record identifies the systems, identities and conditions tested, together with exclusions and assumptions that affect interpretation.
Treatment and retest status
Recommendations are sequenced by risk, dependency and ownership. Any agreed retest records resolved, partly resolved and unresolved issues without implying a new assessment.
Service specific evidence
Policy extracts, effective grants, sharing samples and audit coverage identify treatment priorities.
07 / References
Applicable technical references
References are selected for the technology and objective in scope, and the edition applied is recorded. A framework mapping supports review; it is not certification or proof of complete compliance.
- CISA SCuBA configuration guidance
- SCuBA provides cloud business application configuration references. Selected settings are checked against tenant capabilities, licence dependencies and operational requirements.
- NIST digital identity guidance
- Revision 4 authentication guidance informs authenticator lifecycle, assurance, recovery and verifier requirements. Its scope and any binding local obligations are considered explicitly.
08 / Safeguards
Operational safeguards and evidence governance
Active work is conditional on written authority from the appropriate asset owner and approved rules of engagement. The operating plan specifies permitted procedures, testing windows, prohibited actions, third-party restrictions and nominated stop authority. Unexpected instability or suspected genuine compromise triggers suspension of affected activity pending the client’s operational decision.
Evidence governance applies purpose limitation, data minimisation and access proportionality to collection, transfer, processing, retention and disposal. The signed terms define authorised recipients and any external processing arrangement. Publication, secondary use and disclosure of client material require the applicable written permission.
Conclusions distinguish substantiated exposure, untested consequence and residual uncertainty. Each material finding identifies the control obligation, causal mechanism, observed outcome and verification criteria for the proposed treatment. Technical severity informs analysis; prioritisation and acceptance of residual risk remain decisions for the client’s authorised risk owner.
Unavailable licence features and expired logs limit assurance. Excess permission is not evidence of historical abuse.
09 / Suitability
Commissioning criteria
Use after tenant change, integration adoption or concerns about account and collaboration exposure.
Next step
Define the assessment you need
Tell us the business decision, the systems involved and any operational constraint. We will explain the coverage proposed, the access required and the evidence the engagement can provide.
- Confidentiality first
A mutual confidentiality agreement is signed before any technical detail is exchanged, so scope discussions can happen safely.
- Scope and cost in writing
Deliverables, access expectations, timeline and fee are confirmed before the engagement begins, and a scope change needs agreement.
- Answered by the delivery team
The consultants who scope an engagement are the consultants who perform it and explain the result to your team.
