From the course: GitHub Advanced Security Cert Prep by Microsoft Press

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Explain how to set a review cadence with security teams when appropriate

Explain how to set a review cadence with security teams when appropriate - GitHub Tutorial

From the course: GitHub Advanced Security Cert Prep by Microsoft Press

Start my 1-month free trial Buy for my team

Explain how to set a review cadence with security teams when appropriate

“

- [Instructor] Let's look at a collaboration example. A developer identifies a potential SQL injection vulnerability in their code. They consult the security team because thanks to DevOps, they know each other and they're comfortable with each other and have a degree of trust built up. They consult the security team for best practices and remediation. Security team even reviews the code and verifies the implemented fix. Well, that's a happy story. I know IT doesn't always work that collegially but it's a great goal to have at any rate. Okay, well, yeah, what is the cadence? what does GitHub recommend? Well, I don't think GitHub recommends numbers for security or review cadences. But you'll just want to configure factors. How complicated and large is your code base? What's your development pace? What kind of iteration you doing? What's your tolerance for risk and out-of-date data? More frequent reviews for critical projects. That's normally the case, isn't it? Or rapidly changing code…

Contents