As we move towards architectures designed to cope with changing requirements, and eternal services that go live and iterate, how can we manage change in a secure way? How can we possibly build secure systems in this environment? If you work in a governmental or regulated industry, then you’ll already be familiar with the hollow promises of accreditation. That’s commonly the thing left until the end, about the same time as the testing, and gives rise to the concept that security is the team that just says No. What if it could be different? What if a service could be continually accredited, continually tested against a baseline of security tests, and that the team was able to own and manage the risk register?
In this lesson, Michael Brunton-Spall walks through how government is changing its approach to accreditation, to building secure services. He covers things from continuous security testing through to living risk registers, team threat assessments, and security embracing the entire service design. This clip comes from the 2015 Velocity conference in Amsterdam.
- Title: Agile Security
- Release date: April 2018
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781492037682
You might also like
Risk Management for Cybersecurity and IT Managers
Have you ever wondered why your organization's executives or your manager made a decision to fund …
Agile Application Security
Agile continues to be the most adopted software development methodology among organizations worldwide, but it generally …
Security principles for the working architect
Security is an ever more important topic for system designers. As our world becomes digital, today’s …
The Future of Cyber Security and Security Innovation
Now that an industry of social network manipulation has risen, phenomena like the Arab Spring are …