aisecurity.llc
hello@aisecurity.llc
Commercial Agreement · Negotiation Draft
Acceptable Use and Scan Scope Terms
Allowed targets, authorization requirements, prohibited activity, customer responsibility, and safe testing boundaries.
1. Purpose
These terms define safe and authorized use of aisecurity.llc scanning, assessment, evidence, Academy, and SecEng capabilities.
2. Authorized Targets
Users may scan, test, analyze, or assess only targets they own or are authorized to test.
Authorized targets may include:
- owned repositories
- owned applications
- approved customer applications
- approved staging systems
- approved production systems
- approved AI workflows
- approved RAG configurations
- approved agentic workflows
- approved API specifications
- approved artifacts
- approved logs or traces
3. Prohibited Targets
Users may not scan or test:
- systems they do not own or control
- third-party systems without authorization
- public targets outside agreed scope
- production systems without approval
- systems where testing would violate law, contract, or policy
- systems where testing may cause harm without safeguards
4. Prohibited Activity
Users may not use aisecurity.llc capabilities to:
- conduct unauthorized attacks
- exploit vulnerabilities outside agreed scope
- exfiltrate data
- bypass access controls
- disrupt services
- evade monitoring
- create malware
- create phishing infrastructure
- violate laws or regulations
- harass, threaten, or harm others
- remove license controls
- bypass usage metering
- redistribute software without authorization
5. AI-Specific Restrictions
Users may not use aisecurity.llc capabilities to intentionally create or optimize harmful AI behavior outside legitimate testing and defensive research.
Testing must remain within authorized security review, product security, research, training, or governance purposes.
6. Customer Data
Users are responsible for ensuring they have authority to process any customer data, prompts, logs, traces, repositories, artifacts, or evidence submitted to or processed by the software.
7. Production Systems
Production testing should use appropriate safeguards:
- written authorization
- defined scope
- time windows where needed
- rate limits
- test accounts
- rollback plans
- monitoring
- customer contacts
- incident process
8. Partner Use
Partners are responsible for ensuring their customers understand and comply with acceptable use and scan scope restrictions.
OEM, MSSP, reseller, private-label, and white-label partners must not use the software outside approved commercial scope.
9. Evidence and Reports
Users must not misrepresent findings, evidence, reports, or risk scores.
Reports should preserve limitations, scan scope, methodology, and relevant disclaimers.
10. Suspension
aisecurity.llc may suspend access for suspected misuse, unauthorized scanning, license bypass, redistribution, security risk, non-payment, or material breach.
11. Reporting Misuse
Users and partners should report suspected misuse, credential compromise, unauthorized redistribution, unsafe findings, or security incidents promptly.