---
title: "Continuous Monitoring"
canonical: https://trickest.com/glossary/continuous-monitoring
description: "Continuous monitoring repeatedly checks assets and configurations on a schedule so teams detect new services, drift, and exposures soon after they appear rather than at audit time."
---

# Continuous Monitoring

Continuous monitoring runs the same checks against your assets on a recurring cadence and compares each result with the last. A point-in-time scan tells you the state of an environment on the day it ran. By the next morning a developer has spun up a new host, opened a port, or shipped a misconfigured cloud resource, and the scan no longer reflects reality. Monitoring closes that gap by treating discovery and assessment as an ongoing process.

This matters in attack-surface work because exposure is a moving target. Certificates expire, DNS records repoint, and services come and go faster than any manual review can track. Catching a newly exposed admin panel within hours, rather than at the next audit, shrinks the window an attacker has to act.

Continuous monitoring underpins [attack surface management](/glossary/attack-surface-management) and feeds [exposure management](/glossary/exposure-management) with fresh signal. It pairs naturally with [asset discovery](/glossary/asset-discovery) so the inventory stays current.

In Trickest you build the logic once as a workflow, then attach [scheduled scans](/glossary/scheduled-scans) so it reruns automatically and alerts you only when a diff shows something new or changed.

---
_Markdown source of https://trickest.com/glossary/continuous-monitoring._