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

Daniel Matichuk

dblp:119/1553 · DBLP profile ↗
← Back
8ranked-venue papers
4as first author
0since 2021 · last 2016
—ORCID · none

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

Software engineering, systems software and programming languages · 4 · 2 first-authorTheory of computation · 4 · 1 first-authorArtificial intelligence and machine learning · 2 · 1 first-authorSecurity 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.

Network and information security
1 paper
Systems and software security · 100%
Software engineering, system software, and programming languages
2 papers
Program verification · 59% Empirical software engineering · 23% Operating systems · 18%

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

TopicWeightPapersLastEvidence papers
Systems and software security › information flow control
information flow enforcement
0.212013
seL4: From General Purpose to a Proof of Information Flow Enforcement · IEEE Symposium on Security and Privacy 2013
Systems and software security
operating system security
0.212013
seL4: From General Purpose to a Proof of Information Flow Enforcement · IEEE Symposium on Security and Privacy 2013
Program verification
mechanized verification
0.212013
seL4: From General Purpose to a Proof of Information Flow Enforcement · IEEE Symposium on Security and Privacy 2013
Empirical software engineering
mining software repositories
0.112015
Empirical Study Towards a Leading Indicator for Cost of Formal Software Verification · ICSE (1) 2015
Operating systems › kernel › kernel design
microkernel
0.012013
seL4: From General Purpose to a Proof of Information Flow Enforcement · IEEE Symposium on Security and Privacy 2013

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

intransitive noninterference proof · 0.3formal verification · 0.3regression analysis · 0.2empirical analysis · 0.2
YearPublicationVenuePosition
2016 Proof of OS Scheduling Behavior in the Presence of Interrupt-Induced Concurrency
June Andronick, Corey Lewis, Daniel Matichuk, Carroll Morgan, Christine Rizkallah
ITP3
2016 Eisbach: A Proof Method Language for Isabelle
Daniel Matichuk, Toby C. Murray, Markus Wenzel 0001
J. Autom. Reason.1
2015 Empirical Study Towards a Leading Indicator for Cost of Formal Software Verification
abstract
Formal verification can provide the highest degree of software assurance. Demand for it is growing, but there are still few projects that have successfully applied it to sizeable, real-world systems. This lack of experience makes it hard to predict the size, effort and duration of verification projects. In this paper, we aim to better understand possible leading indicators of proof size. We present an empirical analysis of proofs from the landmark formal verification of the seL4 microkernel and the two largest software verification proof developments in the Archive of Formal Proofs. Together, these comprise 15,018 individual lemmas and approximately 215,000 lines of proof script. We find a consistent quadratic relationship between the size of the formal statement of a property, and the final size of its formal proof in the interactive theorem prover Isabelle. Combined with our prior work, which has indicated that there is a strong linear relationship between proof effort and proof size, these results pave the way for effort estimation models to support the management of large-scale formal verification projects.
Daniel Matichuk, Toby C. Murray, June Andronick, D. Ross Jeffery, Gerwin Klein, Mark Staples
ICSE (1)1
2015 Mining the Archive of Formal Proofs
Jasmin Blanchette, Max W. Haslbeck, Daniel Matichuk, Tobias Nipkow
CICM3
2014 An Isabelle Proof Method Language
Daniel Matichuk, Markus Wenzel 0001, Toby C. Murray
ITP1
2013 seL4: From General Purpose to a Proof of Information Flow Enforcement
abstract
In contrast to testing, mathematical reasoning and formal verification can show the absence of whole classes of security vulnerabilities. We present the, to our knowledge, first complete, formal, machine-checked verification of information flow security for the implementation of a general-purpose microkernel; namely seL4. Unlike previous proofs of information flow security for operating system kernels, ours applies to the actual 8, 830 lines of C code that implement seL4, and so rules out the possibility of invalidation by implementation errors in this code. We assume correctness of compiler, assembly code, hardware, and boot code. We prove everything else. This proof is strong evidence of seL4's utility as a separation kernel, and describes precisely how the general purpose kernel should be configured to enforce isolation and mandatory information flow control. We describe the information flow security statement we proved (a variant of intransitive noninterference), including the assumptions on which it rests, as well as the modifications that had to be made to seL4 to ensure it was enforced. We discuss the practical limitations and implications of this result, including covert channels not covered by the formal proof.
Toby C. Murray, Daniel Matichuk, Matthew Brassil, Peter Gammie, Timothy Bourke, Sean Seefried, Corey Lewis, Gerwin Klein
IEEE Symposium on Security and Privacy2
2012 Noninterference for Operating System Kernels
Toby C. Murray, Daniel Matichuk, Matthew Brassil, Peter Gammie, Gerwin Klein
CPP2
2012 Extensible Specifications for Automatic Re-use of Specifications and Proofs
Daniel Matichuk, Toby C. Murray
SEFM1