...
Report for example 100 - malus.
Limitations of the approach and of GH Sec
There are more sophisticated scoring approaches.
Veracode has a specific application profile setting based on the use case of the product, risks, architecture etc.
GitHub Security doesn’t even distinguish between a NodeJS frontend (Angular) and Backend project ( ) . At a certain site and complexity of the service platform, you will need different approaches.
But you can still start this way and expand later.
With GitHub Security application profiles for PCI DSS or other standards cannot be defined (unless you’re at an SAQ-A, where this can suffice)
you can read the standards and document your decisions (in the tickets)
GH Sec is too generic and QA focused for PSP or critical infrastructure security (imho)
It’s too difficult (cumbersome) to define CI / CD build gates, for example if you want to block deployments with a score, that violates the baseline AppSec score.
the AppSec control here is metrics-based, not preventive.
it’s focused on reporting