Data Warehosing -Security

300 views

Published on

Data Warehosing -Security

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
300
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Data Warehosing -Security

  1. 1. •A data warehouse by nature is an open, accessible system.•Aim : Make large amounts of data easily accessible to theusers•Any Security restrictions seen as obstacles to that goal,become constrains on the design of data warehouse.•This is not to say that security is not important; on thecontrary ,security is paramount to ensuring that the dataitself remains clean,consistent and integral.
  2. 2. •It is important to establish early any security and auditrequirements that will be placed on the data warehouse.•Clearly, adding security will affect performance and designof data warehouse.Security can affect many different parts of the datawarehouse such as User Access  Data Load  Data Movement  Query Generation
  3. 3. Data Classification  Based on sensitivity  Based by role or job functionUser Classification  Based on Department,Section,Group etc.. (User access hierarchy )  Based on their role (Role access hierarchy )
  4. 4. Data warehouse Inc. Sales Marketing Snr Analyst Analyst Analyst Administrator Aggregation Detailed Database Reference Summarized DetailedAdmin Data Data Sales data Sales data
  5. 5. Data Ware House Sales MarketingData Mart Data Mart Users Users
  6. 6. Data warehouse Inc. Sales MarketingAnalyst Administrator Snr Analyst Analyst AdministratorAnalyst Analyst AdministratorAnalyst AnalystAnalyst Detailed Reference Summarized Detailed Sales data Data Sales data Customer Data
  7. 7. Select customer,account_number,sum(value),count(transaction_id)From txn_last_quarterWhere transaction_date between ‘01-jun-96’ and ‘30-jun-96’Group by customer account _number---------------------------------------Restricting users by using views as--------------------------------------------Create view sales_lq asSelect customer,account_number,sum(value),count(transaction_id)From txn_last_quarterWhere transaction_date between ‘01-jun-96’ and ‘30-jun-96’ and account_id<>123456789Group by customer account _number
  8. 8. Create view sales_lq asSelect customer,account_number,sum(value),count(transaction_id)From txn_last_quarterWhere transaction_date between ‘01-jun-96’ and ‘30-jun-96’ and account_id<>123456789 or account_id<>234567891Group by customer account _number•Where possible, avoid the use of views to enforce data access restrictions. They canrapidly become a nightmare to maintain.•Use Multiple Tables instead of views also creates duplication and overheads.•Create a dummy field in position or nullify it from the user.
  9. 9. •Legal RequirementsThe design team will require some analysts with knowledge and experience ofbusiness area.•Audit Requirements connections •disconnections •data access •data changeUnderstand the reasons for each audit requirement. Only implement those that are genuinely required for local, company and security reasons.
  10. 10. •Network RequirementsWhen doing the security requirements capture it is important not to overlook issues such as network security.  encryption of data needed?  which network routes the data can take?•Data Movement  Where is the flat file is stored?  who ha access to that disk space?  do you backup encrypted or decrypted versions?  do these backups need special tapes to store ?  who has access to these tapes ?  Where that temporary table to be held ?  how do we make such tables visible ?
  11. 11. •DocumentationIt is probably better to document all the restrictions as part of a seperate datawarehouse security policy document.  Data Classifications  User Classifications  Network Requirements  Data Movement and storage requirements  All audible actions•High Security Environments Trusted RDBMS ! Trusted RDBMS will generally run on trusted operating systems.  Covert channels ! Avoid creating covert channels that Inadvertently make information about data available. ! Covert channels are not typically a problem, as the majority of data warehouses do not require such high level of security.
  12. 12. •ViewsSome of the common restrictions that may apply to the handling of views are  restricted Data Manipulation Language(DML) operations,  lost query optimization paths.  restriction on parallel processing of view projections.•Data MovementDifferent ways in which bulk data movement can occur  data loads  aggregation creation  results temporary tables  data extracts•AUDITING
  13. 13. •APPLICATION DEVELOPMENTExtra Security code may be needed for each of the process managers :  load manager  warehouse manager  query manager•Data Base Design If a table has three indexes ,three constraints, and five views on it, each copyof the table will probably add not just the copy but 11 other objects to the database aswell.•TestingFurther security additions will increase the complexity of the programme causeincrease in errors during testing phase and also additional added functionality to be

×