Demo Data from VLDB 2026 / reviewers in the wild / expert
Stephen D. Crocker
dblp:96/6480
· DBLP profile ↗
7ranked-venue papers
4as first author
0since 2021 · last 2008
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 6 · 3 first-authorApplied, interdisciplinary, general and emerging computing · 1 · 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
2 papers |
Network security · 89% Systems and software security · 6% Hardware security and side channels · 6% | |
| Computer networks
1 paper |
Network measurement and analytics · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Electronic design automation · 87% Processor architecture and microarchitecture · 13% | |
| Software engineering, system software, and programming languages
2 papers |
Program verification · 58% Program analysis · 32% Programming languages and type systems · 10% |
Topics — the 8 heaviest of 12, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Network security › attack resilience › attack mitigation › denial-of-service defense
DDoS defense |
0.0 | 1 | 2004 | Protecting the Internet from distributed denial-of-service attacks: a proposal · Proc. IEEE 2004 |
Network security › attack strategy
denial-of-service attack |
0.0 | 1 | 2004 | Protecting the Internet from distributed denial-of-service attacks: a proposal · Proc. IEEE 2004 |
Network measurement and analytics
internet resilience |
0.0 | 1 | 2004 | Protecting the Internet from distributed denial-of-service attacks: a proposal · Proc. IEEE 2004 |
Hardware security and side channels › hardware attack detection
malicious modification detection |
0.0 | 1 | 1989 | A Proposal for a Verification-Based Virus Filter · S&P 1989 |
Electronic design automation › hardware verification and test
hardware verification |
0.0 | 1 | 1988 | Reverification of a microprocessor · S&P 1988 |
Electronic design automation › hardware verification and test
processor verification |
0.0 | 1 | 1988 | Reverification of a microprocessor · S&P 1988 |
Program analysis › static analysis
information flow analysis |
0.0 | 1 | 1982 | Precise Information Flow Analysis by Program Verification · S&P 1982 |
Processor architecture and microarchitecture
microprocessor design |
0.0 | 1 | 1988 | Reverification of a microprocessor · S&P 1988 |
Methods — techniques the papers use, named apart from their topics
threat analysis · 0.1program verification · 0.0formal specification · 0.0theorem proving · 0.0state delta verification system · 0.0boyer-moore theorem prover · 0.0set theory · 0.0abstract interpretation · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2008 | Epilogue for RFC 1281, Guidelines for the Secure Operation of the InternetabstractThe Internet ecosystem depended on the cooperation of Internet service providers, private network operators, users and vendors in order to keep the system functioning. In this environment, we boldly attempted to offer guidelines to this growing, diverse, largely cooperating ecosystem. They were a common set of voluntary rules for the successful and increasingly secure operation of the Internet. Security is understood to include protection of the privacy of information, protection of information against unauthorized modification, protection of systems against denial of service, and protection of systems against unauthorized access. Barbara Fraser, Stephen D. Crocker |
ACSAC | 2 |
| 2004 | Protecting the Internet from distributed denial-of-service attacks: a proposalabstractAs the Internet becomes increasingly widely used and as individuals and businesses come to depend on it ever more, disruptions of service are less and less tolerable. Disruptions occur either because of a natural disaster, e.g., a fire or equipment failure, or because of a deliberate attack. Protecting against natural disasters is generally easier than protecting against malicious attacks. Our focus here is on the latter. Malicious attacks fall broadly into two classes. One class is penetration, whereby an unauthorized user gains access to one or more machines. Another class is denial-of-service attacks. In this paper, we analyze the nature and impact of this latter class of attacks and propose a method to reduce their threat and impact. Stephen D. Crocker |
Proc. IEEE | 1 |
| 1992 | Unwinding and the LOCK Proof Referees StudyabstractThe LOCK definition of non-interference and the LOCK unwinding theorem provide a method of using a non-interference model in a system with an identified potential for interference. However, the LOCK work is presented in terms specific to the LOCK system. The authors generalize the LOCK definitions and theorems so that they could be used in systems other than LOCK that have specifically identified potentials for interference They state and prove a general winding theorem for this purpose. They also show that the LOCK unwinding theorem follows from their general unwinding theorem.> Sandra Rawlings Murphy, Stephen D. Crocker, Timothy Redmond |
CSFW | 2 |
| 1989 | Software methodology for development of a trusted BMS: identification of critical problemsabstractThe vast range of security levels/compartments, complex ownership, continuous evolution, adaptive policy requirements, and the large size of battle management systems (BMSs) make it evident that the trust issues are substantial and will require extensive attention throughout the development cycle of the system. The authors outline the software development process for a BMS and identify where trusted system development requirements fit into the process. The focus is on the identification and discussion of eight leverage points that cut across the entire development process and provide the greatest opportunity to affect the security of the software that is developed. These points are visibility, protocols, downloading, configuration control, monitoring and measurement, environment, communication, and verification.> Stephen D. Crocker, Emilie J. Siarkiewicz |
ACSAC | 1 |
| 1989 | A Proposal for a Verification-Based Virus FilterabstractAn approach for filtering out programs that make unauthorized modifications is outlined. The approach is based on formal specification and verification techniques, is fail-safe, and does not require any special architectural support.> Stephen D. Crocker, Maria Pozzo |
S&P | 1 |
| 1988 | Reverification of a microprocessorabstractThe FM8501 microprocessor was defined and verified by W.A. Hunt (1986) using the Boyer-Moore theorem-prover. The authors have carried out a reverification of the machine using the State Delta Verification System. Their work correlates strongly with work done by Hunt, demonstrating that the verification community is capable of supporting its own results, drawing on the diversification of proof tools to provide independent validation of previous work. The proof strategies and the complexities that are encountered in proving correctness of microcoded processors are discussed.> Stephen D. Crocker, Eve Cohen, Sue Landauer, Hilarie K. Orman |
S&P | 1 |
| 1982 | Precise Information Flow Analysis by Program VerificationabstractInformation flow analysis algorithms for programs typically overestimate the amount of information flow that occurs in a program, since they must account for all paths through the computation graph, whether or not they are actually possible. This is the source of the information flow anomalies, which are simple situations not properly handled by syntactic information flow analysis. This paper introduces an abstract information content function for state machine models of programs, and applies it to the information firm analysis problem, in conjunction with a semantic analysis of functional behavior provided by a program verification system. Our method fits well within the framework of many existing program verification systems, requiring only a small amount of knowledge of set theory. Some of the more common information flow anomalies are shown to be handled correctly by the method. Christopher Landauer, Stephen D. Crocker |
S&P | 2 |