Computer security Created 2026-10-24 Updated 2026-11-05
Computer security studies how to preserve intended properties of information and computing systems against failures and adversarial actions. Confidentiality limits disclosure, information integrity limits unauthorized changes, and availability concerns continued access to intended services. Authentication establishes an identity or source claim; access control decides permitted actions. A design needs an explicit threat model: encrypting stored data addresses different risks from verifying who may alter it. Security properties depend on the whole interaction between software, hardware, protocols and operational assumptions.
David Elliott Bell Created 2026-10-31 Updated 2026-11-05
David Elliott Bell is a computer scientist who developed the Bell-LaPadula model with Leonard J. LaPadula. Their work placed requirements about permitted information access inside an explicit mathematical model of a computer.[ref]
Their 1973 report distinguishes a statement of security from the mechanisms needed to enforce it. A theorem about allowed transitions protects an implementation only when the actual system enforces those transition rules. This connects a global security requirement with local obligations on access control.[ref]
Protection against unauthorised disclosure of information. Access control can prevent a subject from reading a file, while cryptographic confidentiality protects message contents against specified adversaries using cryptography.
Multiuser operating system Created 2026-10-31 Updated 2026-11-05
An operating system supporting multiple users with distinct identities and protection requirements. Access control determines which users may access shared resources.
The Bell-LaPadula model protects information confidentiality by controlling information flow between security levels. Its simple security property says that a subject may read only objects whose classification does not exceed its maximum clearance:
Thus a user cleared for confidential material cannot directly read a secret file. A readwrite permission includes reading and must satisfy the same restriction. This is an access control rule about who can learn existing contents; it says nothing by itself about where a cleared subject can subsequently copy them.
Security principal 2026-11-05
A security principal is an identity to which an access control system can attribute requests or permissions. It can represent a user, an access-control group, a service or a machine. Authentication establishes a claimed identity; authorization decides which operations that identity may perform.[ref]
For example, an analysis service can read a file using its own service identity even when a human user initiated the request. The relevant security principal for the file access is the identity carried into that access check, not automatically the human at the keyboard. Explicit identities prevent accidental confusion between who requested an action and whose authority executes it.