All of the database cartridges collect SQL Statements which might include PII data.
By default Foglight will replace Personally Identifiable Information (PII) or “sensitive” data before transferring performance information to the Foglight environment. This will be done by replacing string, integer and decimal literals that are found in SQL statements and queries with placeholder data which has no reference to the original PII or sensitive data. This placeholder data cannot be reversed into the original data and has no association with that data.
A parameter will be added to enable the user to change the default to collecting all data with a warning message.
This functionality allows Foglight to meeting GDPR and HIPPA standards by removing literals and allowing users to use it without concern.
The mechanism to remove literals should be available for all the DB cartridges. At the time of the collection, before storing the data, each cartridge should remove literals by calling this mechanism.
The functionality will remove literals
A customer-facing feature is available to enable/disable the functionality. This will only be at the FMS level using one parameter and will then be applied to all domains. Changing the state will show a clear message about the implication of the state change and request the user to confirm the state change.
Only Foglight administrators will have this capability.
The numeric value (integer and decimal) we use for replacement will be a valid number
The pattern will be 1 and then trailing zeros to the size of the original number.
i.e. 387 > 100; 45827 > 10000; 12 > 10
This functionality is activated at the FMS level and can be accessed by the following:
This functionality was included in Foglight Cloud and SQL Server cartridge beginning with the 7.1 release as part of enhancement FOG-5389. Other cartridges such as DB2, Oracle, and Azure SQL inclided the enhancement in the 7.2.1 or 7.2.2 versions and higher.