Overview
OpsRabbit supports customer-hosted deployments. Security responsibilities are divided among the OpsRabbit provider, the customer and customer-selected service providers. The OpsRabbit provider is responsible for product controls and secure implementation guidance. The customer is responsible for its infrastructure, identities, approved data sources, provider configuration and operational authorization.
Some controls require both parties to perform responsibilities and retain evidence. The applicable agreement and deployment-specific responsibility record take precedence where they establish more specific requirements.
How to use this matrix
- OpsRabbit provider responsibility identifies the product control, documentation or support provided with OpsRabbit.
- Customer responsibility identifies controls operated or approved within the customer environment.
- Expected evidence identifies the artifact a security reviewer should expect to confirm the control.
- Customer-selected cloud, identity, model and integration providers may operate supporting controls under their respective agreements.
- A product capability does not replace customer configuration or operational monitoring.
Detailed Shared Responsibility Matrix
| Control area | OpsRabbit provider responsibility | Customer responsibility | Expected evidence |
|---|---|---|---|
| AI governance | Maintain responsible-AI policies, the AI governance process, product risk assessments, documented limitations and appropriate product review. | Approve the business use case, authorized users, acceptable operational authority and customer risk acceptance. | Approved use case, risk assessment and authorization record. |
| Cloud account and tenancy | Provide supported infrastructure requirements, deployment guidance and versioned deployment artifacts. | Own and secure the cloud account, subscription, project, cluster, hosts and deployment environment. | Approved architecture and deployment record. |
| Network security | Document required ports, endpoints, protocols and recommended network restrictions. | Configure ingress, egress, firewall rules, WAF, DNS, private connectivity, segmentation and network monitoring. | Network flow, approved allowlist and security configuration. |
| Application release | Provide versioned OpsRabbit deployment packages and identifiable release artifacts. | Review, approve and deploy releases into the customer-controlled environment. | Release manifest, approval and deployment record. Do not claim that every image is immutable unless that is currently verified. |
| Identity and access management | Provide product role-based access controls and supported enterprise identity integration. | Configure the identity provider, users, groups, authentication requirements and joiner-mover-leaver process. | Identity configuration, role mapping and access review. |
| Service identities | Document required permissions and support workload identity where available. | Create and govern least-privilege service accounts, tokens and workload identities. | Service-identity and permission inventory. |
| Secrets and credentials | Protect managed secret values, restrict their exposure to models and users, and support secure Connection-based credential handling. | Provision, scope, rotate and revoke customer-issued credentials and protect the applicable encryption keys or secret-management service. | Secret inventory without secret values, rotation record and access configuration. |
| Data sources and integrations | Use approved connectors, apply product authorization controls and minimize task context. | Authorize the systems, environments, fields, accounts, actions and access levels made available to OpsRabbit. | Approved connector and data-source register. |
| Model endpoint | Document supported model-integration behavior, context handling and product safeguards. | Select and approve the model provider, endpoint, region, credentials, retention settings and contractual terms. | Approved model and endpoint record. |
| Model and provider data use | Do not use customer inputs or outputs to train shared or proprietary foundation models. Disclose any provider appointed by the OpsRabbit provider that processes customer data. | Review and configure the selected model provider’s retention, training, data-use and regional settings. | Responsible AI Policy, provider terms and deployment configuration. |
| Human approval | Provide approval mechanisms, policy constraints and safe product defaults for sensitive actions. | Identify authorized approvers and define the actions, environments and risk levels requiring approval. | Approval matrix and approval records. |
| Production actions | Maintain a read-only default posture and prevent state-changing activity outside approved capabilities, tools and Connections. | Do not grant write or destructive access unless it is explicitly approved, scoped and monitored. | Tool and action inventory, access configuration and control test. |
| Prompt injection and untrusted content | Apply trusted-instruction separation, constrained tools, validation, least privilege and relevant security testing. | Restrict untrusted sources and review integrations that can introduce externally controlled content. | Threat model and prompt-injection test results. |
| Data leakage prevention | Bound model context, restrict secret exposure, maintain resource authorization and apply supported redaction safeguards. | Configure network egress, data classification, DLP and additional redaction controls where required. | Data-flow review and data-leakage testing. |
| Retention and deletion | Document product retention behavior and provide supported deletion or configuration mechanisms for provider-controlled data. | Define and operate retention and deletion for customer databases, logs, backups and customer-selected providers. | Approved retention schedule and configuration. |
| Audit logging | Generate application, user, agent, model, tool-call, approval, error and security-relevant audit events supported by the product. | Collect, protect, retain and review the logs generated within the customer-hosted environment. | Logging configuration and sample logging verification. |
| Monitoring and alerting | Provide applicable product health information and support investigation of product-related events. | Operate infrastructure and security monitoring, configure alert routing, integrate relevant events with the customer’s SIEM, and maintain on-call response. | Monitoring dashboard, alert configuration, SIEM integration evidence and escalation contacts. Keep “Audit logging” and “Monitoring and alerting” as separate rows. Do not combine them. |
| Backup and recovery | Document application consistency, configuration and recovery considerations for OpsRabbit components. | Configure backups, encryption, recovery procedures, restore testing, recovery point objectives and recovery time objectives for the customer-hosted environment. | Backup configuration, recovery plan and restore-test record. |
| Vulnerability management | Assess and remediate vulnerabilities affecting OpsRabbit product code, images and dependencies under its control. | Assess and patch the customer cloud environment, cluster, operating systems, network and supporting platform. | Scan results, remediation records and applicable exception approvals. |
| Penetration testing | Maintain available independent VAPT evidence and remediation status for the OpsRabbit product. | Approve the scope and authorization required for testing performed in the customer environment. | Customer-safe assessment summary or completion certificate and remediation closure evidence. Do not publish exploit details or sensitive penetration-test findings. |
| Privacy and data protection | Process customer data according to documented instructions, protect provider-controlled customer data and support applicable contractual privacy obligations. | Determine the processing purpose, lawful basis, notices, data-subject request process and any customer-specific regulatory obligations. | Data Processing Addendum, privacy review and deployment data-flow record. |
| Incident response | Investigate product or AI security incidents affecting provider-controlled components and notify the customer according to the applicable agreement and law. | Lead containment and recovery for the customer environment, preserve relevant evidence and make customer regulatory-notification decisions. | Incident record, communication record and corrective-action tracking. |
| Support access | Use named, authorized, time-bounded and least-privilege support access, and record relevant activity. | Approve, provision, monitor and revoke access to customer-controlled environments. | Support-access approval and access logs. |
| Deployment exit and offboarding | Return or delete provider-controlled customer data as required and confirm removal of provider-controlled access. | Revoke customer accounts and credentials, remove customer-hosted workloads and integrations, and manage deletion or retention of databases, logs and backups. | Offboarding checklist, credential-revocation evidence and deletion confirmation where applicable. |
Deployment responsibility record
Each customer deployment should record these items. Responsibilities should be assigned to named roles or teams and should not be left implied.
- Hosting architecture, cloud account and region
- Identity provider and approved administrators and users
- Authorized integrations and data sources
- Model provider and endpoint
- Credential ownership and rotation
- Read and write capabilities and human-approval requirements
- Log collection and monitoring ownership
- Retention and deletion settings
- Backup and recovery objectives
- Incident contacts and evidence-sharing process
- Offboarding requirements
Important responsibility principles
- Approval cannot grant an agent authority that its configured tools, roles or Connections do not already permit.
- Customer-hosted deployment does not transfer responsibility for OpsRabbit product security to the customer.
- Product logging does not replace customer log collection, monitoring, alerting or retention.
- OpsRabbit documentation does not replace the customer's assessment of customer-selected cloud, identity, model or integration providers.
- Unassigned controls remain deployment risks.
- Contractual terms and deployment-specific agreements take precedence over this public summary.