Docs Getting Started Quick Start

Quick Start

Get WNCYBER connected to your first identity source in under 15 minutes.

This guide walks you through connecting WNCYBER to your first identity source and verifying that the platform can see, classify, and govern identities in your environment.

Prerequisites

Before you begin, ensure you have:

  • An active WNCYBER tenant (request one at wncyber.com/company#contact)
  • Admin credentials for at least one identity source (Microsoft Entra ID, AWS IAM, or an on-premises Active Directory)
  • Network access from your environment to api.wncyber.com on port 443

Step 1 — Log in to the WNCYBER Console

Navigate to your tenant URL (provided in your welcome email). Sign in with your administrator credentials.

On first login, the setup wizard launches automatically. You can also access it later from Settings → Setup Wizard.

Step 2 — Connect Your First Identity Source

  1. From the dashboard, select Identities → Sources → Add Source
  2. Choose your identity provider from the list
  3. Follow the provider-specific connection guide (see Integrations for detailed steps)
  4. Grant the requested read permissions — WNCYBER requires read-only access to perform discovery

The initial sync begins automatically once the connection is saved. Discovery time depends on the size of your directory; most environments complete within 5–15 minutes.

Step 3 — Review Discovered Identities

Once sync completes, navigate to Identities → All Identities. You will see:

  • Human identities — user accounts from your connected directory
  • Machine identities — service accounts, managed identities, and application registrations
  • Unclassified — identities that need manual review or additional context

Click any identity to view its access rights, last activity, and risk score.

Step 4 — Enable Your First Policy

Navigate to Policies → Policy Library and enable the Dormant Account Detection policy. This policy flags accounts with no activity in the past 90 days — a common source of unnecessary access risk.

Configure the notification channel (email or webhook) and set the remediation action to Flag for Review.

Next Steps