ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

APM database user data and General Data Protection Regulation (GDPR)

book

Article ID: 145892

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

We identified some personal user data in CA APM. 
We need to get our Environment working with the General Data Protection Regulation (GDPR) rules
Can you provide us Information about what these DB-Values are used for?

1. table: aca_user
attribute: user_id

2. table: apm_owner
attribute: user_id

3. table: appmap_attribs
attribute: value

4. table: appmap_settings
attribute: user_id

5. table: qrtz_job_details
attribute: discription

Environment

APM 10.7

Resolution

The fields are not related to GDPR, they don't contain personal data unless entered by the user. There is no support to limit saving 

1. table: aca_user
attribute: user_id

There is a table aca_user which is used to store information about user permissions. It uses login name stored in column "user_id".
ACA is an API for storage for a role and authorization information in EM. All tables used by ACA start with aca_

ACA contains data like this:
1. assignment of Universes in ATC UI EM,
2. cached User-Group relations in EM,
3. when ACC Configuration Server (CS) is being used and configured with the ACA endpoint settings then ACC CS stores roles of users in ACA.
When ACC CS is configured this way, it will provide user management features in ACC CS UI.

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/administrating/configure-ca-apm-command-center/user-management-in-ca-apm-command-center.html

ACA in EM allows ACC CS to store a role of user. This operation can be done by administrative user of ACC CS in User Management tab (visible only when ACA is configured). There is an operation to remove such stored role (a "delete" button in ACC CS User management).

2. table: apm_owner 
attribute: user_id
The "owner" here is actually a business transaction, not a person.

apm_* tables are not used in 10.7. These tables are for old legacy map in WS and WV. ATC uses appmap_* tables.

3.table: appmap_attribs
attribute: value
If this contains some name or personal information it was entered by the user. It can be deleted in the UI.

4. table: appmap_settings
attribute: user_id
This shouldn't be used.

5. table: qrtz_job_details
attribute: discription
This shouldn't be used, if there is some personal information it was entered by the user.