Acceptable Use Policy | AURIX SHIELD

Effective Date: September 28, 2026

AURIX SHIELD is a security platform designed to help users analyze and monitor websites, software, and authorized GitHub repositories. The Service must only be used for legitimate, lawful, and authorized security purposes.

Users are responsible for ensuring that they have permission to analyze the websites, domains, repositories, systems, and data they submit to AURIX SHIELD. This policy supplements the Terms of Service.

1. Purpose

This policy exists to protect:

Users
Website owners
Repository owners
Third parties
AURIX SHIELD infrastructure
Security scanning infrastructure
The broader security ecosystem

The purpose is not to prevent legitimate security testing. AURIX SHIELD is intended to support authorized defensive security work.

2. Authorized Security Testing

Users may use AURIX SHIELD to analyze systems they:

Own
Operate
Administer
Are explicitly authorized to test
Have another legitimate legal basis to analyze

Examples of acceptable use:

Scanning your own website
Verifying a domain you are authorized to manage
Analyzing your own application
Analyzing an organization's application when authorized
Analyzing a GitHub repository you own or are authorized to access
Monitoring an authorized website
Investigating security findings on authorized systems
Verifying whether a previously detected issue remains present

Authorization is the user's responsibility. AURIX SHIELD does not grant permission to scan a target merely because the target can technically be submitted to the Service.

3. Domain Verification

Domain verification exists to help establish authorization/control over a website or domain before applicable security functionality is used.

Users must not:

Attempt to verify a domain they do not control or have authorization to manage
Bypass verification controls
Manipulate verification records
Use another person's verification information
Impersonate a domain owner
Attempt to obtain unauthorized access through verification mechanisms

Domain verification does not transfer domain ownership. Users remain responsible for ensuring that their verification activity is authorized. Depending on the verification method supported by the Service, specific technical checks will apply.

4. Website Security Scanning

Users must only scan websites and targets they are authorized to test.

Prohibited uses include:

Scanning third-party websites without authorization
Using scans to intentionally disrupt a website
Intentionally overwhelming a target with requests
Attempting to degrade availability
Using the Service as part of an attack
Using scanning functionality to gain unauthorized access
Repeatedly scanning a target after authorization has been revoked

Legitimate security analysis remains permitted when properly authorized. Note that no security scanning tool operates invisibly; users must recognize scanning activity interacts with the target system.

5. GitHub Security

Users must only connect and analyze repositories they are authorized to access and analyze. GitHub Security exists to help users analyze authorized repositories for security issues.

Prohibited uses include:

Connecting repositories without authorization
Using another person's GitHub authorization
Attempting to bypass GitHub permissions
Using AURIX SHIELD to obtain unauthorized source code
Using repository analysis to facilitate attacks against repository owners
Intentionally submitting repositories that the user has no right to analyze

6. Security Findings

Security findings generated by AURIX SHIELD must not be used as justification for unauthorized activity.

Users must not use findings to:

Threaten or extort another party
Facilitate unauthorized access
Intentionally exploit a third party
Distribute private security information without authorization
Expose sensitive information unnecessarily

Security findings should be handled responsibly and according to the user's authorization and applicable obligations.

7. Fix & Verify

Users may use Fix & Verify to determine whether authorized security findings remain present.

Users must not use verification functionality to:

Bypass security controls
Repeatedly probe unauthorized systems
Intentionally disrupt targets
Evade monitoring or access controls

Verification is intended to validate the status of authorized security findings.

8. Monitoring

Monitoring may only be used for authorized targets.

Users must not:

Monitor websites without authorization
Use monitoring to harass or disrupt a target
Create excessive monitoring activity intended to overload systems
Use monitoring to circumvent security controls

Users are responsible for ensuring that scheduled monitoring remains authorized over time.

9. AURIX AI / Ask AURIX

AURIX AI and Ask AURIX are intended for security explanation, investigation, and assistance.

Users must not intentionally use the AI features to:

Facilitate unauthorized access
Generate instructions for attacking systems without authorization
Bypass AURIX SHIELD security controls
Abuse the platform
Submit another person's confidential information without authorization

AURIX AI output should be reviewed by the user and does not itself authorize security testing or provide permission to act against a target.

10. Prohibited Security Abuse

Users must not use AURIX SHIELD to intentionally:

Gain unauthorized access to systems
Compromise accounts
Steal credentials
Steal secrets or private information
Deploy malware
Distribute malicious code
Conduct destructive attacks
Disrupt services
Conduct denial-of-service activity
Evade authentication
Bypass access controls
Bypass domain verification
Bypass GitHub permissions
Compromise infrastructure
Facilitate credential theft
Facilitate ransomware or extortion
Facilitate fraud
Attack third-party systems without authorization

11. Abuse of AURIX SHIELD Infrastructure

Users must not attempt to compromise, disrupt, overload, or interfere with AURIX SHIELD itself.

Prohibited activity includes:

Attacking AURIX SHIELD infrastructure
Attempting unauthorized access to internal systems
Bypassing authentication
Bypassing quotas or rate limits
Intentionally generating abusive traffic
Interfering with scanners or workers
Attempting to execute unauthorized code through the platform
Abusing APIs or application endpoints
Attempting to access another user's account or security data
Attempting to access internal secrets or credentials
Intentionally exploiting platform vulnerabilities for harmful purposes

Security researchers who discover a vulnerability should use the appropriate security contact: security@aurixshield.com

12. Credentials, Secrets, and Sensitive Information

Users must not intentionally submit:

Passwords
Private keys
API credentials
Authentication tokens
Secrets belonging to another person
Confidential information they are not authorized to process

This restriction applies unless the relevant AURIX SHIELD feature explicitly requires and supports that information.

Where security analysis naturally processes source code, dependency data, or detected secrets, users must have authorization to process that information. Please reference our Privacy Policy for data processing specifics.

13. Privacy and Third-Party Rights

Users must respect:

Privacy rights
Intellectual-property rights
Confidentiality obligations
Contractual restrictions
Access permissions
Applicable law

Users must not use AURIX SHIELD to intentionally expose another person's private information.

14. False or Misleading Use

Users must not:

Impersonate another person or organization
Falsely claim authorization to scan a target
Provide misleading ownership information for domain verification
Misrepresent repository ownership or access rights
Use AURIX SHIELD findings to make knowingly false claims about another organization

15. Evasion and Circumvention

Users must not attempt to circumvent:

Authentication
Authorization
Domain verification
Rate limits
Quotas
Account restrictions
Plan restrictions
Security controls
Monitoring controls
Other technical safeguards

16. Responsible Security Research

AURIX SHIELD supports legitimate defensive security research. Researchers using AURIX SHIELD should:

Only test authorized targets
Minimize unnecessary impact
Protect sensitive information
Avoid disrupting systems
Responsibly handle findings
Stop testing when authorization ends

If a user discovers a security issue in AURIX SHIELD itself, they should report it to: security@aurixshield.com

17. Enforcement

AURIX SHIELD may take reasonable action when it has reason to believe the Service is being abused or used in violation of the Terms or this policy.

Possible actions may include:

Warning the user
Limiting functionality
Suspending access
Terminating access
Investigating abuse
Preserving relevant information where legally permitted or required
Taking other reasonable measures necessary to protect the Service, users, or third parties

This policy applies in conjunction with our Terms of Service.

18. Reporting Abuse

Users can report suspected abuse or unauthorized use to:
abuse@aurixshield.com

For security vulnerabilities affecting AURIX SHIELD:
security@aurixshield.com

For privacy concerns:
privacy@aurixshield.com

For general inquiries:
contact@aurixshield.com

19. Relationship to Terms of Service

This Acceptable Use Policy forms part of or supplements the Terms of Service. If there is a conflict, the applicable Terms of Service and mandatory applicable law govern to the extent of that conflict.

20. Policy Changes

AURIX SHIELD may update this policy as the Service, security practices, or applicable requirements change. Material changes will be communicated where required. The effective date will be updated when changes are made.