Essay: Security of Microservices-based Applications #933
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Essay: Security of Microservices-based Applications (MSAs)
Security on MSA's Layers Communication, Application and Service Orchestration
Members
Felix Seifert (fseifert@kth.se)
GitHub: felix-seifert
Proposal
To focus more on the security of microservices-based applications (MSAs) and strengthen the presence of DevSecOps, I want to describe the need of securing three layers of MSAs and ideas on how to implement them: communication, application and service orchestration.
Suitability of Topic
Martin mentioned the suitability of MSAs during the lecture. Furthermore, a specific GitHub issue mentions it. In addition to the suitability of project works about MSAs, the importance of security is already tremendously big and is an important part of DevSecOps.