Restricting Bank Account Number Access in Azure Synapse Analytics
Question
A famous fintech startup is setting up its data solution using Azure Synapse analytics.
As part of compliance, the company has decided that only the finance managers should be able to see the Bank Account Number and not anyone else.
Which of the following is best suited in this scenario?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C
Column-level security will control the access to particular columns based on the user membership.
In the case of sensitive data, we can decide which user or group can access a particular column.
In this question, the restriction should be given to Bank account numbers.
So, ideally column-level security can be used.
Option A is incorrect: Firewall block will completely block access to the database.
Option B is incorrect: Row-level security will prevent access to row and is not required.
Option C is correct: It will be the best solution.
Option D is incorrect: Azure RBAC cannot control access to a particular column.
To know more, please refer to the docs below:
In this scenario, the fintech startup needs to restrict access to sensitive financial data, specifically the bank account number, to only finance managers. To achieve this, the company can use column-level security in Azure Synapse Analytics.
Column-level security is a feature that enables the restriction of access to specific columns in a database table. With column-level security, the startup can specify which users or groups can view the bank account number column in the database. This is done by creating security policies that restrict access to specific columns in a table, based on the user or group.
Firewall rules to block IP and Azure RBAC roles are not best suited for this scenario. Firewall rules can block access to the entire database or specific IP addresses, but they cannot restrict access to specific columns. On the other hand, Azure RBAC roles provide access control at the Azure resource level and cannot restrict access to specific columns within a table.
Row-level security is another option, but it is not necessary in this scenario as the startup only needs to restrict access to a specific column. Row-level security is used when access to a table needs to be restricted based on the row data, which is not required in this scenario.
In summary, column-level security is the best suited option for this scenario as it enables the fintech startup to restrict access to the bank account number column in the database to only finance managers.
