Prevent Prisma Access Key Secrets from being pushed into github

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Prevent Prisma Access Key Secrets from being pushed into github

L3 Networker

So, we want to prevent developers from pushing Prisma Access Keys' secrets into source-code repository.

A push to a branch would trigger, git-secrets to evaluate a list of regex that detect known secrets.

So, how to identify a Prisma Access Key Secret?

This what I've observed thus far.

  • 28 characters in length
  • always ends with =
  • the 1st 27 characters can be? [0-9|a-z|A-Z|+/]
  • anything else? am i missing some non-alphanum characters?

Can someone confirm and improve on these characteristics?

Tommy Hunt AWS-CSA, Java-CEA, PMP, SAFe Program Consultant

That appears to be correct. Uppercase, lowercase, numbers, and sometimes a forward slash.

Customer Success Engineer | Prisma Cloud Compute | Moderator
  • 1 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!