Virsec
Virsec Systems is a San Jose, California cybersecurity company that builds the Virsec Security Platform (VSP), a deny-by-default, allow-on-trust zero trust runtime defense for cloud and legacy server workloads. VSP combines host protection, memory exploit protection and web protection with a Centralized Management Server (CMS) and distributed Probes, stopping ransomware, remote code execution, living-off-the-land and zero-day attacks at runtime without patching. The platform is customer-deployed (on-prem VM, EC2/Azure/GCP, Kubernetes/Helm or SaaS CMS) and exposes a customer-facing REST surface: a CMS API reference served from the CMS console under Help > API Documentation, the Centralized Probe Management (CPM) API under /rms for probe install, upgrade, migration, log/stat/data collection and vsp-cli execution, and configurable outbound webhooks that push detected incidents into existing SIEM, ITSM and ticketing systems (QRadar, Splunk, Syslog, Zendesk).
Virsec publishes 2 APIs on the APIs.io network. Tagged areas include Company, Security, Cybersecurity, Application Security, and Workload Protection.
The Virsec catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Virsec’s developer surface includes documentation, API reference, getting-started guide, support, authentication, changelog, CLI, and 11 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
Virsec Security Platform CMS API
The Virsec Security Platform Centralized Management Server (CMS) exposes a RESTful API for procuring information from CMS. From VSP 3.0.0 and above, the available APIs are liste...
Virsec Centralized Probe Management (CPM) API
The Centralized Probe Management (CPM) API simplifies upgrade and troubleshooting of VSP Probes deployed across application platforms. Served from the customer's CMS host under ...
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Virsec Cms Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API