Skip to main content

Getting Started

This guide walks you through activating The One Security module and completing first-time setup.

Prerequisites​

  • An active Hub organization
  • Owner or Admin role in Hub
  • A GitHub account (required only for the Application Security / vulnerability scanning module)

First-Time Setup Wizard​

When you first navigate to app.theonesecurity.app and sign in via Hub SSO, you are taken to the three-step onboarding wizard.

Step 1: Connect GitHub​

Install the The One Security GitHub App on your organization. This grants read access to your repositories so the vulnerability scanner can inventory dependencies, detect exposed secrets, and run DAST scans against your endpoints.

  1. Click Connect GitHub
  2. The GitHub App installation page opens in a new tab
  3. Select the GitHub organization or repositories to grant access
  4. Return to the wizard and click Done — I've installed the app
ℹ️GitHub connection is required for the Application Security (AppSec) and dependency scanning modules. You can skip to Step 2 if you are only activating the User Protection, SIEM, or GRC modules.

Step 2: Add Platforms​

Add each application you want to monitor. For each platform you provide:

FieldDescription
NameHuman-readable name (e.g., "Customer Portal")
GitHub Repoowner/repo format
CriticalityCritical / High / Medium / Low — affects alert priority
Target URLBase URL for DAST scanning
DomainsComma-separated list of domains in scope

You can add multiple platforms before moving to Step 3.

Step 3: Run First Scan​

Click Trigger Scan to kick off your first vulnerability scan across all added platforms. The scan orchestrator launches a Docker container (ZAP + Nuclei) in Azure Container Instances.

Scan results appear on the Vulnerabilities page within 5–15 minutes depending on platform size.

Key Concepts​

Organization vs Tenant​

Your organization is your MSP's Hub account. Each tenant is one of your managed clients. Security data (vulnerabilities, SAT results, dark web findings, compliance posture) is isolated per tenant.

Managed Users​

Managed users are your clients' end-users. They are the targets for:

  • Security Awareness Training campaigns
  • Phishing simulations
  • Dark web breach monitoring

Add them manually, import via CSV, or sync from a connected M365 tenant.

Scan Profiles​

Scan profiles define the scope and depth of vulnerability scans:

  • Full — Comprehensive scan of all endpoints and dependencies
  • Quick — Surface-level scan, faster results
  • Targeted — Specific IP range or host
  • Custom — User-defined scope

Policy Templates​

GRC policy templates (CIS preset, MSP preset, custom) define the compliance baseline applied to connected M365 tenants and assessed during compliance assessments.

Suggested First Steps​

  1. Sign in at app.theonesecurity.app via Hub SSO
  2. Complete the onboarding wizard (Connect GitHub → Add Platforms → Run First Scan)
  3. Navigate to SecOps → SaaS Posture → connect your first M365 tenant
  4. Navigate to SecOps → Dark Web Monitoring → add managed user emails
  5. Navigate to SAT → Training Campaigns → create your first awareness training campaign
  6. Navigate to Email Security → DMARC Reports → add your sending domains
💡The Security Command Center (/secops) is your daily driver — it shows critical alerts, open incidents, active threat hunts, and dark web exposures on one screen.