How chanduusc/prismacloud-demo works
Main Components
• CI/CD Pipeline:
• Github repository hosting the code.
• .github folder containing GitHub Actions workflows (aks.yml, eks.yml, gke.yml, lambda.yml, gcp-cloudrun.yml, etc.) that trigger build, deploy, and scan jobs.
• Integration with Prisma Cloud for security scanning (image scans, vulnerability detection during build and PR processes).
• Infrastructure-as-Code (IaC):
• Separate directories under IaC for AKS, EKS, and GKE show how Terraform templates are used to deploy infrastructure. Each folder (IaC/AKS, IaC/EKS, IaC/GKE) contains configuration files like main.tf, variables.tf, and specific resources (ACR, ECR, S3, etc.).
• Application Deployment Components:
• Container Orchestrators:
• Kubernetes configurations (YAML files for deployment, service accounts, ingress, load balancing) placed in the project root (aks-deployment.yml, eks-deployment.yml, gke-deployment.yml, etc.)
• “host” folder: Contains the Python application (app.py, run.py) supporting a host-based deployment.
• Serverless and other form factors:
• “lambda” folder for AWS Lambda based deployments (AWS-Vulnerable-Lambda), integrating with serverless security scanning.
• “gcp-cloudrun” folder with its own Dockerfile and README indicating a Cloud Run deployment.
• Security Stages and Processes:
• Code Security in the IDE: Developers use tools like Checkov (and see copy_to_req file guidance) for early misconfiguration alerts.
• Review/CI Phase: Integration of security tooling that comments on GitHub PRs and blocks code-checkins based on vulnerability scanning.
• Post-build/CD and Deployment:
• Prisma Cloud’s scan of container images (positions in the pipeline where vulnerabilities cause build/deploy failures).
• Dedicated scripts like wild.py in both the project root and within the lambda module hint at deliberate insecure practices to test alerts.
• Runtime Monitoring:
• Several images in the README show monitoring views (k8s audit logs, runtime alerts, and data security alerts).
Relationships and Data Flow
• “CI/CD Pipeline” block:
• Branch out to show various GitHub Actions workflows that trigger different jobs (build, deploy, vulnerability scan).
• Jobs to the “Prisma Cloud” security modules (e.g., code security, image scan on container registry).
• IaC deployment side:
• Use separate blocks for AKS, EKS, and GKE clusters (each coming from their respective Terraform modules).
• “Host” containerized application, “Lambda” serverless module, and “Cloud Run” service.
• Finally, illustrate the monitoring and feedback loop:
• Blocks for “Runtime Monitoring” (displaying audit logs, event alerts, compliance dashboards).
• Flow from deployed environments (K8s clusters, Serverless endpoints) feeding data back into Prisma Cloud and then to the SecOps/Production Engineering teams.
Architectural Patterns & Design Principles
• Separation of Concerns: Clearly separate source code (host, lambda), infrastructure code (IaC directories), and deployment (YAML files, GitHub workflows).
• Multi-cloud/Multi-form Factor Architecture: Emphasize that the system deploys on multiple clouds and supports varied application paradigms (container-based, host, serverless).
• Secure CI/CD Pipeline: Note the integration of security scanning at every phase from code commit to deployment and runtime monitoring.
• Feedback Loop: Stress how vulnerability detection and audit logs provide continuous feedback for developers, security teams, and production engineers.