[New Process Improvement Need]: Best Practices for Coding Standards to Avoid Security Issues

[riverma]

Checked for duplicates

Yes - I've already checked

Category

Security - application, network, hardware, etc. security topics

Describe the need

We have a need for the construction of coding standard training guides for avoiding common JPL language-dependent security weaknesses. (+1'd by @LucaCinquini @ramesh-maddegoda)

[riverma]

+1'd by @ramesh-maddegoda, @MJJoyce, @Scotchester, @kgrimes2

[riverma]

Hi @ramesh-maddegoda - I think this might be duplicated by another ticket that has seen some progress lately. What do you think about sharing your thoughts on the other ticket and I can close this one?

• Ticket: [New Best Practice Guide]: Security Reference Architecture #109
• Associated PR: [DRAFT] of Security Best Practices for Developers Guide #116
• Best Practice Guide (from draft PR above): https://github.com/NASA-AMMOS/slim/tree/issue-109/docs/guides/software-lifecycle/security/developer-best-practices

[ramesh-maddegoda]

@riverma , Agreed. This can be covered under the ticket #109

[ramesh-maddegoda]

Closed as this is getting covered by the following ticket.

[New Best Practice Guide]: Security To-Do's for Devs #109