Data security is top of mind for all organisations, with breaches having regulatory implications such as fines as well as potential reputational damage. This issue is, however, especially high on the agenda of governmental organisations, given the sensitivity of the data that they work with and the important role they play in society. Consequently, for a long time on premise or private cloud strategies were the only option. This situation, however, is starting to change.
In this blog
Read further below 👇
In the Netherlands, the Rijksbreed Cloudbeleid (the National Cloud Policy) was approved in late 2022. It explains the conditions under which governmental entities may, with some exceptions, use public cloud services. Despite this approval, many of these entities remain reluctant to embrace public cloud technology. In Dutch, this is commonly referred to as having ‘Cloudwatervrees’.
Similar to the English saying, ‘Koudwatervrees’ means 'getting cold feet’. ‘Cloudwatervrees’ is a play on this saying. It refers specifically to the fear of plunging one’s organisation into the public cloud when not entirely convinced that one’s data will be safe or systems will remain secure. Whereas modern businesses are generally built using public cloud technologies, older organisations that haven’t yet transitioned tend to be a lot more hesitant to trust it.
So why do we like it?
Visma Connect has built its strategy around cloud technology. Moving from virtualisation to private and later to public cloud are evolutionary steps that have made our company what it is today. We embrace a public cloud-first strategy for our customers for several reasons, the most important of which are summarised below. A more detailed technical breakdown can be found in the blogpost Unpacking our preference for Public Cloud Architecture.
|
Why public cloud |
What Visma Connect does |
|
|
Shared Security and Enhanced Protection |
Shared responsibility, economies of scale | Visma Cloud Delivery Model (VCDM) compliance means automatic ISO27001 and ISAE 3402 Type II certification |
|
Data Sovereignty & GDPR Compliance |
You can choose where data is stored and how it is processed | Use European data centres and incorporate EU principles around pulling vs. pushing data into our architecture |
|
Avoiding Vendor lock-in |
Containerisation has made it easier to migrate between providers | Select software components with an exit strategy in mind |
|
Managed Services |
Faster deployment and time-to-value, avoids over-provisioning your system | Create added value for our customers by focusing on functionality and shorter lead times. |
|
Serverless Technology |
Run on-demand, cost-effective for low or fluctuating data volumes | Tune when to use serverless technology and when to configure clusters - incorporate volume expectations into solution design and monitor against actual usage |
|
Elastic Scaling |
Resources can be dynamically adjusted to meet demand patterns, reducing costs and CO2 emissions | Select tools with service and operational costs in mind |
|
Greener Footprint |
The large public cloud providers have higher server utilisation rates and ambitious climate goals | Tune when to use serverless technology and when to configure clusters - incorporate client emission reduction targets into solution design |
Frontrunners within the banking industry
Once considered too risky, the public cloud is now demonstrably secure, even for highly regulated industries. Take the banking sector, for example. The banking industry's shift to the public cloud wasn't without its challenges. Strict security regulations and the inherently sensitive nature of financial data demanded a cautious approach. However, banks navigated this transition by implementing robust encryption protocols, adhering to strict compliance standards, and leveraging the cloud providers' advanced security infrastructure. This, combined with the cloud's scalability and cost-efficiency, ultimately outweighed the initial concerns, paving the way for a successful migration for many financial institutions. Ohpen, for example, built the world’s first-core banking engine that had all its production data in the cloud. Other frontrunners include Raisin Bank, one of the first all-cloud banks in Germany and Capital One, the first major financial institution in the United States to shift completely to public cloud.
Conclusion
We believe that using a public cloud environment is better for our customers. Our systems remain highly available and resilient while operating at a lower cost and with a lower carbon footprint. Our ability to run a public cloud environment as securely as a private cloud environment opens the door for a broader range of customers to make this transition.
