CloudLock
CloudLock is a cloud-native Cloud Access Security Broker (CASB) that protects data, users, and applications across SaaS, IaaS, PaaS, and IDaaS environments. Founded in 2011 and acquired by Cisco in 2016, it is now delivered as Cisco Cloudlock within Cisco Umbrella / Cisco Security Cloud. The platform uses an API-driven model to discover sensitive content, detect policy violations, flag anomalous user behavior, and manage cloud application (OAuth) risk. Developers integrate through the Cisco Cloudlock API (v2), a Bearer-token REST API exposing activities, incidents, incident entities, incident aggregates, policies, apps, entities, IP libraries, and anomalies. Originally a portfolio company of Bessemer Venture Partners, CloudLock's developer surface is documented on Cisco DevNet and the Cisco Umbrella documentation hub.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles CloudLock the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — CloudLock scores 16.3/100 (emerging), with a separate agent-readiness read of 17/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile CloudLock
Each block below is one kind of artifact we hold for CloudLock. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for CloudLock — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cloudlock · machine-readable index on apis.io