From: spexet@engin.umich.edu (Dennis Robert Spexet)
Subject: C2 Test Procedures (not so long this time) 
Date: Thu, 27 Aug 92 15:22:07 EDT
Organization: University of Michigan Engineering, Ann Arbor
Distribution: world 

In article <1992Aug27.152101.2685@ringer.cs.utsa.edu> mlevis@ringer.cs.utsa.edu (Mike Levis) writes:
>>
>>2.  As for whether or not NT is itself C2-secured, that does not appear to
>>    have been tested yet.  As you have correctly stated, a formal test
>>    and ratings process generally involves a hardware/OS combination, and
>>    not just an OS.  
>                                              ^^^^^^^^^^^
>
>Does this mean that Alpha & NT for Alpha must be tested
>separately from a PC & NT for PC?

Yes.

>
>How much variation in the hardware is allowed after the test
>is completed and the security is verified?  For example, if a
>PS/2 Model 95 & NT is tested and approved, does this mean that
>an untested PS/2 Model 90 & NT is also approved, or does the
>certification require *exact* hardware matching.

To answer the question requires a bit more work than I am prepared to type.

For further reference, I suggest the following books:

"Department of Defense Trusted Computer System Evaluation Criteria"
     -DoD 5200.28-STD

"Computer Security Requirements -- Guidance for Applying the Department
 of Defense Trusted Computer System Evaluation Criteria in Specific
 Environments"
     -CSC-STD-003-85

"Trusted Product Evaluations:  A Guide for Vendors"
     -NCSC-TG-002

"Rating Maintenance Phase - Program Document"
     -NCSC-TG-013

"Trusted Product Evaluation Questionnaire"
     -NCSC-TG-019

These books are all in what is called "The Rainbow Series".  (It was
named this way because the books all come in different colors.)  You may
obtain copies (for free) from:

Director, National Security Agency
Information Security Awareness Program
Attention:  X713
Fort George G. Meade, Maryland 20755-6000
(301) 688-8742, or (301) 766-8729

Now, so that one has an idea of what is involved with these tests, here is
a quote from Section 10.1 of the DoD Trusted Computer System Evaluation
Criteria:

"10.1  Testing for Division C"

"10.1.1 Personnel:  The security testing team shall consist of at least
 two individuals with bachelor degrees in Computer Science or the equi-
 valent.  Team members shall be able to follow test plans prepared by the
 system developer and suggest additions, shall be familiar with the flaw
 hypothesis or equivalent security testing methodology, and shall have
 assembly-level programming experience.  Before testing begins, the team
 members shall have functional knowledge of, and shall have completed the 
 system developer's internals course for, the system being evaluated."

"10.1.2 Testing:  The team shall have 'hands-on' involvement in an 
 independent run of the tests used by the system developer.  The team shall
 independently design and implement at least five system-specific tests
 in an attempt to circumvent the security mechanisms of the system.  The
 elapsed time devoted to testing shall be at least one month and need not
 exceed three months.  There shall be no fewer than twenty hands-on hours
 spent carrying out system developer-defined tests and test team-defined
 tests."

>Thanks in advance to anyone that answers.

You're welcome.

>-- 
>====== Mike Levis   mlevis@ringer.cs.utsa.edu ======
>"I believed what I was told, I thought it was a good   .--.
>life, I thought I was happy.  Then I found something  (OS/2)
>that changed it all..."  --  Anonymous, 2112  [Rush]   ~--~


-- 
D. Robert Spexet II, N0OKR   Internet:  spexet@math.lsa.umich.edu
Department of Mathematics    BITnet:    user68xr@umichum.bitnet
The University of Michigan   UUCP:      uunet!mailrus!math.lsa.umich.edu!spexet
Ann Arbor, Michigan 48109
Xref: sparky comp.os.os2.advocacy:4885 comp.os.os2.misc:28991