The VITI Security Blog
Practical writing on managed IT + cybersecurity.
By the engineers doing the work - not a marketing team summarizing it. We write when we have something to say, not when the calendar says we should.
How Vexta's CISA KEV Coverage Tracker Works
Vexta shows what percentage of the CISA Known Exploited Vulnerabilities catalog it currently probes for, right at the top of the dashboard, and keeps that number synced daily.
Reliability Badges and False-Positive Tracking in Vexta
Vexta labels every finding with a reliability badge and tracks each detector's false-positive rate over time, so a hunter knows how much to trust a result before spending time on it.
Per-Finding Triage State in Vexta
Vexta tracks a status, note, and assignee on every finding, open through paid or wontfix, visible as a badge and editable from the CLI or dashboard.
Cross-Scan Finding Deduplication in Vexta
Vexta fingerprints every finding by target, type, URL, parameter, and payload signature, so repeat scans flag re-discoveries instead of duplicating them.
Finding Lifecycle Metrics: MTTR and KPIs in Vexta
Vexta tracks MTTR, defect density, recurrence rate, and SLA breaches per finding, computed from real scan and fix data rather than a separate tracker.
Compliance Mapping in Vexta: OWASP, NIST, PCI-DSS, SOC 2
Vexta auto-tags findings to OWASP, NIST 800-53, PCI-DSS, and SOC 2 controls and builds a compliance-specific PDF report with evidence per control.
Wordlist Management in Vexta: Custom Lists for Recon
Vexta lets a hunter upload, edit, and pick custom subdomain, directory, and parameter wordlists per scan, so recon fits the target instead of a generic list.
Vexta Notifications: Getting New Findings into Slack, Discord or Email
Vexta pushes new findings out to Slack, Discord, Telegram, Pushover, email, Google Chat, Microsoft Teams or a custom webhook, with multiple instances of each channel and templated messages.
Targeted Subscans in Vexta: Rescan One Endpoint Without Redoing the Whole Job
Vexta's targeted subscans run a single module, like a port scan or a directory bruteforce, against one subdomain, endpoint or IP, instead of forcing a full rescan to check one thing.