Native Sensitivity Classification & Information Protection Framework

Introduce a native Information Classification / Sensitivity Label framework within IBM Maximo Application Suite (MAS) to support handling of sensitive, classified, export-controlled, or regulated information across UI, reports, exports, integrations, and outbound communications.

The capability should provide a scalable and centrally managed approach similar to Microsoft Purview / Outlook Sensitivity Labels rather than requiring bespoke configuration per application, report, or communication template.

Currently, IBM MAS can control data access through Security Groups and data restrictions, however there is no native mechanism to:

• Classify data as OFFICIAL, OFFICIAL SENSITIVE, ITAR, CONFIDENTIAL, etc.

• Apply sensitivity metadata to outbound content

• Enforce classification selection during exports or communications

• Watermark or mark generated reports

• Audit extraction/distribution of sensitive data

• Integrate sensitivity handling consistently across reports, email, APIs and exports

This creates a governance and compliance gap where users may legitimately access data but can subsequently export or distribute it without any indication of classification or handling requirements.

Many organisations now require controls around:

• Export-controlled data (e.g. ITAR)

• Government classifications

• Commercially sensitive information

• Controlled engineering / defence data

• Regulatory and compliance-driven data handling

Proposed Solution

Introduce a native MAS-wide Sensitivity Classification / Information Protection framework similar to Microsoft Purview / Outlook Sensitivity Labels.

Suggested functionality:

• System properties to enable sensitivity handling for reports, exports, and emails

• Mandatory sensitivity selection when generating reports, exports, or communications

• Automatic classification inheritance from records (e.g. ITAR / Sensitive flag)

• Classification banners, watermarks, headers, and footers on reports and exported files

• Integration with BIRT Reports, Communication Templates, Generate Communication dialogs, APIs, and outbound emails

• Audit logging for sensitive data exports and communications

Where possible, generated emails and files should support Microsoft Purview / MIP compatible metadata headers and document properties.

Example:
MSIP_Label_Enabled=true
MSIP_LabelName=OFFICIAL SENSITIVE
MSIP_Label_Method=Manual

This would allow downstream Microsoft 365 tooling, Exchange Mail Flow rules, Purview DLP policies, and audit tooling to recognise and enforce classification policies automatically.

The capability would provide a scalable enterprise approach rather than requiring bespoke customisation across individual reports, templates, and applications.