Agile Security
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 alread...
| Autor Corporativo: | |
|---|---|
| Otros Autores: | |
| Formato: | |
| Idioma: | Inglés |
| Publicado: |
O'Reilly Media, Inc
2018.
|
| Edición: | 1st edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009631271106719 |
| Sumario: | 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. |
|---|---|
| Notas: | Title from title screen (viewed May 7, 2018). A video excerpt from the O'Reilly Velocity conference in Amsterdam, 2015. |
| Descripción Física: | 1 online resource (1 video file, approximately 1 hr., 26 min.) |
