Skip to main content

Product help

Triage an alert without losing the evidence behind it.

Filter to the correct domain, inspect the before-and-after evidence, assign an owner and close the alert only when its named resolution evidence exists.

Bounded collection. Explicit permission. No exploitation or authentication attempts.

What to do

Triage, assign and resolve alerts

Each guide takes you from the current screen or state to one safe, testable outcome. This page helps you triage, assign and resolve alerts. The relevant evidence, owner and limit remain available from the same route.

Useful for: continuous customer · MSP analyst.

In practice

Complete the task safely

01

Where to start

Begin here when you need to triage, assign and resolve alerts. Stay with the domain, relationship or service state named on the page; the task does not widen silently into a different security or product claim.

02

What to check

Shared or provider-managed infrastructure is dependency context and is not automatically customer exposure. Open the relevant report evidence when you need to verify the source, observation time, attribution or qualification behind it.

03

How to complete the task

Complete the step shown on the page, then check the resulting state before moving on. Unknown, unavailable and not-applicable outcomes remain distinct, so absence is never presented as a successful or reassuring result.

04

How to recover safely

Contact support with the correlation reference, never credentials or secret values. Record the resulting owner, evidence or recovery state where the product provides it, so another person can verify what happened without repeating the task.

What you can rely on

Checks that prevent mistakes

Confirm the workspace, domain and evidence state before completing a task.

Clear scope

Continuous monitoring compares assessments only when policy, scope and evidence conditions are comparable.

Traceable evidence

Shared or provider-managed infrastructure is dependency context and is not automatically customer exposure.

Honest limits

Provider or collector failure cannot improve a grade.

Important boundary

What this does not mean

Use alerts supports one defined outcome: triage, assign and resolve alerts. Domain Signals is not a penetration test, certification, data-residency assessment or prediction of breach likelihood. Missing evidence is not evidence of safety.

Questions answered

Read the conclusion and its limits together

What does Use alerts help me decide?

This page helps you triage, assign and resolve alerts.

What evidence sits behind the answer?

Domain Signals keeps the source, observation time and evidence state alongside each conclusion. The relevant report view provides the technical detail when you need to inspect it.

What should I not conclude?

Use alerts supports one defined outcome: triage, assign and resolve alerts. Domain Signals is not a penetration test, certification, data-residency assessment or prediction of breach likelihood. Missing evidence is not evidence of safety.

Keep exploring

Useful next steps

The next responsible step

Open product support

Open product support