Documentation

Core Security Workflow

Detect

A security engine analyzes a configured website or GitHub repository using the appropriate security engines.

Explain

Scanner output becomes a structured security finding containing context such as severity, scanner, rule, target, repository, file, evidence, and status.

Fix

The developer investigates the finding and applies the required remediation to code, dependencies, configuration, or infrastructure.

Verify

AURIX SHIELD checks whether the original security condition is still detectable using the appropriate verification method.

Monitor

Subsequent scans are compared against persistent finding identity so that changes and regressions can be recognized.

This lifecycle is the foundation of AURIX SHIELD.

Security Engine

AURIX SHIELD uses specialized engines for different types of security analysis.

Website Security Components

Katana

web crawling and attack-surface discovery.

httpx

HTTP probing and reachable-target identification.

Nuclei

template-based vulnerability detection.

OWASP ZAP

dynamic web security testing.

GitHub Security Engines

CodeQL

semantic source-code analysis.

Gitleaks

exposed secret and credential detection.

Trivy

dependency and configuration-related security analysis.

OSV-Scanner

dependency vulnerability analysis using the Open Source Vulnerability database.

AURIX Custom

AURIX-specific security detection logic.

Different engines detect different categories of security conditions. Verification also depends on the underlying detection technology.

Findings

Findings are persistent security records created from scan results. A finding can contain information such as:

• Severity
• Title
• Scanner engine
• Rule identifier
• Fingerprint
• Target
• Repository
• File path
• Line information
• Technical evidence
• Current status

AURIX SHIELD uses finding identity and fingerprints to maintain continuity across scans. This allows the platform to distinguish between:

New findings

Newly discovered security conditions.

Existing findings

Conditions that remain present across scans.

Reappeared findings

Previously addressed conditions that appear again.

Resolved findings

Conditions that are no longer detected after appropriate verification.

Changed findings

Existing findings whose relevant security information has changed.

Website Security

Website Security focuses on externally reachable web targets. The workflow can include:

Discovery

Identify reachable URLs and endpoints through web crawling.

HTTP Probing

Evaluate reachable targets and understand their HTTP behavior.

Dynamic Security Testing

Perform dynamic analysis against discovered endpoints.

Vulnerability Detection

Identify supported vulnerability conditions through template-based detection.

Persistent Findings

Convert detected issues into findings that can be investigated and tracked.

A website scan therefore becomes part of the broader security lifecycle rather than simply producing a one-time report.

GitHub Security

GitHub Security extends AURIX SHIELD into the source-code and repository environment. Supported security analysis can cover:

• exposed secrets
• vulnerable dependencies
• insecure source-code patterns
• code-level security issues
• project-specific security conditions

GitHub findings can include repository, file, line, rule, scanner, severity, fingerprint, and evidence information where available.

The resulting findings are normalized into the same AURIX SHIELD findings workflow used throughout the product.

Fix & Verify

A change is not the same thing as proof that the security issue has been resolved. AURIX SHIELD separates remediation from verification.

Targeted Verification

Supported findings can be checked against the original security condition without necessarily running a complete security scan. For example, a supported HTTP security-header finding can be checked through a targeted HTTP request.

Repository-Wide Verification

Some source-code findings depend on relationships and data flow across a repository. These findings can require repository-wide CodeQL analysis.

Verification Results

Verification can determine whether:

• the original condition is no longer detected
• the original condition is still detected
• verification failed to complete reliably
• available evidence is insufficient for a definitive conclusion

Monitor

Monitor extends the security lifecycle beyond an individual scan.

AURIX SHIELD maintains historical security information so that changes can be recognized across subsequent scans. If a previously addressed security condition appears again, the platform can identify the change as a regression.

Detect → Fix → Verify → Monitor → Detect Again

This keeps security findings connected to the ongoing state of the software rather than allowing them to disappear after remediation.

Ask AURIX

Ask AURIX is the AI-assisted security investigation layer of AURIX SHIELD.

Depending on the finding, it can use available context such as:

• scanner information
• finding details
• severity
• technical evidence
• repository information
• affected file
• rule information
• vulnerability context

Ask AURIX can help investigate questions such as:

• What does this finding mean?
• Why is this security issue relevant?
• What does the associated vulnerability mean?
• Could this finding be a false positive given the available context?
• What kind of change could address the issue?
• How should the developer investigate the finding further?

Ask AURIX can provide explanations and remediation-oriented code guidance.

Ask AURIX does not autonomously commit changes to a user's GitHub repository.

The underlying scanner evidence remains the source of security evidence; AURIX AI operates as an intelligence and investigation layer on top of that information.

Dashboard

The AURIX SHIELD dashboard connects the major security workflows in one environment.

Overview

High-level security information and recent activity.

Scan

Initiate supported website and GitHub security scans and review scan information.

Monitor

View monitored security state and historical changes.

Findings

Work with persistent security findings.

Fix

Connect findings to remediation and verification.

Ask AURIX

Perform contextual AI-assisted security investigation.

GitHub Security

Work with repository-focused security analysis and findings.

These interfaces operate on connected security data rather than functioning as isolated tools.

Security Finding Lifecycle

AURIX SHIELD treats security as a lifecycle rather than a single scan event.

1. Detection: A security engine identifies a potential security issue.
2. Finding Creation: The scanner result is normalized into an AURIX SHIELD finding.
3. Investigation: The developer reviews the finding, evidence, and available security context.
4. Remediation: The developer applies the appropriate change.
5. Verification: AURIX SHIELD checks whether the original condition is still detectable.
6. Resolution: Sufficient verification evidence can allow the finding to move toward resolution.
7. Regression Detection: If the same condition appears again, AURIX SHIELD can identify the reappearance as a regression.

Free & Pro

AURIX SHIELD currently uses a Free and Pro product structure.

Free

The Free experience provides access to the platform with defined usage and entitlement limits. Ask AURIX usage is subject to configured AI quotas.

Pro

Pro provides expanded product access and higher configured usage allowances, including access to the premium AI model tier.

Exact limits and entitlements are maintained by the current product configuration and should be reviewed on the Pricing page rather than hardcoded into this documentation.

Who Is AURIX SHIELD For?

Developers

For developers who want security findings presented with actionable context rather than raw scanner output.

SaaS Builders

For people building websites, applications, and SaaS products who need security visibility across their software.

Engineering Teams

For teams working with multiple security engines and looking for a unified findings and verification workflow.

AI-Assisted Developers

For developers using AI-assisted development who want software and repository changes to remain subject to security scanning and verification workflows.

AURIX SHIELD does not assume that software is secure simply because it was generated, reviewed, or modified with AI assistance.

What AURIX SHIELD Does Not Do

AURIX SHIELD does not claim that:

• every security issue can be detected by a single scan
• every finding can be verified with the same method
• AI automatically fixes and commits code to GitHub
• every AI-generated line of code is automatically secure
• every scanner produces the same type of security evidence

Different security engines detect different conditions, and verification methods depend on the finding and underlying detection technology.

Product Terminology

Security Engine

The layer responsible for coordinating security analysis and processing scanner results.

Scanner Engine

An underlying security analysis tool used to detect a particular class of security conditions.

Finding

A persistent security record representing a detected security condition.

Finding Identity

The identity used to maintain continuity for a security condition across scans.

Fingerprint

A finding identifier used to associate the same security condition across scan results.

Targeted Verification

A focused verification check against the original security condition.

Repository-Wide Verification

Verification that analyzes broader repository context when required.

Regression

A security condition that reappears after previously being addressed or verified.

AURIX AI

The AI-assisted security intelligence layer used to investigate and explain available security context.

Frequently Asked Questions

What is AURIX SHIELD?

A security platform for detecting, investigating, verifying, and monitoring security issues across websites, software, and GitHub repositories.

What can AURIX SHIELD scan?

Website security targets and GitHub repositories using multiple specialized security engines.

Which security engines does AURIX SHIELD use?

Katana, httpx, Nuclei, and OWASP ZAP for website security workflows, plus CodeQL, Gitleaks, Trivy, OSV-Scanner, and AURIX Custom for GitHub security analysis.

What is Finding Identity?

The identity used to maintain continuity for a security condition across scans.

Does AURIX SHIELD automatically fix vulnerabilities?

No. It can provide remediation-oriented guidance and AI-generated code assistance, but the developer remains responsible for applying the change.

Does changing the code automatically resolve a finding?

No. A change does not by itself prove that the original security condition has disappeared.

What is Targeted Verification?

A focused security check against the original finding when the detection supports that approach.

Does every GitHub finding use the same verification method?

No. Verification depends on the detection engine and finding type.

What is Ask AURIX?

The AI-assisted security investigation layer of AURIX SHIELD.

Can Ask AURIX commit code to GitHub?

No. It provides explanations and code-generation assistance but does not autonomously commit repository changes.

What happens when a fixed finding appears again?

AURIX SHIELD can identify the reappearance as a regression.

Who is AURIX SHIELD designed for?

Developers, SaaS builders, and engineering teams who need security scanning, persistent findings, remediation workflows, verification, and ongoing security visibility.