Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[New Process Improvement Need]: Recommendations for automated security scans #51

Closed
riverma opened this issue Sep 8, 2022 · 3 comments
Closed

[New Process Improvement Need]: Recommendations for automated security scans #51

riverma opened this issue Sep 8, 2022 · 3 comments
Assignees
@ramesh-maddegoda
Labels
medium complexity Ticket is relatively straightforward but may have a difficult sub-task more requested Requested by community members at a medium level software lifecycle Process improvements involving developing, testing, integrating, deploying software

Comments

@riverma
Copy link
Collaborator

riverma commented Sep 8, 2022

Checked for duplicates

Yes - I've already checked

Category

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

Describe the need

We have a need for:

  • Guidance for repository security scanning (+1'd by @ramesh-maddegoda)
  • Automated source code quality scanning tools (E.g.: SonarCube)  to check the source code quality
  • Automated static security scanning tools (E.g: HP Fortify, IBM AppScan) to check source code for security vulnerabilities
  • Automated 3rd party dependency scanning tools (E.g: Back Duck) to ensure if the algorithms are not using known vulnerable open source libraries
@riverma riverma added enhancement more requested Requested by community members at a medium level labels Sep 8, 2022
@riverma riverma added the medium complexity Ticket is relatively straightforward but may have a difficult sub-task label Sep 29, 2022
@riverma riverma added software lifecycle Process improvements involving developing, testing, integrating, deploying software and removed enhancement labels Nov 1, 2022
@riverma
Copy link
Collaborator Author

riverma commented Dec 1, 2022 •
edited
Loading

+1'd by @ramesh-maddegoda, @jeffreypon, @pymonger

@riverma riverma mentioned this issue Dec 23, 2022
Open
2 tasks
@riverma
Copy link
Collaborator Author

riverma commented Dec 23, 2022

Duplicate? #25

@ramesh-maddegoda ramesh-maddegoda self-assigned this Jan 11, 2023
@riverma riverma moved this to 🆕 New in SLIM Planning Board Feb 14, 2023
@riverma
Copy link
Collaborator Author

riverma commented Dec 11, 2023

Closing this issue as #25 duplicates this.

@riverma riverma closed this as not planned Won't fix, can't repro, duplicate, stale Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ramesh-maddegoda ramesh-maddegoda

Labels
medium complexity Ticket is relatively straightforward but may have a difficult sub-task more requested Requested by community members at a medium level software lifecycle Process improvements involving developing, testing, integrating, deploying software
Projects
SLIM Planning Board
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@riverma @ramesh-maddegoda