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

Darrell M. Kienzle

dblp:17/713 · DBLP profile ↗
← Back
4ranked-venue papers
1as first author
0since 2021 · last 1997
—ORCID · none

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

Security and privacy · 4 · 1 first-author

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.

Network and information security
1 paper
Systems and software security · 100%

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

TopicWeightPapersLastEvidence papers
Systems and software security › trusted computing
trusted computing base
0.011997
Some weaknesses of the TCB model · S&P 1997
Systems and software security › secure system design
security architecture
0.011997
Some weaknesses of the TCB model · S&P 1997

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

position paper · 0.0
YearPublicationVenuePosition
1997 A practical approach to security assessment
abstract
Conventional approaches to building and assessing securitycritical software are based on the implicit assumption that security is the single most important concern and can be the primary factor driving the software development process. Changes in the marketplace and the nature of security requirements have brought this assumption into question. There is now a large class of systems in which security must compete with other development goals. A risk-driven process model of software development provides a framework for building software that balances conflicting requirements. But a risk-driven process invalidates many of the assumptions made by conventional approaches to the specification and verification of security requirements. This paper presents a new approach to assessing the degree to which software meets its security requirements. It does not propose a new specification notation or analysis technique, but provides a general framework into which existing notations and techniques ...
Darrell M. Kienzle, William A. Wulf
NSPW1
1997 Some weaknesses of the TCB model
abstract
This paper summarizes the affirmative argument supporting the proposition that "the concept of the trusted computing base (TCB) as a basis for constructing systems to meet security requirements is fundamentally flawed and should no longer be used to justify system security architectures".
Bob Blakley 0001, Darrell M. Kienzle
S&P2
1996 A Logic of Composition for Information Flow Predicates
abstract
Information flow predicates are properties of sets of traces and therefore cannot be handled under the Alpem-Schneider framework and the Abadi-Lamport Composition Principle. McLean proposed a theory (1994) to investigate the composition properties of these predicates and derived a partial order on them. In this paper we present an alternate framework based on many-sorted predicate logic for specifying the information flow properties and show that this framework can be used to reason about the composition of such properties that is amenable to automated theorem proving.
Ramesh V. Peri, William A. Wulf, Darrell M. Kienzle
CSFW3
1996 A new model of security for distributed systems
abstract
With the rapid growth of the information age, open distributed systems have become increasingly popular.The need for protection and security in a distributed environment has never been greater.The conventional approach to security has been to enforce a system-wide policy, but this approach will not work for large distributed systems where entirely new security issues and concerns are emerging.We argue that a new model is needed that shifts the emphasis from "system as enforcer" to user-definable policies.Users ought to be able to select the level of security they need and pay only the necessary overhead.Moreover.ultimately, they must be responsible for their own security.This research is being carried out in the context of the Legion project.We start by describing the objectives and philosophy of the overall project and then present our conceptual model and design decisions.A set of technical challenges and related issues are also addressed.
William A. Wulf, Darrell M. Kienzle
NSPW3