How to Set Up an Others Target

Last updated: June 23, 2026

Introduction

This guide walks you through setting up an Others Target in Astra. Use this target type when your application does not fit into standard categories such as Web Apps, APIs, Mobile Apps, or Cloud Infrastructure.

Others Targets support applications such as:

  • Chrome Extensions

  • Desktop Applications

  • Office Add-ins

  • Slack or Microsoft Teams Applications

  • Source Code Reviews

  • Web3 Applications

  • Smart Contracts

  • Other custom software requiring manual security assessment

Once configured, the target will be prepared for Astra's security assessment process.

Before You Begin

Ensure you have the following information available:

Mandatory

  • Application name

  • Business name

  • Access URL, download link, repository link, or source code package

  • Installation or setup instructions (if applicable)

Optional

  • Test credentials

  • Documentation links

  • Environment configuration details

  • Additional testing notes

Instructions

Step 1: Access the Target Setup Wizard

  1. Log in to your Astra Dashboard.

  2. Navigate to Targets.

  3. Locate your verified target under Pending Setup.

  4. Click Setup Target.

The setup wizard will open.

Step 2: Enter Basic Information

Provide the following details:

Application Name

Enter a descriptive name for the application.

Example:

Chrome Password Manager Extension

Business Name

Enter your company or organization name.

This information appears in reports and certificates generated by Astra.

Step 3: Select the Application Type

Choose the category that best matches your application.

Available options include:

Chrome Extension

Browser extensions developed for Chrome or Chromium-based browsers.

Desktop Application

Applications installed on Windows, macOS, or Linux.

Office Add-in

Extensions that integrate with Microsoft Office products.

Source Code

Applications submitted for source code review.

Slack / Microsoft Teams App

Bots, integrations, or collaboration platform applications.

Others

Web3 applications, smart contracts, browser plugins, proprietary software, or any custom application type.

Step 4: Provide Application-Specific Details

The required fields vary based on the selected application type.

Chrome Extension

Provide:

  • Chrome Web Store URL or hosted extension URL

  • Source code package (ZIP)

  • Test credentials (if authentication is required)

Example:

Extension URL:
https://chrome.google.com/webstore/...

Source Code:
extension-source.zip

Click Complete Setup after providing the required information.

Desktop Application

Provide:

  • Operating system (Windows, macOS, Linux)

  • Download link

  • Installation package

  • Test credentials (if applicable)

Example:

Platform: Windows
Download Link:
https://downloads.example.com/setup.exe

Click Save & Continue.

Office Add-in

Provide:

  • Add-in URL

  • Documentation link

  • Test credentials (if required)

Click Save & Continue.

Source Code Review

Provide either:

  • Repository URL

or

  • Source code ZIP archive

Examples:

https://github.com/company/project

or

project-source.zip

Click Save & Continue.

Slack / Microsoft Teams Application

Provide:

  • Application URL

  • Installation instructions

  • Test credentials (if applicable)

Click Save & Continue.

Others (Web3 Applications, Smart Contracts, Custom Software)

Provide:

  • Application URL (if available)

  • Documentation URL

  • Setup instructions

  • Additional notes

Examples include:

  • Decentralized Applications (dApps)

  • Smart Contracts

  • Browser Plugins

  • Proprietary Enterprise Software

Click Complete Setup.

Step 5: Add Installation and Setup Instructions

For applications that require installation or environment configuration, provide detailed instructions.

Recommended information includes:

Documentation Link

Share official documentation or internal setup guides.

Installation Steps

Example:

  1. Download the installer.

  2. Install the application.

  3. Configure environment variables.

  4. Enable required permissions.

  5. Log in using provided credentials.

Environment Dependencies

Include:

  • API keys

  • Third-party integrations

  • Required browser settings

  • Database setup requirements

Providing clear instructions helps Astra's security engineers begin testing without delays.

Step 6: Complete Setup

Review all submitted information and click Complete Setup.

Once completed:

  • The target moves to the Active Targets section.

  • Astra's team reviews the submitted information.

  • Security testing can begin based on your subscription and assessment schedule.

Troubleshooting

I do not see the Others Target option

Ensure the target has been successfully verified and is currently listed under Pending Setup.

My application requires custom installation

Provide detailed setup instructions and supporting documentation links in the setup wizard.

My application is not publicly accessible

Upload the required files, installation packages, source code, or provide secure access instructions.

I need to update information after setup

Navigate to the target settings page and update the target details, or contact Astra Support for assistance.

Best Practices

  • Provide test accounts with sufficient permissions.

  • Share source code whenever possible.

  • Include setup documentation for complex environments.

  • Use non-production environments whenever feasible.

  • Clearly document any limitations, dependencies, or required integrations.

Following these recommendations helps reduce onboarding delays and improves testing coverage.

Need Help?

If you encounter issues during setup, contact Astra Support through the dashboard support portal or email help@getastra.com.