Skip to content

awslambda_function_no_secrets_in_code false positive in *.deps.json files #11148

@JaimeArcilaNRW

Description

@JaimeArcilaNRW

Feature search

  • I have searched the existing issues and this feature has not been requested yet or is already in our Public Roadmap

Which component would this feature affect?

Prowler CLI/SDK

Related to specific cloud provider?

AWS

New feature motivation

The problem: .deps.json files in .NET Lambda deployments generate false positive "Secret Keyword" findings

Solution Proposed

The request: add file-pattern exclusions to the mutelist (e.g. Files: - "*.deps.json") so users can suppress findings based on the filename inside the Lambda package rather than only at the function level. When Using AWS Secrets manager there is a reference to this service causing false positives.

Use case and benefits

C# .NET Developers which work in AWS and have many .deps.json files.

Describe alternatives you've considered

Tried to suppress all Lambda warnings but it masks real secrets risks

Additional context

No response

Metadata

Metadata

Assignees

Labels

feature-requestNew feature request for Prowler.severity/mediumResults in some unexpected or undesired behavior.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions