Circle
Events
Blog

Research Topic

Application Containers and Microservices

Latest ResearchWorking Group
Microservices Architecture Pattern
Microservices Architecture Pattern

Download

Application Containers and Microservices
Application containers and a microservices architecture, as defined in NIST SP 800-180, are being used to design, develop and deploy applications leveraging agile software development approaches such as DevOps. The security of application components needs to be considered throughout the Software Development Life Cycle. The use of containers and microservices have been increasingly implemented in organizations. This increase in popularity can be attributed to the ease with which they move through a lifecycle allows for efficient restart, scale-up or scale-out of applications across clouds. However, these unique characteristics also mean there are distinct security ramifications which must be considered.

What are microservices? 
The next evolution of the application architecture is the “service-oriented architecture” (SOA). In SOA, the entire gamut of solutions (e.g. supporting a business process) is broken up into multiple parts or components called services. The design of a microservices architecture is intended to address the limitations of SOA by enabling the individual microservices to communicate with each other using lightweight protocols such as Representational State Transfer (REST). Furthermore, the individual microservices can be developed in platforms best suited for them, allowing for heterogeneity in addition to independent scalability and deployment due to loose coupling between individual microservices. 

What are the security risks associated with microservices?
This new approach presents new security challenges such as an increased attack surface due to an increase in the number of components and secure service discovery as a result of the dynamic nature of service instance due to location changes.

Who should read the research produced by this group?
This group assumes that readers have some knowledge of operating system, networking, and security expertise, as well as expertise with application containers, microservices and agile application development approaches such as DevOps. 

Please note that this project is a subgroup of the DevSecOps working group. To participate you can join our DevSecOps community and let the leaders know you are interested in this particular area of DevSecOps.

Application Containers and MicroservicesDevSecOpsServerless

Discuss this topic in Circle

Have an interesting article or video on this topic that you want to share? Anyone can join the discussion community for this topic to share ideas or ask questions.

View discussion community

Participate in Application Containers and Microservices Research

This working group is a subgroup of the DevSecOps working group. The mission of this subgroup is to conduct research on the security of application containers and microservices and publish guidance and best practices for the secure use of application containers and microservices.

View the working group

Securing Application Containers and Microservices

CSA Research crowd-sources the knowledge and expertise of security experts and helps address the challenges and needs they’ve experienced, or seen others experience, within the cybersecurity field. Each publication is vendor-neutral and follows the peer review process outlined in the CSA Research Lifecycle. We recommend getting started by reading the following documents.

Microservices Architecture Pattern

Microservices Architecture Pattern

This document serves to propose a repeatable approach to architecting, developing and deploying Microservices as a “MAP” (Microservices Architecture Pattern). The proposed MAP contains all the information necessary for a microservice to operate independently and communicate with other microservices which, in aggregate, become capabilities which, in turn, become the components of an application. This paper describes the key elements of the MAP, how they should be designed and deployed, shifting security & compliance left via a continuous compliance-as-code approach. 

Best Practices for Implementing a Secure Application Container Architecture

Best Practices for Implementing a Secure Application Container Architecture

Learn CSA’s recommendations and best practices to address the challenges in securing application containers in the engineering of trustworthy secure systems. This document is intended to be a companion document to Challenges in Securing Application Containers and Microservices as it provides recommendations and best practices to address those challenges. Recommendations were developed through extensive collaboration among a diverse group with strong knowledge and practical experience in information security, operations, application containers, and microservices.

Best Practices in Implementing a Secure Microservices Architecture

Best Practices in Implementing a Secure Microservices Architecture

Learn best practices for securing microservices in the engineering of trustworthy secure systems. This paper provides the background for the evolution of the microservices architecture, its advantages compared with the previous architectures and the new challenges posed in terms of configuration and security. It also describes the benefits of microservices architecture and provides specific use cases where it enjoys advantages over “service-oriented architecture” (SOA. The security and configuration challenges identified for microservices architecture forms the basis for the issues addressed in the rest of this document.

Webinars

Automatically Prioritize Vulnerabilities Using Runtime Intelligence
Automatically Prioritize Vulnerabilities Using Runtime Intel...

July 19 | online

Learn more

Combating Ransomware 2.0: Beyond Backups
Combating Ransomware 2.0: Beyond Backups

June 28 | online

Learn more

Is the security team the bottleneck to remediation?
Is the security team the bottleneck to remediation?

June 20 | online

Learn more

The real way to secure from code to runtime (without breaking development)
The real way to secure from code to runtime (without breakin...

June 16 | online

Learn more

Blog Posts

Definitive Guide to Kubernetes Admission Controller
How to Secure Kubernetes Pods Post-PSPs Deprecation
Why Cloud Native Requires a Holistic Approach to Security and Observability