All templates

Automated Trend Micro Pattern Version Audit

Every morning, WebRun opens Trend Micro, reads the agent and pattern versions on every managed endpoint, works out which machines are behind the current release, posts the list to Slack grouped by device group, and messages you on WhatsApp when an entire group has drifted.

Runs on WebRun · Strict Lockdown policy
Every day at 8:00 AM WebRunorchestrates each step
1 Trend Micro read agent and pattern versions
2 Slack post the out of date list
3 WhatsApp flag a whole group falling behind
In short

How do I find endpoints running out of date Trend Micro patterns?

WebRun opens Trend Micro every morning, reads the agent and pattern version on every managed endpoint, and works out which machines are behind the rest of the estate. It posts the list to Slack grouped by device group and messages you on WhatsApp when a whole group has drifted.

  • Machines running old patterns are named every morning
  • A drifting device group is escalated instead of buried in a list
  • Version coverage is checked daily without opening the console

Built for IT administrators · security teams · managed service providers · SMB IT

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.trendmicro.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Trend Micro - read agent and pattern versions
    trendmicro.com
    WebRun in Trend Micro: read agent and pattern versions
    WebRun opens Trend Micro to read agent and pattern versions.
    • Open your Trend Micro console and list the managed endpoints
    • Read the agent version and pattern version on each one
    • Compare them against the newest version present in your estate
    • Note the last update time and the device group for every machine that is behind

    Done when Every endpoint running an out of date agent or pattern version is listed with its group.

  3. 2
    Slack - post the out of date list
    slack.com
    WebRun in Slack: post the out of date list
    WebRun opens Slack to post the out of date list.
    • Post the out of date machines to your security channel, grouped by device group
    • Put the machines furthest behind at the top with their last update time
    • Show how many endpoints are current so the gap has a denominator
    • Leave the update itself to your admins. WebRun does not push a deployment

    Done when The security channel has this morning's version gap list.

  4. 3
    WhatsApp - flag a whole group falling behind
    whatsapp.com
    WebRun in WhatsApp: flag a whole group falling behind
    WebRun opens WhatsApp to flag a whole group falling behind.
    • Message you on WhatsApp when a whole device group is behind rather than a few stragglers
    • Name the group, the count, and how many days since its last update
    • Stay quiet on mornings when only a handful of machines are behind

    Done when You are told on WhatsApp whenever an entire group has fallen behind.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.trendmicro.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Version gap list · Slack
OutputWhat each run produces - A daily list of endpoints whose agent or pattern version is behind the rest of the estate, grouped by device group.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it push updates to the machines it finds?

No. WebRun reads the console and reports the machines that are behind. Triggering an update or a deployment stays with your admins, so nothing is pushed to a production endpoint without a human deciding.

How is this different from chasing agents that stopped reporting?

An agent can check in perfectly and still run a months old pattern version. This run reads the versions themselves, so a coverage gap does not hide behind a healthy looking agent count.

Does it need admin rights on the console?

Read access to the endpoint list is enough. WebRun signs in with the account you connect once, reads the version columns, and never changes a policy or a setting.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.