If you have problems with the vagrant up command then access this file manually and then do a vagrant box add --name bruntonspall/security-testing
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 tutorial, I will talk through how government is changing its approach to accreditation, to building secure services. We’ll cover things from continuous security testing through to living risk registers, team threat assessments, and security embracing the entire service design.
Michael Brunton-Spall is technical architect at the Government Digital Service. He travels the country helping government agencies and services embrace the digital now. Previously Michael worked at the Guardian for six years, helping to build and scale the website, building the API, helping run the platform team, and acting as developer advocate, talking at conferences and events.
©2015, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org