Nova AI-Native Autonomous Cloud Defense Platform
BY HANSEC

Plan a new connection

Define the purpose, owner, scope, access, validation, and operating expectations before connecting a source.

Before you begin

Choose a business owner and a technical owner. State which Nova outcome needs the evidence, which environment is approved, and whether the connection is for evaluation or ongoing use.

Confirm the supported connection method with Hansec or your Nova administrator before creating access. Do not create broad credentials first and reduce them later.

Record the connection plan

  • Purpose and expected Nova views or outcomes.
  • Included accounts, subscriptions, projects, clusters, products, and regions.
  • Explicit exclusions and known blind spots.
  • Approved access method, owner, review date, and revocation path.
  • Expected evidence interval, initial collection window, and acceptable delay.
  • Validation records and the person who will confirm completeness.

Validate before relying on the connection

  • Confirm that the source reports a healthy state and a recent successful collection.
  • Compare a small approved sample with the provider source.
  • Check that included and excluded scopes behave as planned.
  • Confirm how the team will detect, own, and escalate a future connection failure.
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