From 27198869d8abe9ae7c8136ab88f6f4b51f1d5098 Mon Sep 17 00:00:00 2001 From: carlosmonastyrski Date: Tue, 15 Apr 2025 16:55:05 -0300 Subject: [PATCH] Confused Deputy Attacks docs improvement --- docs/integrations/app-connections/aws.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/integrations/app-connections/aws.mdx b/docs/integrations/app-connections/aws.mdx index 41b6ade4f..ab2f4638f 100644 --- a/docs/integrations/app-connections/aws.mdx +++ b/docs/integrations/app-connections/aws.mdx @@ -61,9 +61,9 @@ Infisical supports two methods for connecting to AWS. When configuring an IAM Role that Infisical will assume, it’s highly recommended to enable the **"Require external ID"** option and specify your **Organization ID**. - This precaution helps protect your AWS account against the [confused deputy problem](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html), a potential security vulnerability where a third party could be tricked into performing actions on your behalf by an unauthorized actor. + This precaution helps protect your AWS account against the [confused deputy problem](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html), a potential security vulnerability where Infisical could be tricked into performing actions on your behalf by an unauthorized actor. - Always enable "Require external ID" and use a unique value such as your Organization ID when setting up the IAM Role. + Always enable "Require external ID" and use your Organization ID when setting up the IAM Role.