Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Checkov permissions #984

Merged
merged 2 commits into from
Nov 18, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,11 @@ See https://www.checkov.io/2.Basics/Visualizing%20Checkov%20Output.html[Visualiz
. Before you begin.
.. xref:../../../../administration/create-access-keys.adoc[Generate and copy the Prisma Cloud access key] to enable access to Prisma Cloud. The access key includes a key ID and secret.
.. Add the Prisma Cloud IP addresses and hostname for Application Security to an xref:../../../../get-started/console-prerequisites.adoc[allow list] to enable access to the Prisma Cloud Console.
.. Grant *Administrator* permissions in the relevant organization to the Prisma user installing Checkov.
.. Grant either the *Developer*, *AppSec Admin* or *System Admin* permissions in the relevant organization to the Prisma user installing Checkov. If you prefer to use a custom permission group, Checkov requires:

* Policies: Policies - 'View' permissions
* Application Security: Projects - 'View' permissions
* Settings: Providers - ('View' and 'Create') OR ('View' and 'Update') permissions
.. Best Practice (*Mandatory* for SCA vulnerability suppression):
+
* Run Checkov within your current working directory (<current_directory_path>). It is recommended to use the absolute file path for your current working directory
Expand Down
Loading