{"id":1437,"date":"2016-04-19T15:45:19","date_gmt":"2016-04-19T21:45:19","guid":{"rendered":"http:\/\/www.designandexecute.com\/designs\/?p=1437"},"modified":"2024-08-31T10:34:37","modified_gmt":"2024-08-31T16:34:37","slug":"security-patterns","status":"publish","type":"post","link":"https:\/\/www.designandexecute.com\/designs\/security-patterns\/","title":{"rendered":"Security Design Patterns in Data Warehousing"},"content":{"rendered":"

Security is the top priority in the digital economy. We are plagued with issues if we build systems that are silo because we cannot make relationships in the data. If we create connected systems, we need to create logical boundaries and constrict how this valuable insight is accessed and shared. The approach is to give the right information at the right level to the people who need it at the right time. In simple language, you get information on a need-to-know basis. Segmented security means we must stratify security levels into key categories or become segmented as needed. The standard security design issues fall into the following categories.<\/span><\/p>\n

    \n
  1. The user\u00a0<\/span>does not have access<\/span><\/strong>\u00a0to the information they need (usually a binary approach of you have access or not)<\/span><\/li>\n
  2. Cross Silo Analysis<\/span><\/strong>\u00a0is difficult and impossible in some cases (usual security to multiple applications)<\/span><\/li>\n
  3. Multi-Hierarchy views<\/span><\/strong>\u00a0of the same data make reporting and security hard to be aligned (If the security is tied to a hierarchy, then what happens when different lines of business use multiple hierarchies)<\/span><\/li>\n
  4. Special Case processing<\/span><\/strong>\u00a0is hard to segment and can create a disconnect.<\/span><\/li>\n
  5. Administer and Re-Certification<\/span><\/strong>, keeping pace with attrition, mergers, and transfers. Inter-organization type restructuring must be easily accounted for.<\/span><\/li>\n
  6. Transactional and Analytic security synch<\/span><\/strong>. Analytic applications of the future need to consume data and spew embedded knowledge in the reports or aggregated data back to the user. Data<\/span>\u00a0<\/span><\/strong>capture of transactional systems and reporting of analytic systems security will need to synchronize if they are different data models. They are usually separate for the performance of both functions.<\/span><\/li>\n<\/ol>\n

    Benefits of Good Security and Data Democracy Design Pattern<\/span><\/strong><\/h2>\n