Abstract: Methods, devices, and systems disclosed herein measure endpoint user security event susceptibility (e.g., a malware infection) and provide information for endpoint posture evaluation. A relatively small software application may be installed using, for example, a systems management push system where the software runs on each endpoint system and reports back to a central repository or base system. The software runs on machines that it is pushed to and generates a score for that endpoint. That score is a quantification of endpoint user security risk, i.e., the likelihood that a particular endpoint is likely to be the source of a security event at some point in the future. This information may be used to generate a Relative Score for each endpoint so that the endpoints can be ranked from most secure to least secure and an Absolute Score so that a given distributed system can be compared to other distributed systems.

Abstract: Techniques are provided for generating descriptions of matching resources in a manner that takes into account the kind, quality, and relevance of the available sources of information about the matching resources. For example, after the search engine identifies matching resources based on the query terms, the search engine determines the kinds of available sources of information about each matching resource. For each matching resource, based on the kinds of available sources of information about the matching resource, one of a plurality of processes is selected to generate a description for the matching resource. Using the content-sensitive description generation techniques described herein, a single result set may include abstracts that were generated using several different processes, where the difference in process corresponds to a difference in the kind, quality, and relevance of the available sources of information about each matching resource.

Abstract: Techniques are provided for generating descriptions of matching resources in a manner that takes into account the kind, quality, and relevance of the available sources of information about the matching resources. For example, after the search engine identifies matching resources based on the query terms, the search engine determines the kinds of available sources of information about each matching resource. For each matching resource, based on the kinds of available sources of information about the matching resource, one of a plurality of processes is selected to generate a description for the matching resource. Using the content-sensitive description generation techniques described herein, a single result set may include abstracts that were generated using several different processes, where the difference in process corresponds to a difference in the kind, quality, and relevance of the available sources of information about each matching resource.

Abstract: Techniques are provided for generating descriptions of matching resources in a manner that takes into account the kind, quality, and relevance of the available sources of information about the matching resources. For example, after the search engine identifies matching resources based on the query terms, the search engine determines the kinds of available sources of information about each matching resource. For each matching resource, based on the kinds of available sources of information about the matching resource, one of a plurality of processes is selected to generate a description for the matching resource. Using the content-sensitive description generation techniques described herein, a single result set may include abstracts that were generated using several different processes, where the difference in process corresponds to a difference in the kind, quality, and relevance of the available sources of information about each matching resource.

Abstract: Techniques are provided for generating descriptions of matching resources in a manner that takes into account the kind, quality, and relevance of the available sources of information about the matching resources. For example, after the search engine identifies matching resources based on the query terms, the search engine determines the kinds of available sources of information about each matching resource. For each matching resource, based on the kinds of available sources of information about the matching resource, one of a plurality of processes is selected to generate a description for the matching resource. Using the content-sensitive description generation techniques described herein, a single result set may include abstracts that were generated using several different processes, where the difference in process corresponds to a difference in the kind, quality, and relevance of the available sources of information about each matching resource.

Abstract: Techniques are provided for generating descriptions of matching resources in a manner that takes into account the kind, quality, and relevance of the available sources of information about the matching resources. For example, after the search engine identifies matching resources based on the query terms, the search engine determines the kinds of available sources of information about each matching resource. For each matching resource, based on the kinds of available sources of information about the matching resource, one of a plurality of processes is selected to generate a description for the matching resource. Using the content-sensitive description generation techniques described herein, a single result set may include abstracts that were generated using several different processes, where the difference in process corresponds to a difference in the kind, quality, and relevance of the available sources of information about each matching resource.

Abstract: Techniques are provided for generating descriptions of matching resources in a manner that takes into account the kind, quality, and relevance of the available sources of information about the matching resources. For example, after the search engine identifies matching resources based on the query terms, the search engine determines the kinds of available sources of information about each matching resource. For each matching resource, based on the kinds of available sources of information about the matching resource, one of a plurality of processes is selected to generate a description for the matching resource. Using the content-sensitive description generation techniques described herein, a single result set may include abstracts that were generated using several different processes, where the difference in process corresponds to a difference in the kind, quality, and relevance of the available sources of information about each matching resource.

Abstract: Various technologies and techniques are disclosed for persisting instance-level report customizations. Input is received from a user to run an original report. An original query associated with the original report is executed against a data store. The original report is displayed to the user. At least one instance-level customization is received from the user to customize an instance of the original report. The instance-level customizations that the user makes to the customized report are tracked in a manner that allows a history of changes from the original report to the customized report to be determined. The customized report is generated in subsequent executions of the report. The instance-level changes the user made to the report can be audited to allow users to see the changes made to the original report.

Abstract: Various technologies for processing a selection on an item on a report. In one implementation, a request to perform an action on the item may be received. Whether one or more actions corresponding to the item exist based on one or more parameters and one or more values of the parameters associated with the item may be dynamically determined. A list of one or more actions may be displayed if the one or more actions exist.

Abstract: Mechanisms are provided for auto-generating reports based on metadata. Entities in databases may have some associated metadata, and this metadata may serve as the basis of the reports. Such reports may be generated not only automatically but also dynamically. The generation of reports may also be a function of the role traversal between entities, such that if a role indicates at most one instance of the target entity is related to an instance of the source entity, a single-type report can be created, whereas if the role indicates many instances of the target entity may be related, a different kind or report can be generated, namely, a multi-type report. Lastly, even though reports are auto-generated, such reports can be overridden or customized via user interfaces or application programming interfaces.

Abstract: Mechanisms are provided for drilling on data elements in arbitrary ad-hoc reports. Data elements in one ad-hoc report can be examined and then drilled on, in order to obtain other related data elements in other ad-hoc reports. Thus, in one exemplary aspect of the disclosure, when a user selects a data element in an ad-hoc report, another ad-hoc report is generated containing data elements that are obtained as a result of taking into account 1) the original query associated with data element in the ad-hoc report; 2) the context of the selection in the ad-hoc report, and 3) the granularity of the resulting query associated with the resulting ad-hoc report.

Abstract: A graphical user interface and method of use thereof that allows users to interact with an entity relationship model. The user interface includes zones that allow users to navigate among the entities, roles and fields to create queries that are run against the model. Clicking on an entity in the shows the available fields for the entity. Users can drag and drop entities and fields onto a design surface to quickly and easily build queries. Rules are applied when either an entity or a field is dropped onto the design surface based upon the item being dropped (either an entity or a field), the position of the drop and also the properties that are associated with the item. Entities may be grouped and filtered to sort and limit the results of the query. After query is run, the results may be displayed in a separate area to the user.

Abstract: A method of creating and defining complex functions and/or expressions that may be run against an entity relationship model. An anchor entity serves as a beginning point of the expression and determines what data that will be returned by the user-created expression within the context of a query. When a relationship from any entity is traversed, including the anchor entity, the role name for the target entity is displayed hierarchically beneath the entity it was navigated from. When an entity is selected, the relationships from this entity are shown as possible navigation paths. The user may select one of these paths to navigate and add to the query tree or chose a field from the field list. Entities can be dragged and dropped into a formula area to create the expression. Functions, and mathematical and logical operations can be performed on the entities and fields in creating the expression. The fields and entities can be filtered to refine the results retrieved by the expression.

Abstract: A preferred path between two selected entities is determined. Initially, there is provided a representation of the data structure in the form of a plurality of entities having relations between them indicative of roles and the relations reflecting a cardinality of one of a one-to-one, one-to-many and a many-to-one relationship between the entities. A query is entered that provides an indication of a first selected entity and a second selected entity. A preferred path is selected through the entities and relations that couples the first selected entity to the second selected entity. The preferred path is selected from a plurality of paths as a function of the number of changes in cardinality along the plurality of paths and a indicator indicative of a preferred role relating two entities.

Abstract: A modular communications, command, and control system with plug-and-play connectivity, utilizing configurable independent base stations and portable handsets that preferably have similar components and functionality so as to be interoperable. The system utilizes an open system interconnection architecture preferably having fully integrated layers permitting inter-operability with adaptive applications and inter/intra-linking with external appliances and/or apparatuses. Optionally, the system may be utilized to perform extended information handling/processing, networking, personal assistance, industrial, commercial, medical, military, and/or security functions.

Abstract: A data query and reporting method and system are provided. The method and system allow non-technical computer users to build and execute complex database queries. The method and system accommodate the need for a simple, easy-to-understand interactive and iterative means for generating and validating database queries. The method and system reduce the complexity and costs associated with retrieving useful information for organizations of all sizes, especially smaller businesses. The method and system support a robust security model, enabling organizations to protect sensitive data while providing broad data access.

Abstract: A method and system for creating and following drill links in a report are disclosed. A relational abstraction of a data store is defined, the definition including a plurality of views, scalar or aggregate fields associated with the views, and relations between the views. A report is generated that includes at least one drill link associated with a sequence of one or more relations originating at a base view of the relational abstraction. Upon selecting a drill link contained in a first report, information about the drill link is extracted from the report, and the extracted information and the destination view associated with the drill link are used to create a second report.

Abstract: A method and system for displaying a relational abstraction data store are disclosed. A relational abstraction of a data store is defined, the definition including a plurality of views, scalar or aggregate fields associated with the views, and relations between the views. The fields and relations associated with views are displayed and related to a base view through a sequence of relations. The fields displayed are constrained based upon the sequence of relations from the base view. Scalar fields are displayed where the sequence of relations does not contain a to-many relation. Aggregate fields are displayed where the sequence of relations contains at least one to-many relation. Distinct aggregate fields are displayed where the relation path sequence contains a to-many relation followed by a many-to-one relation. A field may be displayed with additional information indicating how, or whether, the fields may be used. The display of fields may be constrained in predetermined ways.

Abstract: A medication dispenser for use in a hospital or other medical setting comprises a plurality of containers for holding medication units, packaging apparatus for containing one or more medication units in a package and robotics for manipulating a selected container to transfer one or more medication units from the container directly to said package. Since medication is directly transferred from the container to the package, no cross-contamination occurs.