410m-microservices-security-market-validation-and-the-cicd-pipeline

 

Continous_Delivery_by_Jez_Humble_and_David_Farley_sketch-cartoon

 

Much like the industrial revolution witnessed massive production acceleration with the advent of the assembly line, so too has the onset of continuous integration and continuous delivery been bolstered by the arrival of microservices. These services exist at the core of the CICD pipeline and recently the microservices security market has received a massive validation with the acquisition of Twistlock by Palo Alto Networks.

 

As consumers in the 21st century demand more and more customization for their litany of unique wants and needs, the old school method of software development was bound to give way to a new and better process that enabled reaching that goal. Recently, within the last 5 years or so, the software industry has shifted away from a monolithic culture to one embracing microservices. The microservices industry has been steadily gaining traction and we have witnessed the rise of companies like Docker and Kubernetes that support this new mindset. The new approach has many benefits such as the ability to deploy independently, scale up and maintain each component while simultaneously parallelizing development across numerous teams.

 

About the Microservices Market

Rapid, lightweight and lean development practices have permeated the industry psyche. In contrast to monolithic software development where massive deployments are followed by countless glitches and errors, microservices are smaller in size and are created for singular use cases. Effectively, they are more sniper targeted applications that are faster to iterate, have less moving parts to incur the wrath of Murphy’s Law, and allow for assembly line like specialization.

 

In economic terms, the benefits of specialization allotted by microservices is leading to greater efficiency. The comparative advantages developing between services is driving both increased returns of scale as well as economies of scale. With history as a predictor, we are likely to continue witnessing the evolution of these benefits.

 

Microservices and Containers

Containers are architectural implementations used to develop and manage microservices. They give a user the ability to create, ship, and run any application on any machine by packaging software with everything it needs to run. They are completely isolated from any other software that runs concurrently in the same environment. Furthermore, they let different teams develop different microservices simultaneously. Additionally, containers allow for the ability for both associated and non-associated teams to share in and utilize each others’ productions. Due to their power and flexibility, both containers and microservices have become popular and well regarded tools in DevOps communities.

 

That said, microservices are not without their challenges. One case in point is security. With so many iterations of code and snippets along with increased sharing, the complexities of security can begin to mount. More moving parts means more chances for failure. The more a containerized application is shared, the more chances it has to become tampered, regardless of intent. In traditional monolithic organizations you would run penetration and security tests, but with the speed of delivery, there’s no time for that in DevOps. To complicate matters further, microservices vastly increases the number of ports used in a project leaving significantly more doors to continuously check and prevent bad actors from entering through. Thus it is the burgeoning industry is in need of good security solutions.

 

Details of the Deal

It has been a point of dispute whether or not microservices security is in fact a separate solution and its own industry. However, with the recent $410 million acquisition of container security company, Twistlock, by Palo Alto Networks, the market is validated and happening. To boot, the chairman and CEO of Palo Alto Networks, Nikesh Arora, was quoted as saying they will be integrating the new assets “as soon as possible.”

 

Dror Davidoff, co-founder and CEO of Aqua Security, another container security company, noted that the acquisition demonstrates that customers view container/cloud-native security “as critical to their environments”. He furthered by saying, “The acquisition price is very high for a space that is still only about 4 years old, and a major security player demonstrated with their checkbook that the early movers have a significant advantage (or they would have tried to develop it themselves).”

 

Future Outlook for Global Cloud Microservices

According to market research firm MRFR, the global cloud microservices market is forecasted to be valued at $2.1 billion in 2023, which is a CAGR of 25.0% up from 2017’s market value of $580 million. Some of the major factors driving the market’s growth include:

 

  • Continued microservices architecture proliferation
  • Increased adoption of cloud services
  • Rising demand for secure IT operations
  • Increased enterprise demand for data security through private cloud applications
  • Drive to reduce costs in on-premise IT deployments

 

Microservices Asset Integrity and Blockchain Immutability

At present, CodeNotary is the only player in the market who is delivering DevOps and microservices asset integrity utilizing blockchain technology. It’s vcn tool adds continuous trust to the DevOps process, containers, and Kubernetes environments and instantly verifies the integrity of code, /images/blog, containers, documents, backups, and more. CodeNotary leverages the Zero Trust Consortium’s blockchain and delivers:

 

  • Immutability
  • Scalability
  • Speed
  • High throughput
  • Low cost
  • Distributed governance

 

Click below to secure your DevOps’ microservices assets and CICD pipeline with a test drive of CodeNotary’s solution.

 

 

Yes, Show Me How

 

REFERENCES

https://www.sdxcentral.com/articles/news/palo-alto-networks-buys-twistlock-puresec-in-410m-deal/2019/05/

https://martinfowler.com/articles/microservice-testing/

https://stackify.com/microservices-containers/

https://www.prnewswire.com/news-releases/1-8-billion-cloud-microservices-market—global-forecast-to-2023–300665538.html

https://www.marketwatch.com/press-release/cloud-microservices-market-size-2018-global-trends-industry-share-growth-drivers-business-opportunities-and-demand-forecast-to-2023-2019-02-13

https://www.csoonline.com/article/3268922/why-securing-containers-and-microservices-is-a-challenge.html

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.