> For the complete documentation index, see [llms.txt](https://docs.rad.security/llms.txt).
> Use it to discover all available pages before exploring further.

# Torq

Configure Torq integration with RAD Security for automated security workflows and ticket management.



This guide walks you through integrating Torq with RAD Security for no-code security automation, enabling you to automatically create, update, and manage security tickets while streamlining threat detection and response workflows.

Torq provides a no-code security automation platform that empowers SOC teams to mitigate alert fatigue, false positives, and staff burnout through AI-driven workflows.

## Prerequisites

Before you begin, ensure you have:

<Callout kind="success">
- Access to Torq with admin privileges
- Ability to generate API credentials (Client ID and Client Secret) in Torq
- Access to RAD Security workspace with integration permissions
</Callout>

<Callout kind="info">
**API Access Required:** This integration requires API access in your Torq subscription. Verify that your subscription level includes API capabilities.
</Callout>

---

## Step 1: Generate Torq API Credentials

<Steps>
  <Step title="Log in to Torq">
    Log in to your Torq account with administrator privileges
  </Step>

  <Step title="Navigate to API Settings">
    1. Go to your account settings or workspace settings
    2. Navigate to the **API** or **Integrations** section
  </Step>

  <Step title="Create API Credentials">
    1. Click **Create New Client** or **Generate API Key**
    2. Enter a name for the integration (e.g., "RAD Security Integration")
    3. **Copy the Client ID** that appears
    4. **Copy the Client Secret** that appears

    <Callout kind="alert">
    **Save these credentials immediately!** The Client Secret may only be displayed once. Store both values securely.
    </Callout>
  </Step>
</Steps>

<Callout kind="info">
Refer to [Torq's API documentation](https://torq.com/support) for detailed instructions on generating API credentials specific to your Torq version.
</Callout>

---

## Step 2: Configure in RAD Security

Navigate to your RAD Security workspace and configure the Torq integration with the following parameters:

### Required Parameters

| Parameter | Description | Example |
|-----------|-------------|---------|
| **Client ID** | The Client ID from Step 1 | `your-client-id-here` |
| **Client Secret** | The Client Secret from Step 1 | `your-client-secret-here` |

<Callout kind="info">
Custom field mappings can be configured after the initial connection is established, allowing you to map RAD Security fields to custom Torq fields (optionally scoped per project).
</Callout>

---

## Verify Integration

After completing the setup, verify your integration is working:

1. Navigate to **Data Sources > Integrations > Ticketing** in RAD Security
2. Locate your Torq integration
3. Check the connection status shows as **Connected**
4. Test by creating a sample ticket from RAD Security

<Callout kind="success">
Your Torq integration is now configured! RAD Security can now automatically create and manage security tickets in Torq.
</Callout>

## What Data is Synced

Once configured, RAD Security will sync the following with Torq:

<ExpandableGroup>
  <Expandable title="Ticket Creation" icon="ticket">
    - Automatically create Torq tickets for security incidents
    - Include detailed incident context and metadata
    - Attach relevant threat intelligence
    - Add affected assets and resources
    - Include remediation recommendations
  </Expandable>

  <Expandable title="Ticket Updates" icon="arrows-rotate">
    - Update ticket status in both systems
    - Sync comments and activity
    - Track resolution progress
    - Update priority and severity
    - Maintain audit trail
  </Expandable>

  <Expandable title="Custom Field Mapping" icon="sliders">
    - Map RAD Security fields to Torq fields
    - Configure custom field values
    - Set default ticket types
    - Define priority mappings
    - Configure per-project field mappings
  </Expandable>

  <Expandable title="Workflow Triggers" icon="diagram-project">
    - Trigger Torq workflows on ticket creation
    - Execute automated response actions
    - Initiate investigation playbooks
    - Route tickets to appropriate teams
    - Orchestrate multi-step remediation
  </Expandable>
</ExpandableGroup>

## Use Cases

<Columns cols={2}>
  <div>
  **Automated Incident Response**
    Automatically create Torq tickets when RAD Security detects threats, triggering automated response workflows.
  </div>

  <div>
  **Alert Triage Automation**
    Automatically prioritize and route high-volume alerts to appropriate teams through Torq workflows.
  </div>

  <div>
  **No-Code Orchestration**
    Leverage Torq's no-code workflows to orchestrate complex security responses based on RAD Security detections.
  </div>

  <div>
  **Compliance Tracking**
    Track compliance issues and remediation efforts through Torq's ticketing and reporting capabilities.
  </div>
</Columns>

## Troubleshooting

<ExpandableGroup>
  <Expandable title="Authentication Failed" icon="triangle-exclamation">
    **Possible causes:**
    - Client ID is incorrect
    - Client Secret is incorrect or expired
    - API credentials were revoked
    - Insufficient permissions on the API client

    **Solution:**
    - Verify Client ID is copied correctly (no extra spaces)
    - Check that Client Secret is copied correctly
    - Regenerate API credentials in Torq if needed
    - Ensure the API client has necessary permissions
    - Test credentials using Torq's API testing tools
  </Expandable>

  <Expandable title="Connection Failed" icon="plug-circle-xmark">
    **Possible causes:**
    - Torq API endpoint is unreachable
    - Network connectivity issues
    - Firewall blocking API requests
    - Torq service outage

    **Solution:**
    - Verify Torq service status
    - Check network connectivity from RAD Security
    - Review firewall rules
    - Whitelist RAD Security IP addresses if needed
    - Contact Torq support if service appears down
  </Expandable>

  <Expandable title="Tickets Not Creating" icon="ticket-slash">
    **Possible causes:**
    - API client lacks ticket creation permissions
    - Custom field mappings are incorrect
    - Required fields are missing
    - Workflow configuration issues

    **Solution:**
    - Verify API client has ticket creation permissions
    - Review custom field mappings
    - Check that all required fields are mapped
    - Test ticket creation manually in Torq
    - Review RAD Security integration logs for errors
  </Expandable>

  <Expandable title="Field Mapping Issues" icon="sliders">
    **Possible causes:**
    - Custom fields don't exist in Torq
    - Field types don't match
    - Invalid field values
    - Project-specific field restrictions

    **Solution:**
    - Verify custom fields exist in Torq
    - Check field type compatibility
    - Validate field value formats
    - Review project-specific field requirements
    - Update field mappings in RAD Security
  </Expandable>

  <Expandable title="Workflow Not Triggering" icon="diagram-project">
    **Possible causes:**
    - Workflow disabled in Torq
    - Trigger conditions not met
    - Workflow configuration errors
    - API client lacks workflow execution permissions

    **Solution:**
    - Verify workflow is enabled in Torq
    - Check workflow trigger conditions
    - Review workflow configuration
    - Ensure API client has workflow permissions
    - Test workflow manually in Torq
    - Check Torq workflow execution logs
  </Expandable>
</ExpandableGroup>

## Security Best Practices

<Columns cols={2}>
  <div>
  **Rotate Credentials Regularly**
    Periodically regenerate Client ID and Client Secret as part of your security hygiene practices.
  </div>

  <div>
  **Least Privilege Access**
    Only grant the minimum API permissions required for ticket management and workflow execution.
  </div>

  <div>
  **Secure Credential Storage**
    Store API credentials in a secure password manager or secrets vault. Never commit them to version control.
  </div>

  <div>
  **Monitor API Activity**
    Regularly review API usage in Torq to detect anomalous activity or unauthorized access.
  </div>

  <div>
  **Audit Integration Activity**
    Periodically review tickets created by the integration to ensure proper operation.
  </div>

  <div>
  **Test Workflows**
    Regularly test automated workflows to ensure they function as expected when triggered by RAD Security.
  </div>
</Columns>

## Additional Resources

<Columns cols={2}>
  <Card title="Torq Documentation" icon="book" href="https://torq.com/support" >
    Official Torq support and documentation
  </Card>

  <Card title="Torq API Documentation" icon="code" href="https://torq.com/support" >
    Learn about Torq's API capabilities and endpoints
  </Card>
</Columns>

## Next Steps

<Columns cols={2}>
  <Card title="Ticketing Overview" icon="ticket" href="/rad-security/integrations/ticketing/overview" >
    Learn about other ticketing integrations
  </Card>

  <Card title="Jira Cloud" icon="jira" href="/rad-security/integrations/ticketing/jira-cloud-setup" >
    Add Jira Cloud for additional ticket management
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/rad-security/platform/workspace" >
    Configure custom workflows for incident response
  </Card>

  <Card title="Alerts & Incidents" icon="bell" href="/rad-security/platform/workspace" >
    Set up alert rules that trigger Torq ticket creation
  </Card>
</Columns>