Nice. However, the assumption that a report's classification should be set to the most restrictive classification of all the input columns doesn't always hold. And should have the ability to override. An aggregation of a highly sensitive field could be used to create less sensitive information. eg: Employee Salary could be summed to create the Dept Salary Expense, which is added to other cost items for each dept. Leading to a Cost/Revenue breakdown for each dept. Even a bank account number column could be used to extract the 6 leftmost chars to identify & group the Banks. Useful in a payments company for EOD settlements.
Nice. However, the assumption that a report's classification should be set to the most restrictive classification of all the input columns doesn't always hold. And should have the ability to override. An aggregation of a highly sensitive field could be used to create less sensitive information. eg: Employee Salary could be summed to create the Dept Salary Expense, which is added to other cost items for each dept. Leading to a Cost/Revenue breakdown for each dept.
Even a bank account number column could be used to extract the 6 leftmost chars to identify & group the Banks. Useful in a payments company for EOD settlements.
Thanks Madhu for sharing this security feature
Great stuff! Thanks!