slaalerts-SKILL.md

Vulnerability SLA breach detection is automated by calculating remediation deadlines from discovery dates and CVSS-based severity tiers, then categorizing findings as within SLA, approaching breach, or breached using Python scripts and a local SQLite database.

Yes, vulnerability remediation alerts can be sent to Slack, email, and PagerDuty simultaneously through predefined integration hooks, enabling multi-channel notifications and automated escalation paths to management when SLA breaches occur.

The best way to generate compliance reports for vulnerability SLA adherence is using automated reporting that summarizes overdue trends, remediation velocity, and SLA adherence by severity to support governance reviews and security audits.

This vulnerability SLA alerting tool requires the Python requests and yaml libraries, and it uses a local SQLite database to track vulnerability findings, meaning no external database server is needed for deployment.

Escalation paths for vulnerability SLA breaches are needed to ensure overdue remediations are routed through predefined lines of management, enforcing accountability and reducing security risk when owners miss CVSS-tier remediation deadlines.

JIRA integration for vulnerability SLA tracking is configured through integration hooks in the Python-based scripts, allowing you to link vulnerability findings and SLA breach alerts to JIRA tickets for remediation workflow management.