Data protection & insider risk
Keep client lists and sensitive files from leaving with the person who resigns.
Departing employees walk out with client lists. Forgotten "anyone with the link" shares sit live in SharePoint. Sensitive files sync to personal devices. You have no map of where sensitive data lives or who can reach it.
What this looks like in real life
A senior account manager leaves for a competitor, and the pricing conversations that follow suggest the competitor already knows the numbers. Nobody can say what left with them: client folders in SharePoint are shared "anyone with the link", sensitive files had synced to a personal laptop that was never wiped, and there is no record of what was downloaded or when.
What was at risk
- Client lists and pricing able to leave with no audit trail behind them.
- Live "anyone with the link" shares sitting open across the busiest sites.
- No way to tell leadership what was actually exposed.
The work that resolves it
The ways data could leave are closed as one agreed, scheduled piece of work: sign-in and access policy enforced, risky application consent revoked, stale and departed-user accounts cleaned up, each change tested and recorded. Site-by-site file and sharing cleanup is quoted separately where the work surfaces it.
The relevant scope
Start with a defined piece of work
The scope, the price, and how you will know it is finished are agreed in writing before anyone is given access. Review the engagement below for its deliverables, responsibilities and acceptance criteria.
The engagement
Microsoft 365 Security Hardening
The agreed security controls are implemented and enforced as one agreed scope: sign-in and access policy, administrator roles, risky application consent and account cleanup, each change tested, documented and run in an approved window. The work is scheduled hardening, not emergency incident response or same-day offboarding, and site-by-site file cleanup is scoped separately where the review finds it.
What you walk away with
What the evidence looks like
Result tested before handoff
Every change is checked against what was agreed before the work is signed off, by the one engineer who scoped it and ran it.
Changes in approved windows
Nothing changes until the scope is agreed in writing. Changes to live systems run in windows the business approves, with the way back agreed before the window opens.
Fixed scope
A defined deliverable and a written test for when it is finished, agreed before anything starts.
Not sure this is the one?
Describe what happened, in a paragraph. A reply comes within one business day with the most direct next step, or a clear answer that AZ Innovations is not the right fit.
Discuss the scope and quoteWhat happens next
- 1Describe what happenedA few short fields: company size, environment, and what is going wrong.
- 2A reply within one business dayThe most direct next step, or a clear answer that AZ Innovations is not the right fit.
- 3A fixed-fee proposalNamed scope, price, and how you will know it is finished. No obligation.