AURIX SHIELD
AI Security for Websites, Software, and GitHub Repositories
AURIX SHIELD is a security platform for detecting, investigating, verifying, and monitoring security issues across websites, software, and GitHub repositories. It brings security scanning, persistent findings, remediation workflows, verification, monitoring, and AI-assisted security investigation into a single workspace.
The platform is built around a simple security lifecycle:
- Detect
- Explain
- Fix
- Verify
- Monitor
Instead of treating a scan as the end of the security process, AURIX SHIELD connects what was detected with the investigation, remediation, verification, and ongoing monitoring that follow.
Explore the visual AURIX SHIELD experience. AURIX SHIELD is designed to help developers understand and manage security issues across both externally accessible websites and source-code repositories. The platform combines multiple security engines and transforms their results into a unified findings workflow.
For website security, AURIX SHIELD uses a combination of web discovery, HTTP probing, dynamic security testing, and vulnerability detection. For GitHub repositories, it analyzes source code, secrets, dependencies, and other repository security signals through multiple specialized security engines.
The result is not simply a collection of scanner reports. AURIX SHIELD turns security output into persistent findings that can be investigated, fixed, verified, and monitored over time.
The Problem AURIX SHIELD Solves
Security tools often operate independently. One tool may discover a web vulnerability. Another may identify a vulnerable dependency. Another may detect a hardcoded secret inside a repository.
The developer is then left to connect those results, understand their relevance, determine what needs to change, and decide whether the issue has actually been resolved. This creates several practical problems.
Security Noise
Raw scanner output can contain large amounts of technical information without enough context for determining what requires attention first. Security detection, investigation, remediation, and verification can happen in separate tools and workflows.
Finding a problem is different from fixing it. A configuration change or code change does not automatically prove that the original security condition has disappeared. Without persistent finding identities, every new scan can become another collection of alerts instead of a continuing record of the same security conditions.
AURIX SHIELD connects these stages into one workflow.
How AURIX SHIELD Works
AURIX SHIELD follows a continuous security workflow. A scan analyzes a configured website or GitHub repository using the appropriate security engines. The scanning workflow depends on the target. Website security can include:
- web crawling and endpoint discovery
- HTTP probing
- dynamic security testing
- template-based vulnerability detection
GitHub security can include: Scanner output is transformed into structured security findings. Instead of requiring developers to work directly with raw scanner output, AURIX SHIELD associates the result with useful security context such as:
- severity
- scanner engine
- rule or finding identifier
- affected target
- repository
- file
- line information where available
- technical evidence
- finding status
Ask AURIX can then provide AI-assisted investigation using the available security context. The developer investigates the finding and applies the required remediation to the relevant code, dependency, configuration, or infrastructure.
AURIX SHIELD can provide remediation-oriented AI assistance, but the developer remains responsible for applying the actual change.
4. Verify
AURIX SHIELD separates changing something from proving that the security issue is gone. Where supported, the Fix & Verify workflow can perform a targeted verification against the original security condition.
For example, a supported website security finding involving an HTTP security header can be verified through a targeted HTTP request against the affected target.
GitHub verification depends on the underlying detection engine. Some findings can be evaluated against their original context, while findings that depend on broader source-code relationships can require repository-wide analysis.
5. Monitor
After a finding has been addressed, subsequent scans can be compared against its persistent identity. If a previously resolved or verified security condition appears again, AURIX SHIELD can identify the change as a regression. This allows security findings to remain part of an ongoing lifecycle instead of disappearing after remediation.
AURIX SHIELD Product Architecture
AURIX SHIELD is organized around several connected product areas. The security analysis and finding-processing layer. The interface for initiating security analysis against supported targets. The persistent security record used to track detected issues. The remediation and verification workflow. The historical and ongoing security monitoring layer.
The AI-assisted security investigation layer. The repository-focused security workflow. Together, these areas form a connected security lifecycle rather than isolated tools.
Security Engine
The Security Engine coordinates security analysis and turns scanner output into the structured security information used throughout AURIX SHIELD. AURIX SHIELD uses specialized security engines for different types of analysis.
Website Security Components
Katana
Used for web crawling and attack-surface discovery, helping identify reachable URLs and endpoints. Used for HTTP probing and identifying reachable web targets. Used for template-based vulnerability detection against web targets. Used as part of the dynamic web security testing workflow against discovered targets.
Provides semantic source-code analysis for supported repositories. CodeQL can identify security conditions that depend on relationships within the codebase rather than a single isolated line.
Gitleaks
Detects exposed secrets and credentials within repository content. Provides security analysis for supported dependency and configuration-related content. Checks supported project dependencies against the Open Source Vulnerability database.
Provides AURIX-specific security detection logic for conditions that are handled by the platform's own detection layer. Findings are the persistent security records created from scan results. A finding represents a security condition that AURIX SHIELD can track beyond the individual scan in which it was discovered.
Depending on the source, a finding can contain information such as:
- severity
- title
- scanner engine
- rule identifier
- fingerprint
- target
- repository
- file path
- line information
- technical evidence
- current status
This allows developers to investigate the security condition without having to repeatedly interpret raw scanner output. AURIX SHIELD uses finding identity and fingerprints to maintain continuity between scans.
When the same security condition appears again, the platform can associate it with its existing finding rather than treating every scan result as an entirely new issue. This allows the platform to distinguish changes such as:
- newly discovered findings
- existing findings
- reappeared findings
- resolved findings
- changed findings
The exact state of a finding is maintained by the product's security workflow. Website Security focuses on externally reachable web targets. The workflow combines several stages of web security analysis.
Discovery
The platform identifies reachable URLs and endpoints through web crawling. Reachable targets are evaluated to understand their HTTP behavior. The web security workflow can perform dynamic analysis against discovered endpoints. Template-based security detection identifies supported vulnerability conditions.
Detected issues are converted into findings that can be investigated and tracked. This means a website scan is not simply a one-time report. Its results become part of the broader AURIX SHIELD security workflow.
GitHub Security
GitHub Security extends AURIX SHIELD into the source-code and repository environment. Repositories can contain multiple categories of security risk, including:
- exposed secrets
- vulnerable dependencies
- insecure source-code patterns
- code-level security issues
- project-specific security conditions
AURIX SHIELD uses multiple engines to analyze these areas. The resulting findings are normalized into the AURIX SHIELD findings workflow so that developers can investigate them through the same product environment. GitHub findings can include repository, file, line, rule, scanner, severity, fingerprint, and evidence information where available.
Fix & Verify
Fix & Verify is designed around an important distinction: A developer may update a configuration, remove a secret, change source code, or update a dependency. The next question is whether the original security condition can still be detected. AURIX SHIELD uses verification to answer that question.
Targeted Verification
For supported findings, AURIX SHIELD can perform a focused verification against the original security condition. For example, a website security finding involving a missing HTTP security header can be verified by performing a targeted HTTP request against the affected URL and checking the relevant response.
This avoids requiring a complete security scan when a focused verification is sufficient.
Repository-Wide Verification
Some source-code security findings require broader context. CodeQL findings can depend on relationships and data flow across a repository. For these cases, verification may require repository-wide CodeQL analysis rather than checking only the original file.
Verification Results
Verification distinguishes between different outcomes rather than treating every verification attempt as a successful fix. A verification can establish that:
- 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
Read more about Fix & Verify 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 finding that was previously addressed appears again, the platform can identify the condition as a regression. This provides an important feedback loop: Detect → Fix → Verify → Monitor → Detect Again
If a previously resolved issue returns, it becomes visible again instead of being lost among unrelated scan results. Read more about Monitoring
Ask AURIX
Ask AURIX is the AI-assisted security investigation layer of AURIX SHIELD. It is designed to help developers understand security findings using the actual security context available in the product. Depending on the finding, that context can include:
- scanner information
- finding details
- severity
- technical evidence
- repository information
- affected file
- rule information
- vulnerability context
Ask AURIX can help developers investigate questions such as: Ask AURIX can generate explanations and remediation-oriented code guidance. It does not automatically commit changes to the user's GitHub repository.
The underlying security finding and scanner evidence remain the source of security evidence; AURIX AI provides an intelligence and investigation layer on top of that information.
Dashboard
The AURIX SHIELD dashboard brings the main security workflows into one environment. Provides a high-level view of security information and recent activity. Provides the interface for initiating supported website and GitHub security scans and reviewing scan information. Provides visibility into monitored security state and historical changes.
Provides the persistent security finding workspace. Connects findings to remediation and verification. Provides contextual AI-assisted security investigation. Provides repository-focused security workflows and findings. These interfaces are connected through the same underlying security data rather than functioning as isolated products.
Security Finding Lifecycle
AURIX SHIELD treats security as a lifecycle rather than a single scan event. A security engine identifies a potential security issue. The scanner result is normalized into an AURIX SHIELD finding. The developer reviews the finding, evidence, and available security context. Ask AURIX can be used to investigate the finding using that context.
The developer applies the appropriate change to the relevant code, dependency, configuration, or infrastructure. AURIX SHIELD checks whether the original security condition is still detectable using the appropriate verification method.
When verification provides sufficient evidence that the original condition is no longer detected, the finding can move toward resolution. If the same security condition appears again in a later scan, AURIX SHIELD can identify the reappearance as a regression. AURIX SHIELD currently uses a Free and Pro product structure.
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. The exact limits and entitlements are maintained by the current product configuration and are documented separately on the Pricing page.
Who Is AURIX SHIELD For?
AURIX SHIELD is designed for people building and maintaining software who need security information connected to their development workflow. For developers who want security findings presented with actionable context rather than raw scanner output.
For people building websites, applications, and SaaS products who need security visibility across their software. For teams working with multiple security engines and looking for a unified findings and verification workflow.
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 code is secure simply because it was generated, reviewed, or modified with AI assistance.
What AURIX SHIELD Does Not Do
Understanding the boundaries of the product is as important as understanding its capabilities. 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 types of conditions, and verification methods depend on the finding and its underlying detection technology. The platform is designed to bring these different security workflows into one environment while preserving the context and limitations of each detection method.
Product Terminology
Security Engine
The layer responsible for coordinating security analysis and processing scanner results into the AURIX SHIELD security workflow.
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 help associate the same security condition across scan results.
Targeted Verification
A focused verification check against the original security condition without necessarily performing an entire security scan.
Repository-Wide Verification
Verification that analyzes the broader repository when the detection depends on project-wide source-code context.
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?
AURIX SHIELD is a security platform for detecting, investigating, verifying, and monitoring security issues across websites, software, and GitHub repositories.
What can AURIX SHIELD scan?
AURIX SHIELD supports website security workflows and GitHub repository security analysis using multiple specialized security engines.
Which security engines does AURIX SHIELD use?
The current security workflow includes Katana, httpx, Nuclei, and OWASP ZAP for website security workflows, and CodeQL, Gitleaks, Trivy, OSV-Scanner, and AURIX Custom for GitHub security analysis.
What is Finding Identity?
Finding Identity allows AURIX SHIELD to maintain continuity for a security condition across multiple scans instead of treating every occurrence as an unrelated alert.
Does AURIX SHIELD automatically fix vulnerabilities?
No. AURIX SHIELD can provide remediation-oriented guidance and AI-generated code assistance, but the developer remains responsible for applying the actual change.
Does changing the code automatically resolve a finding?
No. A code or configuration change does not by itself prove that the original security condition has disappeared. Supported findings can go through the Fix & Verify workflow.
What is Targeted Verification?
Targeted Verification performs a focused security check against the original finding when the detection supports that approach. For example, a supported HTTP security-header finding can be checked through a targeted HTTP request.
Does every GitHub finding use the same verification method?
No. Verification depends on the underlying detection engine and finding type. Some findings can be evaluated against localized context, while source-code findings that depend on broader relationships can require repository-wide analysis.
What is Ask AURIX?
Ask AURIX is the AI-assisted security investigation layer of AURIX SHIELD. It uses available finding and security context to help developers understand and investigate security issues.
Can Ask AURIX commit code to GitHub?
No. Ask AURIX can provide explanations and code-generation assistance, but it does not autonomously commit changes to the user's repository.
What happens when a fixed finding appears again?
If a previously addressed security condition is detected again during a later scan, AURIX SHIELD can identify the reappearance as a regression.
Who is AURIX SHIELD designed for?
AURIX SHIELD is designed for developers, SaaS builders, and engineering teams who need security scanning, persistent findings, remediation workflows, verification, and ongoing security visibility.
Explore AURIX SHIELD
Continue exploring the individual parts of the platform: