Nova AI-Native Autonomous Cloud Defense Platform
BY HANSEC

Understand source health and data freshness

Use connection status, last successful collection, expected delay, and coverage together before trusting a result.

Health and freshness answer different questions

Source health tells you whether the connection can complete its expected work. Freshness tells you how old the latest successful evidence is. A connection can be reachable while evidence is delayed, and old evidence can remain visible after a connection fails.

Expected timing varies by provider and evidence type. Judge freshness against the agreed collection interval, not one universal time limit.

Review these details together

  • Current connection state and the time it last changed.
  • Last successful collection and the expected next collection.
  • Included scope, skipped records, partial results, and provider limits.
  • Whether downstream findings and views show the same freshness warning.
  • Who owns the connection and the approved escalation path.

When a source is unhealthy

Record when the problem began, the affected scope, the last known good collection, recent provider or credential changes, and the visible error without including secrets. Treat decisions that depend on the missing evidence as partial until the connection and coverage are verified again.

Need help with your account or deployment?

Contact Hansec Support without including passwords, codes, keys, tokens, or complete customer evidence.

Contact support

Evaluate Nova

See how Nova fits your security needs.

Bring the cloud environments, security tools, and workflows you want to evaluate. We will review the supported connections and show you how Nova can help with your priorities.

Request a private demo