You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@seccubus
In a CI/CD environment, while running scans on products, it's important to know the history alongside version. As a sample case, let's say in current version you find a bug and in next version the bug is fixed. currently in seccubus, we only have the state of each finding, but we don't have a reference on the version. As it's a CI/CD environment and we need to compare the results, we only have one workspace. it will be great if you can add an option to scan execution to accept an input as "tag" or "flag" and place it in run table in database. then show this tag on runs and findings history. this tag can be used as version, remark or anything else the user desire so that by looking in finding history, we can have a clear view on state and version in findings.
what do you think about this?
The text was updated successfully, but these errors were encountered:
@seccubus
In a CI/CD environment, while running scans on products, it's important to know the history alongside version. As a sample case, let's say in current version you find a bug and in next version the bug is fixed. currently in seccubus, we only have the state of each finding, but we don't have a reference on the version. As it's a CI/CD environment and we need to compare the results, we only have one workspace. it will be great if you can add an option to scan execution to accept an input as "tag" or "flag" and place it in run table in database. then show this tag on runs and findings history. this tag can be used as version, remark or anything else the user desire so that by looking in finding history, we can have a clear view on state and version in findings.
what do you think about this?
The text was updated successfully, but these errors were encountered: