Security and compliance carve-in: SOC 2, ISO 27001 and vendor rationalisation
An acquisition changes the scope of what you must protect and prove. Carve the new company in on purpose: close the access gaps first, then extend the programme.
Start with the basics on Day 1: remove shared and former-staff access, turn on multi-factor authentication and know where sensitive data lives. Then extend your control framework to the new company. A SOC 2 report covers the systems and period described in it, and an ISO 27001 certificate covers a defined scope, so a newly acquired company is not automatically covered. Plan a scope change with your auditor.
Okta
Microsoft Entra ID
Google Workspace
Microsoft 365
How to read this chart
The scores are our planning judgement for a typical small or mid-size deal: they show where effort tends to concentrate, not measured data. Replace them with your own once the inventory is done.
What does a SOC 2 or ISO 27001 report cover after an acquisition?
A SOC 2 report describes specific systems over a specific period, and an ISO 27001 certificate covers a stated scope. Neither automatically extends to a company you buy afterwards, so talk to your auditor about bringing it into scope.
- Ask the target for its own reports, and read the scope, not only the opinion.
- Decide whether to extend your scope or keep the target separate for a time.
- Tell customers who rely on your report how the acquisition affects what it covers.
How do you rationalise vendors and licences safely?
List every vendor and licence, mark overlaps, then cancel in order of notice dates and risk, not purely by saving.
- Combine both companies' vendor lists into one.
- Mark overlaps and the owner of each.
- Check data access and contract terms for each vendor.
- Cancel in notice-date order and archive data first.
What should happen in the first days?
Close the obvious gaps: stale accounts, shared admin logins, missing multi-factor authentication and unmanaged devices. These are cheap to fix and expensive to leave.
- Disable accounts for people who have left.
- Rotate shared credentials and move them into a password manager.
- Turn on multi-factor authentication for admins first, then everyone.
Questions on this topic
Does the buyer's SOC 2 cover the acquired company?
Not automatically. The report covers the systems and period it describes. Ask your auditor how the new company enters scope.
Do we need to certify the target separately?
That depends on your customers and your plans for the target. Some deals extend the existing scope; others keep a separate programme for a time.
Can we do this without a security team?
Many small deals do. An outside advisor can run the carve-in, and we can help scope that. This is planning guidance, not an audit.
Vendor documentation to check against
Microsoft Entra ID documentation (Microsoft Learn)
Microsoft 365 for enterprise documentation (Microsoft Learn)
Product details change. Confirm current options in each vendor's own documentation. Consultants in a Box is an independent consultancy; this page is not published or endorsed by any vendor named. Names and logos are trademarks of their owners.
Related guides
Identity, email and tenants
Identity decides who can reach everything else, so it comes first. Pick a tenant strategy, then move mail, files and chat in an order that never leaves people locked out.
Read the guideSynergy capture
Tech savings are real but smaller and slower than deal models often assume. Count the one-time cost to capture them, and size them with your own contract numbers.
Read the guideRisk register
Most integration failures are predictable. A risk register makes them visible early, with an owner and a mitigation each.
Read the guideAll M&A tech stack guides
The full playbook, from diligence to synergy capture.
See the hubMerging two stacks?
Start with the free business analysis, or book a call and we will talk through both companies' systems and where to begin.
