Building Cybersecurity as a Shared Service
summary
Sumitomo shifts from a regional hosting model to a three-tier cybersecurity shared service that keeps operational control at each group company while centralizing detection, standards and training. Implements Microsoft 365 multi-tenant jointly with HQ, deploys a managed SIEM (originally Symantec MSS → Accenture SIEM), runs regional phishing campaigns and tabletop incident response exercises, and standardizes web/endpoint requirements. Headquarters funds rollout and global licensing; group companies retain remediation responsibility. Result: better buy-in, fewer one-off outages, clearer oversight and measurable incident reporting.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:53Sumitomo Chemical Americas structure
- 3:46Introduction
- 8:00Action Plan
- 8:48Lessons learned
- 9:53Gap analysis
- 10:40Develop plan
- 13:30What we did
- 18:08How we implemented the services
- 19:53MSS implementation
- 21:24Regional IRP and pen testing
- 22:47Summary
- 26:21"Apply" Slide • Is my shared service addressing the real issues? - Dol really understand what is needed from a shared service?
related talks
19mNavigating the Cyber Frontier
12mCyberSphere by Deloitte: A simplified platform integrated with AWS
59mCybersecurity as an ecosystem
40m"S"ecurity Convergence of Cyber, Fraud, and Physical Specialties
03mInterview
31mOrganizations' Holistic Approach to Cybersecurity
26mConvergence of AI, Cybersecurity, & Cloud: Shaping the Future of Enterprise IT
14mMerging cloud security with on-premises: How to centralize your SOC