Skip to content
Navigate

Security review and controls

Network requirements, where to get Cephable's security documentation, and the Cephable Portal controls an organization has over the assistant.

IntermediateDifficulty: IntermediateIT adminManage & organizePrivacy & securityGovernanceWeb2 min read

What Cephable processes on the device, what it sends to its services, and the permissions it asks for are covered in Privacy and security. This page covers what an IT team needs on top of that: the network requirements, central control over the assistant, and the documentation for your security review.

Network requirements

Outbound HTTPS only. No inbound connections and no VPN requirement. The apps talk to Cephable services for sign-in, licensing, and syncing; the on-device AI models are downloaded once per device. If you are deploying to many devices on one site, plan for that download traffic — see Deploying at scale.

Get the current endpoint list from Cephable

Exact hostnames for egress allow-listing change between releases and between deployment types. Ask your Cephable contact for the current list rather than copying one from documentation — a stale entry produces an app that fails to sign in with no clear cause.

Pro

Cephable Pro unlocks this section

Cephable Pro organizations control the assistant centrally from the Cephable Portal — automation rules per app and website, extension permissions for skills and connectors, org-published connectors, and a view of which members have enabled each skill and connector.

Included with Pro, Education, SDK.

For your security review

Request access to the Cephable Trust Center for Cephable's security documentation. Your Cephable account team can also provide the security package for your agreement — data processing terms, sub-processors, and any compliance reports available under it. If you are still evaluating and do not have an account team yet, request it through cephable.com.

Related