AI-Powered Security Intelligence for Your Security Findings

AURIX AI is the intelligence layer inside AURIX SHIELD that helps users understand security findings, investigate issues, and work with security context using natural language.

Instead of requiring users to interpret scanner output on their own, AURIX AI provides a conversational interface around the security information already collected by AURIX SHIELD. Its purpose is simple:

Understand security findings, explain what they mean, and help users reason about what to do next.

AURIX AI is the AI-powered security intelligence layer of AURIX SHIELD. It connects conversational AI with the security context generated by the platform. That context can include information such as:

• Security findings
• Finding severity
• Scanner engine
• Repository
• File
• Detection rule
• Evidence
• Finding status
• Verification information

This allows users to ask questions about security findings without manually collecting information from multiple parts of the dashboard. The primary user-facing interface for AURIX AI is Ask AURIX. Ask AURIX provides a conversational way to investigate security information.

A user can ask questions about a finding, repository, file, scanner, or security issue and receive an explanation based on the security context available to AURIX SHIELD. The goal is not simply to provide generic cybersecurity answers. The goal is to make the AI understand the security data already present in the user's AURIX SHIELD workspace.

Security Context

AURIX AI works with structured security context rather than relying only on the user's natural-language question. Depending on the request, the context can include:

• Finding information
• Repository information
• File information
• Scanner information
• Security evidence
• Finding metadata
• Verification information

This context helps AURIX AI connect a user's question with the actual security issue being investigated. For example, instead of asking a generic question about a type of vulnerability, a user can ask about a specific finding associated with a particular repository or file.

Finding-Aware AI

AURIX AI can work directly with security findings. When a finding is available as context, the AI can use information such as:

• Finding identity
• Severity
• Scanner
• Repository
• File
• Rule ID
• Evidence
• Verification state

This allows the conversation to remain connected to the actual security issue. The AI therefore acts as an intelligence layer around the platform's security findings rather than as an isolated general-purpose chatbot.

GitHub Security Context

AURIX AI can work with GitHub security findings. GitHub findings can contain repository-specific information such as:

• Repository
• File
• Scanner engine
• Finding
• Evidence
• Rule identifier

Ask AURIX can retrieve and use this information when answering questions about GitHub security findings. This allows users to investigate repository security findings through the same conversational interface used for other AURIX SHIELD security information.

Website Security Context

AURIX AI can also work with Website Security findings. Website findings can provide security context such as:

• Target
• Finding
• Scanner
• Evidence
• Severity
• Status

This allows users to ask questions about issues discovered during website security scans. AURIX AI can therefore provide a common conversational interface across both major AURIX SHIELD security environments.

How AURIX AI Works

The simplified workflow is: Question → Security Context → AI Analysis → Explanation

1. Question

The user asks a security-related question through Ask AURIX. AURIX SHIELD identifies relevant security information available to the authenticated user. AURIX AI uses the available context to analyze the question. The response is presented conversationally so the user can understand the relevant security issue and its context.

AURIX AI can retrieve security information based on the context of the request. This can include finding-related context from:

• Website Security
• GitHub Security

For GitHub findings, the system can use repository-specific finding information. This helps ensure that an AI response is connected to the correct security data rather than unrelated findings from another repository or user.

Security Boundaries

Security context is tied to the authenticated user's workspace. AURIX AI should only operate on security information that the authenticated user is authorized to access. This is particularly important for GitHub findings because repositories and findings can belong to different users and security contexts.

AURIX SHIELD therefore performs authenticated access and ownership checks when retrieving security information for AI workflows.

Ask AURIX and Finding Investigation

AURIX AI is particularly useful during finding investigation. A typical workflow can be: Finding → Ask AURIX → Understand → Investigate → Fix → Verify For example, a user can start with a finding in the Findings interface and use its context to understand what was detected and why it matters.

The AI can then help explain the security context without requiring the user to manually reconstruct the information from multiple dashboard screens.

Ask AURIX and Fix & Verify

AURIX AI and Fix & Verify serve different roles. AURIX AI helps users understand and reason about security findings. Fix & Verify handles the remediation and verification workflow. The two systems work together as part of the broader AURIX SHIELD lifecycle:

• Detect
• Explain
• Fix
• Verify
• Monitor

AURIX AI therefore provides intelligence around the finding while the verification system determines whether the original detection remains present.

Ask AURIX Does Not Automatically Commit Code

AURIX AI is an analysis and explanation layer. Ask AURIX does not automatically commit code changes to a GitHub repository. Users remain responsible for reviewing and applying code changes or remediation actions. This distinction keeps conversational security analysis separate from repository modification.

AI Responses and Security Findings

AURIX AI responses are based on the security context available to the system. The quality and relevance of an answer therefore depend on the information available for the finding or target being investigated.

For this reason, AURIX AI should be understood as an intelligence layer around security data, not as an independent source of truth about every possible security issue. When investigating a specific finding, the underlying scanner result and finding data remain important sources of technical evidence.

AURIX AI and the Security Engine

The Security Engine is responsible for detection. AURIX AI is responsible for helping users understand and investigate the resulting security information. The relationship can be represented as: Security Engine → Findings → AURIX AI The Security Engine produces security findings from specialized scanners. Those findings become structured security data.

AURIX AI can then use that information to provide conversational security analysis.

AURIX AI and GitHub Security

GitHub Security provides the repository security interface. AURIX AI provides the conversational intelligence layer around that security information. Together they allow users to:

• View repository findings
• Inspect finding context
• Ask questions about findings
• Understand scanner results
• Investigate security issues

This creates a connected experience between automated scanning and AI-assisted investigation. The same principle applies to Website Security. Website scanners identify security issues. Those issues become persistent findings. AURIX AI can then use the available finding context to help users understand those findings.

This creates a common intelligence layer across different security targets.

AURIX AI and Finding Search

Ask AURIX can work with finding context involving information such as: This makes it possible to narrow an investigation to the relevant security context instead of treating every security finding as unrelated. For GitHub findings, repository and file context can be particularly important when investigating source-code security issues.

AURIX AI Quotas and Usage

AURIX SHIELD applies account-level controls to AURIX AI usage. The platform distinguishes between short-term request rate limiting and account usage quotas. A temporary rate limit can require the user to wait before making another request. A usage quota can limit further requests after the account's available allowance has been reached.

The exact limits depend on the user's AURIX SHIELD plan and current product configuration.

Free and Pro Access

AURIX AI is integrated into the AURIX SHIELD plan structure. The platform supports Free and Pro plans. The availability and limits of AI usage can differ between plans. Because product limits can change, users should refer to the current Pricing documentation for the latest plan information.

Privacy and Workspace Context

AURIX AI operates on security information available within the user's authenticated AURIX SHIELD context. Security findings and repository information are not treated as a single global pool of data. Access to security context is subject to authentication and ownership checks.

This is important when working with private GitHub repositories and user-specific security findings.

What AURIX AI Does Not Do

AURIX AI does not replace the underlying security scanners. It does not guarantee that a target is secure. It does not automatically commit code changes to GitHub repositories. It does not replace verification performed by the appropriate security engine. It does not turn an AI response into proof that a security finding has been fixed.

The underlying security engines and verification workflows remain responsible for detection and verification.

AURIX AI Terminology

AURIX AI

The AI-powered security intelligence layer inside AURIX SHIELD.

Ask AURIX

The conversational interface used to interact with AURIX AI.

Security Context

The structured security information made available to AURIX AI for a request.

Finding Context

The specific security information associated with a finding, such as repository, file, scanner, evidence, and severity.

AI Analysis

The process of using available security context to understand and respond to a user's security question.

Workspace

The authenticated user's security environment containing their authorized AURIX SHIELD data.

Frequently Asked Questions

Explore AURIX SHIELD

Learn how AURIX AI connects with the rest of the platform:

• Product Documentation
• Security Engine
• GitHub Security
• Scan
• Fix
• Monitor
• Ask AURIX
• Pricing