Lesson 2.61: Security in the first 100 days after an acquisition
Northwind has bought Kestrel Logistics (the due-diligence capstone of Intro 301). Now the integration team wants to connect networks, merge identities and move systems fast, because that's where the deal's savings are. Security's job isn't to stop integration but to set gates: each connection happens only when the findings that make it dangerous are closed. In the lab you read which diligence findings are still open, see which integration steps they block and which can start now, check the day-25 status and write the gates, including how to handle date pressure.
19 min
You will learn to
- Link due-diligence findings to integration steps
- Find which steps are blocked and which can start
- Order safe steps first (visibility before connectivity)
- Check progress against gates
- Escalate date pressure with the risk stated
Key terms
- Integration gate
- A condition that must be met, with evidence, before an integration step goes ahead.
- Identity federation
- Letting accounts from one organisation sign in to another's systems.
- Synergy
- Cost savings or revenue gains expected from combining companies.
- Day-1 conditions
- Security requirements that must be met before closing or first connection.
- Visibility first
- Deploy monitoring and endpoint protection before connecting networks.
← Regulatory horizon scanning · All lessons · Looking at text files: cat, less and more →