> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/google-security-command-center.md).
# Google Security Command Center
Send Google Security Command Center alerts to ilert for real‑time technical alerting, rapid on‑call notification, and centralized threat tracking.
Connect [Google Security Command Center](/integrations/inbound-integrations/google-security-command-center.md) to ilert to transport security findings, like misconfigurations or suspicious activity, as technical alerts to on-call personnel. This ensures immediate awareness, structured escalation, and a centralized view of security-related events for responders.
## In ilert: Create a Google Security Command Center alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Google Security Command Center**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In Google Security Command Center: Sending notifications via Google Cloud Functions
1. Enable finding notifications for Pub/Sub with the following guide:
2. Create following function example in Google Cloud Functions. Make sure to replace `[WEBHOOK_URL]`with the Url generated in [this step](#in-ilert-create-a-google-security-command-center-alert-source).
{% tabs %}
{% tab title="Go" %}
```go
import (
"context"
"log"
"net/http"
"github.com/go-resty/resty/v2"
)
type PubSubMessage struct {
Data []byte `json:"data"`
}
func WebhookPubSub(ctx context.Context, m PubSubMessage) {
// Send the webhook request with the Pub/Sub message as the content
webhookURL := "[WEBHOOK_URL]"
client := resty.New()
resp, err := client.R().
SetHeader("Content-Type", "application/json").
SetBody(m.Data).
Post(webhookURL)
if err != nil {
log.Printf("Error creating webhook request: %v", err)
return
}
// Check the webhook response
if resp.StatusCode() != http.StatusAccepted {
log.Printf("Webhook request failed with status code: %d", resp.StatusCode())
return
}
}
```
{% endtab %}
{% endtabs %}
3. Deploy the Google Cloud Function by running the following command in the terminal:\
\
`gcloud functions deploy WebhookPubSub --runtime go116 --trigger-topic YOUR_PUBSUB_TOPIC`\
\
Replace `YOUR_PUBSUB_TOPIC` with the actual Pub/Sub topic name that you want the Cloud Function to be triggered by.
## FAQ
**Will alerts in ilert be resolved automatically?**
Yes, as soon as the state of an alert in Google Security Command Center is `RESOLVED`, the associated alert in ilert is resolved.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/integrations/inbound-integrations/google-security-command-center.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
