> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rad.security/llms.txt
> Use this file to discover all available pages before exploring further.

# Torq

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

# Torq Integration Setup

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:

<Check>
  * 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
</Check>

<Info>
  **API Access Required:** This integration requires API access in your Torq subscription. Verify that your subscription level includes API capabilities.
</Info>

***

## 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

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

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

***

## 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` |

<Note>
  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).
</Note>

***

## 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

<Check>
  Your Torq integration is now configured! RAD Security can now automatically create and manage security tickets in Torq.
</Check>

## What Data is Synced

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

<AccordionGroup>
  <Accordion 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
  </Accordion>

  <Accordion 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
  </Accordion>

  <Accordion 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
  </Accordion>

  <Accordion 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
  </Accordion>
</AccordionGroup>

## Use Cases

<CardGroup cols={2}>
  <Card title="Automated Incident Response" icon="wand-magic-sparkles">
    Automatically create Torq tickets when RAD Security detects threats, triggering automated response workflows.
  </Card>

  <Card title="Alert Triage Automation" icon="filter">
    Automatically prioritize and route high-volume alerts to appropriate teams through Torq workflows.
  </Card>

  <Card title="No-Code Orchestration" icon="diagram-project">
    Leverage Torq's no-code workflows to orchestrate complex security responses based on RAD Security detections.
  </Card>

  <Card title="Compliance Tracking" icon="file-check">
    Track compliance issues and remediation efforts through Torq's ticketing and reporting capabilities.
  </Card>
</CardGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion 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
  </Accordion>

  <Accordion 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
  </Accordion>

  <Accordion 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
  </Accordion>

  <Accordion 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
  </Accordion>

  <Accordion 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
  </Accordion>
</AccordionGroup>

## Security Best Practices

<CardGroup cols={2}>
  <Card title="Rotate Credentials Regularly" icon="rotate">
    Periodically regenerate Client ID and Client Secret as part of your security hygiene practices.
  </Card>

  <Card title="Least Privilege Access" icon="shield-halved">
    Only grant the minimum API permissions required for ticket management and workflow execution.
  </Card>

  <Card title="Secure Credential Storage" icon="lock">
    Store API credentials in a secure password manager or secrets vault. Never commit them to version control.
  </Card>

  <Card title="Monitor API Activity" icon="chart-line">
    Regularly review API usage in Torq to detect anomalous activity or unauthorized access.
  </Card>

  <Card title="Audit Integration Activity" icon="clipboard-list">
    Periodically review tickets created by the integration to ensure proper operation.
  </Card>

  <Card title="Test Workflows" icon="flask">
    Regularly test automated workflows to ensure they function as expected when triggered by RAD Security.
  </Card>
</CardGroup>

## Additional Resources

<CardGroup 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>
</CardGroup>

## Next Steps

<CardGroup 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>
</CardGroup>