Protect PII - in BSM and BPM

  • KM03201639
  • 12-Jul-2018
  • 12-Jul-2018

This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.

Summary

Files/folders that may contain (PII) Personally Identifiable Information should be able to be on separate disk partitions with the objective of protect sensitive information

Reference

Requirement:

Files/folders that may contain (PII) Personally Identifiable Information should be able to be on separate disk partitions with the objective of protect sensitive information.
Impacted areas that should be take into account:

1) Log files that are used by the Gateway and Application servers must point to a special disk partition e.g. "L:" drive.
2) BPM temp and log files must be directed to a separate disk partition
3) BPM data/parameter files for the monitor scripts may need to be included in this consideration

Expected behavior:
-Move the files that may can contain sensitive data (PII), of BSM installation folder in a different partition, to protect the PII.
-Protect the data stored under BSM script repository.
-Protect the data that contain the Vugen scripts parameters files and webpages that the Vugen script hits.

Resolution:

Currently, scripts are stored in a binary format in the BSM database and the passwords in the scripts are already encrypted. A note of this will be included in the documentation as part of the enhancement request.

Regarding using different disk location in BSM, there is no way to fulfill this requirement. Micofocus Research and Develpment team (R&D) is currently working on this request and will be included for the next release.

You can reference this article: https://mysupport.microfocus.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1I131263 and may subscribe to the same, in order to get updates on the ER's resolution.