{'fraction_non_alphanumeric': 0.01808785529715762, 'fraction_numerical': 0.0, 'mean_word_length': 4.961538461538462, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
How Can Data Sources Specify Their Security Needs to a Data Warehouse ?

In current warehouse systems, the warehouse administrator is given complete authority to grant user permissions. She is trusted to grant only permissions that respect the security needs of the underlying data sources, but has no tools to ascertain what those needs might be, or to detect changes. We believe that such trust is rarely a good idea, and often is not possible. In earlier papers, we proposed a different strategy, in which source permissions are used to automatically derive corresponding warehouse permissions. In this paper we pull the techniques together, identify concepts missing from standard SQL permissions, and show how to extend the syntax of SQL grant commands to include them.