| Pfleeger, S. L. Software Engineering. Theory and Practice. Prentice Hall Inc., 1998. |
....by the sensitivity of information in the object) This model ensures that information in an object can only flow to a level equal to or higher than the security level of the object. For example, a military type system which adopts this model may have the following security level classifications [14]: Unclassified, Confidential, Secret, and Top Secret, where unclassified information has the lowest security clearance (everyone is allowed to access the information) and top secret information has the highest (only high ranking personnel may access such information) The access control model is ....
....place, and is hence the responsibility of the owner of the extent to which the context belongs. The latter method protects the identity of the real users by storing the encrypted form of the real user identifiers in the activity descriptors maintained in contexts. The encryption and decryption [14] of the identity of the real user should only be successfully performed by the servers, using both a secret key [60] known only to the servers) and the identifier of the job which is running on behalf of the real user (the job identifier is included in every invocation request to the server, and ....
Charles P. Pfleeger. Security in Computing. Prentice-Hall Inc., 1989.
....to price. 2. Vulnerability Analysis. Having listed the assets of a computer system, the next stage is to determine their vulnerabilities. This stage is more difficult than the first, as it requires a degree of imagination to predict what damage might occur to the assets and from what sources [2]. The general aims of computer security are to ensure data secrecy, data integrity and availability. System vulnerabilities are situations that could cause the loss of any of these qualities. A thorough understanding of the threats to the system is required if all the vulnerabilities are to be ....
Pfleeger, C., P.: Security in Computing. Prentice Hall Inc (1997).
No context found.
Pfleeger, S. L. Software Engineering. Theory and Practice. Prentice Hall Inc., 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC