March 4th 2021, San Diego, CA – Prancer Enterprise is announcing that its entire cloud compliance policies repository is now open source. The repository is available on GitHub at
This move reflects Prancer’s commitment to open source technology and harness the power of community collaboration to move great ideas through the pipeline faster.
These compliance policies that focused on IaC Security and live cloud resources are based on CIS, NIST 800, PCI, HIPPA, HITRUST, CSA CCM and ISO 27001 compliance standards. These policies are all in REGO Open Policy Agent (OPA) language.
Prancer Enterprise platform helps companies achieve end-to-end security in the cloud by shifting security to the left and apply it early in the development process. Cloud DevOps engineers could have an early feedback on the security of the Infrastructure as Code (IaC) templates with every commit they are making to the code.
Prancer Enterprise Cloud Compliance repository has more than 1000 policies both on the Infrastructure as Code (IaC) Security and post-deployment resources. This unique Cloud compliance policy repository is the most significant contribution to the open-source community based on the de facto Rego policy language.
IaC Security policies cover Azure, AWS and Google Clouds. Kubernetes Objects are also supported in the IaC Security. Post-deployment security scans based on these cloud providers help businesses to increase cloud security posture and maintaining security in the cloud.
As more companies begin to rely on cloud technologies, they are also looking for ways to apply compliance to their cloud environment easily and make it a secure place for their workloads. Prancer Platform helps companies to leverage security throughout the lifecycle of their cloud deployment. Prancer Platform integrates into DevOps pipelines and provides IaC Security scan.
Prancer Enterprise (https://www.prancer.io) provides a pre-deployment and post-deployment multi-cloud security platform for Infrastructure as Code (IaC) and live cloud environments. It shifts the security to the left and provides end-to-end security scanning based on the Policy as Code concept. DevOps engineers can use it for static code analysis on IaC to find security drifts and maintain their cloud security posture with continuous compliance features.