Automated Kaspersky Scan Coverage Audit
Every Monday, WebRun opens My Kaspersky, goes through every device on the account, reads when each last completed a scan and last updated its databases, checks the protection status and the subscription covering it, writes the audit into Notion, and posts the devices that have gone quiet to Microsoft Teams.
How do I check every device is still scanning and up to date?
WebRun audits your Kaspersky protection every Monday. It reads each device's last completed scan, last database update, protection status and subscription, writes the audit into Notion, and posts the machines that have gone quiet to Microsoft Teams, so an unscanned laptop is found before it becomes an incident.
- The device nobody has scanned in weeks is named every Monday
- Stale databases surface before a detection is missed
- Silent devices are separated from ones that merely skipped a scan
Built for IT admins · small business owners · office managers · managed service providers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
my.kaspersky.comin a real browser with your saved login - no setup, no API keys. -
1
Kaspersky - check scans and updates
kaspersky.com
WebRun opens Kaspersky to check scans and updates. - Open My Kaspersky and list every device on the account
- Read the last completed scan date and the last database update for each
- Read the protection status and which subscription covers the device
- Mark devices with no scan in your agreed window, stale databases, protection switched off, or no recent connection at all
Done when Every device has a last scan date, a database date and a status.
-
2
Notion - write the coverage audit
notion.so
WebRun opens Notion to write the coverage audit. - Add this week's coverage audit page with the date
- Put a row per device with owner, last scan, last update, status and subscription
- Sort the devices that have gone longest without a scan to the top
- Keep past weeks so a device that keeps drifting is obvious
Done when This week's coverage audit is written up in Notion.
-
3
Microsoft Teams - post the quiet devices
microsoft.com
WebRun opens Microsoft Teams to post the quiet devices. - Post the devices that have not scanned or updated inside the window
- Name the device, its owner and how long it has been quiet
- Leave the fix to a person. WebRun never starts a scan, changes settings or removes a device
Done when The IT channel knows which machines are unprotected in practice.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it start scans or change settings?
No. WebRun only reads the device list and reports. Starting a scan, changing protection settings, and removing a device stay with the person who owns the machines.
How long is too long without a scan?
You set the window, for example seven or fourteen days. Any device past it appears at the top of the Notion audit and in the Teams post with how long it has been quiet.
Does it catch a device that has stopped reporting entirely?
Yes. A device that has not connected recently is flagged separately from one that simply missed a scan, because a silent device is usually the real problem.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.