Abstract: A system and computer program product for implementing an object-oriented hierarchical database architecture that supports functionality of an emulator. The hierarchical data architecture is created for implementing a files system and/or a system registry inside the emulator, where malware components are emulated and tested. The data architecture supports the emulator and provides for effective recovery of a database fragments after modifications of the fragments by the emulated malware. The non-relational object-oriented database consists of database objects. Each of the database objects has various data fields. Special user types are assigned to the database objects. Each user type is defined by a selected set of data fields. The database objects have a parent-child relationship. Each database object has a unique parent object and a unique set of index fields. The unique set of the index fields is a unique set of data fields of an object. The database has a root object which is unique for the database.

Abstract: In a computer system having a plurality of software components, a security system for controlling interactions between the software components, the security system including at least one constraint associated with the interaction; and at least one attribute associated with the software components. The attributes and interaction parameters are bound to the constraint. The security system reaches a verdict permitting or forbidding the interaction, by resolving the constraint, based on value of the attribute and values of the parameters. The security system uses constraints and attributes specified during different life stages of each software component, where constraints are incrementally added during each subsequent life stage.

Abstract: A method, system and computer program product for implementing a high level object-oriented component infrastructure is directed to providing efficient development of programmable applications and systems. Objects of a system form an object hierarchy including child-objects and parent-objects. The system components include metadata describing properties of objects that are encapsulated into each of the components. A programmable object-oriented system locates the components placed in one or several catalogs and reads the metadata. This metadata is then used by the system for determining which module needs to be loaded for creation of an instance of an object in order to support functionality requested by another system object or by an external application.

Abstract: In a computer system having a plurality of software components, a security system for controlling interactions between the software components, the security system including at least one constraint associated with the interaction; and at least one attribute associated with the software components. The attributes and interaction parameters are bound to the constraint. The security system reaches a verdict permitting or forbidding the interaction, by resolving the constraint, based on value of the attribute and values of the parameters. The security system uses constraints and attributes specified during different life stages of each software component, where constraints are incrementally added during each subsequent life stage.