Azure Repos
StackHawk’s official Azure Repos integration.
This feature is available on the StackHawk Enterprise plan.
Overview
The Azure Repos integration connects your repositories to StackHawk’s API Discovery feature. Once connected, StackHawk analyzes your codebase to identify APIs and web applications, giving you visibility into your attack surface.
The integration requires a Personal Access Token (PAT) with permissions to your Azure Repos workspace.
Features
- Identify testable APIs and web applications across your Azure Repos repositories
- View repository insights including detected frameworks and commit activity
- Create StackHawk applications directly from discovered repositories
- Connect repositories to existing StackHawk applications
Requirements
StackHawk
- A StackHawk account on the Enterprise plan
Azure Repos
- Login access to the Azure Repos workspace you want to connect
- Read permissions to repositories in your workspace
- Ability to create a Personal Access Token (PAT) with repository read access
Permissions
The Azure DevOps Personal Access Token requires the following scope:
Code -> Readfor the connected Azure Repos workspace
Set a token expiration that meets your organization’s security requirements. Azure DevOps allows tokens with up to 1 year expiration.
Installation
- Log into StackHawk and go to the Azure Repos Integration page.
- Click Connect Azure Repos.
- Enter your Azure DevOps organization name and Personal Access Token.
- The connection modal verifies your credentials and completes the setup.
Usage
Configuration
Configure Azure Repos on the Attack Surface screen. From there you can view discovered repositories and map them to StackHawk applications.
Connecting Multiple Organizations
To connect additional Azure DevOps organizations, click Connect Azure Repos on the integration page. Each connected organization appears in the list below.
Updating Personal Access Token
Azure DevOps Personal Access Tokens expire after 30 days by default (extendable to 1 year during creation). To update an expired token:
- Go to the Azure Repos Integration page.
- Click Manage for the organization.
- Click Update and enter the new token.
Removing the Integration
- Go to the Azure Repos Integration page.
- Click Manage for the organization you want to remove.
- Click Disconnect, then confirm by clicking Yes, Disconnect.
Troubleshooting
Repositories Not Showing in Attack Surface
Repository discovery can take several minutes for organizations with many repositories. A loading indicator displays on the Attack Surface screen while repositories are being processed.
Feedback
Have suggestions or feedback? Contact StackHawk Support.