Vulnerabilities

How Vantyris continuous monitoring works (without daily noise).

Published 2026-07-16 · Last updated 2026-07-16 · Vantyris editorial

What this means for your business

• Monitoring applies only to verified targets (you proved DNS control). That keeps scheduled scans from being abused against domains you do not own and ensures active modules never run against strangers' sites.
• Each scheduled run consumes one scan credit, same as a manual re-scan. A weekly monitor on one domain uses roughly four credits per month. You buy credits as needed; there is no forced subscription to keep monitoring alive.
• Alerts are deliberately narrow: a new high or critical severity finding, a security score drop of ten points or more compared to the previous snapshot, or a TLS certificate inside fourteen days of expiry. Low-severity drift and informational changes accumulate silently in the trend view.
• The comparison is snapshot-to-snapshot, not real-time intrusion detection. Vantyris is watching hygiene posture (certificates, headers, DNS, email auth, exposed services, reputation lists), not live packet streams or endpoint agents on staff laptops.

How to fix

Verify a target, enrol it in monitoring from the target settings page, pick a cadence that matches how often you actually fix things, and confirm alert email delivery. Keep enough credits in the wallet for the cadence you chose.

1. Complete a verified scan first. Run a verified scan on the domain you want to watch. Verification proves DNS control and unlocks the full module set. Monitoring cannot be enabled on teaser-only targets.
2. Open target settings and enable monitoring. In the workspace, open the target → Settings → Continuous monitoring. Toggle on and select cadence: daily, weekly, biweekly, or monthly. Weekly is the default most clinics and agencies pick; monthly is fine for stable brochure sites with infrequent deploys.
3. Set the alert email and confirm delivery. Alerts go to the workspace notification address. Send yourself a test notification from settings if available, and whitelist noreply@vantyris.com so alerts do not land in spam during the first real event.
4. Budget credits for the cadence. Each scheduled run spends one credit. Weekly ≈ 4/month, biweekly ≈ 2, monthly ≈ 1. Top up credit packs before a long weekend if you run daily on multiple targets. The portfolio dashboard shows upcoming runs and remaining balance.
5. Use the trend chart after each alert. When an alert fires, open the target trend chart: one dot per scan, outer ring on dots where critical/high findings landed. Fix the root cause, run a manual re-scan (another credit) to confirm the score moved, and leave monitoring on to catch regressions.

Owner: Workspace owner enrols; IT contact or agency implements fixes when alerts arrive. · Time: Enrolment: 5 minutes. Ongoing: one credit per scheduled run.

Common gotchas

• Do not pick daily cadence on a site you only patch monthly. You will burn credits and learn the same TLS/header facts repeatedly without capacity to act.
• Monitoring does not auto-fix findings. An alert means 'something changed in the external posture'; you still need a human to patch, update DNS, or renew a certificate.
• If INTERNAL_TICK_TOKEN and server cron are not configured on self-hosted deployments, scheduled runs will not fire regardless of UI enrolment. On vantyris.com production, confirm the ops cron hits POST /api/internal/run-monitoring-tick.
• Pausing monitoring during a major rebuild is fine. Document the pause so an auditor does not interpret a gap as neglect.

How to verify the fix

After enrolment, check the target page for the next scheduled run timestamp. Optionally trigger a manual scan, then confirm the trend chart gained a new dot. Simulate an alert threshold by fixing a high finding and re-scanning to watch the score move; the next regression should email you if severity returns.

Cyber Essentials alignment

This finding informs the following UK NCSC Cyber Essentials control areas:

• A2. Secure configuration — devices and services hardened against the inherent default vulnerabilities.
• A3. Security update management — software supported, updated, and patched within 14 days for high-/critical-risk vulnerabilities.

Vantyris is not a CE certifying body. The mapping above is informational.

Common follow-up questions

References

• NCSC: vulnerability scanning guidance NCSC
• Vantyris methodology Vendor
• Vantyris pricing (credit packs) Vendor

Related explainers

• What a passive security scan can and cannot prove about your site.
• Your TLS certificate has expired. Here's how to restore the site fast.
• Google Safe Browsing: how it flags sites and how to clear yours.