What is Security Assistant for Integrations?

Security Assistant for Integrations is an AI skill that helps you configure complex integrations. It works by understanding your evidence requirements and then automatically generating the technical configuration code needed to collect data from your cloud systems and third-party tools.

Instead of manually researching API documentation or learning Terraform syntax, you can simply describe what evidence you need in plain English, and Security Assistant will generate the appropriate configuration for you.

This feature works with:

• Terraform integrations - Collect evidence from cloud providers like AWS, Azure, GCP, DigitalOcean, and version control systems like GitHub and GitLab, as well as other Terraform-based integrations

• Bridge integrations - Collect evidence from tools like ClickUp and ServiceNow using direct API calls

How Security Assistant Helps

Setting up advanced integrations usually requires an understanding of third-party API documentation, Terraform data source syntax, and proper query parameters. Security Assistant removes many of these technical barriers by:

• Understanding your requirements - Describe what evidence you need in plain language

• Generating optimal configurations - Creates properly formatted Terraform data blocks or API endpoints based on current documentation

• Enabling advanced capabilities - Automatically switches to Advanced Mode when needed, allowing for more sophisticated data collection

Using Security Assistant for Integrations

Security Assistant's integration skill is build right into the evidence collection flow. Before proceeding, ensure that you have at least one advanced integration(s) configured in the Integration Manager.

Step 1: Start the integration process

Navigate to the evidence item where you want to collect data, then:

1. Click Attach Directly or Automated Collection

2. Select the Terraform or Bridge integration you want to use

3. Look for the Use Security Assistant button in the configuration modal

Step 2: Describe your evidence needs

Click Use Security Assistant to open the prompt interface. The text box will show a placeholder example based on your integration type.

Describe what evidence you need in plain English. For example:

• "Show me encryption settings for all RDS databases"

• "List S3 buckets with public access enabled"

• "Get IAM user access keys older than 90 days"

• "Retrieve all completed security tickets from the past 30 days"

• "Get a list of admin users and their permissions"

• "Show me recent task assignments for the security team"

Security Assistant will optimistically generate the integration blocks for you, if possible, so be sure that you are clear about what data you want and that the data is actually available in the system you're targeting.

Step 3: Review the generated configuration

Security Assistant will analyze your request and generate the appropriate configuration. This may take up to 1-2 minutes.

Once Security Assistant is complete, it will auto populate the integration configuration settings (like the API route or Terraform data blocks).

For Terraform integrations, Security Assistant automatically switches to Advanced Mode and populates the code editor with the generated configuration. This gives you access to more powerful data collection capabilities while maintaining security controls.

Important: The generated code my require specific variables, like an ID value, instance name, etc, to properly execute. Look carefully for areas called out in the generated code where variables are needed.

Step 4: Refine if needed

If the generated configuration doesn't quite match what you need:

1. Enter a new prompt in the text box to provide additional details or corrections

2. Click Resubmit to generate an updated configuration

3. Security Assistant will update the configuration based on your clarification

You an also refine the generated configuration directly in the collection window.

Step 5: Execute the collection

Once you're satisfied with the generated configuration:

1. Review the code in the Advanced Mode editor (for Terraform) or the API parameters (for Bridge integrations)

2. Click Attach to execute the data collection

3. Strike Graph will collect the evidence based on the configuration

Tips for Better Results

Verify output

AI systems are not fool-proof, so be sure to verify any output from an AI system before using or executing the generated content. Security Assistant can make mistakes.

Be specific about your requirements

Instead of: "Get database information" Try: "Show encryption status for all RDS database instances in us-east-1"

Mention relevant filters

Include details about:

• Time ranges (e.g., "from the past 30 days")

• Status filters (e.g., "only completed tickets")

• Resource types (e.g., "S3 buckets with public access")

• Specific attributes (e.g., "encryption settings")

Provide context when needed

If your first attempt doesn't generate what you expected:

• Clarify what data you're looking for

• Specify which resource types or attributes are important

• Mention any constraints or filters that should apply

Troubleshooting

Security Assistant doesn't appear

Ensure your organization is current with a Scale or Enterprise plan to get access to this advanced Security Assistant skill. Contact your account administrator or Customer Success Manager if you don't see the "Use Security Assistant" button.

Generated code produces errors

If the generated configuration fails validation:

• Check the error message in the code editor

• The validation system prevents unsafe configurations (resource blocks, provider modifications)

• Refine your prompt to be more specific about what data you need

• Contact support if the generated code appears incorrect

Results don't match expectations

If the collected data isn't what you expected:

• Review the rationale provided by Security Assistant

• Check that your prompt clearly described the evidence requirements

• Try a more specific prompt with additional details

• Use a follow-up prompt to refine the configuration

Advanced Mode validation warnings

Real-time syntax validation helps catch errors before submission. Common issues include:

• Missing closing braces or brackets

• Invalid HCL syntax

• Attempting to use restricted configuration types (resources, providers)

The editor will highlight specific errors to help you resolve them.