Governance & Compliance

The procedures in this section provide governance metadata and compliance-oriented reporting across Casabase Cube applications. Classification labels record governance intent, while inventory and privacy reporting provide broader visibility into data handling and security status.

SET_DATA_CLASSIFICATION

Minimum role: CUBE_ADMIN

SET_DATA_CLASSIFICATION(
    P_CUBE_NAME,
    P_CLASSIFICATION
) -> VARCHAR

Sets a cube’s classification label for governance reporting.

Parameters

Parameter	Type	Req/Opt	Description
P_CUBE_NAME	VARCHAR	req	Cube name.
P_CLASSIFICATION	VARCHAR	req	PUBLIC, INTERNAL, CONFIDENTIAL, or RESTRICTED.

Note

The classification label is metadata. It records governance intent and drives reporting, but it does not itself restrict access to the cube.

Example

CALL CUBE.SET_DATA_CLASSIFICATION(
    'FINANCE',
    'CONFIDENTIAL'
);

GET_DATA_INVENTORY

Minimum role: CUBE_ADMIN

GET_DATA_INVENTORY() -> TABLE

Returns an inventory of every cube, including its classification, size, and security status.

This procedure takes no parameters.

Returns

Returns:

• CUBE_NAME
• DATA_TABLE
• DATA_CLASSIFICATION
• DIMENSION_COUNT
• HAS_SECURITY
• LAST_QUERIED

Review DATA_CLASSIFICATION and HAS_SECURITY together. A cube classified as CONFIDENTIAL or RESTRICTED with no security enabled is a combination that warrants review.

LAST_QUERIED can help identify cubes that are no longer being used.

Example

CALL CUBE.GET_DATA_INVENTORY();

GET_PRIVACY_REPORT

Minimum role: CUBE_ADMIN

GET_PRIVACY_REPORT() -> VARIANT

Generates a compliance summary suitable for use in a vendor or privacy review.

This procedure takes no parameters.

Returns

Returns JSON covering:

• summary, including cube counts, classification, and security coverage
• data_handling, including egress, external connections, PII collection, and telemetry
• audit_log, including record count and retained span
• recommendations
• report_date

Example

CALL CUBE.GET_PRIVACY_REPORT();