name: Checkmarx API FinOps specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Checkmarx providerId: checkmarx created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: true tags: - FinOps - FOCUS - Application Security - DevSecOps description: 'FOCUS-aligned FinOps framing for Checkmarx One: tiered enterprise subscriptions priced by tenant tier, scanner coverage, contributing developer counts, and scan volume; pricing is custom-quoted and not publicly listed.' notes: Per-call API pricing is not separately metered; cost driven by subscription tier plus contributing-developer / project counts. sources: - https://checkmarx.com/pricing/ - https://checkmarx.com/product/checkmarx-one/ alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: Checkmarx Ltd. serviceCategory: Application Security billingModel: pricingCategory: Tiered Subscription billingFrequency: Annual billingCurrency: USD chargeCategories: - Purchase - Tax - Adjustment - Credit focusColumns: ServiceName: Checkmarx One ServiceCategory: Application Security ProviderName: Checkmarx PublisherName: Checkmarx Ltd. InvoiceIssuerName: Checkmarx Ltd. BillingCurrency: USD meters: - name: tenant_subscription unit: tenant-year aggregation: sum dimensions: - tier - name: contributing_developers unit: developer aggregation: max - name: projects_scanned unit: project aggregation: max - name: scans_executed unit: scan aggregation: sum dimensions: - engine - name: lines_of_code unit: LOC aggregation: sum dimensions: - engine principles: - name: Visibility description: Use the Checkmarx One admin console and the REST analytics endpoints for scan volume, contributing-developer counts, and engine breakdowns; reconcile against contract entitlements. - name: Allocation description: Tag projects and applications with team / business-unit metadata; allocate subscription cost by contributing-developer attribution. - name: Optimization description: Tune scan triggers (incremental scans, PR-only) to reduce runaway scan volume; right-size tier to actual scanner usage and prune unused engines. - name: Accountability description: AppSec / DevSecOps team owns the Checkmarx subscription; review developer attribution and scan volume monthly to forecast renewal sizing. maintainers: - FN: Kin Lane email: kin@apievangelist.com