![]() |
![]() |
Articles / TULARC / Security / Computer Security Evaluation / | ![]() |
|
![]() |
||||
![]() |
![]() |
|||
![]() |
![]() |
|||
![]() |
||||
|
|
||||
![]() |
![]() |
|||
![]() |
23 What is assurance? (Computer Security Evaluation) |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
|
|
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
This article is from the Computer Security Evaluation FAQ, by Trusted Product Evaluation Program TPEP@dockmaster.ncsc.mil.
In the context of the Trusted Computer System Evaluation
Criteria (TCSEC), assurance coincides with correctness
assurance. It is a measure of confidence that the security
features and architecture of a computer system accurately
mediate and enforce the system security policy. The TCSEC's
assurance-related requirements constrain development methods
(e.g., configuration management) and software engineering
practices (e.g., modular code). Higher evaluation classes
contain more assurance-promoting requirements and give more
confidence in correctness.
 
Continue to:
computer security, evaluation, TREP, Trusted Product Evaluation Program, Federal Criteria, hacker-proof
![]() |
|
|