In the never-ending need to keep applications and other IT resources up to date, federal agency chief information officer shops across the board are turning to the DevSecOps methodology. That is, regular, frequent deployment of new software increments vetted for security, functionality and interoperability. The vetting includes not just the technical people but also the program owners and users who will live with the software.

A wide variety of tools and technologies exist on the market to support the DevSecOps approach to modernization. But success in DevSecOps is ultimately a matter of outcomes.

In this exclusive executive briefing, the following experts examine why establishing an organizational culture around outcomes, with DevSecOps supporting them, is crucial:

• Nathan Jones, Vice President, Federal, Red Hat
• Edmond Kuqo, Lead Systems Engineer, DevSecOps, Naval Information Warfare Center (NIWC) Atlantic
• Rayvn Manuel, Senior Application Developer & Lead DevOps Engineer, National Museum of African American History and Culture, Smithsonian Institution
• Derek Masaki, Systems Development Branch Chief, U.S. Geological Survey
• Cynthia Mendoza, Acting Deputy Intelligence Community Chief Information Officer & IC Chief Architect, Office of Director of National Intelligence
• Stephan Mitchev, Director, Office of Application Engineering and Development, U.S. Patent and Trademark Office
• Eric Mosher, DevX DevOps Pipeline Lead, National Security Agency
• Chuck Svoboda, Lead Transformation Sales Specialist, North American Public Sector Transformation Office, Red Hat