Software Engineering, Project Management, and Effectiveness
We’ve been exploring Azure on the patterns & practices team for potential security guidance. To get our heads around it, we’ve had to create a simple view for our team that we could quickly whiteboard or drill into. We wanted a way to easily compare with our previous security guidance. Here’s what we ended up with …
Today’s application security mental model …
Compare that to our evolving security mental model for Azure …
Now I can clearly see how i can re-use my curent security investment applying it in emerging tech
Thanks, JD, especially for the "mental map" concept and diagram.
What happened to "Parameter Manipulation" (from the "Securing the Application" block)? Is there some reason using the Cloud removes this concern?
We folded parameter manipulation into our validation bucket. We've basically combined parameter manipulation, input and data validation into a simpler bucke - "validation" as our catch all.