Monitoring and Alerts
A baseline establishes what is true. Monitoring verifies it stays true.
A point-in-time assessment describes the day it was taken. Monitoring turns an unannounced change in a third-party script into a visible event rather than an invisible one.
You choose what matters: a new third party appearing, a security header disappearing, a script changing, a sanctioned entity entering the supply chain, a certificate approaching expiry. SCVue re-captures on your schedule and notifies you when a condition is met.
How the watching works
-
Schedules
A capture definition set to repeat on its own rather than be requested each time, on an hourly, daily, weekly or monthly recurrence or a single deferred run. Each schedule shows how many sessions a run will produce before it runs, and can be paused without being deleted.
-
What an Alert Shows
What triggered, when it triggered, and which application and version it affected, with a link straight to the evidence behind it.
-
An Alert History
What has fired, when, and against which application, kept as a record. Continuous monitoring can then be demonstrated rather than asserted.
-
Reconciled Against the Baseline
A call that has never been seen before is added to the version. A call that returns the same result as before has its validation count increased. What you keep is a record of what changed, not a duplicate copy of what did not.
-
Change Over Time
Every resource against every run, so a file that changed shows as changed and one that stopped being served shows as absent. Grouping by date or by location is the difference between watching an application move over time and watching two regions differ from each other.
-
One Definition, Every Run
A schedule reuses one capture definition, so the plan, the device profiles and the locations do not drift between runs. Comparability over months depends on nothing changing except the application.
A weekly capture of your ten most important applications, from three countries, running without anyone remembering to do it.
From an assessment tool into a monitoring one
That is what a schedule does: the same capture definition, run again on its own, with each result reconciled against the version's baseline.
One capture is enough to start
Capture a session in the browser, import it, and read what comes back. A free community account is available immediately.