Picus Security
Picus Security is a cybersecurity company that pioneered Breach and Attack Simulation (BAS) in 2013 and now ships the Picus Security Validation Platform for Adversarial Exposure Validation (AEV) and Continuous Threat Exposure Management (CTEM). The platform continuously simulates real-world adversary techniques against network, endpoint, email and cloud controls, scores prevention and detection effectiveness, maps results to MITRE ATT&CK and the Unified Kill Chain, and returns vendor-specific mitigation signatures and validated detection rules from the Picus Mitigation Library. The Picus Customer API is a public REST API documented at apidocs.picussecurity.com and served from api.picussecurity.com, exposing simulations, simulation run results, the threat library, threat templates, agents, integrations, mitigation and detection content, exposure instance scores, users and roles, and activity logs, authorized with OAuth2-issued refresh and access tokens.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Picus Security the way a machine reads it — 36 machine-readable artifacts across 14 APIs, 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 — Picus Security scores 56.2/100 (strong), with a separate agent-readiness read of 41/100 (agent ready). 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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Picus Security's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/picus-security/"
title="Picus Security on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/picus-security.svg"
alt="Picus Security Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/picus-security/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/picus-security/"
title="Picus Security on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/picus-security/card.svg"
alt="Picus Security Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Picus Security
Each block below is one kind of artifact we hold for Picus Security. 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.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Picus Security Activity Logs API
The Activity-Logs API from Picus Security — 1 operation(s) for activity-logs.
Picus Security Agents API
The Agents API from Picus Security — 6 operation(s) for agents.
Picus Security Authentication API
The Authentication API from Picus Security — 2 operation(s) for authentication.
Picus Security Instances API
The Instances API from Picus Security — 1 operation(s) for instances.
Picus Security Integrations API
The Integrations API from Picus Security — 2 operation(s) for integrations.
Picus Security Mitigation API
The Mitigation API from Picus Security — 15 operation(s) for mitigation.
Picus Security Simulation Latest Result API
The Simulation-Latest-Result API from Picus Security — 7 operation(s) for simulation-latest-result.
Picus Security Simulation Result API
The Simulation-Result API from Picus Security — 8 operation(s) for simulation-result.
Picus Security Simulation Result Reports API
The Simulation-Result-Reports API from Picus Security — 4 operation(s) for simulation-result-reports.
Picus Security Simulations API
The Simulations API from Picus Security — 4 operation(s) for simulations.
Picus Security Summary API
The Summary API from Picus Security — 1 operation(s) for summary.
Picus Security Templates API
The Templates API from Picus Security — 2 operation(s) for templates.
Picus Security Threats API
The Threats API from Picus Security — 13 operation(s) for threats.
Picus Security Users API
The Users API from Picus Security — 5 operation(s) for users.
Scroll within the panel for all 14 ·
Open Collections 15
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONPicus Customer Activity Logs API
OPEN COLLECTIONPicus Customer Agents API
OPEN COLLECTIONPicus Customer Authentication API
OPEN COLLECTIONPicus Customer Instances API
OPEN COLLECTIONPicus Customer Integrations API
OPEN COLLECTIONPicus Customer Mitigation API
OPEN COLLECTIONPicus Customer Simulation Latest Result API
OPEN COLLECTIONPicus Customer Simulation Result API
OPEN COLLECTIONPicus Customer Simulation Result Reports API
OPEN COLLECTIONPicus Customer Simulations API
OPEN COLLECTIONPicus Customer Summary API
OPEN COLLECTIONPicus Customer Templates API
OPEN COLLECTIONPicus Customer Threats API
OPEN COLLECTIONPicus Customer Users API
OPEN COLLECTIONScroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
picus-security-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Picus Security Rate Limits
RATE LIMITSSecurity Posture 4
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.
Picus Security Trust Center
ISO/IEC 27001, ISO/IEC 27701, ISO/IEC 22301, ISO/IEC 20000-1, SOC 2 Type 2, CSA STAR Level One
SECURITYAgentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Picus Security — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
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 6
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/picus-security · machine-readable index on apis.io
This is an independent, third-party profile of Picus Security, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.