From 2276ffb1f6d59c5661db7b971af65ae5ee663a50 Mon Sep 17 00:00:00 2001 From: Kay Agahd Date: Fri, 7 Mar 2025 14:31:03 +0100 Subject: [PATCH] fix(aws): ecs_task_definitions_no_environment_secrets.metadata.json (#7135) --- .../ecs_task_definitions_no_environment_secrets.metadata.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/prowler/providers/aws/services/ecs/ecs_task_definitions_no_environment_secrets/ecs_task_definitions_no_environment_secrets.metadata.json b/prowler/providers/aws/services/ecs/ecs_task_definitions_no_environment_secrets/ecs_task_definitions_no_environment_secrets.metadata.json index 9c87a7c720..55c51417a9 100644 --- a/prowler/providers/aws/services/ecs/ecs_task_definitions_no_environment_secrets/ecs_task_definitions_no_environment_secrets.metadata.json +++ b/prowler/providers/aws/services/ecs/ecs_task_definitions_no_environment_secrets/ecs_task_definitions_no_environment_secrets.metadata.json @@ -12,7 +12,7 @@ "ResourceIdTemplate": "arn:partition:service:region:account-id:resource-id", "Severity": "critical", "ResourceType": "AwsEcsTaskDefinition", - "Description": "Check if secrets exists in ECS task definitions environment variables. If a secret is detected, the line number shown in the finding matches with the environment variable \"Name\" attribute starting to count at the \"environment\" key from the ECS Task Definition in JSON format.", + "Description": "Check if secrets exists in ECS task definitions environment variables.", "Risk": "The use of a hard-coded password increases the possibility of password guessing. If hard-coded passwords are used, it is possible that malicious users gain access through the account in question.", "RelatedUrl": "", "Remediation": {