SYNGENTA
grow , and we have to innovate along with the company ’ s risk appetite . Our goal over the next few years is to move the needle even further across our maturity curve toward a more proactive and metrics-driven organisation , with a predictive , integrated information and cybersecurity programme .
“ We need not only to address the current needs of the business , but to actually predict what those are going to be , if we are to stay one step ahead of our cyber adversaries . And we must be able to build security controls and capabilities into our technological solutions across the organisation as opposed to bolt-on solutions .”
good cadence with our legal , finance and HR partners . We then introduced ourselves and established good partnerships right across the all lines of service as well as in the functional areas of the organisation , especially from an R & D perspective .
“ Where we find ourselves now evolved from what I found to be a baseline maturity model : reactive , unstable , ad hoc and inconsistent into the standards-aligned , documented and risk-based programme that I think is absolutely critical to be able to maintain from a cybersecurity perspective in a global organisation .”
It ' s not a finished job though , given the dynamic threat landscape – ever-evolving and expansive .
“ Without continuing to grow and innovate in this space we will remain static and find our maturity level reducing . We have to
The road to the cloud A great leap forward in capability and tech maturity was taken when the company moved all its on-prem infrastructure to the cloud . The responsibility of Subu Iyer , Global Head of Cloud Services , DevOps and IT Intelligent Automation , Syngenta ' s journey to the cloud started back in 2016 with the setup of Cloud 1.0 in AWS .
" Migration of applications from data centres to the cloud started then , as the cloud promised a 50 % reduction in operating costs . We successfully migrated the initial batch of 500-plus applications to the cloud in 2020 , but project teams soon started running into governor limit-related issues linked to a single account architecture in Cloud 1.0 . Subsequent discussions with AWS led us to setting up the secure multi-account landing zones , or Cloud 2.0 . This proved to be a huge milestone for us . After detailed analysis and careful considerations , we chose to migrate the entire suite of SAP platforms and workloads out to our Cloud 2.0 ecosystem that same year ,” explains Iyer .
“ Following in the footsteps of the AWS operation , we then set up the multi-account
cybermagazine . com 77