Asset Statuses Explained

Asset Statuses Explained

Every asset in FortWatch has a status that reflects its current state. Understanding these statuses helps you know which assets are being monitored and which need attention.

Status Lifecycle

When an asset is first added, it moves through this lifecycle:

1. Pending — The asset has been submitted but the validation process has not yet started. This is a brief transitional state.
2. Validating — FortWatch is actively checking DNS, HTTP connectivity, and CDN detection. This typically takes 10-30 seconds.
3. Active — Validation succeeded. The asset is reachable and enrolled in scheduled scanning.

Error and Inactive States

• Failed — Initial validation did not succeed. Common causes include:
  • The domain does not resolve (DNS failure)
  • The IP address is not reachable
  • The server does not respond to HTTP requests
  If an asset fails validation, check that the domain or IP is correct and that the server is running. You can retry validation by removing and re-adding the asset.
• Inactive — The asset was previously active but failed a daily health check. This means the asset was reachable when first added but has since become unreachable. FortWatch will automatically reactivate it if a future health check succeeds.

Status Indicators

Asset statuses are shown throughout the FortWatch interface:

• In the asset list, each asset displays a colored status badge.
• On the dashboard, inactive or failed assets are flagged so you can address them.
• In project views, you can see the count of assets in each status.

Best Practices

• Regularly review failed and inactive assets to ensure your monitoring coverage is complete.
• If a domain is intentionally decommissioned, remove it from FortWatch to keep your asset list clean.
• Use projects to separate actively monitored assets from archived or deprecated ones.