Compliance-control coverage rollups per framework

GET 
/api/v1/findings/stats/compliance

Map findings to compliance controls with per-control status rollups.

Findings-derived evidence only — not a compliance attestation. Findings without resolvable cwe_id / owasp_category appear in the explicit unmapped bucket.

• Scope required: findings:read.
• Reads are never flag-gated (release_compliance_mapping hides the App tab only).

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.