Skip to main content

CISSP - Biba Model (Biba Integrity Model)


Origin: Published in 1977 at the Mitre Corporation, one year after the Bell La-Padula model. While BLP model addresses Confidentiality (and nothing about Integrity), Biba proposed this model to address Integrity





Biba Integrity model describes a set of access control rules that are designed to ensure data integrity. Subjects and Objects are grouped into various ordered levels of integrity.





Access modes of Biba Model





  • Modify: This allows a subject to write to an object. In layman parlance, it is equivalent to write mode in other models.
  • Observe: This allows a subject to read an object. This command is synonymous to the read command of other models.
  • Invoke: This allows one subject to communicate with another subject.
  • Execute: This allows a subject to execute an object. The command essentially allows a subject to execute a program which is the object




This model is directed towards data integrity (rather than confidentiality). It is also called "read up, write down" model. This implies users can only write content at or below their own integrity level. Similarly, users can only read content at or above their own integrity level.





Set of rules defined by Biba model:





The Simple Integrity Property states that a subject at a given level of integrity must not read data at a lower integrity level (no read down)





Mathematically, denoted as: s ∈ S can observe o∈ O if and only if i(s) ≤ i(o)









The * (star) Integrity Property states that a subject at a given level of integrity must not write data at a higher level of integrity (no write up).





Mathematically, denoted as: s ∈ S can modify to o∈ O if and only if i(o) ≤ i(s)









Invocation Property states that a process from below cannot request higher access; only with subjects at an equal or lower level.





Mathematically, denoted as: s₁ ∈ S can invoke s₂ ∈ S if and only if i(s₂ ) ≤ i(s₁ )






Labels:

Comments

Post a Comment

Popular posts from this blog

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account. ...
7 comments
Read more

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o...
Post a Comment
Read more

MITRE ATT&CK - Tools, Attacks and Related - 1

MASSCAN - Mass IP port scanner https://github.com/robertdavidgraham/masscan TeamTNT - Threat group that has primarily targeted cloud and containerized applications. The group has been active since at least Oct 2019 and has mainly focused its efforts on leveraging cloud and container resources to deploy cryptocurrency miners in victim environments. List of Techniques used by TeamTNT can be found here: https://attack.mitre.org/groups/G0139/ Mimikatz - Is a credential dumper capable of obtaining plaintext Windows account logins and passwords, along with many other features that make it useful for testing the security of networks. Golden Ticket Attack - A golden ticket in Active Directory grants the bearer unlimited access. A golden ticket attack abuses the Kerberos protocol, which depends on the use of shared secrets to encrypt and sign messages. One of these secrets is known only to the Key Distribution Center (KDC): the password hash for the KRBTGT user, which is used to issue the Ke...
2 comments
Read more