aisecurity.llc
AI Governance
AI usage, model-training, human-review, and customer-data boundaries for aisecurity.llc platform and service workflows.
We use AI to accelerate security engineering work, but not to replace authorization, human judgment, customer approval, or written engagement boundaries. Customer data is not used to train public AI models. Consequential outputs such as findings, reports, attestations, and claim language require human review.
AI governance snapshot
- AI assists scoping, packet generation, drafting, analysis, triage, and reporting where enabled.
- Security testing, agent actions, and production access still require explicit written authorization.
- Confidential evidence and customer artifacts are handled under the applicable NDA, SOW, DPA, ROE, or evidence terms.
- SecEng Copilot, packet generation, report drafting, integrations, and platform workflows are governed by feature permissions, customer configuration, and applicable agreements.
- Customers can request AI-free or restricted processing for certain professional services where available and agreed in writing; availability may depend on the feature, workflow, and engagement scope.
Core commitments
Authorization before testing
AI features do not authorize access or testing. Security testing still requires explicit written scope and, where applicable, Rules of Engagement.
No public model training on customer content
Customer content submitted through approved business or API pathways is not used to train public AI models or our own public AI systems.
Human review for consequential outputs
Findings, reports, attestations, claim language, and customer-facing evidence require human review before release.
Evidence minimization and redaction
We minimize, redact, and scope evidence where appropriate and handle confidential materials under the applicable agreement path.
Scoped AI assistance
SecEng Copilot and other AI features may assist with scoping, drafting, analysis, and workflow guidance only within the enabled feature and permissions.
Customer controls and restricted processing
Customers can choose scoped agreement paths, request AI-free or restricted processing where available, and manage users and integrations where supported.
AI governance documents
Responsible AI Principles
Operational principles for authorization, human accountability, evidence minimization, restricted processing, and abuse prevention.
Customer Data & Model Training
Clear statement on customer data, uploaded artifacts, model providers, AI-free paths, and human review for consequential outputs.
AI Usage Policy
How aisecurity.llc uses AI in research, platform operations, and customer work, including review requirements and prohibited uses.
Terms of Service
The contract surface for public website use, self-service purchases, scoping workflows, and order-of-precedence rules.
Privacy Policy
What data we collect, how we use it, retention basics, subprocessors, and controls for platform and procurement workflows.
Subprocessors
Current third-party providers, including AI model providers and feature-specific processors where enabled.
Evidence Handling Policy
How packets, evidence, logs, traces, screenshots, redaction, and publication boundaries are handled.
Related policies
Why this page exists
Buyers and security reviewers need a concise map of how AI is used, what data boundaries apply, and which documents govern customer-facing use cases. This hub points to the operational policy pages that answer those questions without making the site harder to read than it needs to be.