AI Terms | AURIX SHIELD

Effective Date: September 28, 2026

1. Overview

AURIX SHIELD includes AI-assisted functionality under the name AURIX AI, which includes Ask AURIX.

These AI features are designed to help users understand, investigate, and work with security information generated by AURIX SHIELD.

The AI features are part of the AURIX SHIELD Service and are subject to our Terms of Service and Privacy Policy.

2. What AURIX AI Does

AURIX AI may help users:

Understand security findings
Investigate security issues
Explain technical security evidence
Summarize relevant security context
Answer questions about findings
Reason about available security information
Provide security-oriented explanations
Help users understand verification results
Provide contextual assistance around Website Security and GitHub Security

3. Ask AURIX

Ask AURIX is an AI-assisted interface that can use relevant security context from the user's AURIX SHIELD data.

Depending on the request and feature, context may include a finding, severity, scanner engine, rule ID, target, repository, file, evidence, verification information, finding state, or scan context. The AI may use this information to produce a contextual answer.

4. AI Output is Assistance

AURIX AI output is provided as assistance and information.

It is not a security guarantee, a formal security certification, a penetration-test certification, a legal opinion, a compliance certification, a replacement for professional security review, or proof that a system is secure.

AI responses may be incomplete, inaccurate, outdated, or inappropriate for a particular environment. Users are responsible for reviewing AI-generated information before acting on it.

5. AI Does Not Replace Security Engines

AURIX SHIELD's security engines perform security analysis. AURIX AI helps explain and investigate relevant security information.

Examples of underlying security engines may include Katana, httpx, Nuclei, and OWASP ZAP for Website Security, or CodeQL, Gitleaks, Trivy, OSV-Scanner, and AURIX Custom for GitHub Security.

6. AI and Verification

AI explanations must not be confused with Fix & Verify verification results.

AURIX SHIELD's verification system may use engine-specific verification methods (e.g., AURIX Custom for targeted verification, Gitleaks for file-local verification, OSV for lockfile/dependency verification, Trivy for filesystem verification, CodeQL for repository-wide analysis).

AURIX AI may explain a verification result, but an AI response itself is NOT a verification result.

7. User Responsibility

Users are responsible for:

Reviewing AI responses
Checking technical recommendations
Deciding whether to apply suggested changes
Ensuring actions are authorized
Ensuring actions comply with applicable law
Validating security changes in their own environment

AURIX SHIELD does not automatically take responsibility for actions performed by a user based on AI output.

8. Prohibited AI Use

Users must not intentionally use AURIX AI to:

Facilitate unauthorized access
Compromise systems
Steal credentials
Steal secrets
Deploy malware
Bypass authentication
Bypass authorization
Evade security controls
Attack third-party systems without authorization
Abuse AURIX SHIELD infrastructure
Circumvent platform restrictions

For more information, please review our Acceptable Use Policy.

9. User Input

Users may provide prompts, questions, and other information when using AURIX AI. Users are responsible for ensuring they are authorized to submit the information.

Do not intentionally submit passwords, private keys, API credentials, authentication tokens, or confidential third-party information unless a specific AURIX SHIELD feature explicitly requires and supports such information.

Where security analysis naturally contains sensitive information, users must have authorization to process it.

10. AI Processing of Security Context

AURIX AI may process relevant AURIX SHIELD security context to generate a response. Depending on the feature and request, this may include security findings, scanner information, repository information, file information, rule information, evidence, verification information, monitoring/security context, and user questions.

For more information on processing, please refer to the Privacy Policy and the Data Processing Agreement.

11. AI Providers / Third-Party Processing

If AURIX SHIELD uses third-party AI infrastructure, relevant information may be processed by those providers as necessary to provide the AI feature.

12. Accuracy and Limitations

AI systems can produce incorrect explanations, incomplete answers, incorrect assumptions, irrelevant suggestions, or inconsistent responses. Security-related AI output can be especially sensitive because software environments differ.

Users should validate important recommendations against the actual code, actual configuration, actual security findings, actual verification results, and appropriate security testing.

13. Security Decisions

AURIX AI does not make security decisions on behalf of the user.

The user remains responsible for decisions involving remediation, deployment, access control, credentials, production systems, security architecture, compliance, and incident response. AI suggestions should be reviewed before implementation.

14. AI-Generated Code or Configuration

If AURIX AI provides code, configuration, commands, queries, or technical suggestions, users must review them, test them appropriately, and are responsible for determining whether they are safe for their environment.

15. Confidentiality and Security Data

AURIX AI may process security-related information supplied through the Service. Users should avoid submitting unnecessary confidential information.

Where security findings naturally contain sensitive technical information, AURIX AI may need relevant context to answer the user's question.

Reference the Privacy Policy and DPA.

16. AI Availability

AURIX AI availability may depend on Service availability, AI infrastructure, account/plan access, quotas or rate limits, and technical conditions.

17. AI Plan Access

AURIX AI functionality may differ between Free and Pro plans. The exact availability, quotas, or capabilities are determined by the current plan and product interface.

18. Intellectual Property

AURIX SHIELD's AI features, interface, software, branding, documentation, and proprietary systems remain subject to applicable intellectual-property rights.

Users retain their rights in information they provide, subject to the rights necessary to operate the Service.

19. Feedback

If users provide feedback about AURIX AI, AURIX SHIELD may use that feedback to improve the Service, subject to applicable law and the Privacy Policy.

20. Relationship to Other Policies

These AI Terms supplement the Terms of Service, Privacy Policy, Acceptable Use Policy, and Data Processing Agreement. Where applicable, those documents continue to govern the broader use of AURIX SHIELD.

21. Changes to AI Features

AURIX AI features may evolve over time. AURIX SHIELD may improve models, change AI functionality, add or remove capabilities, modify available context, change plan availability, or change technical implementation. Material changes to these Terms will be handled according to the applicable Terms of Service.

22. Changes to These AI Terms

These AI Terms may be updated when AI functionality changes, the Service changes, legal requirements change, or privacy/security practices change. Material changes will be communicated where required. The effective date will be updated when changes are made.