Richard Humphreys's scientific contributions

What is this page?


This page lists the scientific contributions of an author, who either does not have a ResearchGate profile, or has not yet added these contributions to their profile.

It was automatically created by ResearchGate to create a record of this author's body of work. We create such pages to advance our goal of creating and maintaining the most comprehensive scientific repository possible. In doing so, we process publicly available (personal) data relating to the author as a member of the scientific community.

If you're a ResearchGate member, you can follow this page to keep up with this author's work.

If you are this author, and you don't want us to display this page anymore, please let us know.

Publications (1)


Final Evaluation Report of Infosafe Corporation, X-Lock 50. Version 2. 00
  • Article

September 1988

·

8 Reads

Stephen Schneider

·

Richard Humphreys

·

Scott Korthals

·

Jose Rivera

X-LOCK 50 Version 2.0, has been evaluated by the National Computer Security Center (NCSC). X-LOCK 50 is considered to be a security subsystem rather than a complete trusted computer system. Therefore it was evaluated against a relevant subset of the requirements from the Department Of Defense trusted computer system evaluation criteria (Criteria), dated December 1985. The features included in this evaluation were Identification and Authentication (I&A), a limited form of Discretionary Access Control (DAC), and a limited form of Object Reuse (OR). The NCSC evaluation team has determined the X-LOCK 50 when configured as tested, is capable of applying these security features on an IBM PC/XT or PC/AT. I&A is maintained on the protected computer by requiring that user's wanted a valid user identification, and password prior to gaining access to the system. The discretionary access control is implemented on a limited scale by allowing or denying an individual user access to the system or hard disk. Privileges assigned to users are determined by the superuser, (the system security administrator) when user accounts are being established. Object reuse, which is implemented at the user's discretion, only writes over specified files and does not take into consideration other locations (e.g., memory buffers) which could contain residual data. Object reuse implemented in this manner does not meet the Department Of Defense trusted computer system evaluation criteria.

Share