COMPUTER SOFTWARE OPERATIONAL RISK

Brand Owner (click to sort) Address Description
KERBERUS AMERICAN MANAGEMENT SYSTEMS, INC. 4050 Legato Road Fairfax VA 22033 Computer software for operational risk management;
OPSGUARD Thailas Group 11432 Hammock Oaks Ct Lithia FL 33547 Computer software for operational risk management;OPS GUARD;
SWORD Schroder Investment Management Limited 31 Gresham Street London EC2V7QA United Kingdom Computer software for operational risk management in the financial industries;Financial services relating to risk management; corporate financial services relating to risk management; financial risk management services; financial risk management consultancy; provision of financial risk management information from a computer database, the Internet or other communications network; and information, advisory, and consultancy services relating to the aforesaid, namely the provision of such services on-line and from a computer database or via the Internet or extranet, none of the aforesaid being financial clearing house services;Business risk management services, business risk management consultancy, compilation of information relating to operational risk management into a computer database; maintenance of computer databases relating to operational risk management; advisory and consultancy services relating to the aforesaid, namely the provision of such services on-line from a computer database or via the Internet or extranet;
 

Where the owner name is not linked, that owner no longer owns the brand

    
Technical Examples
  1. A method for analyzing impact on binaries, software, and hardware of a planned software upgrade for a computer system. The method includes performing a configuration inventory for the computer system with profiles for the computer system of hardware, software including operating system software, middleware, applications, development tools, and third party software, application interfaces, and binaries. A set of upgrade rules, e.g., rules defining hardware and software requirements including interfaces, libraries, dependencies, and more, are accessed and the binary profiles are analyzed based on the upgrade rules to determine safe binaries and at-risk binaries. The at-risk binaries are further divided into subcategories based on risks of incompatibility with the planned software upgrade. The subcategories include failure, high risk, and low risk. The method includes generating text or graphical reports providing the analysis results to quantify and qualify the impacts on binaries and other portions of the computer system.