Nova AI-Native Autonomous Cloud Defense Platform
BY HANSEC

Prepare for Nova onboarding

Bring the people, scope, access decisions, and support information needed for an orderly start.

Assign the right owners

Name one person who owns the onboarding outcome and one technical contact for each environment being connected. Include an identity or access owner, a security operations representative, and the person who can approve any future response capability.

Record how Hansec Support should reach the team during onboarding and who can make time-sensitive scope decisions.

Prepare the onboarding record

  • The customer and organization names that should appear in Nova.
  • The approved environment scope, including exclusions and data-location requirements.
  • The identity method and the people who need initial access.
  • The intended connections, their owners, and the earliest safe connection window.
  • The support severity path and the contacts who may discuss account or security matters.

Use the first days to prove the foundation

Confirm sign-in and account recovery before connecting production evidence. Then connect one approved scope, verify source health and freshness, and make sure the expected owners can reach the relevant views.

Do not treat a successful connection message as complete onboarding. Review what evidence arrived, what remains outside scope, and how the team will respond when a source becomes stale or unavailable.

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