1. A process for monitoring and analyzing executable computer code comprising the steps of:
providing a client computer having an event monitoring application in a working session, said client computer accessing a central computer through the computer network, said central computer having a database comprising a plurality of executable code identity signatures;
detecting an event on a client computer by said monitoring application;
identifying an executable code triggering the event and associated with an event;
creating a unique signature of a said executable code with said monitoring application on said client computer;
receiving in said central computer said unique signature;
comparing said unique signature with said plurality of executable code identity signatures in said database;
forwarding to said central computer for investigation said executable code when said unique signature is absent from plurality of executable code identity signatures; and
investigating the identity and intent of the said executable code if it is unknown
transmitting from the said central computer to said client computer at least one item selected from the group consisting of: a message and a command to the a monitoring application on a said client computer to perform a respective action.
2. The process of claim 1, wherein said computer network comprises a wide area network.
3. The process of claim 1, wherein said computer network comprises a local area network.
4. The process of claim 1, further comprising a client computer in communication with said central computer through said computer network.
5. The process of claim 1, wherein client computer forwards to the central computer a file containing said executable code or participating in generation of said executable code.
6. The process of claim 1 wherein said monitoring application is adapted to identify said executable code in a stream of data being receivedsend over the network.
7. The process of claim 1 wherein said monitoring application is also a firewall.
8. The process of claim 1 wherein said monitoring application is also an antivirus.
9. The process of claim 1, wherein said executable code is disabled during investigation.
10. The process of claim 1, wherein said executable code is allowed to operate during investigation.
11. The process of claim 9 wherein the user of the client computer overrides the disablement of said executable code.
12. The process of claim 1 further comprising the step of storing within said database usage history data of said client computer.
13. The process of claim 12 wherein usage history data comprises signatures of executable code previously found on said client computer and previously verified signatures.
14. The process of claim 12 wherein said client computer receives from the central computer said usage history data prior the working session and said usage history data is stored it in a local database.
15. The process of claim 14, wherein said local database is preferably stored in random access memory.
16. The process of claim 14 wherein said unique signature of said executable code active in said event is compared to said usage history data in the said local database.
17. The process of claim 16 wherein a match between said unique signature and a datum within said usage history data precludes forwarding of said unique signature to said central computer.
18. The process of claim 14 further comprising the step of comparing of a status of usage history data signature within said local database is with a central database status for said usage history data signature.
19. The process of claim 18 wherein said central database status controls relative to said status of usage history data signature within said local database.
20. The process of claim 18 wherein said status of usage history data signature within said local database controls relative to said central database status.
21. The process of claim 1 wherein said message transmitted is a warning when said unique signature matches a dangerous member of said plurality of executable code identity signatures.
22. The process of claim 1, further comprising the step of adding said unique signature to said plurality of executable code identity signatures.
23. The process of claim 1, wherein each signature of said plurality of executable code signatures in said database is comprised of: signatures related to legitimate executable code, signatures related to malicious executable code, signatures related to potentially dangerous executable code, signatures related to executable codes identities and intent of which are being investigated and signatures relating to mass mailing executable code.
24. The process of claim 1 wherein a plurality of executable codes are active in said event.
25. The process of claim 24 wherein said executable code and plurality of executable codes are simultaneously identified.
26. The process of claim 1 wherein a said respective action is termination of the process corresponding to or triggering the said event.
27. The process of claim 1 wherein a said respective action is a termination of a thread.
28. The process of claim 1 wherein a respective action is removing said executable code active with said event.
29. The process of claim 1 wherein investigation of said executable code comprises the step of analyzing said executable code with a presumed manufacturer.
30. A process for monitoring and analyzing computer executable code comprising the steps of:
providing a client computer having an event monitoring application in a working session, said client computer accessing a central computer through the computer network, said central computer having a database comprising a plurality of executable code identity signatures;
detecting an event on a client computer by said monitoring application;
identifying an executable code associated with an event or triggering the even;
creating a unique signature of a said executable code with said monitoring application on said client computer;
receiving in said central computer a unique signature associated with an executable code;
comparing said unique signature with said plurality of executable code signatures in said database;
matching said unique signature to a malicious executable computer file signature from said plurality of file signatures; and
transmitting an message and command to monitoring application regarding said executable code.
31. The process of claim 30, wherein said computer network comprises a wide area network.
32. The process of claim 30, wherein said computer network comprises a local area network.
33. The process of claim 30, further comprising a client computer in communication with said central computer through said computer network.
34. The process of claim 30, wherein said client computer further comprises a monitoring application, said monitoring application being adapted to identify executable code within a data stream received over the network.
35. The process of claim 14 wherein said database comprises usage history data of said client computer.
36. The process of claim 30 further comprising the step of noticing a second client computer having a usage history datum within said database corresponding to said suspect signature matched said malicious executable computer code signature.
37. The system of claim 30 wherein each signature of said plurality of identity signatures in said database is selected from a group consisting of:
signatures related to legitimate executable code, signatures related to malicious executable code, signatures related to potentially dangerous executable code, and signatures relating to mass mailing executable code.
38. A process for monitoring and analyzing an executable code comprising the steps of:
providing a client computer having an event monitoring application in a working session, said client computer accessing a central computer through the computer network, said central computer having a database comprising a plurality of executable code identity signatures;
providing a client computer in communication with said central computer through said computer network;
detecting an event on a client computer by said monitoring application;
identifying an executable code associated with an event or triggering the event;
creating a unique signature of a said executable code with said monitoring application on said client computer;
receiving in said server a unique signature transmitted from said client computer;
investigating said unique signature to determine if it is related to a malicious executable computer code; and
transmitting from said central computer a message and a respective command concerning said unique signature to said client computer.
39. The process of claim 38, wherein said computer network comprises a wide area network.
40. The process of claim 38, wherein said computer network comprises a local area network.
41. The process of claim 38, further comprising a client computer in communication with said central computer through said computer network.
42. The process of claim 38, wherein said client computer further comprises a monitoring application, said monitoring application being adapted to identify and forward to the central computer a file containing said executable code or participating in creating said of executable code.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A display unit disposed on a console box, comprising:
a monitor pivotally mounted about a hinge shaft;
a monitor base comprising a button;
a return spring mounted around the hinge shaft;
a gear box mounted such that a front portion thereof is directed toward a rear portion of the console box, the gear box being connected to the monitor;
a plurality of gears mounted inside the gear box and engaged with one another; and
a vertical gear disposed substantially vertically and engaged with one of the plurality of gears,
whereby when the button is depressed, the monitor pivots toward an open position by means of the return spring, and the gear engaged with the vertical gear moves substantially vertically along the vertical gear while rotating, such that the gear box and the monitor are lifted;
wherein the return spring is a \u201cV\u201d-shaped coil spring, is coupled at a first end thereof to the lower end portion of the monitor and coupled at a second end thereof to the gear box, and comprises a middle portion disposed around the hinge shaft.
2. A display unit disposed on a console box, comprising:
a monitor pivotally mounted about a hinge shaft;
a monitor base comprising a button;
a return spring mounted around the hinge shaft;
a gear box mounted such that a front portion thereof is directed toward a rear portion of the console box, the gear box being connected to the monitor;
a plurality of gears mounted inside the gear box and engaged with one another; and
a vertical gear disposed substantially vertically and engaged with one of the plurality of gears,
whereby when the button is depressed, the monitor pivots toward an open position by means of the return spring, and the gear engaged with the vertical gear moves substantially vertically along the vertical gear while rotating, such that the gear box and the monitor are lifted;
wherein the plurality of gears comprises a first gear mounted around the hinge shaft, a second gear engaged with the first gear, and a third gear engaged with the second gear and with the vertical gear.
3. The display unit as set forth in claim 2, wherein a rear portion of the gear box comprises an inclined face.
4. The display unit as set forth in claim 3, wherein the display unit further comprises a return means mounted to a bottom portion of the monitor base to move forward and rearward while moving along the inclined face of the gear box.
5. The display unit as set forth in claim 4, wherein the return means comprises:
a spring support mounted to a bottom surface of the monitor base;
a guide rod disposed through the spring support and forwardly and rearwardly movable;
a fixture mounted on the guide rod and spaced apart from the spring support;
a compression spring disposed around the guide rod between the spring support and the fixture; and
a roller mounted to an end of the guide rod so as to be in roll-contact with the inclined face of the gear box;
whereby when the gear box moves upward, the guide rod moves rearward by means of the roller in roll-contact with the inclined face of the gear box and the compression spring is compressed so that when the monitor pivots toward a closed position, an applied pressure is reduced by means of an elastic force of the compression spring.
6. A display unit disposed on a console box, comprising:
a monitor pivotally mounted about a hinge shaft;
a monitor base comprising a button;
a return spring mounted around the hinge shaft;
a gear box mounted such that a front portion thereof is directed toward a rear portion of the console box, the gear box being connected to the monitor;
a plurality of gears mounted inside the gear box and engaged with one another; and
a vertical gear disposed substantially vertically and engaged with one of the plurality of gears,
whereby when the button is depressed, the monitor pivots toward an open position by means of the return spring, and the gear engaged with the vertical gear moves substantially vertically along the vertical gear while rotating, such that the gear box and the monitor are lifted;
further comprising a compression spring mounted to a bottom surface of the gear box and kept at a compressed state before the monitor pivots toward an open position to cause the gear box to be lifted, and increases an ascending force of the gear box by means of an elastic force thereof when the monitor pivots toward the open position.
7. The display unit as set forth in claim 2, wherein the third gear is axially connected to a drive motor that pivots the monitor.