Bug 35984

Summary: automated static code analysis should include security tests
Product: Koha Reporter: Evelyn Hartline <evelyn>
Component: Architecture, internals, and plumbingAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: dcook, emily.lamancusa
Version: unspecified   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Evelyn Hartline 2024-02-02 00:12:49 UTC
A few libraries have asked recently if, prior to production/during the development lifecycle, automated source code analysis tools are used to test for security flaws specifically. Typically these questions are in relation to processes like renewing cybersecurity insurance or initial discovery by a potential partner library's security/IT department.

Perlcritic seems to be currently used, but as far as I can tell it appears the tests are for enforcing the coding standard. 

Using an automated tool to look for security flaws will be a beneficial addition to the project, so I'd like to at least start the discussion here. 

OWASP has an informational page for further reading: https://owasp.org/www-community/controls/Static_Code_Analysis