Approved Tools
Purpose
This procedure is intended to provide guidance on the process for requesting approval to use AI tools within Rygen.
Scope
This procedure applies to all employees, contractors, and temporary workers at Rygen who use or have access to Rygen’s information assets.
This procedure applies to:
- Standalone AI tools and platforms
- AI tool extensions and plugins that process company data
This procedure does not apply to standard integrations used by approved AI tools (e.g., GitHub, Google Drive, Slack integrations within AI platforms) that are pre-configured by the vendor. These integrations fall under Rygen’s general Security Policy and Acceptable Use Policy.
Definitions
AI Tool: A tool that uses AI to process data or perform tasks.
Approved Tools
Tools approved for use are listed in the Approved AI Tools page along with instructions and requirements for their acceptable use. Employees are not required to request approval for tools in the Approved AI Tools list as long as they are able to comply with the requirements for each tool’s acceptable use.
New Tool Approval Request
If an AI tool has not been approved for use but is needed:
- Complete the AI Tool Request Form
- Submit the form to the Information Security Officer by emailing ai-admin@rygen.com
- Allow 5-10 business days for initial review
- Respond to any follow-up questions or requirements
- Await approval by the Information Security Officer before using the tool
Evaluation Criteria
New AI tools are reviewed and approved against the AI-016 Requirements for AI Tool Approval and the following:
- Business necessity and use case justification
- Security features and compliance capabilities
- Data privacy controls and opt-out options
- Data access scope and permissions requested
- Cost and licensing requirements
- Integration with existing systems
- Training requirements
The Information Security Officer reviews the vendor’s terms of service and data processing agreements.
Implementation
Once a new AI tool is approved:
- The Information Security Officer adds the tool to the Approved AI Tools List (AI-020.1) with its safe usage constraints and the sensitive company information the approval permits the tool to receive (Permitted data)
- The Information Security Officer documents the required configuration
- The tool’s administrator enables access, and the user receives setup instructions
- Any training identified in the approval is provided
Non-Compliance
Violations of this procedure are handled as AI-016 Non-Compliance sets.
Responsibilities
The Information Security Officer reviews this procedure and related policy, and they are approved as AI-006 sets. Supporting functions, departments, and staff members shall be responsible for implementing the relevant sections of the policy in their area of operation.
Review Schedule
This document shall be reviewed annually and whenever significant changes occur in the organization.
Revision History
| Version | Date | Author | Summary of Change |
|---|---|---|---|
| 1.0 | 2025-06-05 | Field Bradley | Initial draft. |
| 1.1 | 2025-09-02 | Field Bradley | Migrated to markdown and gitlab |
| 1.2 | 2025-11-04 | Field Bradley | Added Appendix for AI Tool Request Form |
| 1.3 | 2025-12-04 | Field Bradley | Added MCP connector requirements and updated scope |
| 1.4 | 2026-06-10 | Field Bradley | Removed MCP connector approval requirements (RFC) — MCP connectors are APIs accessed through already-approved AI tools and are covered by the tool’s approval; separate MCP approval added no real value |
| 1.5 | 2026-11-09 | Field Bradley | Names the Information Security Officer’s approvals, records permitted data in AI-020.1, takes the approval steps from AI-016, and removes checks that are not carried out (AI-2173, AI-2131). The Information Security Officer reviews vendor terms, and training is provided where the approval identifies it. The tool’s administrator enables access. |
Appendix
AI Tool Request Form
The blank form is the AI Tool Request Form.