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

Dave King 0002

dblp:k/DaveKing2 · DBLP profile ↗
← Back
5ranked-venue papers
2as first author
0since 2021 · last 2010
—ORCID · none

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

Software engineering, systems software and programming languages · 3 · 2 first-authorSecurity and privacy · 2

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
2 papers
Program analysis · 50% Software maintenance and evolution · 26% Program verification · 23%
Network and information security
3 papers
Authentication and access control · 46% Systems and software security · 27% Privacy and data protection · 27%

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

TopicWeightPapersLastEvidence papers
Program analysis
static analysis
0.222008
Effective blame for information-flow violations · SIGSOFT FSE 2008
Mining Security-Sensitive Operations in Legacy Code Using Concept Analysis · ICSE 2007
Privacy and data protection › regulatory compliance
compliance verification
0.112008
Verifying Compliance of Trusted Programs · USENIX Security Symposium 2008
Systems and software security
information flow control
0.112008
Effective blame for information-flow violations · SIGSOFT FSE 2008
Program verification › security property verification
information flow verification
0.112008
Effective blame for information-flow violations · SIGSOFT FSE 2008
Authentication and access control
access control
0.112007
Mining Security-Sensitive Operations in Legacy Code Using Concept Analysis · ICSE 2007
Authentication and access control › access control
authorization policy enforcement
0.112007
Mining Security-Sensitive Operations in Legacy Code Using Concept Analysis · ICSE 2007
Software maintenance and evolution
concept analysis
0.112007
Mining Security-Sensitive Operations in Legacy Code Using Concept Analysis · ICSE 2007
Program analysis
constraint solving
0.012008
Effective blame for information-flow violations · SIGSOFT FSE 2008
Software maintenance and evolution › software maintenance
legacy code
0.012007
Mining Security-Sensitive Operations in Legacy Code Using Concept Analysis · ICSE 2007

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

constraint solver · 0.2blame dependency graph · 0.2concept analysis · 0.1clustering · 0.1
YearPublicationVenuePosition
2010 Automating Security Mediation Placement
Dave King 0002, Susmit Jha, Divya Muthukumaran, Trent Jaeger, Somesh Jha, Sanjit A. Seshia
ESOP1
2010 An architecture for enforcing end-to-end access control over web applications
abstract
The web is now being used as a general platform for hosting distributed applications like wikis, bulletin board messaging systems and collaborative editing environments. Data from multiple applications originating at multiple sources all intermix in a single web browser, making sensitive data stored in the browser subject to a broad milieu of attacks (cross-site scripting, cross-site request forgery and others). The fundamental problem is that existing web infrastructure provides no means for enforcing end-to-end security on data. To solve this we design an architecture using mandatory access control (MAC) enforcement. We overcome the limitations of traditional MAC systems, implemented solely at the operating system layer, by unifying MAC enforcement across virtual machine, operating system, networking and application layers. We implement our architecture using Xen virtual machine management, SELinux at the operating system layer, labeled IPsec for networking and our own label-enforcing web browser, called FlowwolF. We tested our implementation and find that it performs well, supporting data intermixing while still providing end-to-end security guarantees.
Boniface Hicks, Sandra Julieta Rueda, Dave King 0002, Thomas Moyer, Joshua Schiffman, Yogesh Sreenivasan, Patrick D. McDaniel, Trent Jaeger
SACMAT3
2008 Effective blame for information-flow violations
abstract
Programs trusted with secure information should not release that information in ways contrary to system policy. However, when a program contains an illegal flow of information, current information-flow reporting techniques are inadequate for determining the cause of the error. Reasoning about information-flow errors can be difficult, as the flows involved can be quite subtle. We present a general model for information-flow blame that can explain the source of such security errors in code. This model is implemented by changing the information-flow verification procedure to: (1) generate supplementary information to reveal otherwise hidden program dependencies; (2) modify the constraint solver to construct a blame dependency graph; and (3) develop an explanation procedure that returns a complete and minimal error report. Our experiments show that information-flow errors can generally be explained and resolved by viewing only a small fraction of the total code.
Dave King 0002, Trent Jaeger, Somesh Jha, Sanjit A. Seshia
SIGSOFT FSE1
2008 Verifying Compliance of Trusted Programs
Sandra Julieta Rueda, Dave King 0002, Trent Jaeger
USENIX Security Symposium2
2007 Mining Security-Sensitive Operations in Legacy Code Using Concept Analysis
abstract
This paper presents an approach to statically retrofit legacy servers with mechanisms for authorization policy enforcement. The approach is based upon the observation that security-sensitive operations performed by a server are characterized by idiomatic resource manipulations, called fingerprints. Candidate fingerprints are automatically mined by clustering resource manipulations using concept analysis. These fingerprints are then used to identify security-sensitive operations performed by the server. Case studies with three real-world servers show that the approach can be used to identify security-sensitive operations with a few hours of manual effort and modest domain knowledge.
Vinod Ganapathy, Dave King 0002, Trent Jaeger, Somesh Jha
ICSE2