awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-09 21:28:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Confused Deputy Attacks docs improvement

Browse Source
This commit is contained in:
carlosmonastyrski
2025-04-15 16:55:05 -03:00
parent d33b06dd8a
commit 27198869d8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/app-connections/aws.mdx
+2 -2
View File
@@ -61,9 +61,9 @@ Infisical supports two methods for connecting to AWS.
<Warning type="warning" title="Security Best Practice: Use External ID to Prevent Confused Deputy Attacks"> <Warning type="warning" title="Security Best Practice: Use External ID to Prevent Confused Deputy Attacks">
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**. 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.
<strong>Always enable "Require external ID" and use a unique value such as your Organization ID when setting up the IAM Role.</strong> <strong>Always enable "Require external ID" and use your Organization ID when setting up the IAM Role.</strong>
</Warning> </Warning>
</Step> </Step>