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

Foresight Analytics Platform integrity is checked, is the Verify Checksums On Each Platform Start checkbox was selected:

NOTE. If on installing desktop and web application, checksum verification was not activated, then to activate it, start installer and select the Verify Checksums on Each Platform Start checkbox.

Checksums for executable files is verified during loading. On each Foresight Analytics Platform start, the minimum set of executable files is loaded and while calling any functionality, additional libraries required for work are loaded. 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.

NOTE. Checksums are verified only on starting desktop application or on when BI server installed on Windows OS is working. In Linux OS checksums are verified by operating system means.

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.

Checking User Audit Correctness

To check the p4audit service user that is required to perform a correct user audit, locking mechanism of the users. 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.