Frequently Asked Questions

AURIX SHIELD is a security platform for detecting, investigating, verifying, and monitoring security issues across websites, software, and GitHub repositories.

Detect → Explain → Fix → Verify → Monitor.

AURIX SHIELD connects security detection with investigation, remediation, verification, and ongoing monitoring rather than treating a scan as the end of the process.

AURIX SHIELD is designed for developers, indie hackers and solo builders, startups, AI-assisted software builders, product teams, and businesses that need security visibility across websites and software.

No.

AURIX SHIELD is designed for websites, software, and GitHub repositories regardless of whether AI was involved in building them.

AI-assisted software development is an important part of the problem AURIX SHIELD is designed around, but the platform is not limited to AI-generated software.

AURIX SHIELD supports website security analysis and GitHub repository security analysis.

Website security includes web discovery, HTTP probing, vulnerability detection, and dynamic security analysis.

GitHub Security analyzes repositories using multiple specialized security engines.

The website security pipeline uses:

• Katana
• httpx
• Nuclei
• OWASP ZAP

Each engine contributes a different security-analysis capability.

GitHub Security uses:

• CodeQL
• Gitleaks
• Trivy
• OSV-Scanner
• AURIX Custom

Different engines detect different classes of security problems.

Different security problems require different analysis techniques.

A secret exposed in source code is different from a vulnerable dependency, filesystem issue, code-level vulnerability, or web application vulnerability.

AURIX SHIELD combines specialized engines so security findings can be understood in a broader security context.

A security finding represents a detected security issue together with its available security context and evidence.

Depending on the finding, that context can include severity, scanner, detection rule, repository, file, evidence, fingerprint, verification state, and historical state.

AURIX SHIELD connects the finding to investigation, remediation guidance, verification, and monitoring.

The goal is to preserve the connection between what was detected and what happens afterward.

AURIX SHIELD provides remediation guidance and verification workflows.

Users remain responsible for reviewing and applying appropriate changes.

Fix & Verify connects a finding to its remediation context and then verifies whether the original security condition is still detected.

The verification method depends on the original security engine and finding type.

For GitHub findings, verification depends on the original scanner engine.

Examples include:

• AURIX Custom → targeted verification
• Gitleaks → file-local verification
• OSV-Scanner → dependency/lockfile verification
• Trivy → filesystem verification
• CodeQL → repository-wide analysis

No.

AURIX AI can explain security information and help investigate findings, but an AI response is not itself a verification result.

Verification is performed through the appropriate AURIX SHIELD security verification workflow.

GitHub Security provides repository-focused security analysis using multiple specialized security engines.

Depending on the enabled security analysis, AURIX SHIELD may analyze repository information, source-code files, dependencies, secrets, code patterns, and other information required by the relevant security engine.

No.

AURIX SHIELD does not automatically commit code changes to GitHub repositories.

Users remain responsible for reviewing and applying changes.

Yes.

GitHub findings can use engine-specific verification workflows based on the original scanner.

Monitor tracks security state over time and helps identify changes and regressions after previous scans.

Software changes continuously.

New vulnerabilities can appear, previously resolved issues can return, and security conditions can change as websites, repositories, dependencies, and code evolve.

Monitoring connects security analysis to those changes.

No.

Monitoring works alongside security scanning and historical security analysis.

AURIX AI is the AI-assisted security intelligence layer inside AURIX SHIELD.

It helps users understand and investigate security information.

Ask AURIX is the conversational interface through which users can ask questions about available security context.

Depending on the finding, that context can include:

• Finding
• Severity
• Scanner
• Repository
• File
• Detection rule
• Evidence
• Verification information

No.

The Security Engine uses specialized security scanners to detect security issues.

Ask AURIX works with the resulting security information to help users understand and investigate it.

No.

Ask AURIX is an analysis and explanation interface.

It does not automatically commit code changes to GitHub repositories or automatically deploy changes to websites.

No.

Ask AURIX can explain available verification information, but the actual verification result comes from the appropriate AURIX SHIELD verification workflow.

Yes.

AURIX SHIELD provides Free and Pro plans.

The exact capabilities and limits should always follow the current Pricing page.

The Free plan provides access to a limited set of AURIX SHIELD security capabilities.

Refer users to the Pricing page for the current plan details and usage limits.

Pro provides expanded security capabilities for users who need deeper security analysis and more continuous security workflows.

Refer users to the current Pricing page for the exact capabilities and limits.

Plan capabilities and usage limits may change as the product evolves.

The current Pricing page should be treated as the source for current plan information.

No.

AURIX SHIELD does not claim to detect every possible vulnerability or guarantee complete security.

Security analysis provides evidence and security visibility, but users remain responsible for reviewing findings and applying appropriate remediation.

No.

Users are responsible for ensuring that they have appropriate authorization to scan websites, repositories, software, and other security targets they submit to AURIX SHIELD.

Users should avoid intentionally submitting passwords, private keys, API credentials, or other sensitive credentials unless a specific product workflow explicitly requires and supports that information.