Answers are grounded in this paper and cite their sources.
In this paper, we identify security threats in a microservice-based application using the STRIDE framework. The study addresses the question of how the architecture of STRIDE procedure, which is aligned with Data Flow Diagram (DFD) trust boundaries, can support early threat identification in microservice architecture. STRIDE methodology is used for categorizing security threats based on six criteria: identity spoofing, data falsification, denial of action or responsibility, information disclosure, denial of service, and privilege escalation. In addition, STRIDE enables assessment of the severity and status of the identified threats. The research relies on the creation of microservice architectural model created in draw.io and DFD of application that was constructed with Microsoft Threat Modeling Tool. Applied to the case study system, the procedure identified 52 threats that were dominated by Spoofing (29%) and Denial of Service (25%), followed by Elevation of Privilege (21%), Repudiation (17%), and Information Disclosure and Tampering (4% each). The paper presents a simple STRIDE procedure that can be reused for other microservice applications. It includes four steps: prepare an architectural diagram, create a DFD with trust boundaries, run STRIDE analysis in a certain tool, and summarize results in a matrix of threats per microservice to support prioritization of mitigation measures.
No takes yet. Share an insight, caveat, or question.
A 2025 study studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: