Microsoft 365 Copilot & GenAI Data-Oversharing Readiness
Copilot and other GenAI assistants answer with whatever a user can technically reach. This engagement maps overshared SharePoint, OneDrive and Teams content, stale and broken permissions, sensitivity labelling gaps and risky sites, then delivers the remediation and governance plan that makes a Copilot rollout defensible — including an AI acceptable-use policy and the Purview controls to enforce it.
In scope
- Permission and sharing analysis across SharePoint, OneDrive and Teams
- Sensitive data discovery and sensitivity-label coverage
- Copilot / GenAI access-path review (who can reach what)
- Purview DLP, labelling and retention baseline
- AI acceptable-use policy and rollout guardrails
You receive
- Oversharing findings report with the top risky sites and groups
- Remediation plan with owner-ready task lists
- AI acceptable-use policy
- Go / no-go readiness scorecard for the Copilot rollout
Tiers
Choose the depth.
Essential Copilot Readiness
$12.5K
Up to 250 users: oversharing analysis, top-risk remediation plan and AI acceptable-use policy
- Users
- 250
Advanced Copilot Readiness
$18.5K
Up to 1,000 users: adds sensitivity-label design, Purview DLP baseline and a pilot-group rollout plan
- Users
- 1000
Enterprise GenAI Data Governance
$32K
1,000+ users or multiple GenAI tools: adds data-owner workshops, automated remediation runbooks and post-rollout monitoring design
- Users
- 10000
Members: engagement coupons from the CISO Marketplace coupon book apply to services. There is no blanket discount.
What's inside this engagement
Phase by phase.
How a readiness & governance assessment engagement runs, what happens in each phase and what you see. Exact scope, tier and timeline are fixed in your proposal and SOW.
01Scoping & framework selection
The standard or regulation, the systems and the business units in scope are fixed.
You see · Your audit or regulatory driver.
02Evidence collection & interviews
Policies, configurations and records reviewed; control owners interviewed.
You see · Documents and time with control owners.
03Gap analysis
Each requirement mapped to current state: met, partial or missing, with the evidence behind it.
You see · A clear gap register.
04Roadmap & evidence plan
Prioritized remediation with owners, and the evidence an auditor will ask for.
You see · A plan you can execute or hand to us.
Commercials
From first call to final report.
- 01
Scoping call
A practitioner, not a salesperson, walks through targets, constraints and what a good outcome looks like for you.
- 02
Proposal & rules of engagement
A fixed-scope proposal with tier, price and deliverables. Rules of engagement, contacts and out-of-bounds systems are agreed in writing.
- 03
Sign, then start
MSA and SOW are signed electronically and the deposit is paid. Only then does testing begin.
- 04
Execution
Testing runs to the agreed plan. Critical findings are escalated as they are found; you don't wait for the report.
- 05
Report & debrief
An executive summary plus technical findings with evidence, reproduction steps and fixes, walked through with your team.
- 06
Retest
Where the tier includes it, we verify your fixes and reissue the report, so auditors and customers see the issues closed.
Timelines are set per engagement in the SOW.
Related
DevSecOps Pipeline Testing
Comprehensive security testing integrated into your development pipeline with regular assessments.
Cloud Security Monitoring
Continuous monitoring and assessment of your cloud infrastructure security posture.
Cloud Security Posture Management
Advanced cloud security assessment and continuous monitoring implementation across multi-cloud environments, focusing on compliance, cost optimization, and security automation.
Research
Latest from the blog
incident-response · Sep 22, 2026
The Revolut Breach Is a Case Study in Confusing Authentication With Authorization
Revolut disclosed customer data to attackers who spoofed a government agency's email domain for five months. The root cause was not weak email security but a workflow that treated a valid domain as proof of a valid request.
identity-security · Aug 28, 2026
"No Customer Action Required": A CVSS 10.0 in Entra ID and the Disclosure Problem Nobody Has Solved
CVE-2026-69836 was a maximum-severity unauthenticated RCE in Microsoft Entra ID — the identity layer under a large share of the world's enterprises. Microsoft patched it, told customers to do nothing, and briefly flagged it as exploited before correcting the record on August 21. There was no action to take, no IOC to hunt, and no way to verify. That is the actual problem.
operations · Aug 12, 2026
421 CVEs in One Tuesday: Running Risk-Based Triage Under BOD 26-04
Microsoft shipped 421 CVEs on August Patch Tuesday, including an actively exploited afd.sys zero-day. Nobody patches 421 things in a month. CISA's BOD 26-04 already conceded the point in June with a four-variable risk model and a three-day clock for the worst tier. Here is how to run that model in a private enterprise, and why SharePoint proved that patching and remediation are not the same thing.
Start an engagement