Verify whether your PEG configuration is operating correctly in review mode.

Prerequisites

Review the following table for the format and purpose of various URLs in PEG:

URL formatPurpose
analytics-fiq-<UID>.<apex domain> Provides access to Kibana dashboards where we can monitor the number of logs, number of users, what is being forwarded, and so on.
dlp-fiq-<UID>.<apex domain> Is a critical URL as this is where the sensor sends all its logs to. This URL must be used as an input while setting up the sensor.
es-fiq-<UID>.<apex domain> Used for accessing database directly.

This is very important as the key light application accesses database to align meta data with the images.
klite-fiq-<UID>.<apex domain> Provides access to the Klite application where the raw data and the corresponding screen shots can be visualized.
proxy-fiq-<UID>.<apex domain> Monitors the health of Kubernetes services.
Note: This is only required for debugging.
st-fiq-<UID>.<apex domain> Provides a direct link to the OCR service.
Note: This is only required for debugging.
storage-fiq-<UID>.<apex domain> Provides Direct Access to the image storing application.
Note: Images are in raw S3 bucket format that can be accessed through Klite.
To confirm that PEG is running as expected, perform the following steps:

Procedure

  1. In a browser, go to https://storage-fiq-<UID>.<apex domain>.
    You will see a screen like this: ("Access Key" = "your username" and secret key = "your password")

    screen with access key displayed

  2. Log in to https://storage-fiq-<UID>.<apex domain> using a user you created in the configuration steps previously (by running ~/peg/scripts/add-storage-user.rb on the VM).
  3. After you log in, you will see these folders on the left. If you do not, run the "Storage Management" "initialize storage" steps in the configuration steps. If you still do not see them after that, contact Process Discovery.
    The following folders are displayed on the left.
  4. In a browser, go to the analytics URL: https://analytics-fiq-<UID>.<apex domain>
    You will see a screen similar to the following:
    Go to analytics URL and you will see the login screen

    If you do, go to the next step.

  5. In a browser, go to https://dlp-fiq-<UID>.<apex domain>.
    You will just see a blank page. If you encounter an error or it times out, then there is something wrong.
  6. Install the Process Discovery Sensor on a Windows machine. Open a web page, such as https://www.fortressiq.com and then click the page several times.
  7. After 10 minutes (which is the approximate duration for review images to be generated), log in to https://storage-fiq-<UID>.<apex domain>. Log in with one of the storage users that you created previously in the configuration steps.
    Note on the folders on the left side:
    • fiq-screenshots: Shows the screenshot that PEG received
    • forwarded: Shows what the screenshot looks like if it is forwarded. This is populated regardless of whether it was actually forwarded or not.
    • review: PEG adds annotation to the images here to show more clearly what will be redacted. PEG includes a blue rectangle around where the redacted word previously existed and includes the text it found above the rectangle.
  8. Click the fiq-screenshots folder on the left.
  9. Download some of the images from this folder and confirm that they look like the results of your test.
  10. Click on the review folder.
  11. Download some of the images from this folder and confirm that they appear to be from your test. If PEG finds words that must be redacted, PEG includes a blue rectangle around where the redacted word existed and it includes the text it found above the rectangle, as follows.
    An example: PEG finds words that must be redacted, PEG includes a blue rectangle around where the redacted word existed and it includes the text it found above the rectangle
    If this looks as expected, you have validated that PEG is working in review mode.