Software Engineering Institute (SEI) Webcast Series

Jose Morales discusses mobile device security enhancements with defensive and offensive uses.

Greg Shannon discusses the CERT Division's current work associated with cyber community of interest (COI).

CERT researchers discuss risk management and resilience.

Rotem Guttman discusses how mission-readiness can be assessed at a DoD scale.

Will Klieber and Lori Flynn discuss undesired flows of sensitive information within and between Android apps.

The definition of DevOps is a highly contested topic. Despite what some will lead you to believe DevOps is not just a set of tools, nor is it merely a focus on achieving continuous integration, continuous delivery, or continuous deployment. DevOps practices enable a team to achieve the level of coordination and understanding necessary to realize all of these goals, as well as to automate infrastructure, testing, and deployment. Specifically, DevOps provides organizations a way to achieve • collaboration between project teams and roles • infrastructure as code • automation of tasks, processes, and workflows • continuous monitoring of applications and infrastructure Business value drives DevOps development. Without a DevOps mindset, organizations often find their operations, development, and testing teams working toward short-sighted incentives of creating their infrastructure, test suites, or product increment. In this webinar, we'll talk about DevOps, its common misconceptions and roadblocks, and how you can use DevOps to help your organization reach new heights of efficiency and productivity.

While software security is an increasing concern for software and system architects, few architects approach this quality concern strategically. Architects and developers primarily focus on functionality, and security is often applied as a band-aid solution after an application has been developed. In the second talk we report on three case studies of real-world projects—two industrial and one open-source—where we attempted to measure the consequences of various architectural approaches to security. The results of our case studies indicate that a strategic, system-wide, architectural approach to security, implemented as a security framework, results in the best outcome from both security and maintenance cost perspectives.

Software architecture has enormous influence on the behavior of a system. For many categories of systems, early architectural decisions can be a greater influence on success than nearly any other factor. After more than twenty years of research and practice, the foundations for software architecture have been established and codified, but challenges remain. Among other trends, increased connectivity, a shift to the cloud and to mobile platforms, and increased operational and market tempos have precipitated the need for changes in architectural practices and decisions. The first talk shares a perspective on the trends influencing the need for change, the related architectural challenges, and the applicable research and practices.