Extension ID

com.castsoftware.datacolumnaccess

What's new?

Please see Data Column Access - 1.0 - Release Notes for more information.

Description

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 compatibility

This extension is compatible with:

CAST AIP release	Supported
8.3.x
8.2.x
8.1.x
8.0.x
7.3.x

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

Language	Supported?	Notes
Mainframe Cobol
Visual Basic
.NET
Java/JEE
C/C++		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.
Python

Prerequisites

	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

Please see:

• Download an extension
• Install an extension

What results can you expect?

Links

• 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.

class Foo
{
   final static String TABLE_NAME = "Person";

	void method()
	{
    	String query = "select * from " + this.TABLE_NAME;
    	java.sql.Statement.execute(query );
	}
}

• But 'queries' visible in the DLM (that need reviewing) are not analyzed:

class Foo
{
	// not passed to an execute something
	private final static String text = "select name from Person";
}

• 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

GDPR Indicator

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>.

Template

You can also find attached a real example, for the AdventureWorks database: 

• AdventureWorks.sql
• AdventureWorks_gdprIndicator.gdpr

Examples

Schema1.Table1.Col1=GDPR - Very sensitive
Schema1.Table1.Col2=GDPR - Sensitive
Schema1.Table1.Col3=Security
......

When the GDPR Indicator should apply to the same column name from all tables, in a specific schema, use a "*" wildcard:

Schema1.*.Age=GDPR - Very sensitive

When we don't know the schema name, but we do know the Table and Column names, e.g.:

Table1.Col1=GDPR - Very sensitive

Performance

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: