Make and Google Chat webhook

-

Make & Google Chat=Webhook


Make + Google Chat = easypeazywebhook

Today, we are introducing Make, 


Make's mission is to empower people to visually create, build, and automate at the speed of their ideas. Inspired by an amazing community, they've realized their platform is more than just integration and automation. 

Put simply, they realized their users are not users: they’re Makers. No-code tools are just that; they enable users to build and automate, without writing any code. They offer something more: a visual language that democratizes development makes processes tangible, and fosters team collaboration, regardless of technical skills.

“Make” is short, modern, and easy to spell and pronounce. It’s a verb that captures what users do on our platform. Most importantly—it represents the evolution of our product, and the spirit of our customers, and reflects one of the most transformational trends of our era: from rigid, top-down, repetitive jobs to flexible, empowering, and meaningful work. 

What are webhooks?

Incoming webhooks let you send asynchronous messages into Google Chat from applications that aren't Chat apps. For example, you can configure a monitoring application to notify on-call personnel on Google Chat when a server goes down.

To asynchronously send, update, or delete a message in a Chat space with a Chat app, see Create, read, update, and delete messages.




Summary

Well, I needed a quick way to create a webhook for Google Chat. There are many, many ways to do this. I already had a python version working, but wanted to try something new I came across. Which was "Make". So this way is not the only way, but is just a quick blurb on my experience and steps to integrate google chat with a CSPM solution, CloudGuard. You can read more about CloudGuard here.


Quick steps :


1. Grab a token from CloudGuard Portal



2. Configure the Google Chat Webhook details here.



3. Log in to Make and click on Scenarios, Create a new Scenario



4. Click the big "plus" sign and search for webhook add, search for google chat and add.  It should look like something similar.  As you add each object, you will need to provide relevant info, such as the URL from step #2 and any associated tokens/keys.  



5. As added security lockdown, those source IPs can send to the Make API. 



6. Log into CloudGuard and Test and create the Google Chat Notification so:


Summary #2 

This is a quick down and dirty for me to go back and familiarize myself as I plan to do another scenario based on the routing object, combining agnostic logistics such as notifications, automation, etc., but that is for another day.
 

Another Option for Google Chat

Integrating CloudGuard CSPM with Google Chat (Proper with Python)

Requirements:

1. Lil Python, You are Good

2. Knowledge of AWS SNS / Lambda

3. Token/Key- CloudGuard CSPM Account Sign-up / Login

4. Google Chat (Hangouts) Webhook URL: Reference: click here

The next step, for now, is to follow the Google Chat ref guide, which is very good. 


Popular

Federated user activity made easy

-
Image
 Federated user activity made easy. The other day I was auditing a sandboxed account in AWS and started investigating resources connected to a federated role for a group of students that are no longer enabled on the account. I noticed a few objects that should have been elsewhere or terminated after the fact, regardless, neither here nor there. After about 30 minutes of sifting through logs, creating custom queries, and trying to put them together, I lost interest because of the time and day-to-day priorities. I felt this was a good use case for me to test out some of the functionality of CloudGuard's investigation and correlation engine within the platform and try out this voice-over platform. Enjoy - Video below: if you feel inclined to research further, visit the product page
Read more

Google Cloud: Container Registry will be replaced by Artifact Registry

-
Spoiler Alert: (you've got some time) Container Registry will be replaced by Artifact Registry. Please upgrade your projects to Artifact Registry before March 18, 2025. On March 18, 2025 , Container Registry will be replaced by Artifact Registry . We understand this change may affect your production workloads, so we've put together resources to make this transition as smooth as possible for you. What do you need to know? To retain access to your container images, please take note of these critical dates and actions you need to take related to the Container Registry shutdown: March 18, 2025: You will no longer be able to push new images to Container Registry. April 22, 2025: You will lose access to existing images in Container Registry. To maintain access, you must copy them to the Artifact Registry before this date. May 22, 2025: All requests to the gcr.io domain will be handled exclusively by Artifact Registry. Ensure the Artifact Registry...
Read more

Meet Kaniko

-
Image
So, what is kaniko? Kaniko is a tool to build container images from a Dockerfile inside a container or Kubernetes cluster. Another great callout for me is that my CI provider, GitLab makes it super easy to implement in my pipelines. Kaniko doesn't depend on a Docker daemon and executes each command within a Dockerfile entirely in userspace. This enables building container images in environments that can't easily or securely run a Docker daemon, such as a standard Kubernetes cluster. How does Kaniko work? The kaniko executor image is responsible for building an image from a Dockerfile and pushing it to a registry. Within the executor image, we extract the filesystem of the base image (the FROM image in the Dockerfile). We then execute the commands in the Dockerfile, snapshotting the filesystem in userspace after each one. After each command, we append a layer of changed files to the base image (if there are any) and update image metadata. Highly recommend visiting their  repo  ...
Read more