Quickstart
Getting started with Tenurex
This guide walks you through installing the Tenurex CLI, connecting your first integration, and running your first control scan. Estimated time: 20–30 minutes.
Prerequisites
- Node.js 18+ or curl (for CLI install)
- A Tenurex account (request access at tenureq.com/contact)
- A GitHub organization with org admin access (for this guide)
- Your Tenurex API token from the dashboard
Install the Tenurex CLI
Install the CLI via npm or via curl:
npmTerminal
# Install via npm (Node.js 18+)
npm install -g @tenurex/cli
# Or install via curl
curl -fsSL https://cli.tenureq.com/install.sh | sh
# Verify installation
tenurex --version
tenurex-cli/1.4.2 linux-x64 node-v18.20.0
Initialize and authenticate
ShellTerminal
# Initialize a Tenurex workspace in your current directory
tenurex init
# You'll be prompted for your API token
? Enter your Tenurex API token: tnx_live_xxxxxxxxxxxx
✓ Authenticated as [email protected]
✓ Workspace initialized: .tenurex/
Connect your first integration (GitHub)
Generate a read-only GitHub token with read:org and repo:read scopes, then connect:
ShellTerminal
# Connect GitHub — you'll be prompted for your token
tenurex connect github --org=mycompany
? Enter your GitHub read-only token: ghp_xxxxxxxxxxxx
✓ Connected: github/mycompany
✓ Read-only access verified
✓ Permissions: read:org, read:repo (confirmed minimal scope)
Run your first control scan
ShellTerminal
# Run a SOC 2 control scan against all connected integrations
tenurex scan --framework=soc2
# Output:
✓ Scanning github/mycompany...
CC6.1 Logical access PASS (branch protection: enabled)
CC6.2 Access provisioning PASS (PR approval required: yes)
CC6.3 Access removal WARN (2 stale members detected)
CC8.1 Change management PASS (signed commits: enforced)
Scan complete. 3 PASS, 1 WARN, 0 FAIL
Evidence stored: .tenurex/evidence/2026-06-17T14:32:01Z/
View results in dashboard
After your first scan, log in to app.tenureq.com to see your control status dashboard, review drift alerts, and generate evidence packages.
Next steps
- Explore the API reference to automate evidence exports
- Connect additional integrations — AWS IAM, Okta, Jira
- Review SOC 2 TSC coverage to see all controls being monitored