Subscribe to events from Lacework

Lacework supports sending events to Eventarc for delivery to interested subscribers.

The Lacework Polygraph® Data Platform delivers end-to-end visibility and automated insight on risks across multicloud environments, collecting, analyzing, and correlating data. Customers depend on Lacework to drive revenue, bring products to market faster and safer, and consolidate security solutions into a single platform. Learn more about using Lacework.
Lacework logo

To subscribe to events from Lacework, complete the following steps:

Before you begin

  1. Ensure that you have enabled the Eventarc and Eventarc Publishing APIs:


    Enable the APIs


    gcloud services enable \ \
  2. If you are enabling a customer-managed encryption key (CMEK) for a channel, enable the Cloud Key Management Service API.


    Enable the API


    gcloud services enable

Retrieve the provider name used by Lacework

The provider name is required when creating and using a channel. You can list all Eventarc providers and retrieve their details, including supported event types, by running gcloud commands.

For example, you can list all third-party providers in any location:

gcloud eventarc providers list --filter='eventTypes.type!~^google*' --location=-

The output should include something similar to the following:

NAME: lacework
LOCATION: us-central1

For details, see List event providers.

Retrieve the events supported by Lacework

An event type is needed when creating an Eventarc trigger. You can list Lacework's supported event types, by running a gcloud command:

gcloud eventarc providers describe lacework \

Replace LOCATION with a supported Eventarc region.

For example:

gcloud eventarc providers describe lacework --location=us-central1

The output should resemble the following:

displayName: Lacework
- type: lacework.v1.alert
name: projects/project-id/locations/us-central1/providers/lacework

Make note of the event type to use when creating an Eventarc trigger.

Create a channel for Lacework events

To subscribe to events from Lacework, you must create a channel:


  1. In the console, go to the Eventarc > Channels page.

    Go to Eventarc

  2. Click Create channel.

  3. In the Provider list, select a provider.

  4. In the Channel name field, enter a name for the channel.

  5. In the Region list, select a supported Eventarc region.

  6. Optionally, select the Use a customer-managed encryption key (CMEK) checkbox and, in the CMEK encryption key list, select a key ring that you have created for the region.

    For more information, see Use customer-managed encryption keys.

  7. Click Create.


gcloud eventarc channels create CHANNEL_ID \
  --provider lacework \
  --project PROJECT_ID \
  --location LOCATION

Replace the following:

  • CHANNEL_ID: a name for the channel
  • PROJECT_ID: your Google Cloud project ID

    You can find your project ID on the Dashboard page of the Google Cloud console.

  • LOCATION: a supported Eventarc region

You can optionally use a --crypto-key flag to specify a fully qualified Cloud KMS key name in the format projects/PROJECT_NAME/locations/LOCATION/keyRings/RING_NAME/cryptoKeys/KEY_NAME.

For more information, see Use customer-managed encryption keys.

For details, see Create a channel.

Retrieve specific details to convey to Lacework

After creating a channel, you can retrieve specific details to convey to Lacework:


  1. In the console, go to the Eventarc > Channels page.

    Go to Eventarc

  2. From the list of channels, click a channel to view its details.

    The channel status should be Pending.

  3. Copy the Channel full name and Activation token value to convey to Lacework.


gcloud eventarc channels describe CHANNEL_ID \
  --project PROJECT_ID \
  --location LOCATION

The output is similar to the following:

activationToken: aS7dXs1b79AcXsf
createTime: '2021-11-15T15:20:31.582356065Z'
name: projects/project-id/locations/us-central1/channels/lacework-channel
provider: projects/project-id/locations/us-central1/providers/lacework
pubsubTopic: projects/project-id/topics/eventarc-channel-us-central1-lacework-channel-077
state: PENDING
uid: c6703a91-ccd3-4c32-a729-967393f23a29
updateTime: '2021-11-15T15:21:03.689597653Z'

Note the activationToken value and the channel name.

Learn more about the channel state.

Send the channel details to Lacework

Use the form available at to convey to Lacework the following channel details.

  • Lacework instance: a name for the instance. This is used to name the Pub/Sub topic and is required when configuring the alert channel. We suggest using the Eventarc channel short name.

    For example: lacework-alerts

  • Channel: the full channel name, including the Google Cloud project ID and location of the resource. For example:

  • Activation token: the token is valid for 24 hours after the channel's creation. After 24 hours, the channel becomes INACTIVE.

    For example: aS7dXs1b79AcXsf

After completing the form, submit it.

Configure the Lacework alert channel

After you have submitted the channel details, follow the Lacework instructions to configure the alert channel.

Once Lacework receives the required information, and has initialized the connection between their ecosystem and the channel, the state of the channel changes from PENDING to ACTIVE.

Lacework can now send events to your project and you can start consuming the events.

Deploy an event receiver

To test the configuration, deploy an event receiver—in this case, a Workflows workflow that logs received events—and create an Eventarc trigger that routes events from Lacework to the event receiver. You must use a service account that has been granted the appropriate roles to access your Google Cloud project resources.

  1. Enable the Workflows and Workflow Executions APIs:


    Enable the APIs


    gcloud services enable \ \
  2. Create a service account and grant it the roles/logging.logWriter and roles/workflows.invoker roles:


    1. In the console, go to the Create service account page.

      Go to Create service account

    2. Select your project.

    3. In the Service account name field, enter a name. The console fills in the Service account ID field based on this name. Optionally, add a description.

    4. Click Create and continue.

    5. In the Select a role list, select Logging > Logs Writer.

    6. Click Add another role and select Workflows > Workflows Invoker.

    7. Click Continue.

    8. To finish creating the service account, click Done.


    gcloud iam service-accounts create MY_SERVICE_ACCOUNT
    gcloud projects add-iam-policy-binding PROJECT_ID \
      --role="roles/workflows.invoker" \
    gcloud projects add-iam-policy-binding PROJECT_ID \
      --role="roles/logging.logWriter" \

    Replace MY_SERVICE_ACCOUNT with a name for your service account.

    For more information about how to control access to Workflows resources, see Use IAM to control access.

  3. Create and deploy a workflow that logs a received event:


    1. In the console, go to the Workflows page.

      Go to Workflows

    2. Click Create.

    3. Name your workflow logEventsWorkflow.

    4. Choose a supported Workflows region; for example, us-central1.

    5. Select the service account you previously created.

    6. Click Next.

    7. In the workflow editor, enter the following definition for your workflow:

        params: [event]
        - logStep:
            call: sys.log
              data: ${event}
    8. Click Deploy.


    1. Open a terminal or Cloud Shell.
    2. In your home directory, create a new file called logEventsWorkflow.yaml.
    3. Copy and paste the following into the new file and save it:

        params: [event]
        - logStep:
            call: sys.log
              data: ${event}
    4. Deploy the workflow:

      gcloud workflows deploy logEventsWorkflow \
        --source=logEventsWorkflow.yaml \
        --location LOCATION

      Replace LOCATION with a supported Workflows region; for example, us-central1.

  4. Create an Eventarc trigger to route events from Lacework to the target workflow:


    1. In the console, go to the Eventarc page.

      Go to Eventarc

    2. Click Create trigger.

    3. Type a Trigger name.

      This is the ID of the trigger and it must start with a letter. For example, my-event-channel-trigger.

    4. Select an Event provider.

      This is the partner service that is the source of events. For example, select Partner sources > Lacework.

    5. Select the appropriate Channel.

    6. Select an Event.

      For example: lacework.polygraph.v1.application

    7. Optionally, in the Filters section, specify an appropriate attribute and value.

    8. Select the Service account you previously created to invoke your workflow.

    9. For the Event destination, select Workflows, and then select the workflow you previously created.

    10. Click Create.


    gcloud eventarc triggers create TRIGGER \
      --location=LOCATION \
      --destination-workflow=logEventsWorkflow  \
      --event-filters=type=lacework.polygraph.v1.application \
      --channel=CHANNEL_NAME \
      --project=PROJECT_ID \

    Replace TRIGGER with the ID of the trigger or a fully qualified identifier. For example, my-event-channel-trigger.

    For more information, see Create a trigger for a third-party provider.

Test the routing of events

You can now test the entire configuration and ensure that an event from Lacework is routed to the workflow event receiver which logs the received event.

  1. From the Lacework Console, in the list of alert channels, find your channel and, under Integration, click Test.

    This triggers an execution of the workflow and you should see an Integration test was successful message.

  2. To verify that a workflow execution was triggered, list the last five executions:

    gcloud workflows executions list ${MY_WORKFLOW} --limit=5

    The output should be similar to the following, listing a NAME and STATE equal to SUCCEEDED for each workflow execution.

    NAME: projects/606789101455/locations/us-central1/workflows/logEventsWorkflow/executions/8c02b8f1-8836-4a6d-99d9-fc321eb9668f
    START_TIME: 2021-09-13T19:15:10.275677049Z
    END_TIME: 2021-09-13T19:15:10.963136883Z
    NAME: projects/606789101455/locations/us-central1/workflows/logEventsWorkflow/executions/a6319d9d-36a6-4117-904e-3d1118bdc90a
    START_TIME: 2021-09-13T17:28:51.492864252Z
    END_TIME: 2021-09-13T17:28:52.227212414Z
  3. Every time a workflow executes a single run of the logic contained in a workflow's definition, it automatically triggers at least two execution logs: one at the start of an execution and one at the end. To view the logs do the following:

    1. In the console, go to the Workflows page:
      Go to Workflows

    2. To access a workflow's Details page, click the workflow's name.

    3. To view the logs, click Logs. The output should be similar to the following:

    2022-06-10 13:49:50.019 BST {data: {…}, datacontenttype: application/json,[...]
      "eventCategory": "TestEvent",
      "id": "a91ca1a5-85e7-4dad-a329-cf7deba8e14d",
      "severity": "0",
      "source": "//lacework/alertChannel/test",
      "type": "lacework.polygraph.v1.application",
      "link": "",
      "eventName": "Test Event",
      "datacontenttype": "application/json",
      "resource": "TestEvent",
      "specversion": "1.0",
      "data": {
        "EVENT_ID": "0",
        "EVENT_TYPE": "TestEvent",
        "START_TIME": "10 Jun 2022 12:49 GMT",
        "LINK": "",
        "EVENT_DETAILS": {
          "data": null
        "SEVERITY": 0,
        "SUMMARY": "This is a test Message.",
        "EVENT_CATEGORY": "TestEvent",
        "EVENT_NAME": "Test Event"

What's next