Skip to content

Add support for scoped GitHub audits #8111

@FallenAtticus

Description

@FallenAtticus

New feature motivation

I should be possible to narrow down the scope of an GitHub audit, to not entirely scan all repositories within the scope of the used PAT (or GitHub app) but only one or multiple repositories, depending on the used parameter.

Currently if an org owner PAT is used for an audit, all repositories within the scope of the PAT are scanned, which can be a lot in bigger companies, and the result is, that the audit will take multiple hours to complete, due to rate limit backoffs.

Solution Proposed

I can imagine to have parameters like

  • "--repository [REPOSITORY_NAME]"
  • "--repositories-file [REPOSITORIES_FILE]"

for which the audit and the report is done.

Describe alternatives you've considered

I thought about temporary PATs, generated on the fly for a repository that needs to be audited to ensure that only this repository is in the scope of the PAT, but this requires further development outside of prowler.

Additional context

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions