Monitoring
Detection
How a raw infrastructure change becomes an actionable issue — detection events, issue types, statuses, and what gets created.
From monitoring to detection
Monitoring runs continuously and records the state of every check. Detection is what happens when the state changes. When a monitoring check finds something different from the last known state — a record that was present is now missing, a certificate that was valid is now expired, a reputation signal that was clean now shows a blacklist hit — Infraova creates a detection event.
What a detection event contains
A detection event records the domain affected, the check type that triggered it, what the previous state was, what the current state is, and when the change was detected. Detection events are the raw record of what Infraova found. They are the input to the prioritization and proposal stages.
Issue types
Detection events are classified into issue types based on what was found. Authentication issues cover SPF, DKIM, and DMARC problems — missing records, invalid configuration, policy failures. DNS issues cover unexpected record changes, missing records, and propagation failures. Certificate issues cover expiring and expired SSL certificates. Reputation issues cover blacklist appearances and reputation signal degradation.
Issue status
Every issue has a status that reflects where it is in the operational workflow. Open means the issue has been detected and no action has been taken. Proposed means Infraova has generated a proposal for the issue and it is awaiting review. Approved means the proposal has been approved and is queued for execution. Resolved means the issue has been remediated and verified. Dismissed means the issue was reviewed and no action was taken.
Not every detection creates an issue
Not every monitoring change is a problem. Infraova evaluates each detection event and determines whether it represents a genuine issue. Some changes are expected — a DNS record updated by the provider, a certificate renewed before expiry. Infraova suppresses noise from expected changes so that the issues that surface in the dashboard are the ones that actually need attention.
Note
If Infraova dismisses a change you believe is significant, you can manually flag it from the domain's monitoring history.
Detection and the operating model
Detection sits between monitoring and prioritization in the operating model. It is the moment where raw infrastructure data becomes a structured problem. Every proposal Infraova generates is rooted in a detection event — the proposal exists because something specific changed, and that change is recorded in the detection.