CybeDefend Configuration
| Field | Description | Example |
|---|---|---|
| Harbor URL | Full URL of your Harbor instance | https://harbor.example.com |
| Harbor Project | Name of the Harbor project | my-project |
| Robot Username | Robot account username | robot$my-project+deploy |
| Robot Token | Robot account token | ***** |
| Description | Optional description | Production Harbor Registry |
Required Robot Account Permissions
| Resource | Permission |
|---|---|
| Artifact | List, Read |
| Label | List, Read |
| Project | Read |
| Repository | List, Pull, Read |
| Tag | List |
How to Configure Harbor Container Registry
1
Access Harbor
Connect to your Harbor instance and navigate to your project
2
Create Robot Account
Go to Robot Accounts and create a new robot account with read access
3
Set Permissions
Configure the robot account permissions as listed above for scanning access
4
Copy Credentials
Copy the robot username (e.g.,
robot$project+name) and the generated token5
Configure CybeDefend
Enter your Harbor URL, project name, robot username, and token in CybeDefend
Security Best Practices
Use Robot Accounts
Prefer robot accounts over personal credentials for automated scanning.
Minimal Permissions
Grant only the required permissions listed above for security.
Set Expiration
Configure robot account expiration dates to limit exposure.
Use HTTPS
Always use TLS for Harbor connections to encrypt data in transit.
Troubleshooting
Authentication Failed
Authentication Failed
- Verify robot username format:
robot$project+name - Check if the robot account has expired
- Ensure the Harbor URL is correct
Permission Denied
Permission Denied
- Verify robot account has the required permissions
- Check project visibility settings