Design Partner Program
API SECURITY VALIDATION

Prove which API endpoints attackers can abuse.

Hayrok sends the same API request under every identity you configure and compares what came back with what should have. Authorization gaps, broken object-level access, and workflow abuse become evidence your team can replay, fix, and retest.

01 · API SECURITY TESTING COVERAGE

API Security Validation: It’s About Who Can Call What

Most serious API exposure is not a malformed payload. It is a valid request from the wrong identity. Hayrok tests access and behavior across every identity you configure, on REST and GraphQL APIs.

02 · RESPONSE COMPARISON

Broken Object-Level Authorization Testing: See What Leaked

Hayrok compares responses field by field across identities. Over-shared fields and objects that should have been denied are highlighted, and sensitive values are redacted before they are stored.

ILLUSTRATIVE
buyer_aOrder owner 200 OK
1 {
2 "order_id": "ord_7741",
3 "owner": "buyer_a",
4 "name": "",
5 "ship_to": "",
6 "card_last4": "",
7 "total": 60.00,
8 "status": "delivered"
9 }
buyer_bOther customer · expected 403 200 OK
1 {
2 "order_id": "ord_7741",
3 "owner": "buyer_a",NOT OWNER
4 "name": "",NOT OWNER
5 "ship_to": "",NOT OWNER
6 "card_last4": "",NOT OWNER
7 "total": 60.00,NOT OWNER
8 "status": "delivered"NOT OWNER
9 }
Reproduced buyer_b received buyer_a’s full order, including shipping address and payment details. Expected 403.
03 · FROM DEFINITION TO PLAN

How API Validation Runs: Describe, Approve, Then Test

Bring your API definitions and test identities. Nectar builds a validation plan around the endpoints and boundaries that matter, and your team approves it in Hive.

01

Import the API

Start from the definitions your team maintains. Hayrok maps endpoints, methods, and object identifiers.

OpenAPISwaggerGraphQL schema
02

Configure identities

Add test identities for each role and tenant, and state what each should be allowed to do.

buyer_abuyer_bsupport_agent
03

Approve the plan

Nectar proposes the requests and scenarios. Your team approves methods, scope, and limits in Hive.

read-only firstrate limitsstop conditions
04 · API BUSINESS LOGIC TESTING

API Business Logic Testing: The Rules Your API Enforces

Define a rule in plain terms. Hayrok exercises the workflow that should enforce it, using approved identities and test resources, and records whether the rule held.

RULE CHECKILLUSTRATIVE DATA

A refund never exceeds the order total.

01 POST /api/orders/ord_7741/refunds { amount: 40.00 }201 Created · refund 1 of 2
02 POST /api/orders/ord_7741/refunds { amount: 40.00 }201 Created · refund 2 of 2
03 GET /api/orders/ord_7741total 60.00 · refunded 80.00
Rule broken · Reproduced Two partial refunds were each accepted on their own. Together they exceeded the order total.
05 · CONTINUOUS API PENETRATION TESTING

Continuous API Validation: Proof Ships Every Week

New endpoints and changed definitions are picked up release by release. Nectar proposes the validation, your team approves it, and regressions surface before an attacker finds them.

orders-api · release pipeline#1288 · v4.10 · main@a41c9e2 · 2026-10-07
Success
✓
Sourcemain · a41c9e2 0s
✓
Build & test214 tests passed 1m 12s
✓
Containerorders-api:4.10 38s
✓
Deploy stagingstaging · 3/3 pods 54s
✓
Hayrok validation168 requests · 0 mismatches 2m 41s
✓
Security gatepassed · 0 open 1s
✓
Promoteproduction 47s
JOB LOG · PROMOTEILLUSTRATIVE
00:36deployment "orders-api" successfully rolled out (staging)
00:47$ hayrok validate --plan api-authz --env staging ✓ 0 mismatches
00:58gate: open mismatches 0 ≤ threshold 0 → PASS
01:09promoted orders-api to production
BASELINE2026-10-07

Every endpoint in scope validated across four identities.

The first approved plan sets the baseline: expected access for each endpoint and identity, recorded as evidence.

SCOPE42 endpoints · 4 identities
ENDPOINTS 42 in approved scope
REQUESTS 168 identity × endpoint
MISMATCHES 0 boundaries held
APPROVAL 1 security lead
06 · GOVERNED API TESTING

Governed Testing: Production APIs on Your Terms

Every request is checked against the approved plan before it is sent. Anyone with authority can stop a run instantly.

methods: [GET]

Read-only first

Start with read requests. Write methods are added to the plan only when someone approves them.

rate: 60/min

Rate and volume limits

Request rates stay inside the limits your team sets for each environment.

stop_on: [5xx]

Stop conditions

Error spikes or unexpected responses pause the run automatically.

resources: test_only

Test resources

Write tests use approved test accounts, orders, and payment methods, with cleanup recorded.

07 · OWASP API SECURITY TOP 10

OWASP API Security Top 10: Validated, Not Just Listed

The OWASP API Security Top 10 (2023) names the risks. This is the method Hayrok applies to each, and where a conversation about your environment comes first.

API1

Broken Object Level Authorization

Same request replayed under every identity; responses compared with expected ownership. Core method
API2

Broken Authentication

Approved token and session scenarios: expired, revoked, and cross-environment credentials. Supported scenarios
API3

Broken Object Property Level Authorization

Response fields compared across identities to find over-shared or writable properties. Core method
API4

Unrestricted Resource Consumption

Observed within approved rate limits only. Load and denial-of-service testing is out of scope. Discuss your environment
API5

Broken Function Level Authorization

Role boundaries tested by calling privileged operations from lower-privilege identities. Core method
API6

Unrestricted Access to Sensitive Business Flows

Business rules you define, exercised as multi-step workflows with test resources. Core method
API7

Server Side Request Forgery

Scenario-dependent and environment-specific. Scoped with your team before any run. Discuss your environment
API8

Security Misconfiguration

Configuration observations recorded where supported scenarios touch them. Supported scenarios
API9

Improper Inventory Management

Definition diffs surface new and changed endpoints for validation each release. Supported scenarios
API10

Unsafe Consumption of APIs

Depends on third-party integrations in scope. Discussed during planning. Discuss your environment
08 · API PENETRATION TESTING

API Penetration Testing Compared: Beyond the Annual Test

Scanners check requests against known patterns. A penetration test explores what one engagement can reach. API security validation keeps proving access boundaries as your API changes.

API security scanner
API penetration test
Hayrok API security validation
WHAT IT CHECKS
Requests against known vulnerability patterns.
What a tester explored during the engagement.
Expected vs observed access for every endpoint and identity.
IDENTITIES
Usually one token.
The roles the tester was given.
Every configured role and tenant, side by side.
BUSINESS LOGIC
Rarely covered.
Depends on tester time and context.
Rules you define, exercised as workflows.
CADENCE
Scheduled or pipeline scans.
Point-in-time engagements.
Continuous or on demand, within approved scope.
AFTER A FIX
The next scan.
A retest scheduled separately.
Retest from the evidence record; the result joins the same record.
09 · FAQ

API Security Validation FAQ: What Evaluators Ask

It proves whether your API enforces the access and behavior it should. Hayrok sends approved requests under each configured identity, compares the responses with your policy, and records the evidence for each result.

Book an API Validation: On an API You Choose

Walk through importing a definition, configuring test identities, approving the plan, and reading the authorization matrix and evidence.

✓Import an OpenAPI or GraphQL definition✓Configure identities and approve the plan✓Read the authorization matrix and evidence
Book a Demo