Getting Started: How to Use Rezliant
Welcome to Rezliant, your all-in-one platform for finding and fixing security issues across your code, cloud infrastructure, and web applications. This guide walks you through everything you need to get up and running — from creating your account to shipping your first automated fix.
1. Getting Started / Onboarding
1.1 Create Your Account
- Go to the Rezliant sign-up page and fill in your organization name, first and last name, company email, and a password.
- Click Sign up.
Note: The Sign up button stays disabled until every field is filled in correctly. If nothing happens when you click it, double-check for any missed fields.
1.2 Verify Your Email
- After signing up, you'll be taken to a confirmation screen asking for a one-time code.
- Check your inbox for an email from Rezliant containing the code.
- Enter the code and click Confirm Code.
Tip: If the email doesn’t arrive within a minute or two, check your spam or junk folder.
1.3 Set Up Your Workspace
Once your email is verified and you log in for the first time, a setup wizard will guide you through configuration:
- Accept the terms of service and click Accept Terms.
- Select your company type: Startup, SME, or Enterprise.
- Choose your company size.
- Select your department (e.g., IT/Security, Engineering, Operations).
- Choose your main goal (e.g., Compliance, Risk Management).
Click Next after each step. These selections help personalize your experience but do not restrict functionality.
1.4 Take the Guided Tour
After setup, Rezliant provides a short walkthrough of the workspace. Click Next to proceed or Close to skip. Once complete, you’ll land on your dashboard.
2. Connecting Your First Repository
Before scanning, you need to connect a repository.
2.1 Open the Import Flow
- Click Repository in the sidebar.
- Click Connect → Add Repo.
- This opens the Import Git Repository page.
2.2 Choose a Provider and Account
- Select a provider (GitHub, GitLab, Azure DevOps, Bitbucket or AWS CodeCommit).
- Choose your account from the Source Account dropdown.
- If not connected, select Add new repo and complete the authorization flow.
- If already connected, simply select your account.
Note: Allow a few seconds for repositories to load after switching accounts.
2.3 Import Your Repository
- Search for your repository by name.
- Click Import.
- Add a description.
- Click Save & Continue.
Note: This button may be temporarily disabled while branches are being checked.
- Confirm branch and tech stack when prompted.
- Click Save & Continue again.
Your repository will now appear in the list.
2.4 Connect a Cloud Account (Optional)
To scan cloud infrastructure:
- Click Cloud → Connect Cloud.
- Choose a provider (AWS, Azure or Google Cloud Platform ).
- Enter credentials.
- Name the account and select an environment.
- Click Continue.
3. Running Your First Scan
A scan analyzes your systems for security risks.
Types of Scans
- Code Check – Scans source code and dependencies
- Cloud Check – Scans cloud infrastructure
- Web Check – Scans live web applications
3.1 Start a Scan
- Go to Repository or Cloud.
- Open the actions menu.
- Select Rescan or Force Full Rescan.
Tip:
- Use Rescan for quick checks
- Use Force Full Rescan after major changes
3.2 While the Scan Runs
Scans run automatically in the background and may take a few minutes depending on size and type.
3.3 When It’s Done
You’ll receive a “Scan completed successfully” notification. You can then view the results.
Note: Delays may be due to queue time.
4. Understanding Scan Results
4.1 What a Finding Includes
Each finding shows:
- What it is – Description of the issue
- Where it is – File, resource, or endpoint
- Severity – Critical, High, Medium, Low
- Details – Explanation and technical specifics
4.2 Severity Levels
- Critical/High – Fix immediately
- Medium – Address in normal cycles
- Low – Lower priority improvements
4.3 Reports
You can filter findings and export reports for sharing or compliance.
5. Fixing Issues with Maestro
5.1 What Maestro Does
Maestro is Rezliant’s remediation assistant that automatically generates fixes for supported issues.
5.2 Applying a Fix
- Open a finding
- Click Apply Fix
- Maestro generates a fix
- A pull request is created in your repo
5.3 Reviewing and Merging
Review the pull request as usual. Once merged, rerun a scan to confirm the fix.
Tip: Not all issues have automated fixes; manual guidance will still be provided.
6. Tips & Troubleshooting
Repository Won’t Connect
- Ensure authorization is completed
- Check for duplicate repository names
Scan Issues
- Allow time for queue processing
- Confirm the connection is still active
Permissions & Access
- Ensure correct workspace is selected
- Verify user roles (Admin vs Member)
- Re-login if session expires
Invitations
- Resend invites if emails are not received
- Avoid creating duplicate invites
You’re now ready to connect your first project, run scans, and resolve issues using Maestro. Use the dashboard to navigate between Code Check, Cloud Check, Web Check, and your fix history.
Shadow AI Risk Assessment Checklist
Your Complete Guide to Discovering Hidden AI Usage in Your Organization