The Importance of Documenting Changes in the Security Lifecycle

The sooner you spot the bug after writing it, the cheaper and quicker it is to fix it. So if we can spot a potential security issue based on either the initial checking of the template or change, then people can make that adjustment. You know, there's actually a really good analogy here, I just thought about it. If you're deploying some resources, and they're running Microsoft Defender for Cloud to see if you've got vulnerabilities, that's a lot like a dynamic analysis scan. But if you're actually looking at the code for potential issues, that's very similar to a static analysis scan.