Security Policy

CamberCloud protects customer data and AI workloads with layered technical and organizational controls. These controls cover least-privilege access, encryption, managed execution, network boundaries, monitoring, and incident response. This policy also explains the security boundaries for agents that use code, notebooks, data, credentials, and external tools.

For current compliance information, monitored controls, and subprocessors, visit the CamberCloud Trust Center.

1. Security and Compliance

1.1 Security Ownership

CamberCloud maintains an information security program for the confidentiality, integrity, and availability of systems and customer data. Security roles are assigned to appropriate personnel. Management reviews the program and supporting policies at least annually.

Personnel are required to follow applicable security and confidentiality requirements. Access is removed when it is no longer required, including as part of personnel offboarding.

1.2 Compliance Assurance

The public CamberCloud Trust Center currently lists SOC 2 Type II. It also lists:

• AWS Foundational Technical Review
• HIPAA
• NIST 800-171 Rev. 2

The Trust Center is the source of truth for current status, scope, and restricted assurance reports. CamberCloud Trust Center.

2. Infrastructure and Access

2.1 Environment Isolation

CamberCloud separates development and production environments. Production uses distinct public and internal access paths, restricted service identities, and secure web connections.

Production services use health monitoring and redundant capacity where appropriate. Customer isolation does not imply dedicated cloud infrastructure or physical hardware for each customer.

2.2 Authentication and Authorization

CamberCloud uses a managed identity provider to authenticate product requests. Access checks confirm that users are active and authorized for the requested role or team resource. Internal service access uses separate authentication controls.

User and team context determines which workspaces, conversations, agents, project files, and connectors a request can access. Administrative access follows least privilege, and system owners perform scheduled access reviews.

2.3 Workforce Security

Personnel controls include confidentiality obligations, annual security-policy acknowledgement, and background screening where permitted by law. Company-managed endpoints use strong passwords, anti-malware protection, and disk encryption.

Physical security is supported by access-control processes for company facilities and by the safeguards operated by CamberCloud’s cloud and data-center providers.

3. Data Protection

3.1 Encryption

Service data is encrypted at rest and in transit using industry-standard encryption. User secrets and supported connector credentials are encrypted before storage. Encryption keys are managed separately according to the type of protected data and are restricted to authorized services.

3.2 AI Data Processing

Depending on the workflow, CamberCloud may process prompts, source code, notebooks, selected files, tool results, and authorized connector data. Only the conversation context and supporting content required for the requested workflow are sent for AI processing.

CamberCloud minimizes the storage and retention of user data and does not use customer data to train, develop, or improve AI models. When selecting model providers and configurations, CamberCloud uses options under which submitted customer data is not used to train provider models.

Relevant content may then be sent to the configured model provider. Provider retention terms depend on the provider configuration and contract.

3.3 Data Lifecycle and Backups

Retention and deletion follow applicable contracts, security policies, and the lifecycle of each storage system. Because product data may be stored across different service components, deletion follows the workflow defined for each resource rather than one universal immediate-purge process.

Backups are retained under business continuity and disaster recovery controls. Backup data is restored to a non-production environment at least annually to validate integrity.

4. Application Security

4.1 Secure Development

CamberCloud’s secure development and change-management controls require changes to be documented, tested, tracked, reviewed, and approved before production deployment. Production data is not used in development or testing unless required to resolve a customer issue under controlled access.

4.2 Vulnerability Management

CamberCloud maintains vulnerability and patch-management processes for identified vulnerabilities. Remediation is prioritized by assessed risk and the affected system. Current remediation commitments are available through restricted assurance materials rather than a universal public patch deadline.

4.3 Third-Party Security

Applicable vendors and subprocessors follow CamberCloud’s vendor risk-management process. Vendor SOC 2 reports or equivalent assurance materials are reviewed at least annually. The current subprocessor list is maintained in the CamberCloud Trust Center.

5. Agent Security

5.1 Agent Execution

CamberCloud coding agents execute code in managed workspace environments. Personal and team workspaces are separated, use scoped storage, and operate within defined resource limits.

Agent sessions run within the authorized workspace environment. The workspace is the primary isolation boundary for agent execution.

5.2 Permissions and Least Privilege

An agent receives the user and team context associated with the request. Access to conversations, projects, workspaces, agents, and connectors is checked against ownership, membership, and role permissions as applicable.

Within an authorized workspace, a coding agent may read or modify files, create notebook content, execute code, and call configured tools as required to complete the user’s request. Customers should grant connectors and repositories only the permissions needed for their intended workflows.

5.3 Repository Access

Source code and project context become available only when supplied, mirrored, or connected for the relevant workflow. Personal and team content is stored within the corresponding authorized scope. Internal services use scoped credentials within CamberCloud-managed boundaries.

6. Credentials and Network Security

6.1 Secrets and Credentials

CamberCloud encrypts user secrets and supported connector credentials before storage. Secret values are not returned through standard user-facing responses. Credentials are made available only to authorized workflows after the requesting identity and workspace have been verified. Production secrets are stored in protected form rather than as plaintext configuration.

6.2 Model Provider Data

Model requests may include prompts, relevant conversation context, selected tool results, agent instructions, and files required for the requested task. Provider-specific retention and training terms are governed by the configured provider and applicable contract.

6.3 Network and Tool Access

CamberCloud retrieves knowledge only from documents that users upload to knowledge bases within their authorized personal or team scope. The platform does not search the public Internet or use web search results as a knowledge source.

Agent environments may access the public Internet only to retrieve software packages or communicate with external services authorized for the workflow. This access is governed by authentication, authorization, and network controls that restrict connections to private systems, infrastructure metadata, known high-risk destinations, cryptocurrency-mining services, and unauthorized tunnels.

7. Monitoring and Incident Response

7.1 Activity Monitoring

CamberCloud uses infrastructure logging, service metrics, health checks, network controls, and automated alerting. Production monitoring covers service availability, storage capacity, resource anomalies, and workload health.

The platform also records selected workflow events and usage metadata for operations, troubleshooting, and security review. These records provide workflow visibility but are not represented as an immutable or complete audit log of every agent action.

7.2 Incident Response

CamberCloud maintains and periodically tests an incident response plan. Confirmed incidents are documented, prioritized, communicated, assigned, and tracked through resolution. Lessons learned feed back into security and operational controls.

Production monitoring sends configured warning and critical alerts to Slack. Automated controls monitor for abnormal resource use, cryptocurrency-mining indicators, unauthorized network tunnels, and potential data-exfiltration paths. Findings are reported through Slack for investigation, and confirmed misuse may result in account deactivation. These controls support the detection of suspected security leaks and unusual behavior but do not represent a universal leak-detection system.

7.3 Availability and Recovery

CamberCloud uses availability monitoring, backups, and restoration testing to support resilience. Its business continuity and disaster recovery plan defines how critical services and infrastructure are restored. The plan is reviewed through periodic exercises, and backup restoration is tested at least annually.

For more information, see the CamberCloud Trust Center and Privacy & Terms.