Initial commit - 611 cybersecurity skills across all subdomains

2026-07-30 07:56:52 +03:00 · 2026-02-25 10:47:44 +01:00
commit 22a7ab1462
1765 changed files with 280648 additions and 0 deletions
@@ -0,0 +1,58 @@
+# Standards and References - Vulnerability SLA Breach Alerting
+
+## Primary Standards
+
+### NIST SP 800-40 Rev 4
+- **Title**: Guide to Enterprise Patch Management Planning
+- **URL**: https://csrc.nist.gov/publications/detail/sp/800-40/rev-4/final
+- **Relevance**: Defines organizational patch management lifecycle and remediation timelines
+
+### CISA Binding Operational Directive 22-01
+- **Title**: Reducing the Significant Risk of Known Exploited Vulnerabilities
+- **URL**: https://www.cisa.gov/binding-operational-directive-22-01
+- **SLA Mandate**: Federal agencies must remediate KEV-listed vulnerabilities within specified timeframes (typically 14 days for new additions)
+
+### PCI DSS v4.0 Requirement 6.3
+- **Title**: Security Vulnerabilities Are Identified and Addressed
+- **URL**: https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0.pdf
+- **SLA Requirement**: Critical and high-severity vulnerabilities must be patched within 30 days of release; risk-ranked approach for all others
+
+### SOC 2 Type II - CC7.1
+- **Title**: Detection and Monitoring of Security Events
+- **Relevance**: Requires evidence of vulnerability management program with defined remediation timelines and tracking
+
+### ISO 27001:2022 - Control A.8.8
+- **Title**: Management of Technical Vulnerabilities
+- **Relevance**: Requires timely identification and remediation of technical vulnerabilities with defined response timelines
+
+## Industry SLA Benchmarks
+
+### SANS Vulnerability Management Maturity
+- **Critical**: 24-48 hours
+- **High**: 7-30 days
+- **Medium**: 30-90 days
+- **Low**: 90-180 days
+
+### CIS Controls v8 - Control 7
+- **Title**: Continuous Vulnerability Management
+- **URL**: https://www.cisecurity.org/controls/continuous-vulnerability-management
+- **Implementation Group 1**: Remediate detected vulnerabilities monthly
+- **Implementation Group 2**: Automated remediation tracking with SLA enforcement
+- **Implementation Group 3**: Real-time SLA monitoring with automated escalation
+
+## Integration APIs
+
+### PagerDuty Events API v2
+- **URL**: https://developer.pagerduty.com/api-reference/a7d81b0e9200f-send-an-event-to-pager-duty
+- **Endpoint**: https://events.pagerduty.com/v2/enqueue
+
+### Slack Incoming Webhooks
+- **URL**: https://api.slack.com/messaging/webhooks
+- **Rate Limit**: 1 message per second per webhook
+
+### Microsoft Teams Incoming Webhook
+- **URL**: https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook
+
+### Jira REST API
+- **URL**: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
+- **Relevance**: Create and track remediation tickets with SLA metadata
@@ -0,0 +1,72 @@
+# Workflows - Vulnerability SLA Breach Alerting
+
+## Workflow 1: SLA Assignment on New Findings
+
+### Trigger
+New vulnerability findings imported from scanner.
+
+### Steps
+1. Parse incoming vulnerability data (CVE ID, CVSS score, affected asset)
+2. Look up asset criticality from CMDB to determine if SLA should be tightened
+3. Calculate SLA tier based on CVSS score and asset criticality
+4. Compute SLA deadline: `discovered_at + remediation_days`
+5. Insert SLA record into tracking database
+6. Assign finding owner based on asset ownership mapping
+7. Send initial notification to asset owner with SLA deadline
+
+## Workflow 2: Hourly SLA Breach Check
+
+### Trigger
+Cron job running every hour.
+
+### Steps
+1. Query all open vulnerability SLA records
+2. For each record, calculate current SLA status:
+   - **within_sla**: Less than 80% of SLA window elapsed
+   - **approaching_breach**: 80-100% of SLA window elapsed
+   - **breached**: Past SLA deadline
+3. For approaching_breach findings (first notification):
+   - Send Slack/Teams warning to asset owner
+   - Send email notification to asset owner and team lead
+4. For breached findings:
+   - Send immediate Slack alert to security team channel
+   - Trigger PagerDuty incident for critical/high severity
+   - Send escalation email to management chain
+   - Update escalation_level in database
+5. For post-breach findings (already breached, escalation increase):
+   - Every 12 hours, increase escalation level
+   - Level 1: Team lead notification
+   - Level 2: Director notification
+   - Level 3: VP/CISO notification
+
+## Workflow 3: Remediation Confirmation
+
+### Trigger
+Vulnerability scanner re-scan confirms finding resolved.
+
+### Steps
+1. Match resolved finding to SLA record
+2. Record remediation timestamp
+3. Calculate if remediation was within SLA
+4. Update SLA record status to `remediated_within_sla` or `remediated_breach`
+5. Close any associated PagerDuty incidents
+6. Send confirmation notification to asset owner
+7. Update metrics dashboard
+
+## Workflow 4: Monthly SLA Compliance Report
+
+### Trigger
+First business day of each month.
+
+### Steps
+1. Query all SLA records for the previous month
+2. Calculate metrics by severity tier:
+   - Total findings per tier
+   - SLA compliance rate per tier
+   - Mean time to remediate per tier
+   - Count of currently overdue findings
+3. Identify top 10 assets with most SLA breaches
+4. Identify teams with lowest compliance rates
+5. Generate HTML report with charts
+6. Email report to security leadership
+7. Update executive dashboard