Here's my first file, which is a C# file named lazy-consts.cs with some credentials: // For demo purposes. I've done this in hope of enforcing the tools to fail the DevOps pipelines to stop any of these sensitive artifacts to be pushed onward to any releases. I have created a scenario in which I have a set of files that contains some sensitive details, like account keys and passwords, and some certificate (.pem) files. Scenario: Ensure all new and existing code is more secure I will cover some other aspects in other posts in this blog. The Microsoft Security Code Analysis tools have a lot more power built-in than these build tasks I'm showing right now. To try and paint a picture of what I will demonstrate, I'll line up an example scenario where I already know I have some files that contains some security issues. Microsoft Security Risk Detection (Deprecated June 2020).Microsoft have done an amazing job with making this extension available, so we can make use of automated build tasks to check for some commonly encountered security issues.įollow me in this article to explore how we make use of the Azure DevOps extension for Microsoft Security Code Analysis, which includes these build tasks to help us: This post is about increasing automated security posture with Azure DevOps by using the ' Microsoft Security Code Analysis extension', which is a set of tasks that helps implement security analysis of your files and code in your pipelines.

Microsoft safety scanner log file