How to onboard a GCP account to Kloudle
This document details the steps that are required to create a Google Cloud service account token to be onboarded to Kloudle so that Kloudle can make API requests to Google Cloud.
Category: blog
-
![This document details the steps that are required to create a Google Cloud service account token to be onboarded to Kloudle so that Kloudle can make API requests to Google Cloud.]()
-
![This document details the steps that are required to create an AWS user that will be onboarded to Kloudle so that Kloudle can make API requests to AWS.]()
How to onboard an AWS account to Kloudle
This document details the steps that are required to create an AWS user that will be onboarded to Kloudle so that Kloudle can make API requests to AWS.
-
![The AWS RDS service, by default, does not enable secure transport layer security, allowing clients to connect insecurely if they want to. This is a blogpost to look at its discovery, why this is a problem and what you can possibly do to mitigate it.]()
AWS RDS does not force clients to connect using a secure transport layer
The AWS RDS service, by default, does not enable secure transport layer security, allowing clients to connect insecurely if they want to. This is a blogpost to look at its discovery, why this is a problem and what you can possibly do to mitigate it.
-
![Google Cloud Armor provides a rule-based policy framework that can be used by customers of the Google Cloud Platform to mitigate various types of common web application attacks. The Cloud Armor service has a documented limitation of 8 KB as the maximum size of web request that it will inspect. The default behavior of Cloud Armor in this case can allow malicious requests to bypass Cloud Armor and directly reach an underlying application.]()
Piercing the Cloud Armor - The 8KB bypass in Google Cloud Platform WAF
Google Cloud Armor provides a rule-based policy framework that can be used by customers of the Google Cloud Platform to mitigate various types of common web application attacks. The Cloud Armor service has a documented limitation of 8 KB as the maximum size of web request that it will inspect. The default behavior of Cloud Armor in this case can allow malicious requests to bypass Cloud Armor and directly reach an underlying application.
-
![The AWS WAF and Shield service can be used to protect web applications against a lot of different types of attacks. However, it has a limitation on the size of the packet that it can inspect that could result in attackers being able to bypass its protection features.]()
Bypassing the AWS WAF protection with an 8KB bullet
The AWS WAF and Shield service can be used to protect web applications against a lot of different types of attacks. However, it has a limitation on the size of the packet that it can inspect that could result in attackers being able to bypass its protection features.
-
![AWS recently added default transparent server side encryption to every object in S3. This post shows how the APIs and SDK do not reflect the supposed reality of Server Side Encryption.]()
AWS S3 Default Server Side Encryption - Detection and Support
AWS recently added default transparent server side encryption to every object in S3. This post shows how the APIs and SDK do not reflect the supposed reality of Server Side Encryption.
