A static analysis technique based on Integrity Breach Conditions (IBCs) effectively identifies sensitive methods or security spots that may contain malicious code injected by insiders in the program source code.However, static IBC analysis does not account for runtime execution behavior, where user inputs may trigger sensitive methods dynamically.This paper extends the application of IBCs beyond static analysis by analyzing control paths in functions to identify sensitive control (execution) paths in runtime contexts.Constructing and comparing control flow graphs (CFGs) with IBCs assists programmers in systematically tracing sensitive control paths that might otherwise be overlooked during code reviews.The methodology is applied across singlethreaded programs, multi-threaded environments, client-server architectures, and blackboard models, demonstrating the effectiveness of IBCs in identifying direct and indirect interactions with sensitive methods.Through real-world examples, we show how the application of IBCs enhances code review by providing a structured way to analyze runtime control paths and validate sensitive methods.

This paper describes an extension to the Integrity Breach Conditions (IBCs) by introducing a set of IBCs for interfaces and lambda expressions in Java.This paper addresses the integrity breaches caused by exploitation of interfaces and lambda expressions, proposing the IBCs to detect the potential breaches.A prototype tool is developed to identify the security spots that might indicate integrity breaches in code.An online banking system is developed to validate our approach using the developed prototype tool.