ZIN continuously analyzes:
| Data Source | What ZIN Looks For |
|---|---|
| Integrations | New vulnerabilities, configuration changes, alert spikes |
| Asset Changes | New assets appearing, assets going offline, unexpected changes |
| Compliance Data | Controls falling out of compliance, evidence becoming stale |
| Vendor Risk | Vendor risk score changes, overdue assessments |
| Threat Intelligence | New threats relevant to your technology stack |
When ZIN detects something noteworthy, it generates a proactive insight with:
| Type | Example |
|---|---|
| Critical Vulnerability | "A critical vulnerability (CVE-2026-XXXX) affects 12 of your internet-facing servers" |
| Configuration Drift | "MFA was disabled for 3 admin accounts in the last 24 hours" |
| Compliance Gap | "Evidence for Control AC-2 is now 45 days stale — due for refresh" |
| Anomalous Activity | "Unusual outbound traffic detected from asset X" |
| Vendor Risk Change | "Vendor Y's risk score increased by 20 points due to a recent breach" |
For each proactive insight:
> Tip: Prioritize insights by severity. Critical insights with remediation steps should be acted on immediately.
| Issue | Solution |
|---|---|
| No proactive insights appearing | Connect more integrations. ZIN needs data sources to generate insights. |
| Insights seem irrelevant | ZIN improves with more context. Ensure your asset inventory and integrations are complete. |
| Insight recommendations are unclear | Ask ZIN Copilot for clarification — type "Explain this insight in more detail". |
| Too many low-priority insights | Focus on Critical and High severity. The platform will prioritize the most important findings. |