Classification of Gui Items According to Exposure to Security Sensitive Operations

1. A computer-implemented method for reducing a risk of application errors by disabling application interface elements, the method comprising: developing a mapping associated with an application, the mapping linking a plurality of application interface elements with a plurality of hooks associated with invocation of the plurality of application interface elements; identifying a permissions profile associated with an identity interacting with the application, the permissions profile specifying rights of the identity to invoke one or more of the plurality of application interface elements; determining, based on the permissions profile, an application interface element from the plurality of application interface elements that the identity is not permitted to invoke; and disabling the application interface element from being invoked by the identity through the application, wherein the disabling of the application interface element includes at least one of: changing a visual appearance of the application interface element, or preventing a graphical depiction of the application interface element.

2. The computer-implemented method of claim 1 , wherein the permissions profile is configurable and unique to the identity.

3. The computer-implemented method of claim 1 , wherein the permissions profile is configurable and associated with a group to which the identity belongs.

4. The computer-implemented method of claim 1 , further comprising generating a graphical user interface associated with the application, the graphical user interface including a plurality of enabled application interface elements and a plurality of disabled application interface elements.

5. The computer-implemented method of claim 1 , wherein the mapping is based on a classification of the plurality of application interface elements in terms of their privileged access requirements.

6. The computer-implemented method of claim 1 , wherein the mapping is developed through a learning process involving the invocation of the plurality of application interface elements.

7. The computer-implemented method of claim 6 , wherein the learning process is automated.

8. The computer-implemented method of claim 6 , wherein the learning process is based on static analysis of a control flow associated with the application.

9. The computer-implemented method of claim 1 , wherein the disabling of the application interface element is performed remotely from the application.

10. The computer-implemented method of claim 1 , wherein the disabling of the application interface element is performed by sending a window message to the application.

11. The computer-implemented method of claim 1 , wherein the disabling of the application interface element includes disabling a control option in a browser associated with the application.

12. A non-transitory computer readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for reducing a risk of application errors by disabling application interface elements, the operations comprising: developing a mapping associated with an application, the mapping linking a plurality of application interface elements with a plurality of hooks associated with invocation of the plurality of application interface elements; identifying a permissions profile associated with an identity interacting with the application, the permissions profile specifying rights of the identity to invoke one or more of the plurality of application interface elements; determining, based on the permissions profile, an application interface element from the plurality of application interface elements that the identity is not permitted to invoke; and disabling the application interface element from being invoked by the identity through the application, wherein the disabling of the application interface element includes at least one of: changing a visual appearance of the application interface element, or preventing a graphical depiction of the application interface element.

13. The non-transitory computer readable medium of claim 12 , wherein the plurality of hooks are each associated with a log file.

14. The non-transitory computer readable medium of claim 12 , wherein the plurality of hooks are each associated with security-sensitive operations.

15. The non-transitory computer readable medium of claim 12 , wherein the mapping is developed through a learning process involving the invocation of the plurality of application interface elements.

16. The non-transitory computer readable medium of claim 15 , wherein the learning process is automated.

17. The non-transitory computer readable medium of claim 15 , wherein the learning process is based on static analysis of a control flow associated with the application.

18. The non-transitory computer readable medium of claim 12 , where the plurality of hooks are application programming interface hooks associated with the application.

19. The non-transitory computer readable medium of claim 12 , wherein the disabling of the application interface element is performed remotely from the application.

20. The non-transitory computer readable medium of claim 12 , wherein the disabling of the application interface element is performed by sending a window message to the application.

21. The non-transitory computer readable medium of claim 12 , wherein the disabling of the application interface element includes disabling a control option in a browser associated with the application.