METHOD, SYSTEM AND APPARATUS FOR SECURE DATA EDITING
A system, method, and apparatus for secure data editing is disclosed. A data field receives focus to accept a data entry from a user. The user inputs a data entry into the data field via a user interface. A determination is made of whether a manual lock event, a change focus event, or a time out event has triggered based on the user's action or inaction with the user interface. Upon the triggering of a manual lock event, a change focus event, or a time out event, the data entry in the data field is obscured. The user interface may display a data entry with a validation character which provides a reference point within the data entry while the data entry is displayed and while the data entry is obscured. The system may allow a user to have a specified function set based on his user access level.
1 . A method for secure data editing, comprising:
receiving a data entry in a first data field, the data entry being specified by a user interface;
displaying the data entry for a first period of time;
determining whether a period of inactivity on the user interface exceeds a threshold;
determining whether the user interface has received a change focus request;
determining whether the user interface has received a manual lock request;
triggering a security event when at least one of the period of inactivity on the user interface exceeds the threshold, the user interface has received a change focus request, and the user interface has received a manual lock request;
obscuring the data entry for a second period of time following the first period of time, the data entry being obscured upon the triggering of the security event; and
displaying a validation character within the data entry during the second period of time.
2 . The method of claim 1 , wherein the validation character is at least one of a hyphen and a slash.
3 . The method of claim 1 , wherein the threshold period of inactivity on the user interface is at least five seconds.
4 . The method of claim 1 , wherein the change focus event is triggered when the user interface receives a change focus request from activation of a tab key.
5 . The method of claim 1 , wherein the change focus event is triggered when the user interface receives a change focus request from activation of a mouse click on a second data field.
6 . The method of claim 1 , wherein the manual lock event is triggered when the user interface receives a manual lock request from activation of a function key.
7 . The method of claim 1 , wherein the manual lock event is triggered when the user interface receives a manual lock request from activation of a mouse click on a lock button.
8 . The method of claim 1 , further comprising displaying a lock button during the first time period, wherein activating the lock button via the user interface triggers the manual lock event.
9 . The method of claim 1 , further comprising displaying an unlock button during the second time period, wherein activating the unlock button via the user interface triggers a manual unlock event.
10 . The method of claim 1 , wherein the first data field reveals information regarding the data entry during the second time period.
11 . The method of claim 1 , wherein the period of inactivity on the user interface exceeds the threshold and the first data field maintains a focus.
12 . A method for secure data editing, comprising:
receiving a user identifier, the user identifier being specified by a user interface;
determining a user access level associated with the user identifier, wherein at least two user access levels exist and each user access level provides a different set of user functions;
receiving a data entry in a first data field, the data entry being specified by the user interface;
displaying the data entry for a first period of time;
determining whether a period of inactivity on the user interface exceeds a threshold;
determining whether the user interface has received a change focus request;
determining whether the user interface has received a manual lock request;
triggering a security event when at least one of the period of inactivity on the user interface exceeds the threshold, the user interface has received a change focus request, and the user interface has received a manual lock request; and
obscuring the data entry for a second period of time following the first period of time, the data entry being obscured upon the triggering of the security event.
13 . The method of claim 12 , wherein the user identifier includes at least a user name and a password.
14 . The method of claim 12 , wherein the user access level provides a function set including at least a delete capability and an overwrite capability.
15 . The method of claim 12 , wherein the user access level provides a function set including a manual unlock event.
16 . The method of claim 12 , wherein the user access level specifies a first function set for the first data field and a second function set for a second data field.
17 . The method of claim 12 , wherein the threshold period of inactivity on the user interface is at least five seconds.
18 . The method of claim 12 , wherein the change focus event is triggered when the user interface receives a change focus request from activation of a tab key.
19 . The method of claim 12 , wherein the change focus event is triggered when the user interface receives a change focus request from activation of a mouse click on a second data field.
20 . The method of claim 12 , wherein the manual lock event is triggered when the user interface receives a manual lock request from activation of a function key.