Each requirement your tenant can meet, mapped to a setting, an owner and a piece of evidence.
- We match NIST SP 800-171, SOC 2, ISO 27001 or HIPAA aligned safeguards to the tenant settings that meet them.
- We set up Purview, Entra ID and Intune with your IT team or MSP, in stages, and show any license change before you decide.
- Requirements no setting can meet, such as physical access and training, are documented with the people who own them.
200+ Microsoft 365 and Azure tenants. 100+ engagements. 20+ years in regulated technology.
One requirement, traced from the framework to the person who owns it
Your evidence map has one row like this for every requirement in scope.
Evidence map, one row traced end to end
Sample format, illustrative content
-
Requirement
3.3.1 Create and retain audit logs
NIST SP 800-171
-
Microsoft 365 setting
Purview audit on for every workload, with retention set to the requirement
-
Evidence
The retention policy export and a dated audit search of last month’s sign ins
-
Owner
The IT lead runs the search each month. Leadership signs off.
Met Evidence pulled again each month
Keeping logs longer than 180 days can need a license change, and we show that before you decide. Audit (Standard) keeps records for 180 days. Keeping them longer in Purview needs Audit (Premium), which comes with Microsoft 365 E5 or a separate Purview license. Sending the logs to a log store you already run is another route.
Not every row ends in a setting
- In the tenant
- 3.5.3 Multifactor authentication. A Conditional Access policy requires MFA for all users.
- Partly in the tenant
- 3.9.2 Personnel actions. Accounts are disabled in Entra ID at exit, and the HR exit checklist covers the rest.
- Outside the tenant
- 3.10.1 Physical access. The office access policy and badge records, owned by your operations lead.
When the framework meets the tenant
Three requests that usually start this work, and what is behind each one.
“Show us how this requirement is met in Microsoft 365.”
They want the setting and the proof, not the policy alone.
“Where does our data live, and who can open it?”
Labels, sharing settings and access policies answer that, once they are set and kept current.
“We have the policies. Are they switched on?”
A policy on paper and a setting in the tenant are different things. The evidence map shows which is which.
What we set up, and what each part shows an auditor
Configured to your framework, documented as it goes in, and recorded in the evidence map.
| Area | What we configure | What it shows an auditor |
|---|---|---|
| Identity and access, Entra ID | Conditional Access, MFA for all users, and admin roles held by the few people who need them | Who can sign in, from where and with what |
| Devices, Intune | Compliance policies, disk encryption and app protection for phones | Which devices can reach company data |
| Labels and data loss prevention, Purview | Sensitivity labels and data loss prevention policies for the data your framework names | Where sensitive data lives and who can share it |
| Retention, Purview | Retention policies for mail, files and Teams, set to your requirement | How long records are kept, and that deletion follows the rule |
| Audit, Purview | Audit on for every workload, with retention set to the requirement. Longer than 180 days can need a license change. | Who did what, and when |
| The evidence map | Every requirement in scope with its setting or outside control, its evidence and its owner | That each requirement is met, and who keeps it that way |
How the work runs, and what sets the time
Four steps in every engagement. We do not quote a length before the mapping is done, because the number of changes it finds sets it.
-
Choose
What sets the length One call, then a written scope
Name the framework and what is in scope: which users, data and systems. If more than one framework applies, we map them to one set of settings.
-
Map
What sets the length How many requirements are in scope
Each requirement matched to the settings that meet it and checked against your tenant as it is today. Requirements met outside the tenant are listed with their owners.
-
Configure
What sets the length The number of changes, your licenses and how users are told
Purview, Entra ID and Intune set up with your IT team or MSP, in stages. Data loss prevention policies run in simulation mode first, and labels go to a pilot group before everyone.
-
Prove
What sets the length Built as each change lands
Exports, samples and owners recorded in the evidence map, each with a date, so your auditor can follow it requirement by requirement.
What usually drives the time
- How many requirements are in scope, and how many already have a setting behind them
- How much data needs labels, and where it lives
- Whether a license change is needed, and how long your approval takes
- How many devices are not yet managed in Intune
- How quickly changes can be approved and announced on your side
What we need from your side
Admin access agreed with your IT team or MSP, a person who can approve changes, someone who decides on licenses, and your auditor’s request list if you have one.
What an auditor will ask for
Evidence gets checked three ways. The evidence map is built so your team can answer all three.
Examine
Documents and records they read
- The evidence map
- Policy exports from Purview and Entra ID
- Audit searches with dates
Interview
Questions your people answer
- Who owns this requirement?
- How do you know it is still on?
- What happens when someone leaves?
Test
Things they watch work
- A sign in without MFA is blocked
- A labeled file cannot be shared outside
- An audit search returns last month’s events
Evidence index, audit folder
Sample format, illustrative content
| Evidence | For | Pulled | Owner |
|---|---|---|---|
| Conditional Access policy export | 3.1.1, 3.5.3 | October 3 | IT lead |
| Audit retention policy export | 3.3.1 | October 3 | IT lead |
| Audit search, September sign ins | 3.3.1 | October 1 | IT lead |
| Intune compliance report, Windows | 3.4.1 | October 2 | MSP |
| Visitor log sample, main office | 3.10.1 | October 6 | Operations lead |
Work we have delivered
Real engagements, described without naming the clients.
-
Defense, CMMC Level 2
One defense contractor started with a four week gap assessment that scored all 110 NIST SP 800-171 requirements. It passed its CMMC Level 2 C3PAO assessment with every requirement met.
-
Healthcare
Healthcare clients carried through HITRUST e1 and i1.
-
Microsoft Secure Score, one tenant
One tenant moved from 28% to 68% Microsoft Secure Score in six weeks.
Your starting point and timing will differ. Secure Score measures tenant settings, not compliance with a framework.
Who this is for, and who it is not for
A good fit
- Organizations on Microsoft 365 that answer to a framework.
- Compliance leads preparing for an audit, an assessment or a customer review.
- IT leads who need the evidence, not only the settings.
Not a fit
- You want policies without the settings behind them.
- You need the audit itself. Your auditor or assessor is independent of us.
- You need help desk or day to day IT support.
- You run on Google Workspace rather than Microsoft 365.
Not sure which framework applies? Take the Starting Point check
Questions before you book
Which licenses will we need?
It depends on your framework and your plan. Conditional Access needs Microsoft Entra ID P1, which Microsoft 365 Business Premium and E3 include. Keeping audit logs in Purview for longer than 180 days needs Audit (Premium), which comes with Microsoft 365 E5 or a separate Purview license.
We start with what you already own. If a requirement needs more, we show what the license change buys before you decide.
Will labels and data loss prevention disrupt users?
They should not, if they go in the right order. Labels go to a pilot group first. Data loss prevention policies run in simulation mode, which reports what a policy would have matched without blocking anything. We widen each step once the results look right, and users hear what changes before it does.
Can a tenant meet every requirement?
No. Frameworks such as NIST SP 800-171 and ISO 27001 include physical, people and governance requirements that no Microsoft 365 setting meets. We document those with the people who own them, and the evidence map shows each one.
What does an auditor accept as evidence?
Usually something dated that shows the setting is on and working: a policy export, a log or report sample, or a dated screenshot, plus a named owner who can explain it. Your auditor has the final say, so we confirm what they expect early.
How long will this take for us?
The mapping comes first and tells us how many changes are needed. The length depends on that, on your licenses and on how quickly changes can be approved on your side, so the plan comes from the mapping, not from a guess on the first call.
How is this different from the security assessment?
The security assessment finds and fixes gaps across the tenant, the way an attacker or an auditor would see it. This service configures the tenant to one framework and produces the evidence for it.
Do you replace our IT provider or MSP?
No. We work with your IT team or MSP. We make or guide the changes in Purview, Entra ID and Intune, and they keep running the environment day to day.
How is the work priced?
As a fixed scope project, or as part of a fractional security and compliance officer retainer. We agree the scope in writing before work starts.
What happens after you book
- Pick a 30 minute time that suits you.
- We talk through your framework, your audit date and the licenses you have.
- You leave knowing what your tenant can cover, what sits outside it and what comes next.
Bring the framework you answer to, and your audit date, to a 30 minute call.
You leave knowing which requirements your tenant can meet, what sits outside it and what comes next.