Guide on Code Security Scanning

[ingyhere]

Purpose

• Add new security scanning guide focused on the NASA SCRUB tool

  Proposed Changes

• [ADD] README contents

  Issues

• 25

  Testing

• Locally tested with sample repository: full scan, pre-commit hook
• See rendered guide here: https://github.com/NASA-AMMOS/slim/tree/issue_25/docs/guides/software-lifecycle/security/security-scanning

[riverma]

@ingyhere - just a note, adding labels for the type of SLIM best practice category each PR applies to (i.e. governance, software lifecycle, information sharing) helps to make future release notes more readable. See information about categories here.

Also - adding the SLIM Project Board in the PR right hand menu, and tagging the status as well as the iteration helps people understand the time line for the PR.

[ingyhere]

@ingyhere - just a note, adding labels for the type of SLIM best practice category each PR applies ...

Also - adding the SLIM Project Board in the PR right hand menu, and tagging the status ...

Done

[nutjob4life]

@jpl-jengelke, quick favor: when this moves out of "draft" state, could you ping me @nutjob4life? I tend to mute draft PRS both logically and mentally 😇 Nevermind, I saw it go out of draft "live" during the tag-up meeting on 2024-05-02

[ingyhere]

Superbly written guide with a great cadence and feel as well as utility. Should make SCRUB a much easier pill to swallow. Bravo! 🎉

Unfortunately as things go ... I see some areas for improvement. But I will make changes and ask for re-review.