Contributor: Anthony Dezonno, Chief Engineer, Open Source Program Office, Boeing
In an era where agility and speed define success in software development, security must evolve alongside innovation. The Scaled Agile Framework (SAFe) enables organizations to deliver complex systems quickly and collaboratively. Without embedded cybersecurity practices, however, that speed can introduce vulnerabilities. This is where principles aligned with the Systems Software Integrator (SSI) certification become critical not just for compliance, but for delivering resilient, secure systems.
One of the key competencies emphasized in the SSI content outline is "Secure System Integration," a capability that translates directly into the SAFe domain, particularly within Agile Release Trains (ARTs) and Continuous Delivery Pipelines. In SAFe, development happens across interconnected teams that frequently integrate and release software. Each integration point presents a potential security challenge, such as misconfigured APIs or insecure data handling across components.
By applying SSI-aligned practices, system integrators working within SAFe environments can proactively address these risks. For instance, automated security checks during Continuous Integration (CI) pipelines, secure dependency management, and validation of system-to-system interfaces all help ensure that what gets deployed is not just functional but hardened against attack.
Moreover, SSI's emphasis on lifecycle security encourages teams to treat security as an enabler, not an afterthought. This mindset aligns closely with SAFe’s Lean-Agile principles, particularly the focus on built-in quality and relentless improvement. As cross-functional Agile teams embrace security integration as part of their definition of done, they foster collaboration between developers, testers, and security professionals, bridging the very gaps that create vulnerabilities in traditional models.
Ultimately, the intersection of SSI competencies and SAFe principles empowers organizations to move fast and stay secure. It's not about layering security on top; it's about building it in from the first story point.
Learn More and Take the Next Step
Anthony Dezonno serves as Chief Engineer for Boeing’s Open Source Program Office. He specializes in intellectual property concerns surrounding engineering. He is listed as inventor in over 100 patents worldwide, and referenced in more than 2,000 patents. He has a broad skillset that includes innovation & intellectual property management, program management, project management, open source licensing, hardware engineering, systems development, engineering & supplier management, software export & import requirements.