![]() |
![]() |
Articles / TULARC / Security / Computer Security Evaluation / | ![]() |
|
![]() |
||||
![]() |
![]() |
|||
![]() |
![]() |
|||
![]() |
||||
|
|
||||
![]() |
![]() |
|||
![]() |
27 What is a Network Security Architecture Design (NSAD) document? (Computer Security Evaluation) |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
|
|
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
This article is from the Computer Security Evaluation FAQ, by Trusted Product Evaluation Program TPEP@dockmaster.ncsc.mil.
The documentation for a network component (see Section III,
Question 5) must include a Network Security Architecture Design
(NSAD) document which describes the security expectations by this
component about other components. Each component evaluation
proceeds under the assumption that the expectations of the NSAD
are met by the other components. A collection of components
designed around the same architecture should interoperate
securely.
 
Continue to:
computer security, evaluation, TREP, Trusted Product Evaluation Program, Federal Criteria, hacker-proof
![]() |
|
|