The paradigm shift of 'Build Security In' has emerged in recent decades with the underpinning idea that software security has to be an integral part of all the phases of the software development lifecycle. As a result, each practices such as threat modelling and static code analysis. It was observed that various artefacts (i.e., security requirements, as a result of security best practices tend to be disconnected incorporated in the implementation level. In order to address this issue, this paper presents a knowledge-modelling based approach to semantically infer the associations between bugs, which is manually tedious. Threat modelling and static respectively. The case study based experimental results reveal originating security bugs in the code level. Security touchpoints, software security, static code analysis, threat modelling.

No abstract