Should microservices’ security smells stay or get refactored? Towards a trade-off analysis
If you are interested in contributing your experience to the presented research, please share your experience on microservices here: https://forms.office.com/r/mBCfQv0dHK.
Security smells, i.e. possible symptoms of (often unintentional) bad design decisions, can occur in microservice-based applications, resulting in violations of key security properties as well as design soundness (i.e. adherence to microservice design principles). However, it is non-trivial to decide in each case whether to apply a refactoring to mitigate the effects of a smell, or whether it is more convenient to keep the smell in the application, so a careful trade-off analysis must be carried out. To enact such trade-off analysis, we propose a method base on Softgoal Interdependency Graphs (SIGs), a visual formalism that provides a holistic view of the positive/negative impacts of, in our case, security smells and refactorings on software quality attributes and design soundness. (Speaker: Francisco Ponce, Universidad Tecnica Federico Santa Maria, Valparaiso, Chile)