DoD 5200.28-STD, DoD Trusted Computer System Evaluation Criteria, December 26, 1985. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
A Guide To Procurement Of Single And Connected Systems - Language For Rfp (Correct)
....Control (DAC) in Trusted Systems, September 30, 1987. 11] NCSC TG 004, Glossary of Computer Security Terms, October 21,1988. 12] NCSC TG 005, Trusted Network Interpretation, July 31, 1987. 13] NCSC TG 006, A Guide to Understanding Configuration Management in Trusted Systems, March 28, 1988. [14] NCSC TG 007, A Guide to Understanding Design Documentation in Trusted Systems, October 2, 1988. 15] A1 Only) NCSC TG 008, A Guide to Understanding Trusted Distribution in Trusted Systems, December 15, 1988. 16] NCSC TG 010, Version 1, A Guide to Understanding Security Modeling in Trusted ....
DoD 5200.28-STD, DoD Trusted Computer System Evaluation Criteria, December 26, 1985.
The "Session Tty" Manager - Bellovin Ulysses (Correct)
....part of any solution) noting when a session has ended is another. Today, detecting logout is insufficient; the process using the drive may be running in the background. Sessions, however, persist until the last process is gone. Session based ttys are also useful to B2 level secure UNIX systems [2] . Such systems require the existence of a trusted path a mechanism invoked by the user that will reliably connect that user to a trusted program. The trusted path must be used at login time; that way, the user is guaranteed that the Password: prompt is not coming from a Trojan horse ....
DoD Computer Security Center. DoD Trusted Computer System Evaluation Criteria , 1983, CSCSTD -001-83. done with aps
A Guide To Procurement Of Single And Connected Systems - Language For (Correct)
....Control (DAC) in Trusted Systems, September 30, 1987. 11] NCSC TG 004, Glossary of Computer Security Terms, October 21,1988. 12] NCSC TG 005, Trusted Network Interpretation, July 31, 1987. 13] NCSC TG 006, A Guide to Understanding Configuration Management in Trusted Systems, March 28, 1988. [14] NCSC TG 007, A Guide to Understanding Design Documentation in Trusted Systems, October 2, 1988. 15] A1 Only) NCSC TG 008, A Guide to Understanding Trusted Distribution in Trusted Systems, December 15, 1988. 16] NCSC TG 010, Version 1, A Guide to Understanding Security Modeling in Trusted ....
DoD 5200.28-STD, DoD Trusted Computer System Evaluation Criteria, December 26, 1985.
Security Problems in the TCP/IP Protocol Suite - Bellovin (1989) (57 citations) (Correct)
....so as to disguise the intrusion. It should be noted, of course, that any of these encryption schemes provide privacy. Often that is the primary goal of such systems. 7. 3 Trusted Systems Given that TCP IP is a Defense Department protocol suite, it is worth asking to what extent the Orange Book [48] and Red Book [49] criteria would protect a host from the attacks described above. That is, suppose that a target host (and the gateways ) were rated B1 or higher. Could these attacks succeed The answer is a complex one, and depends on the assumptions we are willing to make. In general, hosts ....
DoD Computer Security Center. DoD Trusted Computer System Evaluation Criteria , 1983, CSCSTD -001-83.
A Guide to Understanding Audit in Trusted Systems - National Computer (1988) (3 citations) Self-citation (Security) (Correct)
No context found.
National Computer Security Center, DoD Trusted Computer System Evaluation Criteria, DoD, DoD 5200.28-STD, 1985.
Pcis Architecture - Framework Definition Self-citation (December) (Correct)
....access control) is brought about by explicitly calling the appropriate interface functions. 2.3.7 Internal (1) In an implementation of the PCIS that supports access control, every request for access to an object by a subject must be evaluated by some central authority. The TCSEC (see [3] on page 181) uses the term reference monitor for this concept. This authority then either passes on the request to the service addressed or refuses it. Such an authority must be tamper proof, and it must be impossible to circumvent it. 2.3.8 Related Services (1) The access control service within ....
....(7) There are many possible trigger models. They depend on the kind of event that are taken in account, how they can be composed, the ability to describe constraints to be checked before action execution, the kind of action that can be triggered, the context in which they have to execute (see [3] [17] 31] 18] on page 181) There is no consensus yet on the exact nature of such language. SQL 3 (see [24] on page 182) provides a limited definition of a trigger mechanism specific to a relational model. The PCIS trigger model will at least support its implementation. 3.7.1.1 Event Type (1) ....
DoD Trusted Computer System Evaluation Criteria (TCSEC), United States Department of Defense, DoD 5200.28-STD December 1985, Library # S 225,711.
Technical Rational Behind Csc-Std-003-85: Computer Security.. - Unknown (1985) Self-citation (Security) (Correct)
No context found.
DoD Computer Security Center, DoD Trusted Computer System Evaluation Criteria, CSC-STD-001-83, IS August 1983.
Pretty Good Assurance - Williams, Schaefer, Landoll (1995) (1 citation) (Correct)
No context found.
DOD 5200.28-STD, "DoD Trusted Computer System Evaluation Criteria." December 26, 1985.
An Enterprise Assurance Framework - Douglas Landoll Landoll (Correct)
No context found.
DoD 5200.28-STD, "DoD Trusted Computer System Evaluation Criteria." December 26, 1985.
Emerging Challenge: Security And Safety In Cyberspace - Hundley, Anderson (1995) (1 citation) (Correct)
No context found.
DOD Trusted Computer System Evaluation Criteria (TCSEC), DoD 5200.28-STD. Washington, DC: U.S. Government Printing Office, Dec. 1985.
Tool Integration And Coordination - The (Correct)
No context found.
DoD Trusted Computer System Evaluation Criteria (TCSEC), United States Department of Defense, DoD 5200.28-STD December 1985, Library # S 225,711.
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