Sample alert How it works Coverage PENTEST METHODOLOGY DOCS PRICING FAQ MCP CONTACT LOG IN SCAN MY APP →

How to Monitor Vulnerabilities Across Multiple Websites

GUIDE / OPERATIONS

For agencies, MSPs, and portfolio owners. Keep one inventory, scan each site as its own target, triage all findings in one view, and send reports to each client.

SCAN YOUR FIRST CLIENT SITE

Enter the URL of a site you manage. Each site becomes its own target, so you can add more sites to the same account one by one.

To monitor vulnerabilities across many websites, keep one inventory, add each site as its own target, and triage all findings in one list by severity. Then route alerts to a webhook and export a report for each client.

Why is multi-site monitoring different from single-site monitoring?

One site needs one scan plan. Thirty sites need an operating process. The risk is not only a weak site. The risk is a site that nobody owns, nobody scans, and nobody reports on.

Agencies and managed service providers (MSPs) have the same problem. Each client has a different stack, a different host, and a different owner. Each client also wants proof that you did the work.

A portfolio owner has a related problem. Some sites have no active developer.

This page covers the operation across many sites. It covers the inventory, the target rules, the triage, the alerts, the reports, and the team roles. For always-on checks of one production application, read security monitoring. For the scan itself, read the automated website vulnerability scanner page.

How do I build a site inventory?

An inventory is the list of everything you must scan. Start it before you run the first scan. A scanner can only test the sites that you add.

  1. Export the list of domains from your registrar and your DNS provider.
  2. Add the sites from your hosting accounts and your CDN accounts.
  3. Add the sites from your billing system. Each paid client has at least one site.
  4. For each site, write the production URL, the owner, the host, and the stack.
  5. Mark which sites are live, which are staging, and which are retired.
  6. Check each client contract for the right to test the site.

Review the inventory each month. Remove retired sites, and add new ones when a client launches.

Include the hosts that people forget. These include old campaign sites, preview deploys, admin subdomains, and test copies. The guide discover forgotten web apps shows how to find them with DNS and certificate logs.

Use the inventory as a table with one row for each site.

Column Why you need it
Production URL The address you scan
Client and owner The person who gets the report
Host and stack Helps you read the findings
Test permission A link to the written scope
Scan profile The depth you use for this site
Last scan date Shows which sites are late
Status Live, staging, or retired

How many targets do I need?

Use one target for each site. A target is a single origin, such as https://shop.client-a.com. Scans, findings, and monitoring attach to the target.

The host name is lower-cased and trailing slashes are removed. For this reason, https://Example.com/ and https://example.com are the same target.

Note the limits of each plan. The Pro and Lifetime plans hold up to 50 targets. The Enterprise plan holds an unlimited number. The Enterprise plan is the plan named Team on the landing page. See the billing page for the full table.

The scan count is a separate limit. Pro and Lifetime plans include 100 scans each month. Every scan and every re-run uses one scan. Use this simple calculation before you add sites.

  1. Count the sites you will scan.
  2. Count how many times you will scan each site in a month.
  3. Multiply the two numbers.
  4. If the result is more than 100, plan for the Enterprise plan or fewer scans.

What scope rules should I set for each site?

The scope controls how far the crawler goes. Set it on purpose for each site, not by habit.

Scope Use it when
Single URL only You test one page and what it links to on the same path
Entire domain The site is one origin and you want the full crawl
Include subdomains The client owns the subdomains and gave permission for them

Follow these rules for every site.

  1. Test only the domains that are named in the written scope.
  2. Give a sitemap URL so the crawler does not miss a page.
  3. Give an OpenAPI URL if the site has a documented API.
  4. Add excluded paths for routes that cause side effects, such as /logout.
  5. Lower the request rate for sites on small hosts.
  6. Use a test account for authenticated scans.

If a site is behind a login, VibeEval accepts a bearer token, a cookie, basic auth, or a form login. Use the Secret instruction field for credentials that must not appear in a report. This matters when you send the report to a client.

The tool refuses private addresses, localhost, and government and military domains. To test a pre-production build, deploy it to a public preview URL. Read the targets page for all validation rules.

Which scan profile should I use for each site?

Do not use one profile for all sites. Match the profile to the risk of the site.

Site type Suggested profile
Brochure site with no login Quick Scan
Shop or site with forms DAST Full
Site with a documented API API Scan
Site with special needs Custom

A Quick Scan takes 1-3 minutes. A DAST Full scan takes 10-30 minutes. See Running scans for the details of each profile.

Run a DAST Full scan on a new client site first. Use the result as the baseline. Then use the Quick Scan for the routine passes between releases.

How do I triage findings across many sites?

The Findings page shows every finding across all targets. You can filter it by domain, severity, and status. This is your roll-up view.

Follow this triage order each week.

  1. Filter to critical findings on all domains. Handle these first.
  2. Filter to high findings. Assign an owner to each one.
  3. Open the Feed to see what is new in the last 7 days.
  4. Use the quick filter for findings that are due soon or out of SLA.
  5. Mark each confirmed false positive, so it does not come back.
  6. Snooze low-priority items.

The severity names are critical, high, medium, low, and info. The risk score from 0 to 100 uses these weights: critical 35, high 20, medium 10, low 3. The score is capped at 100. The risk score page explains the formula.

Use the risk score to rank sites against each other. Do not use it as proof that a site is safe.

Wait for the on-call review before you open tickets. Findings from a scan in review carry a Preliminary badge. They can change or disappear. The review finishes in a final email.

Findings are deduplicated by organization, target, and title. A re-run updates the same finding. The trend then shows it as new, fixed, or unchanged. This helps you see the change from week to week without a second copy.

Read the findings reference for all fields and actions.

How do I route alerts for many sites?

Alerts must go to the person who can act. Send them by webhook or by email.

To add a webhook, open Settings, then Webhooks, then Add webhook. Enter an HTTPS URL and select the events. VibeEval sends each event as a POST request with a JSON body. The body includes the ID, the target, the severity, and the status.

Event Use it to
finding.critical Page the on-call person at once
finding.new Add a ticket to the client queue
finding.statusChanged Update the ticket when a finding is fixed or re-opened
scan.completed Start the report job for the client
scan.failed Tell the operator to re-run the scan

Follow these rules for alert routing.

  1. Send finding.critical to a channel that someone watches all day.
  2. Send finding.new to a ticket system, not to a chat channel.
  3. Use the target in the JSON body to find the client and the owner.
  4. Keep a table that maps each target to a client channel.
  5. Test the webhook with one site before you add the others.

Email notifications are on the Notifications page. Critical findings, high findings, completed scans, and failed scans are on by default. The weekly security digest is off by default. Turn it on if your team wants one summary each week.

For the full list of events, read the webhooks page. If you want to send scan data to your own systems with code, see security testing API.

How do I report to clients?

A client report must be short, clear, and in the format that the client can use. Export it from the Report tab of a scan.

Export Send it to
PDF The client owner, with an executive summary
PDF (anonymized) A public place, such as a forum or a case study
CSV The client risk register or spreadsheet
JSON Your ticket system or your own dashboard

The PDF has the target, the date, the profile, and the risk score. It also has the summary counts, the on-call review notes, the issues, and the passed checks. The Passed Checks table shows the client what you tested, not only what failed. This is useful proof of work.

The anonymized PDF removes the target host, its subdomains, email addresses, and backend project identifiers.

For a report across several scans, open Reports, then New report. Select the scans and a format. Then select a framework, such as OWASP Top 10 or ISO 27001:2022. Compliance mapping to OWASP, PCI-DSS, and CWE is an Enterprise feature. Other plans get the framework-structured report with findings only.

Use this monthly report routine for each client.

  1. Run a re-run scan for the site.
  2. Wait for the status to change to completed.
  3. Open the trend and note what was fixed and what is new.
  4. Export the PDF.
  5. Write two sentences at the top: what changed and what you will fix next.
  6. Send the report to the client owner.

An exported report from a scanner is a smoke-test output. It is not a signed penetration test. If a client or an auditor needs a signed report, use a formal engagement. See pentest services.

How should I assign team roles?

VibeEval has four roles.

Role Use it for
Owner The account that created the organization
Admin Manages members, settings, billing, and integrations
Analyst Runs scans, triages findings, and generates reports
Viewer Read-only access to scans, findings, and reports

Give the Analyst role to the people who run the weekly triage. Give the Viewer role to account managers who only read reports. Keep the Admin role to a small group.

Note two limits. The Pro and Lifetime plans include one seat. The Enterprise plan includes unlimited seats. For teams of more than one person, use the Enterprise plan.

Members of one organization share all data. There are no private targets for each member. If you must keep one client away from another, use separate organizations. Read the team page for the invitation and the access rules.

How often should I scan each site?

Choose the frequency by the rate of change of the site.

  • Sites with weekly changes: scan after each release.
  • Sites with monthly changes: scan each month.
  • Static sites: scan each quarter and after any plugin or theme change.
  • New client sites: scan at the handover and again at launch.

VibeEval also offers Set up monitoring on a completed scan. It registers the target for weekly re-checks and change alerts. It is an early-access capability and is opt-in for each target. Treat the one-off re-run as the dependable path today. See security monitoring for the always-on model.

What are the common mistakes?

  • Missing sites. A site that is not in the inventory is not scanned.
  • No written scope. You cannot prove that you had permission.
  • Alerts with no owner. A webhook that nobody reads is not an alert.
  • Mixed client data. Use separate organizations if clients must not see each other.
  • No retest. A finding is closed only after a retest proves the fix.

For a plain-language list for non-technical owners, share the SMB web app security checklist with your clients. For the OWASP view of the most common web risks, see the OWASP Top 10. For test methods, see the OWASP Web Security Testing Guide.

Common questions

How do I monitor vulnerabilities across many websites?
Make an inventory of every site. Add each site as one target. Scan each target on a fixed schedule that you keep. Triage all findings in one list sorted by severity. Send critical events to a webhook and export a report for each client.
How many websites can one account hold?
A target is one origin. The Pro and Lifetime plans hold up to 50 targets. The Enterprise plan holds an unlimited number. Each scan counts against the monthly scan quota of the plan.
Can I keep client data separate?
Members of one organization share all data. There are no private targets for each member. If you need separation between clients, use separate organizations.
How do I send a report to a client?
Open a scan and use the Report tab. Export a PDF for the client. Use the anonymized PDF if the report goes to a public place. Use CSV or JSON to feed your ticket system or your risk register.
Can I get an alert when a critical finding appears?
Yes. Add a webhook and subscribe to the finding.critical event. You can also keep the email notification for critical findings, which is on by default.
Does this replace monitoring for one application?
No. This page covers the operation of many sites. For always-on checks of one production application, read the security monitoring page.

One account, many sites

Add each site as a target, run scans, and triage all findings by severity in one list. Export PDF, CSV, and JSON reports, and send events to your webhooks.

14-day free trial · Cancel anytime

START FREE TRIAL →