Threat Score Overview

Based on the latest Threat Center score and analysis across all widgets:

Threat Center Score & Key Metrics

• Overall Threat Center Score: 56.4% (Moderate -- requires attention)
• Platform Security Compliance: 52.9% (18 best practices passed, 16 not passed)
• Data Recovery Health: 64.8% healthy restore points (236 healthy, 128 unhealthy)
• Data Protection Status: 77.8% of workloads protected (7 protected, 2 not protected)
• Backup Immutability: 30% of workloads have immutable backups (3 compatible, 7 incompatible)

RPO Anomalies

• 2 workloads have missed their backup RPO on server bgpdvbr.betagrounds.local
• These workloads may have never been backed up or have not met RPO at all

Malware & Suspicious Restore Points

• No infected restore points detected
• 14 suspicious restore points found in repository SOBR-Wasabi\NAS02-NFS1, affecting workloads in Christchurch
• No increase in infected or suspicious restore points in the last 7 days

SLA Compliance

• 327 successful sessions, 5 failed sessions in the last 30 days
• SLA compliance is high at 98%, with only 1 non-compliant day

Your environment shows moderate security and data protection posture. While most workloads are protected and SLA compliance is high, there are notable gaps:

• Only half of security best practices are implemented
• Immutability is enabled for just 30% of workloads
• Over one-third of restore points are unhealthy
• 2 workloads are not meeting RPO
• 14 suspicious restore points require investigation

1. Improve Security Compliance: Implement the 16 missing best practices for Veeam Backup & Replication servers
2. Increase Immutability: Configure more workloads to use immutable backup repositories
3. Address Unhealthy Restore Points: Investigate and resolve the 128 unhealthy restore points
4. Resolve RPO Issues: Ensure all critical workloads are meeting their RPO by reviewing backup job schedules and statuses
5. Investigate Suspicious Restore Points: Analyze the 14 suspicious restore points, especially in the 'SOBR-Wasabi' repository
6. Maintain SLA Compliance: Review failed backup sessions and address root causes to prevent future SLA breaches

If you need step-by-step guidance on any of these recommendations, please let me know!