Summary: This document provides information about the extension that provides data column access support for the SQL Analyzer extension (from version ≥ 2.4)
Please see Data Column Access - 1.0 - Release Notes for more information.
The Data Column Access extension provides support for:
- GDPR policy based on GDPR indicators
- column access links with the SQL Analyzer ≥ 2.4
In what situation should you install this extension?
- If you need to check that the application is GDPR compliant using the indicators
- If you need to see Access Read and Access Write links for columns on SELECT, INSERT, UPDATE, DELETE and MERGE statements
|CAST AIP release||Supported|
Supported DBMS servers used for CAST AIP schemas
This extension is compatible with the following DBMS servers used to host CAST AIP schemas:
|CAST AIP release||CSS||Oracle||Microsoft|
|All supported releases|
Supported client languages
Provided that queries are located in EXEC SQL statements and the com.castsoftware.cpp extension was used to analyze the client code, then links to columns will be created if they exist.
|An installation of any compatible release of CAST AIP (see table above)|
|An installation of SQL Analyzer extension (from version ≥ 2.4)|
Download and installation instructions
The latest release status of this extension can be seen when downloading it from the CAST Extend server.
What results can you expect?
- Links are created for transaction and function point needs.
- You can expect the following links on the DDL side within the same sql file:
- accessRead from View / Procedure / Function / Trigger / Event to Column
- accessWrite from Procedure / Function / Trigger / Event to Column
- You can expect the same links for the following client side, only if the server-side code has been analyzed with the SQL Analyzer extension and only if they have dependencies with the SQL Analyzer analysis results:
COBOL PB VB .NET JAVAC/C++/OBJC IOS PYTHON
Special notes about Links on client side
- For Java client-side code, SQL statements used in parameters of methods including a SQL parametrization rule are analyzed.
- But 'queries' visible in the DLM (that need reviewing) are not analyzed:
Explicit queries used in an ORM context are analyzed (or not) based on if they are visible in Enlighten
COBOL EXEC SQL queries are analyzed
SQL queries founded in Python code are analyzed
- SQL queries founded in .properties (Java Property Mapping objects) are analyzed
To enable GDPR Indicator for columns, it is necessary to provide the analyzer with a configuration file (*.gdpr extension), in the same folder alongside the source code. The pattern to be used in the configuration file is: schema_name.table_name.column_name=<GDPR_indicator>.
GDPR - Very sensitive
The information stored in the column is very sensitive on its own from a GDPR point of view without being correlated with other information. The type of information involved is for example: Credit card number, health insurance number, passport number etc.
GDPR - Sensitive
The information in the column is sensitive because, when correlated with other information, it became very sensitive. The type of information involved is for example: the address, the phone number etc.
The information stored is critical for the security of the platform, such as the administrators list, etc.
The column is not involved in GDPR legislation.
You can also find attached a real example, for the AdventureWorks database:
When the GDPR Indicator should apply to the same column name from all tables, in a specific schema, use a "*" wildcard:
When we don't know the schema name, but we do know the Table and Column names, e.g.:
When using the Data Column Access extension, analysis execution time is slightly different (usually slightly longer). Here are some details of the performance we have experienced using AIP Core 8.3.24 and SQL Analyzer 3.4.4-funcrel:
|Use case||Technical details||Execution details|
100% SQL (Teradata)
1 single SQL file, file size 14.5MB
Detected variant: Ansisql
Analysis duration for 1 analysis unit:
988 access links are added
|Cobol + SQL (Db2)|
SQL: 1 single file, file size 289KB
Detected variant: Db2
Cobol: 1,996 files, 11 folders, 52MB
Analysis duration for 2 analysis units:
15,245 access links are added, all of them on the Cobol side
|.NET + SQL (Microsoft SQL Server)|
SQL: 6 files (3 files of 6 are .sqltablesize), 1 folder, 4.08 MB
Detected variant: SQL Server
.NET: 14,062 files, 2,747 folders, 1.04GB
Assemblies: 218 files, 214 folders, 68.2MB
Analysis duration for 185 analysis units:
From a total of 2,562 added access links, 6 are detected on the .NET side