Abstract: A method and apparatus for performing actions of a graph-based activity on a subset of an entity-relationship database, wherein the database has entity instances related by relationship instances. Each relationship instance is associated with a relationship type. Each relationship type has associated metadata. Method steps include identifying an entity instance in the entity-relationship database upon which the action is to be performed, performing the action, determining one or more entity instances related to the identified entity instance, and for each determined entity instance, determining the relationship type of the relationship instance relating the determined entity instance to the identified entity instance, and determining, based upon the metadata associated with the relationship type, whether the action is to be performed on the determined entity instance, and repeating the method steps for each entity instance for which it is determined that the action is to be performed on that instance.

Abstract: Disclosed is a method of accessing a network of relationship instances and data field values of entity instances in a combined entity relationship- and relational-model database management system. The method comprises the steps of receiving a query that natively references relationship types including data fields to be accessed; parsing the query into a parse tree; converting the parse tree to a query graph; optimising the query graph by consolidating equivalent nodes in the query graph; analysing the nodes in the optimised query graph; codifying each node of the optimised query graph into a first table of state transition rules; codifying the data fields to be accessed into a second table of field rules; preparing a query that includes the first and second tables; identifying entity instances to be accessed by the prepared query by iteratively following relationship instances according to the first table; and loading data fields of the identified entity instances according to the second table.

Abstract: Disclosed is a method of accessing a network of relationship instances and data field values of entity instances in a combined entity relationship- and relational-model database management system. The method comprises the steps of receiving a query that natively references relationship types including data fields to be accessed; parsing the query into a parse tree; converting the parse tree to a query graph; optimising the query graph by consolidating equivalent nodes in the query graph; analysing the nodes in the optimised query graph; codifying each node of the optimised query graph into a first table of state transition rules; codifying the data fields to be accessed into a second table of field rules; preparing a query that includes the first and second tables; identifying entity instances to be accessed by the prepared query by iteratively following relationship instances according to the first table; and loading data fields of the identified entity instances according to the second table.

Abstract: A computer implemented method of securing information stored in an entity relationship database system comprising at least one entity relationship database, the information stored in the entity relationship database system being stored according to an entity relationship model, the method comprising the steps of: specifying access rules limiting access to the entity relationship database system; storing the access rules in the entity relationship database system according to the entity relationship model; permitting an accessor to create an entity in the entity relationship database system if a “create-check” process dependent upon at least one of the one or more stored access rules grants permission; and permitting the accessor to read or modify or delete an entity stored in the entity relationship database system if a “non-create-check” process dependent upon at least one of the one or more stored access rules grants permission.

Abstract: A computer implemented method of securing information stored in an entity relationship database system comprising at least one entity relationship database, the information stored in the entity relationship database system being stored according to an entity relationship model, the method comprising the steps of: specifying access rules limiting access to the entity relationship database system; storing the access rules in the entity relationship database system according to the entity relationship model; permitting an accessor to create an entity in the entity relationship database system if a “create-check” process dependent upon at least one of the one or more stored access rules grants permission; and permitting the accessor to read or modify or delete an entity stored in the entity relationship database system if a “non-create-check” process dependent upon at least one of the one or more stored access rules grants permission.

Abstract: A method and apparatus for performing actions of a graph-based activity on a subset of an entity-relationship database, wherein the database has entity instances related by relationship instances. Each relationship instance is associated with a relationship type. Each relationship type has associated metadata. Method steps include identifying an entity instance in the entity-relationship database upon which the action is to be performed, performing the action, determining one or more entity instances related to the identified entity instance, and for each determined entity instance, determining the relationship type of the relationship instance relating the determined entity instance to the identified entity instance, and determining, based upon the metadata associated with the relationship type, whether the action is to be performed on the determined entity instance, and repeating the method steps for each entity instance for which it is determined that the action is to be performed on that instance.

Abstract: A computer-implemented method for validating client authentication using timing data is described. A connection request is received from a client. Data are transmitted to the client. The client is instructed to retransmit the data. The retransmitted data are received from the client. Timing data that indicates a time to transmit the data to the client and receive the retransmitted data from the client are calculated. A protective element is applied to the timing data.

Abstract: A computer-implemented method for retaining an executable environment during a data archive process is described. An executable file that is associated with an archived data file is identified. The executable file is part of a virtualization application layer. An identifier is archived that identifies the virtualization application layer. The identifier is associated with the archived data file. The virtualization application layer is provided when the archived data file is restored. The restored data file is accessed with the executable file.

Abstract: Systems and methods are provided for pre-emptively isolating vulnerabilities, or potential vulnerabilities in a network. In one embodiment, application data corresponding to a plurality of software applications hosted by respective network devices is stored in a network database. Based on the application data, a set of applications is determined that correspond to a software update. The set of applications are then blocked such that they cannot be executed until the software update is applied or until it is determined that they do not include a vulnerability targeted by the software update. In some embodiments, applications are blocked when a vulnerability becomes known, even if a fix for the vulnerability is not yet known. In one embodiment, new devices attempting to connect to the network are restricted until known vulnerabilities are resolved.