This article details a practical implementation of DevSecOps for a Node.js and Express API, emphasizing early security integration. It showcases how a GitHub Actions pipeline was configured to automatically analyze code security using Bearer CLI. The goal was to demonstrate that intentionally introduced vulnerabilities could be automatically detected before deployment. A simulated vulnerability involving sensitive information in authentication logs was used for the demonstration. Bearer successfully identified the high-severity issue, causing the pipeline to fail. After code correction, the pipeline succeeded, allowing deployment to Render. The solution integrates development, version control, SAST, automation, and cloud deployment. The security pipeline workflow is triggered by code pushes or pull requests, with Bearer CLI scanning for high and critical severity issues. Bearer's ability to analyze code for sensitive data, credentials, and potential security flaws makes it valuable for DevSecOps. The intentional vulnerability involved logging passwords, which Bearer detected as a high-severity finding (CWE-134). This failure acted as a quality gate, preventing insecure code from progressing. The remediation involved removing sensitive data from logs, ensuring only necessary information for traceability remained. Verifying the fix, a new push triggered the pipeline again, which now completed successfully. This process illustrates how SAST tools can detect, block, and verify vulnerability remediation within the development workflow. The complete flow from development to cloud deployment, incorporating security checks, was successfully demonstrated. Key lessons learned include the importance of early security integration, automation, protecting sensitive data, using security gates, and embedding security into the development process.