The model stipulates the capabilities of those principals deployed within the system and the model delineates certification and enforcement rules. An integrity policy depicts the method to be used by the data items in the system in order to remain valid as they are transitioned from one system state to another. The chief concern of this model is the formalizing of a notion of information integrity through the prevention of data corruption in a system as a result of either faults or malicious purposes. The Clark-Wilson integrity model presents a methodology to specify and analyze an integrity policy for a data system. The Bell-LaPadula model only addresses data confidentiality and not integrity. The Biba model was created to thwart a weakness in the Bell-LaPadula Model. Biba is designed so that a subject cannot corrupt data in a level ranked higher than the subject's and to restrict corruption of data at a lower level than the subject's.
Data and subjects are ordered by their levels of integrity into groups or arrangements. The Biba Model or Biba Integrity Model is a formal state transition system of data security policies designed to express a set of access control rules in order to ensure data integrity. Guidelines for Securing Teleworking Environments 569Ĭraig Wright, in The IT Regulatory and Standards Compliance Handbook, 2008 Biba and Clark Wilson Obtaining Approval for Teleworking 569 12.6.10 Monitoring and Reviewing System Access and Use 568 12.6.8Įnabling Teleworking For Users 569 12.6.9.1 User Identification and Authorization 567 12.6.6.4 Managing Operating System Access Control 566 12.6.6.1Īutomatic Terminal Identification 566 12.6.6.2 Restricting Access to Information 566 12.6.6 Managing Application Access Control 566 12.6.5.1 Suspending an Existing User Account 565 12.6.4.7ĭeleting an Existing User Account 565 12.6.5 Retrieving a Secure Server Password 561 12.6.3.4Ĭhanging a Secure Server Password 562 12.6.4Īn Overview of User Accounts 562 12.6.4.2Ĭreating a New Application User Account 564 12.6.4.5Īmending an Existing User Account 565 12.6.4.6 IT Manager Role and Responsibilities 561 12.6.3.3 Guidelines for Securing Server Passwords 561 12.6.3.2 Maintaining Server Passwords 561 12.6.3.1
Managing Privileges for User Accounts 561 12.6.3 Access Control Rules for Users and User Groups 560 12.6.1.1
0 kommentar(er)
