Contrast Security · Schema

V4Rule

A rule defines a data flow pattern used to categorize vulnerability and attack types. Some common rules are sql-injection, ssrf, and reflected-xss.

Application SecurityAppSecIASTRASPSoftware Composition AnalysisDevSecOpsRuntime Protection

Properties

Name Type Description
name string Unique name identifying this rule.
title string Human-readable title of this rule.
description string Description of the vulnerability type the rule is checking for.
category string Rule category. Rules are grouped into categories that have similar characteristics.
severity string Default severity to assign for vulnerabilities violating the rule. This can be customized by your organization.
confidence string Level of confidence that vulnerabilities detected by this rule are true positives.
likelihood string Likelihood of vulnerabilities detected by this rule to actually be exploited.
impact string The level of negative impact an exploit of this vulnerability would have.
cweUrl string Link to information about the CWE this rule addresses.
owaspUrl string Link to OWASP information about the vulnerability this rule addresses. QUESTION--Should these two be named Url, Uri or Link?
View JSON Schema on GitHub

JSON Schema

contrast-security-v4-rule-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/contrast-security/main/json-schema/contrast-security-v4-rule-schema.json",
  "title": "V4Rule",
  "description": "A rule defines a data flow pattern used to categorize vulnerability and attack types. Some common rules are sql-injection, ssrf, and reflected-xss.",
  "x-generated": "2026-10-04",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/contrast-security-rules-api-openapi.yml#/components/schemas/V4Rule",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Unique name identifying this rule."
    },
    "title": {
      "type": "string",
      "description": "Human-readable title of this rule."
    },
    "description": {
      "type": "string",
      "description": "Description of the vulnerability type the rule is checking for."
    },
    "category": {
      "type": "string",
      "description": "Rule category. Rules are grouped into categories that have similar characteristics.",
      "enum": [
        "ACCESS_CONTROL",
        "AUTHENTICATION",
        "CONFIGURATION",
        "AVAILABILITY",
        "CACHING",
        "CVE",
        "CRYPTOGRAPHY",
        "ERROR_HANDLING",
        "INJECTION",
        "SECURE_COMMUNICATION",
        "SESSION_MANAGEMENT",
        "INPUT_VALIDATION",
        "XSS"
      ]
    },
    "severity": {
      "type": "string",
      "description": "Default severity to assign for vulnerabilities violating the rule. This can be customized by your organization.",
      "enum": [
        "CRITICAL",
        "HIGH",
        "MEDIUM",
        "LOW",
        "NOTE"
      ]
    },
    "confidence": {
      "type": "string",
      "description": "Level of confidence that vulnerabilities detected by this rule are true positives.",
      "enum": [
        "LOW",
        "MEDIUM",
        "HIGH"
      ]
    },
    "likelihood": {
      "type": "string",
      "description": "Likelihood of vulnerabilities detected by this rule to actually be exploited.",
      "enum": [
        "LOW",
        "MEDIUM",
        "HIGH"
      ]
    },
    "impact": {
      "type": "string",
      "description": "The level of negative impact an exploit of this vulnerability would have.",
      "enum": [
        "LOW",
        "MEDIUM",
        "HIGH"
      ]
    },
    "cweUrl": {
      "type": "string",
      "description": "Link to information about the CWE this rule addresses."
    },
    "owaspUrl": {
      "type": "string",
      "description": "Link to OWASP information about the vulnerability this rule addresses. QUESTION--Should these two be named Url, Uri or Link?"
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/contrast-security-v4-rule"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.