→ Back to Home
CI/CD

InvisiRisk Bolsters TeamCity CI/CD Security with Build Application Firewall Integration

InvisiRisk has announced the general availability of its JetBrains TeamCity integration for the Build Application Firewall (BAF). This integration provides a tested and supported setup path for TeamCity, enabling inline policy enforcement and the generation of a TruSBOM™ for self-hosted agents and on-premises servers. The BAF aims to protect CI/CD pipelines by controlling what builds are allowed to access and transmit during execution, directly within the build process. This development is significant for any organization utilizing TeamCity, particularly given the recent surge in software supply chain attacks. By integrating directly into the CI/CD workflow, InvisiRisk's BAF allows for the enforcement of security policies at build-time, a crucial shift-left strategy. This means that potentially malicious or vulnerable packages can be blocked before they are ever incorporated into an application, drastically reducing the risk of a compromised build reaching production. For practitioners, this translates to a more secure pipeline, fewer post-deployment fire drills, and a stronger posture against evolving threats. The move aligns with a broader, well-established trend in DevOps and cloud-native security: the increasing focus on securing the software supply chain. As highlighted by recent incidents involving critical vulnerabilities in CI/CD systems and compromised open-source packages, traditional perimeter security is insufficient. The industry is moving towards a zero-trust model for dependencies and build processes, where every component and action is verified. Solutions like InvisiRisk's BAF, which provide granular control and visibility into runtime behavior, are becoming indispensable for maintaining integrity from code commit to deployment. In practice, this integration means TeamCity users can now implement egress and dependency policies using Open Policy Agent (OPA) and Rego, with decisions made in real-time as the build runs. Furthermore, the TruSBOM™ generated from observed build activity offers a more accurate representation of what was actually included in the artifact, as opposed to static SBOMs that list everything declared. Practitioners should evaluate this integration to enhance their build-time security, focusing on defining strict policies for dependency access and network egress. This proactive approach can significantly mitigate the impact of supply chain attacks and improve overall software integrity, moving beyond mere vulnerability patching to a more robust, preventative security stance.
#ci/cd security#supply chain security#teamcity#build application firewall#sbom#devsecops
Read original source