​
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="http://username:password@proxy-host:port"
mindgard test
n.b. Mindgard does not currently support SOCKS proxies.

​
Typical Deployment Topology

A typical SaaS deployment involves the CLI or an always-on broker running in the customer environment to interact with the target model/application APIs. Mindgard SaaS application devises attacks, assesses their efficacy, and aggregates test results for reporting.

​
Single Tenant or Regional Deployments

Customers who have purchased a plan with a region specific or single tenant deployment must access Mindgard via their instance endpoint.

​
Web

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>
If you are not sure what your instance name is then contact support@mindgard.ai.

​
Organizations & Teams

Organization user management can be found in the user drawer top right corner.

​
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.