Breadcrumbs

Initialize the Prisma Cloud Beat

Prerequisites

  • Open Collector is installed. If you have not already installed it, follow the instructions in the Open Collector Installation and User Guide, and then return to this topic.

  • API URL (These are specific to audit and alert logs, and the version of these APIs depends on the users. For example, https://api.prismacloud.io/alert).

  • Prisma Cloud Access Key ID (User-provided).

  • Prisma Cloud Secret Key (User-provided).

  • The following port is open:

    Direction

    Port

    Protocol

    Source

    Outbound

    443

    HTTPS

    prismacloudbeat

Initialize the Beat via the Web Console (Recommended)

  1. Ensure that the Open Collector Connection to the SIEM (WebUI) setup has been completed.

  2. Ensure that the System Monitor Agent to which you intend to send these logs has been Configured for JSON Parsing.

Use either the Enable JSON Parsing on System Monitor Agents or the Enable JSON Parsing for an Existing System Monitor Agent sections at the above link to configure the System Monitor Agent for JSON Parsing.

  1. Follow the steps outlined in Add a Beat in the Web Console to create the Beat via the Web UI.

Initialize the Beat via Command Line (Legacy)

  1. Start the beat:

    ./lrctl prismacloudbeat start

  2. Use the Up and Down Arrow keys to select New prismacloudbeat instance from the list, and then press Enter.

  3. Enter the unique identifier for this prismacloudbeat instance, and then press Enter.

  4. Enter the Prisma Cloud API URL, and then press Enter.

    Create a new Prisma Cloud Beat instance with the Alert API URL to collect Prisma Cloud CSPM Alert logs simultaneously.

  5. Enter the Prisma Cloud Client ID (the Access Key ID obtained in the Configure Prisma Cloud topic), and then press Enter.

  6. Enter the Prisma Cloud Client Secret (the Secret Key obtained in the Configure Prisma Cloud topic), and then press Enter.

    For security purposes, the Client ID and Client Secret are stored in an encrypted format.


  7. Enter the hostname or IP address of the System Monitor Agent that has been Configured for JSON Parsing, and then press Enter.

Use either the Enable JSON Parsing on System Monitor Agents or the Enable JSON Parsing for an Existing System Monitor Agent sections at the above link to configure the System Monitor Agent for JSON Parsing.

  1. Enter the port on which the System Monitor Agent is configured to listen for JSON data (the default is 5044), and then press Enter.
    The prismacloudbeat service started message appears.

  2. Check the status of the service to confirm that it’s running:

    ./lrctl prismacloudbeat status

  3. (Optional) Edit the prismacloudbeat configuration to update the values set above if needed. Ensure that you have all the needed information for each step available as you will need to re-enter it:

    ./lrctl prismacloudbeat config edit