Using the CLI with a Proxy
To configure the Mindgard CLI to use a proxy set the https_proxy environment variable e.g.
export https_proxy="https://username:password@proxy-host:port"
mindgard test
Mindgard does not support SOCKS proxies.
Deployment Topology
Mindgard deployments use a command-line client or Burp Suite extension running in the customer environment to interact with target applications’ API’s. Mindgard’s SaaS application devises attacks, assesses their efficacy, and aggregates test results for reporting.
Mindgard Instances
All Mindgard customers are assigned to an instance. Instances are deployed around the world to meet any requirements you might have regarding data residency. Using Mindgard requires specifying the instance name to your browser, Burp Suite extension and CLI.
Web browser
Your instance name is a subdomain of mindgard.ai. To get started visit:
https://<instance name>.mindgard.ai/ |
|---|
CLI
Login with your instance name to get started:
mindgard login --instance <instance name> |
|---|
Burp Suite Extension
| Configure Burp Suite with the same url used via web browser. |
|---|
Organizations & Teams
User management for your organization can be found in the user drawer in the bottom left corner of the Web UI.
SSO
SAML based authentication can be enabled on request for your organization. This allows your team to log into Mindgard using your corporate identity provider (IdP), such as Microsoft Entra (Active Directory), Okta, or Google Workspace.
Organizations with SSO setup can auto-enroll any users from their domain into your organization within Mindgard.
SSO is not presently user-configurable, so please contact support@mindgard.ai to enable this for your organization.
Custom Integrations
If you require an integration with a system beyond the capabilities of the webhooks detailed above, contact support to check if there is already an integration available or to prioritize it on our roadmap.
