Agile - Gavin Johnson-Lynn

Why do we Perform Secure Code Reviews

Why do we use secure code reviews, instead of just a generic code review?

When Should we Perform a Secure Code Review?

Working in an agile environment we need to consider what we do and how important it is that we do it. We want efficiency, but not at the expense of quality. So when we think about secure code reviews we shouldn't assume

Agile

Who can Perform a Secure Code Review?

You need to pick the right person for a job. Here's how to find the right person for a secure code review.

Security

Agile Secure Code Review

Performing secure code reviews in an agile environment.

Agile

Agile Secure Code Review - References

A list of references that have been useful when writing about Secure Code Reviews. I haven't found much yet! * FxCop [https://en.wikipedia.org/wiki/FxCop] * OWASP Code Review Guide [https://www.owasp.org/index.php/OWASP_Code_Review_Guide_Table_of_

Security

Defence in Depth Meets the Software Development Life-cycle

Security in software development can get time consuming. Thinking about it in an Agile way can save time and may even be better...

Security

Is your business unwilling to add security features to software?

I recently took part in a meeting of the North-East England chapter of (ISC)2 [https://www.isc2.org/], where security experts from the region used the world café conversational format to discuss a number of topics. I lead a table discussing secure software

Efficiency

Don't forget the small things.

Little things in software development are important, sometimes really important. Little things can seem so small that they don't deserve attention, tiny little tasks that can take seconds to do. If however these tasks a repeated over and over again, that time

Agile

3 Ways to Switch Off Code Analysis

Code analysis is a useful tool. The ability to stop code analysis in visual studio and from the command line can be important and save a lot of time. Here's how to do it.

Team

Everyone is crap, that’s why you need a team.

I'm talking specifically about software development here but this applies just as well to other areas too. Is everyone really crap? Yes, at something, whether it’s user interfaces, clean code, writing tests, design patterns, security, giving presentations or communication. Everyone has

Subscribe to Gavin Johnson-Lynn