Extensible framework for system security state reporting and remediation

[0001] Although the Internet has had great successes in facilitating communications between computer systems and enabling electronic commerce, the computer systems connected to the Internet have been under almost constant attack by hackers seeking to disrupt their operation. Many of the attacks seek to exploit vulnerabilities of the application programs, operating systems, and other computer programs executing on those computer systems. One of the most destructive methods of attacking a computer system has been to infect the computer system with software that is designed specifically to damage or disrupt the computer system. Such software is referred to as “malware” because of its malicious nature. When malware invades a computer system, the integrity of the computer system is greatly compromised. Malware includes computer worms, viruses, Trojan horses, spyware, and so forth. Some malware behave nefariously, such as by illicitly collecting and transmitting personal information. Some malware can hijack resources needed by operating system components or use these resources to subvert the security of the operating system. For example, such malware can cause an unprotected network resource to open a TCP/IP port that allows a third party to access the operating system's resources.

[0002] Conventional techniques of detecting and disabling malware include installing anti-malware software and hardware products, such as antiviral software, spyware detection software, firewalls, and so forth. It is not uncommon for numerous anti-malware products to be installed and executing on a computer system. Each of the numerous anti-malware products that are executing on a computer system each generates its own report on the state of the health of the computer system. For example, an anti-virus product will generate a report regarding the presence of a virus, an anti-spyware product will generate a separate report regarding the presence of spyware, and an anti-phishing product will generate still a separate report regarding the exposure to a phishing attack. Unfortunately, the computer system user may easily become overwhelmed with the number of reports provided by the various anti-malware products that are executing. Moreover, the user may find it difficult to digest the information contained in the various reports to determine the actual health of the computer system.

[0003] A method and system for providing an extensible framework for system security state reporting and remediation is provided. A security health reporting system provides an application program interface (API) for use by independent software vendors (ISVs) to extend the security health reporting capabilities of the security health reporting system. For example, an ISV security solution can register with the security health reporting system, create a schema that describes a new security class, and use the API to publish an instance of the schema for the new security class with the security health reporting system. When a registered ISV security solution publishes an instance of a schema for a new security class via the provided API, the security health reporting system creates the new security class, and recognizes the definition for the security class within the security health reporting system along with its own security solutions (i.e., the security solutions provided by the security health reporting system itself). Registered ISV security solutions can then use the published schema to report their health statuses (i.e., the security states) for the new security class. The security health reporting system can then display the reported health statuses on, for example, a user interface (UI), or similarly the status can be consumed through a subscriber API by an application that requires the computer security health state information to perform an operation.

[0004] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

[0016] A method and system for providing an extensible framework for system security state reporting and remediation is provided. In some embodiments, a security health reporting system provides an application program interface (API) for use by independent software vendors (ISVs) to extend the security health reporting capabilities of the security health reporting system. For example, an ISV security solution can register with the security health reporting system, create a schema that describes a new security class, and use the API to publish an instance of the schema for the new security class with the security health reporting system. Examples of security classes include, by way of example, anti-virus, anti-phishing, anti-spyware, spam protection, worm protection, host intrusion prevention, firewall, parental controls, rootkit protection, and other security solutions that provide protection to computing systems. When a registered ISV security solution publishes an instance of a schema for a new security class via the provided API, the security health reporting system creates the new security class, and recognizes the definition for the security class within the security health reporting system along with its own security solutions (i.e., the security solutions provided by the security health reporting system itself). Registered ISV security solutions can then use the published schema to report their health statuses (i.e., the security states) for the new security class. The security health reporting system can then display the reported health statuses on, for example, a user interface (UI), or similarly the status can be consumed through a subscriber API by an application that requires the computer security health state information to perform an operation.

[0017] By way of an example scenario, Contoso Anti-virus Company may be developing a new personal computer (PC) security solution. This new solution scans for and remediates a new class of malware called “botware.” Unfortunately, the security health reporting system as developed (i.e., “out-of-the-box”) only provides anti-virus and anti-spyware security solutions, and does not include protection for this new class of malware. Because Contoso would like to add support for botware in the security health reporting system, Contoso creates a schema for a new security class for botware, names this security class “Botware Protection,” and includes this schema with their software distribution. When the Contoso security solution program is installed on a computing system (e.g., an end user computer) that is running the security health reporting system, the Contoso security solution program registers with the security health reporting system, and uses the provided API to publish an instance of the schema for the security class Botware Protection. In response, the security health reporting system creates the Botware Protection security class within the security health reporting system, and recognizes the published definition for the Botware Protection security class. The Contoso security solution program can then report the health status for the new security class Botware Protection.

[0018] In some embodiments, the security health reporting system allows a publisher of an instance of a schema for a new security class to share the published schema with other applications. ISV applications that are knowledgeable of the shared schema can then consume and use the shared schema to report the health status for the security class defined by the shared schema. Consuming applications can also use the schema to consume or obtain the security health status reported through the schema. For example, a publishing ISV can share a published schema by requesting that the security health reporting system make the instance of the schema “public.” In response, the security health reporting system makes the published schema available for consumption through an API. A knowledgeable ISV application can then programmatically consume the schema through the provided API. Continuing the botware example above, Target Anti-virus Company may have also developed a security solution that scans for and remediates botware. Moreover, Target may have knowledge of Contoso's schema for the security class Botware Protection. Because Target would like to report its health status to the security health reporting system using Contoso's schema, Target develops code to query and report using Contoso's schema, and includes this code with their software distribution. When the Target security solution program is installed on a computing system that is running both the security health reporting system and the Contoso security solution program, the Target security solution program registers with the security health reporting system, and uses the provided API to query Contoso's published schema for the security class Botware Protection. The Target security solution program can then use Contoso's schema to report its (i.e., Target's) health status for the security class Botware Protection to the security health reporting system.

[0019] In some embodiments, the security health reporting system provides its own security solutions. For example, the security health reporting system may directly provide security solutions for the security class anti-virus and the security class anti-spyware. The security health reporting system may share the schemas that describe one or both of these security classes with other applications. Consuming applications that are knowledgeable of the shared schemas can then consume and use the shared schema to report their health status for the shared security class and/or obtain the security health status reported through the schema.

[0020] In some embodiments, the security health reporting system verifies the identity of an application prior to allowing the application to use a shared schema. For example, the security health reporting system may verify the digital identity of an application prior to allowing the application to use the provided API to write data in the class instance described by the shared schema.

[0021] In some embodiments, the security health reporting system consolidates and synthesizes the received health statuses reported by the security solutions, and provides a synthesized health status for consumption through an API. Within each security class, the security health reporting system may aggregate the health statuses reported for a security class to provide a single security state for the security class (i.e., a single indication of the health of the security class). For example, for each security class, the security health reporting system may aggregate the reported health statuses by selecting the best (i.e., the healthiest) health status that was reported for the security class, and provide the best reported health status as the single security state for the security class. The security health reporting system may also aggregate the single security states across the multiple security classes to provide a single indication of the overall health of a computing system. For example, the security health reporting system may aggregate the single security states across the security classes by picking the poorest (i.e., unhealthiest) single security state that was determined for a security class, and provide the poorest single security state as the single indication of the overall health of the computing system. In some embodiments, the security health reporting system displays the synthesized health status on a UI.

[0022] In some embodiments, the security health reporting system allows for remediation of registered ISV applications. A registered ISV security solution can use a published schema to provide a remediation program to the security health reporting system. The security health reporting system can then provide users access to the remediation program through, for example, a UI, and allow the users to launch (i.e., start) the remediation program directly from the UI. Additionally, subscribers or consumers of the reporting API may also access the path to the remediation program so that an ISV application may use the remediation program to secure the computer automatically (i.e. without user intervention). Continuing the botware example above, the Contoso security solution program may use the published schema to report to the security health reporting system that it is currently “out-of-date.” Along with this report, the Contoso security solution program may have provided a path to an executable program that may be executed to obtain an updated version of the Contoso security solution program. The security health reporting system can then display the path to the executable program as a link on its UI, along with an alert that the Contoso security solution program is currently out-of-date. The user can then select (i.e., activate) the link to remediate the out-of-date Contoso security solution program directly through the security health reporting system.

[0023] In some embodiments, the security health reporting system provides for ISV product branding within the security health reporting system. A registered ISV security solution can use a published schema to provide its logo (i.e., brand) to the security health reporting system. For example, the ISV security solution may provide its logo when reporting its health status for a security class. The security health reporting system can then display the ISV security solution's brand along with the reported health status on its UI.

[0024] In some embodiments, the security health reporting system allows users to view the registered ISV security solutions that are reporting their health statuses to the security health reporting system. For example, the security health reporting system may display on a UI the names of the ISV security solutions along with their reported health statuses. The security health reporting system may also allow users to launch one or more ISV security solutions and/or stop the execution of one or more currently executing ISV security solutions directly from the UI.

[0025] FIG. 1 is a block diagram that illustrates selected components of a security health reporting system, according to some embodiments. The security health reporting system is implemented to execute within a computing system, and to function as a central, neutral security platform that evaluates, synthesizes, and reports on the various security heath states of the computing system. The security health reporting system also provides the user of the computing system a choice as to which security solutions on the computing system, including the security solutions directly provided by the security health reporting system, should be run, updated, and/or stopped. As depicted in FIG. 1, a security health reporting system 102 comprises a provider API 104, a security health component 106, and a consumer API 108. The provider API is the interface that allows both internal operating system components and software security solutions executing on the computer system to provide their security health statuses to the security health component. The security health component synthesizes the security health statuses reported by the various security solutions on the computer system. In some embodiments, the security health component may be implemented as a state machine that utilizes state tables to generalize the health statuses as reported by the security solutions. The consumer API is the interface that allows applications, including the software security solutions, to consume the synthesized or detailed security health statuses as reported by the security health component. Also depicted in FIG. 1 is a plurality of provider ISVs 110, a plurality of consumer ISVs 113, and a UI 114. Each of the provider ISVs are coupled to the provider API, and each of the consumer ISVs and the UI is coupled to the consumer API. The provider ISVs correspond to registered ISV security solutions that are reporting their health statuses to the security health reporting system. The consumer ISVs correspond to registered ISV applications that are knowledgeable of the shared schemas, and which are consuming the synthesized or detailed security health statuses. As consumers of the shared schemas, one or more of the consumer ISVs can also report their health statuses to the security health reporting system, thereby functioning as provider ISVs. The UI is the user interface that is provided by the security health reporting system. Although not shown in FIG. 1, the security health reporting system includes components that allow applications, including ISV security solutions, to register with the security health reporting system and publish instances of schemas that describe security classes. The security health reporting system may also include components that implement the security solutions that are directly provided by the security health reporting system. Accordingly, the aforementioned components of the security health reporting system are only illustrative and are not intended to suggest any limitation as to the implementation of the illustrated components and/or the scope of use or functionality of the security health reporting system.

[0026] The computing device on which the security health reporting system is implemented may include a central processing unit, memory, input devices (e.g., keyboard and pointing devices), output devices (e.g., display devices), and storage devices (e.g., disk drives). The memory and storage devices are computer-readable media that may contain computer executable instructions that implement the security health reporting system. As used herein, “computer-readable media encoded with computer executable instructions” means computer-readable media comprising computer executable instructions. In addition, the data structures and message structures may be stored or transmitted via a data transmission medium, such as a signal on a communications link. Various communication links may be used, such as the Internet, a local area network, a wide area network, a point-to-point dial-up connection, a cell phone network, and so on.

[0027] Embodiments of the security health reporting system may be implemented in various operating environments that include personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, digital cameras, network PCs, minicomputers, mainframe computers, network devices, distributed computing environments that include any of the above systems or devices, and so on. The computer systems may be cell phones, personal digital assistants, smart phones, personal computers, programmable consumer electronics, digital cameras, and so on.

[0028] The security health reporting system may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, and so on that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.

[0029] FIG. 2 is a display page that illustrates an example display of synthesized health statuses reported by the security health reporting system, according to some embodiments. A display page 200 includes a synthesized health status reporting area 202. The synthesized health status reporting area displays a synthesized health status for the computing system as determined from the health statuses reported to the security health reporting system. The synthesized health status reporting area includes a display box 204 that displays a single indication of the overall health of the computing system, and a plurality of display boxes 206 and 208 that each displays a single security state for a respective security class. In the example, display box 204 displays an indication that the overall health state of the computing system's malware protection is “on” as indicated by a text indicator 210 and a visual colored indicator 212 (e.g., a green colored indicator). Display box 204 also includes a control 214 that allows a user to control the display of additional information regarding the overall health of the computing system's malware protection. For example, control 214 was previously selected to cause the display of display boxes 206 and 208. As can be seen from the contents displayed in display boxes 206 and 208, virus protection and spyware protection security classes were synthesized to determine the overall health of the computing system's malware protection. Display box 206 displays an indication that the single security state of the virus protection (i.e., the anti-virus security class) on the computing system is “on” as indicated by a text indicator 216 and a visual color indicator 218 (e.g., a green colored indicator). The contents of display box 206 further indicate that the “Contoso Anti-virus” report is being used as the single security state of the virus protection on the computing system. Display box 206 also displays a logo 220 of the ISV Contoso. Display box 208 displays an indication that the single security state of the spyware protection (i.e., the anti-spyware security class) on the computing system is “on” as indicated by a text indicator 222 and a visual color indicator 224 (e.g., a green colored indicator). The contents of display box 208 further indicate that the “Target Anti-spyware” report is being used as single security state of the spyware protection on the computing system. Display box 208 also displays a logo 226 of the ISV Target. Display page 200 also includes display boxes 228, 230 and 232. Display box 228 displays an indication of the firewall health status that is being reported to the security health reporting system running on the computing system. Display box 230 displays an indication of the status of the automatic updates feature provided by the security health reporting system. Display box 232 displays an indication of the synthesized status for the other security settings that is being reported to the security health reporting system running on the computing system.

[0030] FIG. 3 is a display page that illustrates an example display of installed anti-virus solutions, according to some embodiments. A display page 300 includes a virus protection window 302 that includes a virus protection status window 304, an update control 306, and a close control 308. The virus protection status window displays the name of each virus protection solution that is installed on the computing system along with its current health status. In the example, virus protection solutions from Security Health Reporting, Target, and One Care are installed on the computing system. The virus protection status window indicates that the “Security Health Reporting anti-virus” security solution, which is the anti-virus security solution being directly provided by the security health reporting system, is currently “Off” and, therefore, not active on the computing system. The virus protection status window also indicates that the “Target anti-virus” security solution is currently “On” and, therefore active on the computing system, and that the “One Care anti-virus” security solution is currently active on the computing system, but is “Out of Date” and, therefore, needs to be updated. Also displayed are the respective logos of Target and One Care. The update control allows the user to remediate the installed virus protection solutions whose statuses are either “Out of Date” and thus require updating, or “Off” and thus require activation. In the example, selecting the update control may cause a display of one or more windows through which the user can activate (i.e., start running) the Security Health Reporting anti-virus solution and/or update the One Care anti-virus solution. The close control allows the user to close the virus protection window. The security health reporting system may provide similar displays for the other security classes that are supported by the security health reporting system.

[0031] FIG. 4 is a display page that illustrates an example display of synthesized health statuses reported by the security health reporting system, according to some embodiments. A display page 400 includes a synthesized health status reporting area 402. The synthesized health status reporting area displays a synthesized health status for the computing system as determined from the health statuses reported to the security health reporting system. The synthesized health status reporting area includes a display box 404 that displays a single indication of the overall health of the computing system, and a plurality of display boxes 406 and 408 that each displays a single security state for a respective security class. In the example, display box 404 displays an indication that the overall health state of the computing system's malware protection is “Out of Date” as indicated by a text indicator 410 and a visual colored indicator 412 (e.g., a red colored indicator). Display box 404 also includes a control 414 that allows a user to control the display of additional information regarding the overall health of the computing system's malware protection. As can be seen from the additional information displayed in display boxes 406 and 408, virus protection and spyware protection security classes were synthesized to determine the overall health of the computing system's malware protection. Display box 406 displays an indication that the single security state of the virus protection (i.e., the anti-virus security class) on the computing system is “Out of Date” as indicated by a text indicator 416 and a visual color indicator 418 (e.g., a red colored indicator). The contents of display box 406 further indicate that the “Contoso Anti-virus” report is being used as the single security state of the virus protection on the computing system. Display box 406 also provides a control 420 that the user can select to remediate the Contoso anti-virus solution. Display box 406 also displays a logo 422 of the ISV Contoso. Display box 408 displays an indication that the single security state of the spyware protection (i.e., the anti-spyware security class) on the computing system is “on” as indicated by a text indicator 424 and a visual color indicator 426 (e.g., a green colored indicator). The contents of display box 408 further indicate that the “Target Anti-spyware” report is being used as the single security state of the spyware protection on the computing system. Display box 408 also displays a logo 428 of the ISV Target.

[0032] FIG. 5 illustrates a portion of an example XML schema used to register with the security health reporting system, according to some embodiments. ISV security solutions report values to the attributes defined in the schema in order to register with the security health reporting system. ISV security solutions register prior to using the services provided by the security health reporting system (e.g., publishing schemas, consuming published schemas, reporting its health status to the security health reporting system, etc.). The schema contains a “<registerISV>” section 502 that includes a “Company Name” element 504, a “Product Identifier” element 506, a “Digital Signature” element 508, and a “Path to Binary” element 510. The company name element specifies the name of the registering ISV. The product identifier element specifies a unique identifier for the security solution (e.g., the security software product) the ISV is registering. The digital signature element specifies the digital signature of the security solution binary (e.g., the security software product executable) that the ISV is registering. The security health reporting system uses the specified digital signature to verify the authenticity of the binary, for example, prior to executing the binary. The path to binary element specifies a path to the security solution binary that the ISV is registering.

[0033] FIG. 6 illustrates a portion of an example XML schema for defining a security class, according to some embodiments. A registered ISV security solution may create the schema, and report values to the attributes defined in the schema in order to create an instance of the security class. The schema contains a “<State Map>” section 602 that provides a state mapping for the values that are provided to populate each possible state of a security class. The State Map section contains a “<State Values>” section 604 that defines the possible states of the security class. Examples of possible states include enabled, disabled, snoozed, up-to-date, out-of-date, and the like. A consuming ISV that provides a security solution for the security class can report any one of the defined states as its health status. The State Values section includes a “State Value” element 606, a “State Description” element 608, a “State Expanded Text” element 610, a “State Color” element 612, and a “State Alert” element 614. The state value element specifies an identifier that identifies a particular security state that is being defined. The state description element specifies a literal string that describes the security state. The state expanded text element specifies a literal string that further describes the security state. The state color element specifies a color to display, for example, in the UI, when the security state is entered. The state alert element specifies whether or not an icon is to be displayed when the security state is entered. The icon may be displayed, for example, in the system tray on the UI, and may serve to provide notification that the security state has been entered.

[0034] FIG. 7 illustrates a portion of an example schema instance defining a security class, according to some embodiments. A registered ISV security solution may create and publish an instance of a schema describing a security class with the security health reporting system. The schema contains a “<Class>” section that contains a “<State Values>” section 704 and a “<State Attributes>” section 706. The Class section includes a “Class” element 706 that specifies the name of the security class that is being defined by the instance of the schema. In the example, the class element indicates that the instance of the schema is defining an “Anti-phishing” security class. The State Values section contains a plurality of “<State Value>” sections 710. Each State Value section defines a possible state of the security class. In the example, the first State Value section defines the state “Off” as indicated by a “State Description” element 712, the second State Value section defines the state “On” as indicated by a “State Description” element 714, and the last State Value section defines the state “Snooze” as indicated by a “State Description” element 716. The State Attributes section specifies the attributes whose values need to be provided to report a state (i.e., health status) for the defined security class to the security health reporting system. For example, a consuming security solution may report values to these attributes to report its health status for the defined security class. The State Attributes section includes a “product name” element 718, a “product state” element 720, a “state severity rating” element 722, a “path to executable” element 724, and a “path to logo” element 726. The product name element specifies a literal string of the name of the consuming security solution that is reporting its health status. The product state element specifies an identifier that identifies the state (i.e., health status) that is being reported for the security class. The state severity rating specifies an indication (e.g., a rating) of the severity within the state that is being reported for the security class. The state severity rating provides granularity within the various states of the security class. The path to executable element specifies a path to the security solution program executable. For example, the security solution program executable may be launched through the security health reporting system to remediate the security solution. The path to logo element specifies a path to the security solution's logo.

[0035] FIG. 8 is a flow diagram that illustrates the processing of an ISV application to create a security class within the security health reporting system, according to some embodiments. For example, the ISV application may be a security solution that is running on the computing system on which the security health reporting system is running. Alternatively, the ISV application may be a security solution that is executing outside the computing system on which the security health reporting system is running (i.e., on a different computing system), but which wants to report its health status to the security health reporting system. In block 802, the ISV application registers with the security health reporting system. In block 804, the ISV application defines a schema for a security class that it wants to register with the security health reporting system. For example, an ISV application that provides anti-phishing services may define a schema for an anti-phishing security class. In block 806, the ISV application creates an instance of the schema by providing values to the attributes that are defined in the schema. In block 808, the ISV application publishes the instance of the schema with the security health reporting system. The ISV application may also request that the security health reporting system make the published schema public for use by other registered ISVs. In block 808, the ISV application uses the published schema to report the health status for the security class. For example, the above ISV application that provides anti-phishing services can use the published schema to report the heath status (i.e., the security state) of the anti-phishing services that is being provided by the ISV application. The ISV application continues reporting its health status as necessary, until it completes.

[0036] One skilled in the art will appreciate that, for this and other processes and methods disclosed herein, the functions/steps performed in the processes and methods may be altered in various ways. For example, the order of the outlined steps is only exemplary, and the steps may be rearranged, some of the steps may be optional, substeps may be performed in parallel, some of the steps may be combined into fewer steps or expanded into additional steps, other steps may be included, etc.

[0037] FIG. 9 is a flow diagram that illustrates the processing of the security health reporting system to process a request to publish an instance of a schema for a security class, according to some embodiments. For example, an ISV security solution may publish the instance of the schema with the security health reporting system. In block 902, the security health reporting system receives a request to publish the instance of the schema for a security class from the ISV security solution. In decision block 904, if the ISV security solution is registered, then the security health reporting system continues at block 906, else the security health reporting system continues at block 910. In block 906, the security health reporting system creates the security class within the security health reporting system. In block 908, the security health reporting system provides the published schema for the security class for consumption, and completes. In block 910, the security health reporting system reports the error condition, and completes. For example, the security health reporting system may record in a log file the unregistered ISV's attempt to publish an instance of a schema.

[0038] FIG. 10 is a flow diagram that illustrates the processing of the security health reporting system to process a health status report for a security class, according to some embodiments. In block 1002, the security health reporting system receives a health status report for a security class. For example, a registered ISV security solution may report its health status for the security class to the security health reporting system. In block 1004, the security health reporting system synthesizes the reported health statuses. The security health reporting system may synthesize the reported health statuses to determine a single security state for each security class, and an overall health of the computing system. In block 1006, the security health reporting system provides the synthesized health status for consumption, and completes. For example, the security health reporting system may display the synthesized health status on its UI. The security health reporting system may also provide the synthesized health status available programmatically for consumption by other applications.

[0039] FIG. 11 is a flow diagram that illustrates the processing of the security health reporting system to synthesize the health statuses, according to some embodiments. In block 1102, the security health reporting system selects the next security class. In decision block 1104, if all the security classes have already been selected, then the security health reporting system continues at block 1108, else the security health reporting system continues at block 1106. In block 1106, the security health reporting system assigns as the security state for the security class the best health status reported for the security class. For example, two security solutions may have reported their respective health statuses for the same security class. The security health reporting system selects the better of the two reported health statuses as the security state for the security class. The security health reporting system then loops to block 1102 to select the next security class. In block 1108, the security health reporting system assigns as the overall health of the computing system the poorest security state, and returns. In this manner, the security health reporting system reports, for each security class, the best health status that was reported for that particular security class. For the overall health of the computing system, the security health reporting system reports the poorest health status that was reported by a security solution running on the computing system.

[0040] Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. Accordingly, the invention is not limited except as by the appended claims.