Falco has a powerful rule engine to monitor Kubernetes for suspicious activity. Unfortunally this doesn't work with Google Kubernetes Engine, because GKE is currently not supporting Dynamic Audit Webhook Backends. GKE sends its audit logs by default to Stackdriver.
This tool will act as a bridge between the GKE Audit logs and Falco. It uses Pub/Sub to receive the Audit event from Stackdriver almost in Real-time. Then it convert the Audit Event from Stackdriver into an Kubernetes Audit Event and sends it to Falco.
falco-gke-audit-bridge has a Docker image ready to deploy in Kubernetes.
- An example of deploying it in Kubernetes can be found in deploy/kubernetes.
- To configure the export of the Audit logs from Stackdriver via Pub/Sub to falco-gke-audit-bridge, see the Terraform example in deploy/terraform.
The falco-gke-audit-bridge can be configured through the following Environment Variables:
| Variable | Description | Default |
|---|---|---|
| LOG_LEVEL | Log level, supported values are: debug,info,warn,error. | info |
| SERVER_PORT | Port for the builtin webserver to listen on. This webserver exposes a health-check and Prometheus metrics endpoint. | 8080 |
| GCP_PUBSUB_SUBSCRIPTION | PubSub Subscription name to listen on for GKE Audit Events. | falco-gke-audit-bridge |
| FALCO_URL | Falco endpoint to send to Audit Events to. | http:https://falco:8765/k8s-audit |
| RATE_LIMIT_PER_SECOND | Rate limit of events to send to falco per second | 2 |
| RATE_LIMIT_WINDOW | Time window in seconds to apply the rate limit | 1 |
This code uses Google's google-auth-library, to find application default credentials.
You may set GOOGLE_APPLICATION_CREDENTIALS environment variable
or rely or GCE's metadata server for the running service account.
Learn more at the repo's readme.
MIT