proomt

Search

Search posts, papers, and topics

Hall of Fame

Hall of FameJerome H. Saltzer, Michael D. Schroeder1975137 min readpaperadvanced

The Protection of Information in Computer Systems

Read on virginia.eduHN 33·0 comments

Summary

This 1975 paper is a foundational tutorial on computer system information protection, detailing architectural structures (hardware/software) needed to prevent unauthorized use or modification. It introduces core concepts like access control lists, capabilities, and protected subsystems, and categorizes security violations into release, modification, and denial of use.

  • Protection mechanisms are essential for multi-user systems to enforce authority structures.
  • Security violations are categorized as unauthorized information release, modification, or denial of use.
  • The paper introduces core architectural concepts like access control lists (ACLs) and capabilities.
  • It defines fundamental terms such as principal, domain, and protected subsystem.

This seminal 1975 paper laid the groundwork for modern computer security principles, making it essential reading for anyone studying the history or foundational concepts of system security.

9/10
securityarchitecturehistoryoperating systemsaccess controlfoundations

Related reading

  1. Hints for Computer System Design

    Lampson’s 1983 essay distills practical design hints for computer systems, emphasizing simple, well‑defined interfaces, predictable costs, and separating common‑case from worst‑case paths. The advice, illustrated with examples from Alto, Dorado, and early OSes, remains relevant for modern system architects.

    Hall of Famemicrosoft.com62 minpaper

  2. The UNIX Time-Sharing System

    The 1974 paper outlines the original UNIX operating system for the PDP‑11, detailing its hierarchical file system, device file abstraction, and rewrite in C. It demonstrates how a small, self‑contained OS could provide multi‑user time‑sharing with a simple, uniform I/O model.

    Hall of Fameberkeley.edu43 minpaperHN71

  4. What Continuous Security Is and What It Isn’t

    The article defines continuous security as an AI‑augmented, unified control plane that embeds security checks into CI/CD pipelines, contrasting it with fragmented tool sprawl that creates alert fatigue. It promotes CloudBees Unify as a solution that deduplicates findings, enforces policy‑as‑code, and automates audit evidence.

    Codeshipcloudbees.com4 min

  5. Pragmatic principles for more rights-respecting age assurance architectures

    The article proposes a rights‑respecting approach to age‑assurance, assigning actuation to services, using devices for privacy‑preserving signal creation, offering user choice of providers, and leveraging zero‑knowledge credentials. It argues that policy must enforce open standards and end‑to‑end risk assessment to avoid privacy, security, and competition harms.

    Mozilla Automation Teammozilla.org10 min

  6. Article: Your Next DSL Author Is a Language Model

    Typed Domain Grounding (TDG) embeds a DSL inside a mainstream language the LLM already knows (e.g., Kotlin) and uses the host compiler as an oracle. The author describes five building blocks—embedding, choosing a host language with high training‑data frequency, compiler‑driven type safety, a generate‑compile‑repair loop, and an on‑demand teaching tool—and shows measured results from kUML, a Kotli…

    InfoQinfoq.com18 min