

Thank you for Subscribing to Insurance Business Review Weekly Brief
Digital transformation is synonymous with the use of third parties, and the need for robust security measures across an increasingly interconnected estate is crucial. While partnerships with cloud, software, and external service providers offer numerous advantages, they also introduce potential vulnerabilities. This calls for organizations considering digital transformation to recognize their security posture extends beyond traditional network boundaries. We’ll explore key practices in gaining assurance over the security of third parties for digital transformation projects.
A Risk Based Security and Resilience Evaluation Consider the importance of the information, or services, being handled by the vendors as part of your digital transformation project. Ask yourself what protections you have in place today for those information or services, and seek to understand if the vendors can at least match them. It may call for some compromise over the design of controls, but exercise caution if it means growth in risk. Get assurance where it matters. While they may have scalable cloud capabilities, it may be continuity and recovery where your focus lands. Match controls to threat scenarios. Consider the risk you’re willing to accept. Cloud Shifts Responsibilities The use of cloud service providers (CSPs) is a common element of digital transformation. While this changes the dynamic of security responsibilities, it never removes it. Software as a Service (SaaS) will have the customer responsible for Identity and Access Management, data classification, and some application security configuration. Platform as a Service (PaaS) also requires the customer consider penetration testing and software development security. Infrastructure as a Service (IaaS) provides the most freedom, such as resources to deploy operating systems and software, and customers may be responsible for its patching, network security, and even host infrastructure security, in addition to software, access, and data security. All of this comes with cost, necessitates expertise, and shifts risk. Contractual Obligations and Accountability Establishing clear contractual obligations, that match your regulatory obligations, is another critical aspect when dealing with third parties. Contracts should explicitly outline security expectations, data retention, sharing, include breach notification requirements, define roles and responsibilities, and specify which party is responsible for different security measures. Consider incorporating clauses that mandate vulnerability assessments, penetration testing, and periodic security audits to provide assurance over the design and operating effectiveness of their controls, and consider the right to audit. To ensure accountability, consider the inclusion of recovery of loss in the event of a security incident. Regularly review and update contracts to align with evolving security standards and industry best practicesBy investing in third-party security, organisations can identify weaknesses, mitigate risks, and partner in success
I agree We use cookies on this website to enhance your user experience. By clicking any link on this page you are giving your consent for us to set cookies. More info