The pace of cloud computing adoption will accelerate as more organizations explore hybrid IT strategies. CIOs and CTOs will fine-tune the mix of on-premises and managed cloud services for their user's varied applications and workloads.

Worldwide spending on public cloud services and infrastructure will more than double over the 2019-2023 forecast period, according to the latest market study by International Data Corporation (IDC).

With a five-year compound annual growth rate (CAGR) of 22.3 percent, public cloud spending is forecast to grow from $229 billion in 2019 to reach nearly $500 billion in 2023.

Public cloud service market development

"Adoption of public (shared) cloud services continues to grow rapidly as enterprises, especially in professional services, telecommunications, and retail, continue to shift from traditional application software to software as a service (SaaS) and from traditional infrastructure to infrastructure as a service (IaaS) to empower customer experience and operational-led digital transformation initiatives," said Eileen Smith, program director at IDC.

SaaS will remain the largest category of cloud computing, capturing more than half of all public cloud spending in throughout the forecast period. SaaS spending, which is comprised of applications and system infrastructure software (SIS), will be dominated by applications purchases.

The leading SaaS applications will be customer relationship management (CRM) and enterprise resource management (ERM). SIS spending will be led by purchases of security software and system and service management software.

Infrastructure as a service (IaaS) will be the second largest category of public cloud spending. IaaS spending, comprised of servers and storage devices, will also be the fastest growing category of cloud spending with a five-year CAGR of 32 percent.

Platform as a service (PaaS) spending will grow nearly as fast (29.9 percent CAGR) led by purchases of data management software, application platforms, and integration and orchestration middleware.

Three industries – professional services, discrete manufacturing, and banking – will account for more than one-third of all public cloud services spending throughout the forecast period. While SaaS will be the leading category of investment for all industries, IaaS will see its share of spending increase significantly for industries that are building data and compute-intensive services.

For example, IaaS spending will represent more than 40 percent of public cloud services spending by the professional services industry in 2023 compared to less than 30 percent for most other industries. Professional services will also see the fastest growth in public cloud spending with a five-year CAGR of 25.6 percent.

On a geographic basis, the United States will remain the largest public cloud services market, accounting for more than half the worldwide total through 2023. Western Europe will be the second largest market with nearly 20 percent of the worldwide total.

China will experience the fastest growth in public cloud services spending over the five-year forecast period with a 49.1 percent CAGR. Latin America will also deliver strong public cloud spending growth with a 38.3 percent CAGR.

Outlook for cloud service applications growth

Very large businesses will account for more than half of all public cloud spending throughout the forecast period, while medium-sized businesses will deliver around 16 percent of the worldwide total.

Small businesses will trail large businesses by a few percentage points while the spending share from small offices will be in the low single digits.

Moreover, all the company size categories – except for very large businesses – will experience spending growth greater than the overall market.

Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases? Attend the Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London and Amsterdam to learn more.

Forbes has put out its latest Cloud 100, and while payments provider Stripe remains top of the shop the big five has a refreshing feel to it.

Stripe remains at #1 for the third successive year in the media firm’s list of private cloud companies – as in cloud companies which are privately held – while behind it the top five consists of data warehouse Snowflake, robotic process automation (RPA) provider UiPath, infrastructure automation firm HashiCorp, and data analytics company Datadog.

Part of this turnover is down to a strong year of exits. No fewer than five of last year’s top 10 went public over the past 12 months; Slack, Zoom Video Communications, CrowdStrike, Elastic and Eventbrite. In addition, Qualtrics, which placed at #7 last time out, was acquired by SAP for $8 billion (£6.2bn) in November. Looker, which ranked just outside the top third (#34) in 2018, was acquired by Google for $2.6bn while Cylance, ranked #18, was bought by BlackBerry.

UiPath is a particularly interesting case. Last year’s list saw the company debut at #14, with Forbes admitting its rise ‘absolutely came out of left field.’ In a statement acknowledging its bronze medal, CEO Daniel Dines said the company ‘could not have achieved this kind of growth and success without teams around the world, investors who are true partners, and customers and partners who have bet on [their] automation technology to transform their businesses.’

As before, the Cloud 100 is put together alongside Bessemer Venture Partners and Salesforce Ventures. The investors do have skin in the game in certain cases; cloud CRM software builder Vlocity, ranked at #24, received a $60 million series C funding round in March to which Bessemer and Salesforce both contributed. The hopefuls were whittled down based on growth, sales, valuation and culture, as well as consultation from 40 CEOs at publicly-held cloud companies.

The list was praised by Forbes as being the ‘strongest and most diverse’ group of companies assembled yet. “Though infrastructure and development companies lead the way on the 2019 Cloud 100 list, design tools are making a move and no-office, fully remote setups are gaining traction,” the company wrote.

In terms of what the companies do, this holds a strong case. Plenty of big data and backend-facing companies now infiltrate the top end of the rankings, which could be seen as affirmation of the money getting behind it. Snowflake secured a mammoth $450 million funding round back in October, while Apache Kafka software provider Confluent, which made the top 10, was valued at $2.5 billion following a $125m series D round in January. Rubrik, Cloudflare and Databricks – which nabbed $250m in series E funding in February – also made the top 20.

While it means fewer fluffy SaaS and B2C cloud apps are taking the honours, the diversity charge struggles when it comes to who runs the Cloud 100. Only four CEOs in the 100 are female, with two – Nicole Eagan and Poppy Gustafsson at Darktrace – at the same company. Melanie Perkins, CEO of Canva, and Rachel Carlson, chief executive of Guild Education, complete the set.

This appears to be a recurring challenge for Forbes; the company’s list of 100 most innovative leaders earlier this month featured a grand total of one woman. Barbara Rentler, CEO of Ross Stores, placed #75 and was not even afforded the luxury of a photo. Forbes has since taken its medicine; editor Randall Lane noted the disparity of women chief executives as a contributor to the ‘flawed’ methodology behind the list.

The top 10, in descending order, are Stripe, Snowflake, UiPath, HashiCorp, Datadog, Procore, Tanium, InVision, Rubrik and Confluent. You can see the full list here.

Postscript: The 2019 Cloud 100 already has its first graduate; Cloudflare has gone for IPO, with the NYSE doing the honours earlier today.

Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases? Attend the Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London and Amsterdam to learn more.

The impact of cloud-native readiness on applications, which are mostly orchestrated using Kubernetes, can be seen on VMware’s announcements at the recent VMworld 2019. This made it clear to the IT world that focus of IT infrastructure has shifted to containerisation from virtualisation. Going cloud-native and shifting workloads on top of Kubernetes clusters is a key trend being followed by the industry.

CNCF (Cloud Native Computing Foundation) has shown the aggression to push their projects to enterprise IT infrastructure and telecom service providers to build the core of data centres using new containerised and microservices methods.

NFV and telecom use cases have also started shifting to a cloud-native landscape in the last two years. NFV techniques have help CXOs move to the software-defined and centric data centre with virtual network functions (VNFs) as core elements, being orchestrated using VNF managers (VNFM). The VNF's orchestration can be done using commercial VNFM platforms offered by Nokia, Cisco, Ericsson, Huawei, and NEC; and an open-source platform like OpenStack Tacker. Now with the cloud-native movement in the IT domain, VNFs are becoming cloud-native network functions (CNFs).

Cloud-native development of network functions:

• Makes applications or code portable and reusable – in other words can be repetitively used independent of the underlying infrastructure
• Allows the application to scale up and down where there is demand
• Can be deployed with microservices way but not mandatorily
• Is suitable for elastic and distributed computing environments

Cloud-native development also enables NFV to embrace DevOps, agile techniques, and more importantly allows container orchestration engines like Kubernetes to handle workloads – which also means that more dynamism comes into the picture at the core stack of NFV.

Earlier, CNFs were in evaluation phase to check for readiness by several vendors and service providers to be used in NFV use cases. In 2018, I wrote about the benefits of deploying network functions in containers and being architected using microservices. Also, I wrote on why cloud-native VNFs are important in NFV success.

The below image shows how VNFs were managed in the past, how it is currently managed along with CNFs, and showing how Kubernetes can be a de facto framework to handle network functions and applications pushed into CNFs and VNFs.

Kubernetes in the picture

We can now see how Kubernetes has evolved so much in the data centre of every size for handling every workload type. Kubernetes is also becoming a choice to orchestrate workloads at edges as well. We have seen several collaborations for new solutions for 5G that specifically focused on handling containers using Kubernetes and legacy virtual machines using OpenStack.

There are several ways Kubernetes can be useful for NFV use cases for handling network functions and applications. Kubernetes can be useful in hosting all cloud-native software stack into the clusters.

If you are a software or solution provider, Kubernetes can help you orchestrate all workload types like VNFs, CNFs, VMs, containers, and functions. With Kubernetes, it has become possible for all workloads to co-exist in one architecture. ONAP is leading service orchestrator and NFV MANO platform to handle services deployed in NFV. A Kubernetes plugin specifically developed for ONAP makes it possible to orchestrate different services and workloads cater through multiple sites.

ONAP has challenges in terms of installation and maintenance, while concerns have also been noted related to heavy consumption of resources like storage and memory. To work along with Kubernetes, ONAP release a lightweight version, which will fit with many NFV architectures. It is called ONAP4K8S. Requirements and package contents are published on its profile page.

There can be cases where it is not possible to completely get away from virtual machines. Some of the existing functions need to reside with virtual machines and cannot be containerised. For such cases, Kubernetes community KubeVirt and Mirantis’s Virlet frameworks can be integrated to dynamically manage virtual machines along with containers. Kubernetes also becomes a choice for enabling orchestration at the edge of the network. Kubernetes based control plane uses less number of resources that makes it suitable for edge nodes even with one server.

Cloud-native NFV stack

The Akraino edge stack is hosting a blueprint, Integrated Cloud Native (ICN) NFV Stack, under which all developments of making NFV core cloud-native are in progress. The current progress of integrating open-source cloud-native projects for NFV stack is shown below:

Srinivasa Rao Addepalli (senior principal engineer and chief architect at Intel) and Ravi Chunduru (Associate Fellow, Verizon) will be presenting a session at the upcoming Open Networking Summit Europe 2019 on how Kubernetes can be used at core of NFV and how Linux Foundation communities (ONAP, OPNFV, CNCF, LFE) are doing efforts to make NFV core a cloud-native.

Editor's note: Download Calsoft’s eBook – A Deep-Dive On Kubernetes For Edge – which focuses on current scenarios of adoption of Kubernetes for edge use cases, latest Kubernetes and edge case studies, deployment approaches, commercial solutions and efforts by open communities.

Image sources: https://events.linuxfoundation.org/wp-content/uploads/2018/07/ONS2019_Cloud_Native_NFV.pdf

The post How is Kubernetes Leading the Game in Enabling NFV for Cloud Native? appeared first on Calsoft Inc. Blog.

Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases? Attend the Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London and Amsterdam to learn more.

Lacework, a provider of end-to-end cloud security automation across the biggest public clouds, has raised $42 million (£34m) in a financing round aimed at building momentum and educating security teams.

The funding, which was put together by Sutter Hill Ventures and Liberty Ventures, will be aimed at ‘supporting product innovation and go-to-market activities to help educate security, compliance and DevOps teams that want a way to embed security continuously through build-time to run-time operations’, as the company puts it.

Lacework’s platform covers both public and private cloud, aiming to automate overall cloud security and compliance while providing comprehensive risk assessment across cloud workloads and containers. The company promises ‘unprecedented visibility, automating intrusion detection, delivering one-click investigation, and simplifying cloud compliance.’

The company appears to be in solid hands when it comes to its funders, with Sutter Hill Ventures having already bet this year on Vlocity – leading a $60 million series C round in March – as well as participating in a series D round for network monitoring and intelligence firm ThousandEyes. Yet Lacework may be the horse to bet on from this stable. Sutter Hull managing director Stefan Dyckerhoff was previously CEO of Lacework, and combined the leading roles at both companies before passing on the chief exec’s role in June.

The new CEO is Dan Hubbard, previously chief product officer, while Andy Byron, previously of Cybereason and Fuze, is joining as president to lead Lacework sales and marketing teams.

“Our new funding, new perspectives on the board of directors, and with Andy joining, are all going to be critical for how we build on our solid foundation as a cloud and container security leader,” said Hubbard. “Lacework and our growing list of customers agree that there is a need for a new generation of security companies that are purpose-fit to secure today’s modern infrastructure.”

Lacework has gained two other board members, with Mike Speiser, partner at Sutter Hill, and John McMahon, currently on the board of data warehouser Snowflake, joining. Speiser argued that the goal was for Lacework to become ‘the Snowflake for security'. “It’s clear that DevOps and security teams want a single platform for their security and compliance needs, and only Lacework provides that,” said Speiser.

It's worth noting that Snowflake trousered a whopping $450 million in its last funding round, back in November – so perhaps there is a little while to go before Lacework gets to that point.

Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases? Attend the Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London and Amsterdam to learn more.

Keumars Afifi-Sabet

Keumars Afifi-Sabet

Bobby Hellard

The demands of today’s tech-savvy customer have placed huge emphasis on software development and user experience as a barometer for success. DevOps adoption has grown rapidly as a result, with many businesses looking at routes to either introduce or accelerate DevOps workflows within their IT organisations.

‘Tool chains’ are an integral part of any DevOps programme, helping automate the delivery, development, and management of software applications and deliver better products to both customers and business units, more efficiently and effectively. The collaborative nature of these development and production environments makes them difficult to protect however, particularly the privileged accounts and secrets associated with them.

Navigating this risk and securing key tools and infrastructure is therefore critical if organisations are to achieve successful DevOps outcomes and progress on their digital transformation journeys. To do so, there are five key measures they must consider to prioritise protection of DevOps tools and processes:

The crucial importance of selection and configuration policies

Any security conversation should always begin a full inventory of the DevOps tools being used by dev teams. After all, it’s impossible to defend environments if you don’t know they exist. This process can be cumbersome, but is massively important for open source tools.

Once these tools are accounted for, security teams should undertake an evaluation to identify any existing security deficiencies and address them promptly. This could involve making sure tools are not being used in an unsecure default configuration for example, and that they are kept up to date.

As part of this evaluation process, security teams should also find a way to get a seat at the table. That means collaborating with the group with the business that is responsible for tool selection and configuration, or working closely with IT procurement to select the best tools for the organisation so that enterprise security standards are established at the outset.

Keep your DevOps tools on lockdown

Attackers only need to exploit one vulnerability to carry out their mission, so it’s important to take a holistic approach to addressing security requirements and potential vulnerabilities. This starts with securing the secrets and credentials associated with DevOps and cloud management tools in an encrypted vault protected with multi-factor authentication (MFA).

Once complete, access privileges should be reviewed so that users are only granted “just in time” access. In other words, provide high-level access only when it’s needed to perform certain tasks, and ensure that this temporary usage is closely monitored.

Access to high-risk commands within DevOps tools should also be limited. For instance, Docker users often run a Docker container with the —privileged flag, which provides the container with direct access to host elements. Where possible, security teams should mandate that users are not able run containers with this flag, and if it’s a “must,” severely limit user access and monitor and record all activities with the –privileged flag.

Once you have addressed access, it’s also advisable to adopt other cyber hygiene best practices, such as setting up access controls that segregate DevOps pipelines. This prevents attackers from gaining access to one and then moving to another, ensuring that credentials and secrets are not shared between DevOps tool accounts and Windows sysadmin accounts. It also removes all unnecessary accounts with access to DevOps tools, including those of developers who may have changed roles or no longer require access to these tools.

Manage the proliferation of privilege

Enforcing the principle of least privilege should be a requisite for every company. Doing so limits each user’s level of access to DevOps tools to the minimum necessary for their role. However, it will be less effective unless security teams configure DevOps tools to require dual authorisation for certain critical functions. They should for example require that a second person must review and approve any changes before a change to a Puppet manifest file goes live.

Additionally, teams should ensure separation of duties for build automation tools such as Jenkins, which often retain permission to perform all duties without restriction, from building and testing to packaging. In the case of Jenkins this problem can be overcome by separating duties by implementing multiple Jenkins nodes, each dedicated to one function (build or test or package) for each application.

This ensures each node will have a unique identity and a limited set of privileges, which minimizes the impact of a potential compromise.

Keep your secrets safe in code repositories

Code repositories such as GitHub have become infamous in recent years due to IT teams erroneously leaving code in publicly accessible locations. Security teams should therefore develop risk-based policies for developers that secure the use of such repositories.

It’s worth noting however that beyond credentials, code may contain details about the organisation’s internal network that could be useful to attackers. Ideally firms should therefore use an on-premises rather than a cloud-based code repository, if it’s possible to do so without adversely affecting workflow.

If this approach is applied, then the next step is to scan the environment to make sure that any on-premises code repositories are inaccessible from outside the network. If cloud-based repositories are used however, then security teams should ensure they are configured to be private.

Above all, every organisation should make it their policy that code is automatically scanned to ensure it does not contain secrets before it can be checked in to any repository.

Invest in the protection of your infrastructure

Cyber attackers seek the path of least resistance, and for many organisations, this remains their employees. Well-crafted phishing emails can often do the trick, so IT teams should make sure that all workstations and servers undergo regular patching, vulnerability scanning and security monitoring.

Away from hardware, it’s also important to monitor your cloud infrastructure for signs of unusual credential usage or configuration changes (such as making private data stores public). This means ensuring VM and container images used in development and production environments come from a sanctioned source and are kept up to date.

To ensure security remains “baked in” to countless rounds of automatic rebuilds, security teams should also work with their DevOps counterparts to automate the configuration of VMs and containers so that, when a new machine or container is spun up, it is automatically configured securely and given appropriate controls – without requiring human involvement.

The benefits of DevOps are plain and clear for all to see – hence the rapid adoption that we have witnessed in recent years. Adopting a DevSecOps approach, using the measures outlined above, is critical to ensuring application and infrastructure security from the outset of any software development activity.

Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases? Attend the Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London and Amsterdam to learn more.

Google Cloud has announced the launch of Cloud Dataproc on Kubernetes, adding another string to the bow for the product which offers a managed cloud service for running Apache Spark and Hadoop clusters.

Google – which originally designed Kubernetes before handing it to the Cloud Native Computing Foundation (CNCF) – is promising ‘enterprise-grade support, management, and security to Apache Spark jobs running on Google Kubernetes Engine clusters’, in the words of a blog post confirming the launch.

Christopher Crosbie and James Malone, Google Cloud product managers, noted the need for Cloud Dataproc to utilise Kubernetes going forward. “This is the first step in a larger journey to a container-first world,” Crosbie and Malone wrote. “While Apache Spark is the first open source processing engine we will bring to Cloud Dataproc on Kubernetes, it won’t be the last.

“Kubernetes has flipped the big data and machine learning open source software world on its head, since it gives data scientists and data engineers a way to unify resource management, isolate jobs, and build resilient infrastructures across any environment,” they added. “This alpha announcement of bringing enterprise-grade support, management, and security to Apache Spark jobs on Kubernetes is the first of many as we aim to simplify infrastructure complexities for data scientists and data engineers around the world.”

To say Kubernetes is not a major priority for both vendors and customers would be something of a falsification. The recent VMworld jamboree in San Francisco two weeks ago saw the virtualisation giant launch a major attack on the product, with the primary launch being VMware Tanzu, a product portfolio which looked at enterprise-class building, running and management of software on Kubernetes.

As this publication put it when KubeCon and CloudNativeCon hit Barcelona back in May, it was a ‘milestone’ for the industry. Brian Grant and Jaice Singer DuMars certainly thought so; the Google Cloud pair’s blog post at the time agreed Kubernetes had ‘become core to the creation and operation of modern software, and thereby a key part of the global economy.’

The goal now is to get the most out of it, whether you’re an enterprise decision maker or developer alike. Writing for CloudTech last month Ali Golshan, co-founder and CTO at StackRox, noted the acceleration in user deployments. “Despite the fact that container security is a significant hurdle, containerisation is not slowing down,” Golshan wrote. “The advantages of leveraging containers and Kubernetes – allowing engineers and DevOps teams to move fast, deploy software efficiently, and operate at unprecedented scale – is clearly overcoming the anxiety of security concerns.”

Golshan also noted, through StackRox research, that Google still ranked third among the hyperscalers for container deployments in the public cloud but had gained significantly in the past six months.

“Enterprises are increasingly looking for products and services that support data processing across multiple locations and platforms,” said Matt Aslett, research vice president at 451 Research. “The launch of Cloud Dataproc on Kubernetes is significant in that it provides customers with a single control plane for deploying and managing Apache Spark jobs on Google Kubernetes Engine in both public cloud and on-premises environments.”

Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases? Attend the Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London and Amsterdam to learn more.

Microsoft has announced the launch of new Azure availability in Germany and Switzerland, citing increased data residency and security concerns as key to European expansion.

Azure is now available from cloud data centre regions located in Zurich and Geneva, for the Switzerland release announced at the end of last month, while Germany’s newest regions are in the North and West Central zones, in Berlin and Frankfurt respectively.

The communications announcing the Germany and Switzerland releases, from Azure corporate vice president Tom Keane, were almost identical, save swapping out a customer story here and stock photo there. Among Microsoft’s German customers are Deutsche Bank, Deutsche Telekom and SAP, while Swiss companies utilising Azure include Swisscom, insurance firm Swiss Re, and wealth manager UBS Group.

Customers in Germany are promised compliance specific to the country, including C5 (Cloud Computing Compliance Controls Catalogue) attestation. Alongside Office 365, Dynamics 365 and Power Platform, customers will be able to benefit from containers, Internet of Things (IoT), and artificial intelligence (AI) solutions, Microsoft added.

“These investments help us deliver on our continued commitment to serve our customers, reach new ones, and elevate their businesses through the transformative capabilities of the Microsoft Azure cloud platform,” wrote Keane.

Microsoft is not the first hyperscaler to hoist its flag atop Switzerland, with Google opening its Zurich data centre region back in March. Both Google and AWS have sites in Frankfurt, with AWS first to launch there back in 2014.

This is not the end of the European expansion for Microsoft, with two new regions in Norway planned. The sites, in Stavanger and Oslo, are set to go live later this year.

Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases? Attend the Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London and Amsterdam to learn more.