Controlling Foresight Analytics Platform and Metadata Integrity

Controlling Foresight Analytics Platform and repository metadata integrity is executed as a result of:

Checking Foresight Analytics Platform integrity.
Checking repository metadata integrity.
Checking user auditing correctness.
Backup and restore of security policy.

Checking Foresight Analytics Platform Integrity

If on installing Foresight Analytics Platform checksum verification is enabled, then each time Foresight Analytics Platform starts, the integrity check is executed: the existence of all executable files, and their checksums are verified. Checksums are also verified on dynamic loading of libraries. If integrity violation is detected, the user receives the corresponding message with description of corrupted files. The further work with Foresight Analytics Platform is locked.

To restore program integrity, the administrator’s involvement is required.

Executed files or their contents can be corrupted due to:

Malicious acts.
User errors.
Viruses.
Other reasons.

Checksums are verified both at desktop application start and when BI server is enabled (for Windows and Linux OS).

NOTE. If on installing Foresight Analytics Platform, checksums verifications was not enabled, to enable it, restart the installer and select the Check Control Sums Every Time Foresight Analytics Platform Starts checkbox.

Checking Repository Metadata Integrity

To check up repository metadata integrity, the checksums are performed using a specific method by object contents. A checksum changes after any object modification. To verify checksum, it has to be initially performed. After checking the object for the second time, the previous checksum is compared to the current one. If the checksum has been changed, this means that the object was changed.

NOTE. Repository metadata integrity check is available only in the desktop application.

Checking User Audit Correctness

To check the p4audit service user that is required to perform a correct user audit, user locking mechanism check is used. The p4audit service user is created in security manager or in repository manager. In case of incorrect creation of the p4audit user, schema reinstallation or malicious actions, the security system might function with errors.

To check user locking mechanism, use the Tools section.

NOTE. User locking mechanism check is available only in the desktop application.

Backup and Restore Security Policy

To save security policy, audit settings, group and user information, object access permissions, backup and restore security policy is used. Operations on copying and restoring security policy are saved to the log.

To save backup and restore security policy, use the Tools section.