Software security control system and method
First Claim
1. A method of implementing a software security system, the method comprising the acts of:
- requesting permission to display a security-controlled file when a user attempts to access the security-controlled file;
determining a type of data in the security-controlled file from at least two types of data, the at least two types of data changing dynamically;
determining whether the user has access to the type of data; and
providing access to the security-controlled file if the user has permission to access the type of data.
1 Assignment
0 Petitions
Accused Products
Abstract
A method and apparatus for implementing a software security system in a customer computer system. The method includes requesting permission to display a security-controlled file or application feature when a user attempts to access the security-controlled file or application feature, determining a type of data in the security-controlled file or associated with the security-controlled application feature from at least two types of data, the at least two types of data changing dynamically, and determining whether the user has access to the type of data and providing access to the security-controlled file or application feature if the user has permission to access the type of data. The apparatus for the software security system includes a security repository module, an access security module, and a dynamic security module.
187 Citations
80 Claims
-
1. A method of implementing a software security system, the method comprising the acts of:
-
requesting permission to display a security-controlled file when a user attempts to access the security-controlled file;
determining a type of data in the security-controlled file from at least two types of data, the at least two types of data changing dynamically;
determining whether the user has access to the type of data; and
providing access to the security-controlled file if the user has permission to access the type of data. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A software security system at least partially stored on a server and at least partially stored on a client computer, the software security system comprising:
-
a security repository module stored on the server, the security repository module storing a configuration file;
an access security module stored on the client computer for requesting permission from the security repository module for a user to access on the client computer a security-controlled file; and
a dynamic security module stored on the client computer for determining a type of data in the security-controlled file from at least two types of data, the at least two types of data changing dynamically, and for determining whether the user has access to the type of data based on the configuration file. - View Dependent Claims (21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35)
-
-
36. A method of implementing a software security system, the method comprising the acts of:
-
assigning a security permission for a user to a security key;
assigning the security key to a security-controlled application feature;
requesting access to the security-controlled application feature before allowing the user to access the security-controlled application feature;
determining a type of data associated with the security-controlled application feature from at least two types of data, the at least two types of data changing dynamically;
determining whether the user has access to the type of data; and
displaying the security-controlled application feature if the security permission assigned to the security key gives the user access to the type of data. - View Dependent Claims (37, 38, 39, 40, 41, 42, 43, 44, 45, 46)
-
-
47. A software security system at least partially stored on a server and at least partially stored on a client computer, the software security system comprising:
-
a security repository module stored on the server, the security repository module storing a security permission for a user, the security permission being assigned to a security key, and the security key being assigned to a security-controlled application feature;
a security module stored on the client computer for requesting access from the security repository module for the user to access on the client computer the security-controlled application feature; and
a dynamic security module stored on the client computer for determining a type of data associated with the security-controlled application feature from at least two types of data, the at least two types of data changing dynamically, and for determining whether the user has access to the type of data based on the security permission for the user assigned to the security key for the security-controlled application feature. - View Dependent Claims (48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61)
-
-
62. A computer system comprising:
-
a network;
a server connected to the network, the server including a security repository module; and
a web server connected to the network, the web server including an operating system;
a web application running on the operating system; and
a foundation interacting with the web application, the foundation configured to interact with a web-browser-based client computer connected to the web server, the foundation including a security module for controlling a user'"'"'s access to a security-controlled web page. - View Dependent Claims (63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79)
-
-
80. A software security system stored on a server and a client computer, the software security system comprising:
-
a security repository module stored on the server, the security repository module storing a configuration file and generating a security table based on the configuration file;
an access security module stored on the client computer for requesting permission from the security repository module for a user to access on the client computer a security-controlled file, the access security module downloading the security table from the security repository module when the user logs on to the client computer and removing the security table from the client computer when the user logs off the client computer; and
a dynamic security module stored on the client computer for determining a type of data in the security-controlled file from at least two types of data and for determining whether the user has access to the type of data based on the security table.
-
Specification