Update security-best-practices.md #14189
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The use of IaC tools has been barely mentioned in the current documentation, whether on this page or the Secure Azure Pipelines Overview page. In fact, the use of IaC tools (not necessarily YAML), continuous scanning of these tools, and policy-as-code are crucial pillars of DevOps security. I have added this information to inform readers.
FYI, Azure Bicep is an IaC tool, but it is not YAML.