#032Guide3 min

Understand items marked To watch

Decide what a lower-severity observation means without mistaking it for continuous monitoring or a confirmed incident.

Hackaiz team · updated 21/11/2026

Illustration: a team reads a security report and marks priorities.
Illustration: a team reads a security report and marks priorities. Illustrative photo, not a screenshot.

01A report category, not a monitoring switch

To watch is one of the three severity labels used in Hackaiz reports, alongside Danger and To fix. It groups lower-severity and informational observations. The wording tells you how the report classifies an item; it does not activate a background service, subscribe you to alerts or mean that someone is continuously investigating it. Monitoring is optional and only concerns connected systems.

A lower-severity observation can still help a developer understand an application’s exposure. For example, an informational detail about a server response may reveal something useful about configuration without demonstrating unauthorized access to customer records. Treat that as context to assess, not as evidence of a breach. The specific finding and its evidence, rather than the words To watch alone, determine the next useful action.

02Find the observation behind the summary

From Projects, enter the project and select the observation. Read What was found and Evidence before drawing conclusions from the total number of To watch items. Then use Why does it matter? and What should you do next? to understand the suggested response. Check whether the location is a repository file or a tested address. This helps you involve the person who can actually change the relevant setting.

Look at the confidence label separately. High confidence can accompany a low-severity item: the observation may be reliable but limited in impact. Low confidence does not automatically make a finding false; it means the available support is weaker. An informational observation about a publicly visible component is different from proof that the component grants privileged access. Ask what the evidence establishes and where the explanation goes beyond that observation.

  1. 1Open the project and select the individual To watch result.
  2. 2Compare the location and analyzed version with the system you maintain.
  3. 3Read Evidence and confidence before deciding whether to investigate, improve configuration or document the observation.

03Choose a proportionate response

You can use your own work tracker to record why a particular observation matters, who will review it and which change would make you reconsider it. This is a suggested team practice, not a promise of an automatic deadline feature in Hackaiz. If a small configuration improvement is appropriate, test it against normal application behavior. Do not disable a useful integration simply to make a report shorter without understanding the consequence.

Consider a response that reveals a framework version. The observation may justify checking update practices and unnecessary information exposure. It does not, by itself, prove that a known exploit works against your deployment. Conversely, an apparently modest observation on an administrative service may warrant closer attention because of that service’s permissions. Document these contextual reasons instead of treating every item in the category as equally urgent or equally harmless.

04Revisit with evidence rather than assumptions

Read later results against the original scope and version. An item absent from a later report may reflect a real improvement, a changed target or a check that was not run. Only selected checks are executed; unticked checks are not billed. Additional analyses use credits. Select the checks relevant to the question you are trying to answer rather than repeatedly launching broad work just to reduce a count.

If an observation is technically wrong, the finding detail offers Report a false positive. Use it to explain the contradiction in the evidence, not to hide a valid result you have decided to tolerate. A business decision to accept a minor exposure is not the same as a mistaken detection. Keep the rationale in your internal records. Neither a short To watch list nor its complete disappearance establishes that the rest of the application has no vulnerabilities.

Frequently asked questions

Was this article helpful?

Related articles