Detecting unsecured secrets
As mentioned previously, secrets should not be stored in source control, which is why the capabilities discussed earlier are available. Still, a developer can, by accident or for local testing, write down secrets in the application source code.
To ensure that these secrets do not end up in source control, a local plugin can be used to detect secrets and emit a warning to alert the developer to this risk. One tool that can do this for Visual Studio is the Continuous Delivery Tools for Visual Studio extension. This extension scans any open file for secrets and emits a compiler warning when it detects a possible secret. A link to this extension is added to the references at the end of this chapter. After running the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access