Abstract: Technologies for a contract platform versioned according to the set of API contracts provided. API contracts are both development-time and run-time executable components. Each such contract defines a particular set of APIs that are fully supported at run-time by a corresponding implementation module. Contract applications are written to API contracts as opposed to the monolithic APIs of a legacy platform. Such applications are “platform agnostic”.

Abstract: Technologies for a contract platform versioned according to the set of API contracts provided. API contracts are both development-time and run-time executable components. Each such contract defines a particular set of APIs that are fully supported at run-time by a corresponding implementation module. Contract applications are written to API contracts as opposed to the monolithic APIs of a legacy platform. Such applications are “platform agnostic”.

Abstract: Evaluating a threat model for structural validity and descriptive completeness. A threat modeling application provides a progress factor or other overall score associated with the structural validity and descriptive completeness of the threat model being evaluated. The structural validity is evaluated based on a data flow diagram associated with the threat model. The descriptive completeness is evaluated by reviewing descriptions of threat types in the threat model. The progress factor encourages modelers to provide effective models to a model reviewer, thus saving time for the model reviewer.

Abstract: Evaluating a threat model for structural validity and descriptive completeness. A threat modeling application provides a progress factor or other overall score associated with the structural validity and descriptive completeness of the threat model being evaluated. The structural validity is evaluated based on a data flow diagram associated with the threat model. The descriptive completeness is evaluated by reviewing descriptions of threat types in the threat model. The progress factor encourages modelers to provide effective models to a model reviewer, thus saving time for the model reviewer.

Abstract: Identifying threats to an information system by analyzing a structural representation of the information system. In some embodiments, a data flow diagram corresponding to the information system is analyzed based on predefined criteria. Potential threats to elements of the data flow diagram are identified based on the predefined criteria. The threats are prioritized and provided to a user for further testing. In an embodiment, the user performs fuzz testing of application programs in the information system based on the prioritized threats.

Abstract: A computer-implemented method uses out-of-band notifications to reduce overhead associated with notifying a client process of events that have occurred at a server process in a computer system employing a request-response protocol. Initially, a notification transmission connection is established between the client process and the server process using the request-response protocol. Thereafter, notifications are transmitted from the client process to the server process using the connection, and without using the request-response protocol to transmit the notifications.

Abstract: A computer-implemented method uses out-of-band data transmission to reduce overhead associated with data transmission between a client process and a server process in a computer system employing a request-response protocol. Initially, a data transmission connection is established between the client process and the server process using the request-response protocol. Thereafter, data is transmitted between the client process and the server process using the connection, and without using the request-response protocol to transmit the data.

Abstract: A computer-implemented method selects a desired copy of a particular interface in a computer system that includes a client computer and a server computer. The method includes, at the server computer, annotating the desired copy of the interface with an identifier, and, at the client computer, selecting the desired copy of the interface based on the associated identifier. The annotating and selecting steps may be implemented using the RPC protocol.