DOC PREVIEW
UTD CS 4398 - Multilevel Secure Data Management

This preview shows page 1-2-15-16-17-32-33 out of 33 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Data and Applications Security Developments and DirectionsOutlineWhat is an MLS/DBMS?Why MLS/DBMS?Summary of DevelopmentsAir Force Summer StudyOutcome of the Air Force Summer StudyTDITaxonomy for MLS/DBMSsIntegrity LockOperating System Providing Mandatory Access ControlExtended KernelTrusted SubjectDistributed Approach - IDistributed Approach IIOverview of MLS/DBMS DesignsOverview of MLS/DBMS Designs (Concluded)Some MLS/DBMS Commercial Products Developed (late 1980s, early 1990s)Some Challenges: Inference ProblemSome Challenges: PolyinstantiationSome Challenges: Covert ChannelMultilevel Secure Data Model: Classifying DatabasesMultilevel Secure Data Model: Classifying RelationsMultilevel Secure Data Model: Classifying Attributes/ColumnsMultilevel Secure Data Model: Classifying Tuples/RowsMultilevel Secure Data Model: Classifying ElementsMultilevel Secure Data Model: Classifying ViewsMultilevel Secure Data Model: Classifying MetadataMLS/DBMS Functions OverviewMLS/DBMS Functions Secure Query ProcessingMLS/DBMS Functions Secure Transaction ManagementMLS/DBMS Functions Secure Integrity ManagementStatus and DirectionsData and Applications Security Developments and DirectionsDr. Bhavani ThuraisinghamThe University of Texas at DallasMultilevel Secure Data ManagementFebruary 11, 2011OutlineWhat is an MLS/DBMS?Summary of DevelopmentsChallengesMLS/DBMS Designs and PrototypesData Models and FunctionsDirectionsWhat is an MLS/DBMS?Users are cleared at different security levelsData in the database is assigned different sensitivity levels--multilevel databaseUsers share the multilevel databaseMLS/DBMS is the software that ensures that users only obtain information at or below their levelIn general, a user reads at or below his level and writes at his levelWhy MLS/DBMS?Operating systems control access to files; coarser grain of granularityDatabase stores relationships between dataContent, Context, and Dynamic access controlTraditional operating systems access control to files is not sufficientNeed multilevel access control for DBMSsSummary of DevelopmentsEarly Efforts 1975 – 1982; example: Hinke-Shafer approach Air Force Summer Study, 1982Research Prototypes (Integrity Lock, SeaView, LDV, etc.); 1984 - PresentTrusted Database Interpretation; published 1991Commercial Products; 1988 - PresentAir Force Summer StudyAir Force convened a summer study to investigate MLS/DBMS designsThen study was divided into three groups focusing on different aspectsGroup 1 investigated the Integrity Lock approach; Trusted subject approach and Distributed approachGroup 2 investigated security for military messaging systemsGroup 3 focused on longer-term issues such as inference and aggregationOutcome of the Air Force Summer StudyReport published in 1983MITRE designed and developed systems based on Integrity Lock and Trust subject architectures 1984 - 1986Rome Air Development Center (RADC, now Air Force Research Lab) funded efforts to examine long-term approaches; example: SeaView and LDV both intended to be A1 systemsRADC also funded efforts to examine the distributed approachSeveral prototypes and products followedTDITrusted Database Interpretation is the Interpretation of the Trusted Computer Systems Evaluation criteria to evaluate commercial productsClasses C1, C2, B1, B2, B3, A1 and BeyondTCB (Trusted Computing Base Subsetting) for MAC, DAC, etc. (mandatory access control, discretionary access control)Companion documents for Inference and Aggregation, Auditing, etc.Taxonomy for MLS/DBMSsIntegrity Lock Architecture: Trusted Filter; Untrusted Back-end, Untrusted Front-end. Checksum is computed by the filter based on data content and security level. Checksum recomputed when data is retrieved. Operating Systems Providing Access Control/ Single Kernel: Multilevel data is partitioned into single level files. Operating system controls access to the filedExtended Kernel: Kernel extensions for functions such as inference and aggregation and constraint processingTrusted Subject: DBMS provides access control to its own data such as relations, tuples and attributesDistributed: Data is partitioned according to security levels; In the partitioned approach, data is not replicated and there is one DBMS per level. In the replicated approach lower level data is replicated at the higher level databasesIntegrity LockDatabaseTrusted Agentto computechecksumsSensorData ManagerUntrustedData ManagerCompute ChecksumBased on stream data valueand Security level;Store data value, Security level and ChecksumCompute ChecksumBased on data valueand Security level retrievedfrom the stored databaseOperating System Providing Mandatory Access ControlUnclassifieddeviceSecretdeviceTopSecretdeviceMultilevelData ManagerUnclassifiedDataSecretDataTopSecretDataExtended KernelMultilevelDataKernel ExtensionsTo enforce additional security policies enforced on datae.g., security constraints, privacy constraints, etc.MultilevelData ManagerTrusted SubjectUnclassifieddeviceSecretdeviceTopSecretdeviceMultilevelData ManagerMultilevelDataTrustedComponentDistributed Approach - IUnclassifiedData ManagerTopSecretData ManagerUnclassifiedDataSecretDataTopSecretDataTrusted Agentto manage Aggregated DataSecretData Manager UnclassifiedData ManagerTopSecretData ManagerUnclassifiedDataSecretDataTopSecretDataTrusted Agentto manage Aggregated DataSecretData ManagerDistributed Approach IIUnclassifiedData ManagerTopSecretData ManagerUnclassifiedDataSecret + UnclassifiedDataTopSecretSecret + UnclassifiedDataTrusted Agentto manage Aggregated DataSecretData ManagerOverview of MLS/DBMS DesignsHinke-Schaefer (SDC Corporation) Introduced operating system providing mandatory access controlIntegrity Lock Prototypes: Two Prototypes developed at MITRE using Ingres and Mistress relational database systemsSeaView: Funded by Rome Air Development Center (RADC) (now Air Force Rome Laboratory) and used operating system providing mandatory access control and introduced polyinstationLock Data Views (LDV) : Extended kernel approach developed by Honeywell and funded by RADC and investigated inference and aggregationOverview of MLS/DBMS Designs (Concluded)ASD, ASD-Views: Developed by TRW based on the Trusted subject approach. ASD Views provided access control on viewsSDDBMS: Effort by Unisys funded by RADC and investigated the distributed approachSINTRA:


View Full Document

UTD CS 4398 - Multilevel Secure Data Management

Documents in this Course
Botnets

Botnets

33 pages

Botnets

Botnets

33 pages

Load more
Download Multilevel Secure Data Management
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Multilevel Secure Data Management and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Multilevel Secure Data Management 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?