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.

The malicious code injected by an insider into a program can compromise sensitive data that is one of the most valuable assets in an organization. This paper describes the Integrity Breach Conditions (IBCs) used to determine security spots that change sensitive data values in a program. A malicious insider can create a security spot to compromise sensitive data using the reference to a class object. We have specified the IBCs by considering object references in the coupling relationships between objects. The IBCs have been implemented in a prototype tool to validate our approach with a case study.

This paper describes an approach to detecting malicious code introduced by insiders, which can compromise the data integrity in a program. The approach identifies security spots in a program, which are either malicious code or benign code. Malicious code is detected by reviewing each security spot to determine whether it is malicious or benign. The integrity breach conditions (IBCs) for object-oriented programs are specified to identify security spots in the programs. The IBCs are specified by means of the concepts of coupling within an object or between objects. A prototype tool is developed to validate the approach with a case study.