{
  "id": "bell-lapadula-model",
  "title": "Bell–LaPadula Model",
  "lang": "en",
  "source_lang": "en",
  "summary": "The Bell–LaPadula model formalizes confidentiality in multilevel computer systems by restricting access and preventing information from flowing to lower security levels.",
  "category": "computer-science",
  "subcategory": "networks-security",
  "type": "concept",
  "aliases": [
    "Bell–LaPadula security model",
    "BLP model"
  ],
  "generated_at": "2026-11-05",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/bell-lapadula-model/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/bell-lapadula-model/",
      "json": "https://aiwiki.page/zh/bell-lapadula-model.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "The Bell–LaPadula model is a formal access-control model designed to protect the confidentiality of information in computer systems that handle multiple security classifications. Developed by David Elliott Bell and Leonard J. LaPadula at the MITRE Corporation in the early 1970s, it describes permitted relationships between active subjects, such as processes, and passive objects, such as files. Its best-known rules are “no read up” and “no write down”: ordinary subjects cannot read information above their authorized level or transfer information to objects below the level at which they are operating."
    },
    {
      "heading": "Historical context and purpose",
      "text": "The model emerged from research on securing shared computer systems, particularly systems intended to process classified government and military information. Conventional file permissions could specify who was allowed to access a file, but did not necessarily prevent an authorized program from copying sensitive information into a less protected location.\n\nBell–LaPadula addressed this problem by combining individual permissions with system-wide restrictions based on security labels. Its foundational reports appeared in 1973, followed by further development and a consolidated exposition in 1976.\n\nThe model became an important foundation for multilevel security and influenced the treatment of mandatory access controls in the United States Department of Defense’s Trusted Computer System Evaluation Criteria, commonly called the Orange Book. It is a model of a particular security objective, not a complete specification for a secure operating system."
    },
    {
      "heading": "Subjects, objects, and security labels",
      "text": "The model distinguishes three central elements:\n\n- Subjects: active entities that request access, typically executing processes acting on behalf of users.\n- Objects: passive entities that contain or receive information, such as files, memory regions, or communication endpoints.\n- Access modes: operations that subjects may perform on objects, including reading and writing.\n\nA security label commonly contains both a hierarchical classification and a set of categories or compartments. For example,\n\n\\[L=(h,C),\\]\n\nwhere \\(h\\) is a classification level and \\(C\\) is a set of categories.\n\nA label \\(L_1=(h_1,C_1)\\) dominates another label \\(L_2=(h_2,C_2)\\), written \\(L_1\\succeq L_2\\), when\n\n\\[h_1\\geq h_2 \\quad\\text{and}\\quad C_1\\supseteq C_2.\\]\n\nThus, a higher hierarchical classification alone does not necessarily authorize access. A subject must also possess the required categories.\n\nFor example, Secret, {Nuclear, Naval} dominates Confidential, {Naval}. By contrast, Secret, {Nuclear} does not dominate Confidential, {Naval}, because it lacks the Naval category.\n\nThis produces a lattice-based access-control structure rather than merely a single ranked list. Two labels can be incomparable: neither dominates the other.\n\nClearance and current operating level\n\nA subject’s maximum authorized label, often associated with its clearance, need not be identical to its current operating label. A highly cleared user may run a process at a lower level, but that process must not retain access to higher-level information while using its lower-level permissions.\n\nThis distinction matters when interpreting the model’s rules. Clearance expresses an upper authorization bound; the current level governs information flow during execution. Simplified presentations often represent both with one subject label, which is useful for illustration but omits this distinction."
    },
    {
      "heading": "Core security properties",
      "text": "Bell–LaPadula combines mandatory restrictions with discretionary permissions. An access must satisfy all applicable conditions; passing a classification check does not automatically grant permission.\n\nSimple-security property: no read up\n\nThe simple-security property restricts reading. In a simplified fixed-label presentation, a subject \\(s\\) may read an object \\(o\\) only if the subject’s label dominates the object’s label:\n\n\\[L(s)\\succeq L(o).\\]\n\nA subject operating at Secret can therefore read a Confidential object, provided the categories and other permissions permit access, but cannot read a Top Secret object.\n\nIn formulations that distinguish maximum and current subject labels, the simple-security condition checks the subject’s authorization bound, while the star property imposes additional constraints on its current accesses.\n\nStar property: no write down\n\nThe star property, written \\(*\\)-property, prevents a subject from passing information to a lower security level. In the simplified presentation, write-only access is permitted only when the destination dominates the subject’s operating label:\n\n\\[L(o)\\succeq L(s).\\]\n\nThe purpose is to prevent a subject that can read sensitive information from depositing that information into a less protected object. Restricting reads alone would not stop an authorized program, including a malicious one, from copying a secret into a public file.\n\nThe underlying principle is that an ordinary subject must not write to a destination that fails to dominate information it is permitted to obtain through its current accesses.\n\nTechnical descriptions distinguish access modes more carefully than the slogan suggests. A write-only or append operation can be permitted upward. An operation that both reads and modifies an object generally requires equality of the relevant labels, because both the reading and writing constraints apply. Here, “append” denotes an access mode that does not reveal existing contents, not necessarily a particular file-system command.\n\nDiscretionary-security property\n\nThe discretionary-security property requires access to be authorized by the system’s discretionary permissions, commonly represented by an access-control matrix.\n\nThis corresponds to discretionary access control: permissions can depend on identities, ownership, or explicit grants. The label-based constraints implement mandatory access control, which ordinary users cannot override merely by changing file permissions.\n\nA subject may therefore have a suitable clearance but still be denied access because the file’s permissions do not authorize it."
    },
    {
      "heading": "Example of permitted information flow",
      "text": "Consider three labels with no additional categories:\n\n\\[\\text{Unclassified}<\\text{Confidential}<\\text{Secret}.\\]\n\nFor a subject operating at Confidential, the simplified mandatory rules yield:\n\nObject label | Read | Write-only\nUnclassified | Permitted | Prohibited\nConfidential | Permitted | Permitted\nSecret | Prohibited | Permitted\n\nThese permissions remain subject to discretionary authorization and any additional policy restrictions.\n\nThe apparently unusual permission to write upward reflects the model’s confidentiality objective: sending information from Confidential to Secret does not disclose it to a less authorized audience. It does not establish that such a write is safe for data integrity or operational purposes.\n\nConversely, a Secret-level subject cannot write to an Unclassified object merely because it is highly trusted as a user. Under the ordinary rules, that would create a downward information path."
    },
    {
      "heading": "State transitions and the basic security theorem",
      "text": "Bell–LaPadula describes a system in terms of states and permitted transitions. A state records security-relevant information such as current accesses, labels, and permissions. Operations such as opening an object or changing an access right move the system from one state to another.\n\nThe basic security theorem establishes an invariant-preservation result: if the initial state satisfies the model’s security conditions and every permitted transition preserves them, every reachable state remains secure with respect to those conditions.\n\nThis approach supports formal verification. It makes security claims precise enough to reason about mathematically, but the theorem is conditional. It does not prove that an implementation correctly enforces the modeled transitions, that every relevant communication mechanism has been modeled, or that the policy captures every desired security objective.\n\nTranquility and label changes\n\nChanging a security label can undermine an otherwise valid access policy. Lowering the classification of a file after sensitive information has been written into it can expose that information even if every earlier read and write passed its access checks.\n\nThe tranquility principle addresses this issue:\n\n- Strong tranquility keeps security labels unchanged during normal operation.\n- Weak tranquility allows label changes only when they do not violate the security policy.\n\nThese are constraints on label management, not alternative formulations of “no read up” and “no write down.” Dynamic labels require explicit rules that account for the information already held by subjects and objects."
    },
    {
      "heading": "Trusted subjects and declassification",
      "text": "Strictly preventing downward flow makes ordinary publication and release workflows impossible. An organization may legitimately need to review classified material, remove sensitive content, and release the result at a lower level.\n\nSuch operations require explicitly trusted mechanisms. Some formulations distinguish trusted subjects that are exempt from specified star-property restrictions. Their permitted behavior must be justified separately; exemption does not mean that arbitrary downward transfers are safe.\n\nDeclassification therefore lies at a boundary of the basic model. The access rules do not determine whether a document has been adequately reviewed or whether a release has proper authorization. Those questions require additional policy and mechanisms.\n\nEnforcement also depends on a trusted computing base: the components whose correct operation is necessary to maintain the policy. A reference monitor is the conceptual mechanism that mediates access. In implementations, protection against bypass, complete mediation, and correct handling of labels are essential."
    },
    {
      "heading": "Applications and related models",
      "text": "Bell–LaPadula provides a foundation for reasoning about labeled files, processes, and communication paths in multilevel systems. Similar principles can be applied within a database management system, where records or other data objects carry security labels, or across communication interfaces that separate security domains.\n\nIt is not a specific software product or an encryption technique. Cryptographic protection may secure stored or transmitted data, but does not by itself prevent an authorized process from copying plaintext into a lower-classified destination.\n\nThe model is often contrasted with the Biba model, which focuses on integrity. A common strict-integrity formulation of Biba uses the opposite directional restrictions: “no read down” and “no write up.” These aim to prevent lower-integrity information from contaminating higher-integrity objects. Systems requiring both confidentiality and integrity need compatible policies for both objectives."
    },
    {
      "heading": "Limitations",
      "text": "Confidentiality is not complete security\n\nBell–LaPadula does not, by itself, ensure data accuracy, authorized business transactions, or service availability. A subject might corrupt information at its own level without violating the model’s confidentiality rules. Additional controls are required for other information-security objectives.\n\nCovert channels\n\nThe explicit access rules do not automatically eliminate covert channels. A high-level process might signal information to a low-level process through resource consumption, timing, or another shared system property rather than through a modeled file write.\n\nWhether such behavior is excluded depends on what the formal system represents and what its transitions permit. Compliance with the standard access rules alone is not a comprehensive proof that no information can leak.\n\nImplementation and policy assumptions\n\nThe model assumes that labels, subject identities, and enforcement mechanisms are trustworthy. Mislabeling a sensitive object as public defeats the intended protection without necessarily violating the formal access rules.\n\nIt also does not replace authentication, protect against every software vulnerability, or control what a person does with information outside the modeled system. Its guarantees are bounded by the accuracy of the policy, the completeness of the model, and the correctness of enforcement."
    }
  ],
  "links": [
    "access-control",
    "operating-system",
    "formal-verification",
    "database-management-system",
    "encryption",
    "information-security",
    "authentication",
    "security-vulnerability"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}