Skip to content

Commit b723bce

Browse files
committedSep 17, 2020
Fix blocking issues.
1 parent 52eb5d8 commit b723bce

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
 

‎articles/security/develop/threat-modeling-tool-feature-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ You can connect elements in two ways:
153153

154154
If you create a threat model and forget to connect data flows to elements, you get a notification. You can ignore the message, or you can follow the instructions to fix the issue.
155155

156-
![Screenshot show a thread model a connector not connected to elements, with the message that this issue causes.](./media/threat-modeling-tool-feature-overview/messages.png)
156+
![Screenshot shows a threat model connector not connected to elements, with the message that this issue causes.](./media/threat-modeling-tool-feature-overview/messages.png)
157157

158158
### Notes
159159

‎articles/synapse-analytics/sql-data-warehouse/column-level-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Since this video was posted [Row level Security](/sql/relational-databases/secur
2222

2323
Column-level security simplifies the design and coding of security in your application, allowing you to restrict column access to protect sensitive data. For example, ensuring that specific users can access only certain columns of a table pertinent to their department. The access restriction logic is located in the database tier rather than away from the data in another application tier. The database applies the access restrictions every time data access is attempted from any tier. This restriction makes your security more reliable and robust by reducing the surface area of your overall security system. In addition, column-level security also eliminates the need for introducing views to filter out columns for imposing access restrictions on the users.
2424

25-
You could implement column-level security with the [GRANT](/sql/t-sql/statements/grant-transact-sql?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json&view=azure-sqldw-latest) T-SQL statement. With this mechanism, both SQL and Azure Active Directory (AAD) authentication are supported.
25+
You could implement column-level security with the [GRANT](/sql/t-sql/statements/grant-transact-sql?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json&view=azure-sqldw-latest) T-SQL statement. With this mechanism, both SQL and Azure Active Directory (Azure AD) authentication are supported.
2626

2727
![Diagram shows a schematic table with the first column headed by a closed padlock and its cells an orange color while the other columns are white cells.](./media/column-level-security/cls.png)
2828

0 commit comments

Comments
 (0)
Please sign in to comment.