Overview
This document summarizes the organizational, technical and operational safeguards used to protect OpsRabbit and customer information. The applicable control set depends on the agreed architecture, enabled capabilities and allocation of responsibilities.
It begins with the overall control boundary, then describes access, engineering, data protection, monitoring, resilience and supplier safeguards.
Control scope
OpsRabbit supports customer-hosted and customer-controlled deployment patterns. Controls are allocated among the OpsRabbit provider, the customer and customer-selected cloud, identity, model and integration providers. The applicable agreement and architecture take precedence.
Organizational safeguards
- Security and AI governance responsibilities are assigned and reviewed.
- Personnel access is role-based and limited to approved support or operational needs.
- Security, privacy, secure-AI and incident-reporting training is required for relevant personnel.
- Third parties are reviewed before receiving customer data or privileged access.
Technical safeguards
- Authentication and authorization integrate with customer-controlled identity patterns where configured.
- Credentials are handled through managed connections or secret-management facilities and are not intended to be placed in prompts.
- Encryption in transit is required; encryption at rest depends on the customer-hosted platform and selected services.
- Agent and tool access is least-privilege, policy-constrained and auditable.
- Logging covers user, agent, model, tool-call, approval, error and security-relevant events.
- Secure-development practices include peer review, dependency and vulnerability management, testing and controlled changes.
Resilience and response
- Backups, recovery objectives and platform resilience are shared with the customer in customer-hosted deployments.
- Security and privacy incidents follow documented triage, containment, investigation, remediation and communication processes.
- Independent penetration testing and remediation evidence are maintained; detailed results are controlled.
Identity and access management
Administrative and support access under OpsRabbit provider’s control is uniquely assigned, approved for a documented purpose, limited by role, and removed when no longer required. Shared credentials are prohibited where individual accountability is feasible. Customer users, service accounts and integration tokens are provisioned and revoked by the customer in customer-hosted deployments. Privileged access must use strong authentication supported by the selected platform and be reviewed periodically.
Asset, configuration and change management
OpsRabbit provider identifies product components, repositories, dependencies and release artifacts under its control. Changes are reviewed, tested and traceable to an authorized request. Security-impacting changes to models, prompts, agents, skills, integrations or tool permissions require proportionate risk review and regression testing. Emergency changes are documented and reviewed after implementation.
Secure development and vulnerability management
Product development uses peer review, separation of duties appropriate to team size, dependency and secret checks, security testing and controlled release practices. Vulnerabilities are triaged by exploitability, exposure, data impact and operational consequence. Remediation is prioritized by risk; compensating controls may be used when immediate correction is not practicable. Independent testing evidence is shared in customer-safe form, while raw findings remain restricted.
Data protection and cryptography
Data collection is limited to the approved operational purpose. Data in transit must use current secure protocols. At-rest encryption, key custody, backup protection and database security inherit controls from the customer-selected hosting environment unless OpsRabbit provider operates the relevant component. Secrets are stored through approved secret-management or connection mechanisms. Production customer content must not be copied into development or demonstration environments without written approval and protective controls.
Logging, monitoring and incident response
OpsRabbit records security-relevant product activity needed to establish who initiated an action, what evidence and policy applied, which model or tool was involved, whether approval was requested, and the resulting status. Customers are responsible for collection, retention, alerting and SIEM integration in their hosted environment. Suspected incidents are handled under the Incident Response Plan and the public notification summary.
Supplier, personnel and physical controls
OpsRabbit provider assesses third parties before granting access to customer data or privileged environments and contractually addresses confidentiality, security and processing obligations. Personnel receive appropriate training and are subject to confidentiality requirements. Physical and environmental controls for customer-hosted infrastructure are the responsibility of the customer and its hosting providers; OpsRabbit provider relies on approved workspace and device safeguards for the systems it controls.
Evidence and exceptions
Evidence may include policies, risk assessments, access reviews, training records, change records, testing results, incident records and customer-safe independent-assessment summaries. Exceptions require a documented owner, reason, risk assessment, compensating control, approval and expiration or review date.