Information Security
Protection Models
BS IT 6th Semester
Government College University, Fiasalabad
Prepared by:
Gul Farheen Ulfat
09/09/2024
Protection Models
•A protection model refers to a conceptual framework or set of principles
designed to safeguard data and systems from unauthorized access, misuse,
or breaches. These models outline how to enforce security policies and
manage access controls to protect sensitive information. Protection models
are used to design and implement security mechanisms and policies
tailored to the needs and risks of an organization. They help in
structuring security measures and controls to manage the complexities of
safeguarding information in various environments.
Access Conctrol
• Access Control: This defines who can access what data and under what conditions.
Common access control models include:
• Discretionary Access Control (DAC): Allows owners of resources to set permissions.
• Mandatory Access Control (MAC): Enforces access policies based on classifications and
labels, often used in military or governmental contexts.
• Role-Based Access Control (RBAC): Grants access based on user roles, simplifying
management and ensuring users get access aligned with their duties.
Key Aspects of Protection Models
• Principle of Least Privilege: Ensures that users and systems have the minimum level of access
necessary to perform their functions, reducing the potential damage from accidental or malicious actions.
• Separation of Duties: Divides tasks and privileges among multiple individuals to prevent fraud or
error, ensuring no single person has control over all aspects of a critical process.
• Data Integrity: Protects data from being altered or corrupted, ensuring that it remains accurate and
trustworthy.
• Confidentiality: Ensures that information is only accessible to those who are authorized to view it,
protecting it from unauthorized disclosure.
• Availability: Ensures that authorized users have reliable access to information and resources when
needed, protecting against disruptions and ensuring business continuity.
Bell Lapadula
•The Bell-LaPadula (BLP) model, introduced by David Bell and Leonard
LaPadula in 1973, is a formal model designed to enforce data
confidentiality in computer systems. It primarily focuses on
preventing unauthorized access to sensitive information by
implementing a set of access control rules. The BLP model is often
applied in military and governmental contexts where confidentiality is
crucial.
Security Levels
•Classification Levels: Data is categorized based on its sensitivity.
For example:
•Top Secret: Highest level of sensitivity; unauthorized disclosure
could cause exceptionally grave damage.
•Secret: Unauthorized disclosure could cause serious damage.
•Confidential: Unauthorized disclosure could cause damage.
•Unclassified: No damage expected from unauthorized disclosure.
Security Levels
•Clearance Levels: Users are granted access based on
their clearance, which should be equal to or higher than
the classification of the data they need to access.
• Users are assigned security clearances corresponding to
the data classification levels they are permitted to access.
Access Control Rules
•Simple Security Property (No Read Up): A subject (e.g., a user or
process) with a lower security clearance cannot read data at a higher security
level. This rule prevents users from accessing information they are not
authorized to see.
•Example: A user with a "Confidential" clearance level cannot read a
document classified as "Secret" or "Top Secret." This restriction helps to
protect higher-level information from being accessed by less authorized users.
Access Control Rules
•Star Property (No Write Down): A subject at a higher security level
cannot write data to a lower security level. This prevents the inadvertent or
malicious leakage of sensitive information to less secure levels.
•Example: A user with "Top Secret" clearance cannot write or modify a
document classified as "Confidential" or "Unclassified." This ensures that
sensitive information does not inadvertently affect less sensitive data.
Access Control Rules
•Strong Tranquility Property: This rule states that the security
level of data cannot change while a subject is accessing it. In other
words, once a piece of data is assigned a classification level, it does
not change during the access period.
•Example: If a user with "Secret" clearance is accessing a document,
the classification of that document cannot be changed to "Top Secret"
or "Confidential" during the access session.
Access Control Rules
•Weak Tranquility Property: This rule allows for changes in
security levels of data as long as the changes do not violate the
current access control policies.
•Example: If a document's classification is changed from
"Confidential" to "Secret," this change is permissible as long as it
complies with the existing access controls and does not lead to
unauthorized access.
Practical Implementation
•The Bell-LaPadula model is highly relevant in environments where maintaining
data confidentiality is paramount. It is commonly applied in:
•Military Systems: Protects sensitive military information from unauthorized
access.
•Government Agencies: Ensures classified information remains confidential.
•Corporate Environments: Safeguards proprietary and confidential business
information.
Limitations
•While the Bell-LaPadula model is effective for ensuring
data confidentiality, it does not address other aspects of
security, such as data integrity or availability. To address
these aspects, other models or additional security
mechanisms must be implemented.
Conclusion
•In summary, the Bell-LaPadula model is a cornerstone of
confidentiality-focused security policies, providing a structured
approach to managing access based on security clearances and
data classifications. Its rules ensure that sensitive information is
protected from unauthorized access and modification,
supporting a secure and reliable information environment.
Biba Model
•The Biba model is a security model used in information security
to ensure data integrity. Developed by Kenneth Biba in 1977, it
focuses on preventing unauthorized modifications of data,
rather than ensuring data confidentiality. It’s a key model in the
realm of computer security, particularly for environments
where maintaining the integrity of information is critical.
Integrity Levels
•Low Integrity Level: This level pertains to data or users
that are considered less trustworthy or less reliable.
•High Integrity Level: This level pertains to data or
users that are deemed more trustworthy and reliable.
Integrity Policies
•Simple Integrity Property (No Write Down): This rule stipulates that a
subject (e.g., a user or process) at a higher integrity level cannot write to an
object (e.g., a file or database) at a lower integrity level. The idea is to prevent
data from being compromised by less reliable sources.
•Example: Imagine a high-level analyst working on classified information.
According to the Biba model, they should not be able to modify a public
document (lower integrity level) because their input might corrupt or
introduce inaccuracies into less critical documents.
Integrity Policies
•Star Integrity Property (No Read Up): This rule stipulates that a subject
at a lower integrity level cannot read an object at a higher integrity level. This
is intended to prevent a less trustworthy subject from obtaining potentially
more reliable data, which could be used to corrupt or taint more reliable
information.
•Example: If a data entry clerk (lower integrity) attempts to access a high-
integrity financial report, the model prevents this action to ensure that less
trustworthy users don’t read or potentially manipulate sensitive information.
Integrity Constraints
•Prevention of Integrity Downgrade: The model ensures that once data
is classified at a certain integrity level, it cannot be intentionally downgraded
to a lower level. This maintains the quality and reliability of data as it is
processed or stored.
• Prevention of Integrity Upgrade: To prevent data from being mistakenly
or maliciously upgraded, the Biba model includes checks and validations to
ensure data integrity levels are appropriately managed and verified.
Practical Implementation
•In practice, the Biba model might be used in environments where
maintaining the accuracy and trustworthiness of information is
crucial. For instance:
•Financial Systems: To prevent corruption of financial records by
unauthorized or less reliable sources.
•Medical Records: To ensure that sensitive and critical medical data
remains accurate and untarnished by less secure systems or
personnel.
Limitations
•While the Biba model is effective at ensuring data integrity, it does not
address issues of data confidentiality. For comprehensive security, it is
often used in conjunction with other models, such as the Bell-LaPadula
model, which focuses on data confidentiality.
•By integrating both integrity-focused models and confidentiality-
focused models, organizations can achieve a more robust security
posture, safeguarding both the accuracy and privacy of their data.
Conclusion
•In summary, the Biba model plays a crucial role in
information security by enforcing rules to maintain the
integrity of data. Its emphasis on preventing unauthorized
modifications and ensuring data integrity makes it a
fundamental component of a well-rounded security
strategy.

protection models. information securitypptx

  • 1.
    Information Security Protection Models BSIT 6th Semester Government College University, Fiasalabad Prepared by: Gul Farheen Ulfat 09/09/2024
  • 2.
    Protection Models •A protectionmodel refers to a conceptual framework or set of principles designed to safeguard data and systems from unauthorized access, misuse, or breaches. These models outline how to enforce security policies and manage access controls to protect sensitive information. Protection models are used to design and implement security mechanisms and policies tailored to the needs and risks of an organization. They help in structuring security measures and controls to manage the complexities of safeguarding information in various environments.
  • 3.
    Access Conctrol • AccessControl: This defines who can access what data and under what conditions. Common access control models include: • Discretionary Access Control (DAC): Allows owners of resources to set permissions. • Mandatory Access Control (MAC): Enforces access policies based on classifications and labels, often used in military or governmental contexts. • Role-Based Access Control (RBAC): Grants access based on user roles, simplifying management and ensuring users get access aligned with their duties.
  • 4.
    Key Aspects ofProtection Models • Principle of Least Privilege: Ensures that users and systems have the minimum level of access necessary to perform their functions, reducing the potential damage from accidental or malicious actions. • Separation of Duties: Divides tasks and privileges among multiple individuals to prevent fraud or error, ensuring no single person has control over all aspects of a critical process. • Data Integrity: Protects data from being altered or corrupted, ensuring that it remains accurate and trustworthy. • Confidentiality: Ensures that information is only accessible to those who are authorized to view it, protecting it from unauthorized disclosure. • Availability: Ensures that authorized users have reliable access to information and resources when needed, protecting against disruptions and ensuring business continuity.
  • 5.
    Bell Lapadula •The Bell-LaPadula(BLP) model, introduced by David Bell and Leonard LaPadula in 1973, is a formal model designed to enforce data confidentiality in computer systems. It primarily focuses on preventing unauthorized access to sensitive information by implementing a set of access control rules. The BLP model is often applied in military and governmental contexts where confidentiality is crucial.
  • 6.
    Security Levels •Classification Levels:Data is categorized based on its sensitivity. For example: •Top Secret: Highest level of sensitivity; unauthorized disclosure could cause exceptionally grave damage. •Secret: Unauthorized disclosure could cause serious damage. •Confidential: Unauthorized disclosure could cause damage. •Unclassified: No damage expected from unauthorized disclosure.
  • 7.
    Security Levels •Clearance Levels:Users are granted access based on their clearance, which should be equal to or higher than the classification of the data they need to access. • Users are assigned security clearances corresponding to the data classification levels they are permitted to access.
  • 8.
    Access Control Rules •SimpleSecurity Property (No Read Up): A subject (e.g., a user or process) with a lower security clearance cannot read data at a higher security level. This rule prevents users from accessing information they are not authorized to see. •Example: A user with a "Confidential" clearance level cannot read a document classified as "Secret" or "Top Secret." This restriction helps to protect higher-level information from being accessed by less authorized users.
  • 9.
    Access Control Rules •StarProperty (No Write Down): A subject at a higher security level cannot write data to a lower security level. This prevents the inadvertent or malicious leakage of sensitive information to less secure levels. •Example: A user with "Top Secret" clearance cannot write or modify a document classified as "Confidential" or "Unclassified." This ensures that sensitive information does not inadvertently affect less sensitive data.
  • 10.
    Access Control Rules •StrongTranquility Property: This rule states that the security level of data cannot change while a subject is accessing it. In other words, once a piece of data is assigned a classification level, it does not change during the access period. •Example: If a user with "Secret" clearance is accessing a document, the classification of that document cannot be changed to "Top Secret" or "Confidential" during the access session.
  • 11.
    Access Control Rules •WeakTranquility Property: This rule allows for changes in security levels of data as long as the changes do not violate the current access control policies. •Example: If a document's classification is changed from "Confidential" to "Secret," this change is permissible as long as it complies with the existing access controls and does not lead to unauthorized access.
  • 12.
    Practical Implementation •The Bell-LaPadulamodel is highly relevant in environments where maintaining data confidentiality is paramount. It is commonly applied in: •Military Systems: Protects sensitive military information from unauthorized access. •Government Agencies: Ensures classified information remains confidential. •Corporate Environments: Safeguards proprietary and confidential business information.
  • 13.
    Limitations •While the Bell-LaPadulamodel is effective for ensuring data confidentiality, it does not address other aspects of security, such as data integrity or availability. To address these aspects, other models or additional security mechanisms must be implemented.
  • 14.
    Conclusion •In summary, theBell-LaPadula model is a cornerstone of confidentiality-focused security policies, providing a structured approach to managing access based on security clearances and data classifications. Its rules ensure that sensitive information is protected from unauthorized access and modification, supporting a secure and reliable information environment.
  • 15.
    Biba Model •The Bibamodel is a security model used in information security to ensure data integrity. Developed by Kenneth Biba in 1977, it focuses on preventing unauthorized modifications of data, rather than ensuring data confidentiality. It’s a key model in the realm of computer security, particularly for environments where maintaining the integrity of information is critical.
  • 16.
    Integrity Levels •Low IntegrityLevel: This level pertains to data or users that are considered less trustworthy or less reliable. •High Integrity Level: This level pertains to data or users that are deemed more trustworthy and reliable.
  • 17.
    Integrity Policies •Simple IntegrityProperty (No Write Down): This rule stipulates that a subject (e.g., a user or process) at a higher integrity level cannot write to an object (e.g., a file or database) at a lower integrity level. The idea is to prevent data from being compromised by less reliable sources. •Example: Imagine a high-level analyst working on classified information. According to the Biba model, they should not be able to modify a public document (lower integrity level) because their input might corrupt or introduce inaccuracies into less critical documents.
  • 18.
    Integrity Policies •Star IntegrityProperty (No Read Up): This rule stipulates that a subject at a lower integrity level cannot read an object at a higher integrity level. This is intended to prevent a less trustworthy subject from obtaining potentially more reliable data, which could be used to corrupt or taint more reliable information. •Example: If a data entry clerk (lower integrity) attempts to access a high- integrity financial report, the model prevents this action to ensure that less trustworthy users don’t read or potentially manipulate sensitive information.
  • 19.
    Integrity Constraints •Prevention ofIntegrity Downgrade: The model ensures that once data is classified at a certain integrity level, it cannot be intentionally downgraded to a lower level. This maintains the quality and reliability of data as it is processed or stored. • Prevention of Integrity Upgrade: To prevent data from being mistakenly or maliciously upgraded, the Biba model includes checks and validations to ensure data integrity levels are appropriately managed and verified.
  • 20.
    Practical Implementation •In practice,the Biba model might be used in environments where maintaining the accuracy and trustworthiness of information is crucial. For instance: •Financial Systems: To prevent corruption of financial records by unauthorized or less reliable sources. •Medical Records: To ensure that sensitive and critical medical data remains accurate and untarnished by less secure systems or personnel.
  • 21.
    Limitations •While the Bibamodel is effective at ensuring data integrity, it does not address issues of data confidentiality. For comprehensive security, it is often used in conjunction with other models, such as the Bell-LaPadula model, which focuses on data confidentiality. •By integrating both integrity-focused models and confidentiality- focused models, organizations can achieve a more robust security posture, safeguarding both the accuracy and privacy of their data.
  • 22.
    Conclusion •In summary, theBiba model plays a crucial role in information security by enforcing rules to maintain the integrity of data. Its emphasis on preventing unauthorized modifications and ensuring data integrity makes it a fundamental component of a well-rounded security strategy.