Purpose
This site accompanies a technical demonstration prepared for the GitLab Solutions Architect panel interview. The scenario is a fictional Cabinet-level agency, the Department of Citizen Services (DCS), that needs secure, standardized software delivery after a security incident. The demonstration shows how GitLab can support secure delivery, security scanning, governance and AI-assisted development across two separated environments.
What is demonstrated
- A personnel directory application deployed to Kubernetes through GitLab CI/CD.
- GitLab-native security scanning and approval controls.
- Integration with existing security tools alongside GitLab-native scanners.
- GitLab Duo and the Duo Agent Platform for development and vulnerability remediation.
- Delivery of approved source code from an unclassified environment to a simulated restricted environment.
Some of these capabilities are still being built. This page does not report which ones are finished.
Limits of the simulation
- Every employee record in both applications is fictional.
- Both environments run on the same GitLab-managed Kubernetes cluster, separated only by namespaces and separate databases. This is not a real classified boundary.
- Cross-domain transfer is simulated with GitLab CI/CD. It is not a data diode, a sneakernet process or an approved cross-domain solution.
- Nothing here claims FedRAMP, FISMA, ATO or SLSA compliance.