The protection of information in computer systems

By J. Saltzer, M. D. Schroeder. 1975

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

Prochlo: Strong Privacy for Analytics in the Crowd (2017, background): “Generally, privacy is intuitively understood as individuals’ socially-defined ability to control the release of their personal information [5,64].”
Machine Unlearning (2019, background): “Additionally, such a guarantee should be intuitive and easy to understand for non-experts [28].”
On Evaluating Adversarial Robustness (2019, background): “The open design of security mechanisms is a cornerstone of the field of cryptography (Saltzer & Schroeder, 1975).”
PROCHLO: Strong Privacy for Analytics in the Crowd (2017, background): “Generally, privacy is intuitively understood as individuals’ socially-defined ability to control the release of their personal information [5,64].”
Secure and Flexible Monitoring of Virtual Machines (2007, background): “For example, some of our requirements could be seen as specialized versions of Saltzer and Schroeder’s classic security design principles [28].”
Relationships and data sanitization: a study in scarlet (2010, background): “But either approach is possible when sharing data, and in fact the Principle of Least Privilege [79] would require the former A key part of any research is validation.”
The CHERI capability model: Revisiting RISC in an age of risk (2014, background): “Strong memory protection has long been sought for computer systems [10, 35].”
An Attack Surface Metric (2011, background): “, Saltzer and Schroeder’s design principles for protection mechanisms [87].”
Singularity: rethinking the software stack (2007, background): “The Singularity ABI follows the principle of least privilege [ 23 ].”
Challenges for Securing Cyber Physical Systems (2009, background): “While all these efforts are important, we believe that we need to find other incentives (e.g., new policies, education and outreach efforts, or economic programs) to complement these self-regulated standards.”
A systems and control perspective of CPS security (2019, background): “In particular, three security breaches were often considered to be important for the protection of information [2]–[4]: Confidentiality, Integrity, and Availability which denote as an unauthorized information release, an unauthorized information modification, and an unauthorized denial of use of the”
Labels and event processes in the asbestos operating system (2005, methodology): “A powerful tool to contain exploits is the p rinciple of least privilege [37], which directs that each system comp nent”
Distributed computing in practice: the Condor experience (2005, unknown): “The box has already received much attention [41, 61, 15, 63], so we will focus here on describing the sand.”
Secure Control: Towards Survivable Cyber-Physical Systems (2008, background): “Finally, there are several security design principles that can be useful for designing secure control systems [27, 3].”
seL4: formal verification of an operating-system kernel (2010, background): “The kernel is a mandatory part of a system’s trusted computing base (TCB)—the part of the system that can bypass security [10].”
IRM enforcement of Java stack inspection (2000, background): “For a reference monitor [2] to enforce a security policy, (i) it must mediate all events relevant to the policy being enforced, (ii) its integrity must be protected from subversion by applications, and (iii) its presence must be transparent to applications [15].”