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
Add a download option for the Trivy scan report in HTML or XLS format, along with the ability to send the report via email.
🎤 Pitch / Usecases
Add a download option for the Trivy scan report in HTML or XLS format, along with the ability to send the report via email.
Audit and Compliance:
Security teams often require scan reports in readable formats (HTML/XLS) for compliance documentation, internal audits, and external security reviews.
Being able to archive these reports supports traceability and governance.
Sharing with Stakeholders:
Developers, DevSecOps, and security teams may work in different tools or environments. Emailing the reports ensures that relevant stakeholders are informed promptly without requiring access to the scanning platform.
Ease of Analysis:
XLS format allows users to filter, sort, and analyze vulnerabilities by severity, package, or fix availability.
HTML reports provide a clean and navigable UI for quick inspection of issues.
Integration with Ticketing Systems:
Emailing reports makes it easier to attach them to Jira tickets, ServiceNow requests, or other incident tracking tools as supporting evidence.
Offline Access:
Downloadable reports can be reviewed offline or shared over restricted networks where tool access may be limited.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🔖 Feature description
Add a download option for the Trivy scan report in HTML or XLS format, along with the ability to send the report via email.
🎤 Pitch / Usecases
Add a download option for the Trivy scan report in HTML or XLS format, along with the ability to send the report via email.
Audit and Compliance:
Security teams often require scan reports in readable formats (HTML/XLS) for compliance documentation, internal audits, and external security reviews.
Being able to archive these reports supports traceability and governance.
Sharing with Stakeholders:
Developers, DevSecOps, and security teams may work in different tools or environments. Emailing the reports ensures that relevant stakeholders are informed promptly without requiring access to the scanning platform.
Ease of Analysis:
XLS format allows users to filter, sort, and analyze vulnerabilities by severity, package, or fix availability.
HTML reports provide a clean and navigable UI for quick inspection of issues.
Integration with Ticketing Systems:
Emailing reports makes it easier to attach them to Jira tickets, ServiceNow requests, or other incident tracking tools as supporting evidence.
Offline Access:
Downloadable reports can be reviewed offline or shared over restricted networks where tool access may be limited.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: