From f539a9e2d9a9229e17fbf8658c7ed6ff6c3ddcd9 Mon Sep 17 00:00:00 2001 From: JaimePolop Date: Mon, 29 Sep 2025 17:15:59 +0200 Subject: [PATCH] stsgetfederatedtoken --- .../aws-post-exploitation/aws-sts-post-exploitation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pentesting-cloud/aws-security/aws-post-exploitation/aws-sts-post-exploitation.md b/src/pentesting-cloud/aws-security/aws-post-exploitation/aws-sts-post-exploitation.md index e8e8b0079..1456ccb65 100644 --- a/src/pentesting-cloud/aws-security/aws-post-exploitation/aws-sts-post-exploitation.md +++ b/src/pentesting-cloud/aws-security/aws-post-exploitation/aws-sts-post-exploitation.md @@ -110,7 +110,7 @@ aws sts get-federation-token --name The token returned by sts:GetFederationToken belongs to the federated identity of the calling user, but with restricted permissions. Even if the user has administrator rights, certain actions such as listing IAM users or attaching policies cannot be performed through the federated token. -Additionally, this method is somewhat more stealthy, since the federated user does not appear in the AWS console (IAM portal), it can only be observed through CloudTrail logs or monitoring tools. +Additionally, this method is somewhat more stealthy, since the federated user does not appear in the AWS Portal, it can only be observed through CloudTrail logs or monitoring tools. {{#include ../../../banners/hacktricks-training.md}}