As businesses embrace digital transformation, many are interested in cloud-native architectures to support their work. Cloud services can help with scalability and connectivity, but like any change, it comes with challenges that must be managed.
As we are cloud-native, we thought there was no better person to talk to about the benefits and risks than our own CISO, Ben Trethowan MSc CITP CISSP CISM.
Ben is an accomplished hands-on Cyber Security leader, with extensive experience working in the Financial Services, Entertainment, Transport and Defence sectors. He has led Cyber activities at all levels, from governance and strategy to transformation and technical implementation, and continues to expand his skills through both academic and professional development.
He is also a trustee (and longstanding volunteer) for The National Museum of Computing at Bletchley Park and serves as a Police Support Volunteer within the Cyber Crime Unit of his local Police force.
As a leading figure on cloud-native services, he has spoken at many conferences including;
Being cloud-native means we operate fully in the cloud. It’s relatively rare in financial services, where many organisations are hybrid or even still on-premises. Our approach offers simplicity and consistency – everything resides in one ecosystem, giving us better oversight of our software and security.
Cloud technologies are also hugely useful for innovation, as we get access to a whole toolbelt of pre-built services. We can focus on solving business problems and staying ahead of the market, rather than building the underlying infrastructure to support our strategies.
One of the biggest upsides is visibility. A unified cloud platform lets us view and manage our architecture from a single vantage point and respond to any issues, which is critical for maintaining a secure environment. Still, there are security risks that come with these technologies, even if they give a better view of how we are exposed. The pace of innovation in the cloud means developers and engineers have a great deal of autonomy and responsibility. While cloud providers secure their infrastructure, configuring their services securely falls on us.
At Brit, we believe that overcoming challenges is key to innovation. There are things organisations can do to manage the risks of going cloud-native and reap the benefits.
My team uses two security approaches: proactive and reactive.
On the proactive side, we focus on training and enforcement. We educate our teams on cloud security best practices, so everyone understands their role in maintaining a secure environment. Enforcement is about adding layers of automated control, meaning someone can’t make risky decisions that may breach critical security protocols without getting prior review / approval.
On the reactive side, as I’ve mentioned, visibility is a huge benefit of cloud-native architecture. Because our software is all in one place, we use tools that give us real-time insight into what is going on in the business. These tools detect unusual activity and let us know about it, which means we can respond quickly.
It’s important to prioritise those vulnerabilities that pose significant threats to the business. We take a two-pronged approach:
The goal is for these two perspectives to meet in the middle – the vulnerabilities that are both business-critical and targets for potential attackers. This approach lets us manage risks systematically, starting with the most pressing ones.
Identity is the concept that every person, machine or service accessing our system obtains a certain level of trust. Identities earn that trust – for example, by entering a password – in order to gain access and perform their tasks.
Our identities get the minimum access needed to perform their tasks, a principle known as ‘least privilege’. That limits the potential damage if a person’s account is compromised.
Machine identities are important but often overlooked. These are the relationships between machines and services within our architecture, and if compromised, they allow attackers to move laterally within the network. Again, visibility is crucial here – our visibility tools flag if a machine or service is behaving unusually, which means we can investigate whether a security breach has occurred.
Automation is about making the secure way the easy way. For example, a developer who’s trying to create a machine identity – if they’re just working on a test product, they should be able to create that identity without layers of review, but if the product will be customer-facing, additional checks are triggered.
This is a risk-based approach that allows the lowest-risk activities to be approved automatically, while higher-risk ones require more intervention. It’s a bit like the boy who cried wolf – if people trust the system to alert them in proportion with the true nature of the threat, they’re more likely to listen and follow protocol.
Becoming cloud-native isn’t just a technology decision; it unlocks huge potential for innovation. To reap those benefits, security must be embedded at every step in a way that’s easy for your team.
To be agile, businesses need to be the first to market or innovate in some other way, and therefore a zero-risk approach isn’t realistic. Proportional risk-taking, backed by strong security practices, can allow you to innovate safely and stay ahead of your peers.
Ben has outlined the opportunities and challenges of adopting a cloud-native approach, highlighting the importance of visibility, automation, and proactive security strategies. As organisations embrace digital transformation, securing their cloud environments is essential to remain agile and innovative.
To learn more about how cyber insurance can help safeguard businesses against emerging risks that come in the wake of cloud adoption, explore our cyber expertise here.