Prevent Prisma Access Key Secrets from being pushed into github

[TommyHunt]

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?

[AHamilton-Sutherland]

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