Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Deborah A. Tavilla

dblp:156/4168 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1985
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Operating systems · 67% Program verification · 33%
Network and information security
1 paper
Systems and software security · 100%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Operating systems › system security
operating system security
0.011985
Trusted Software Verification: A Case Study · S&P 1985
Program verification
security property verification
0.011985
Trusted Software Verification: A Case Study · S&P 1985
Operating systems › system security › operating system security
trusted computing base
0.011985
Trusted Software Verification: A Case Study · S&P 1985
Systems and software security
multilevel security
0.011985
Trusted Software Verification: A Case Study · S&P 1985

Methods — techniques the papers use, named apart from their topics

hierarchical development methodology · 0.0gypsy methodology · 0.0
YearPublicationVenuePosition
1985 Trusted Software Verification: A Case Study
abstract
This paper presents a case study of the verification of the trusted software component of the SCOMP system Trusted Computing Base (TCB). The SCOMP system was developed by Honeywell and is the first system to achieve an A1 rating from the DoDCSC. A number of papers have been published that discuss the verification approach for the SCOMP system security kernel [15, 14, 12, 10]. The SCOMP system security kernel was verified using the Hierarchical Development Methodology in a manner similar to those used for previous kernel verifications [13]. Most of the research and applications to date have been directed towards verifying the security properties of kernel software. Much less is known about verifying the security properties of trusted software. This paper will present a case study of these trusted software verification in the SCOMP system. The case study will focus on defining what trusted software is in a kernelized systems, why trusted software is trusted, what are the security requirements to be proved, and how should these requirements be proven. Then a method developed at MITRE for the review of trusted software werification evidence using the Gypsy methodolgy will be presented. Finaly, area requiring futher research will be discussed.
Terry V. Benzel, Deborah A. Tavilla
S&P2