HighFile-scopeJava Plug & play

Return explicit HTTP responses from API methods

API endpoints should return an explicit status code and minimal error body on failures; avoid 200 with error payload.

Why this matters

Correct semantics enable predictable client handling and monitoring.

Side-by-side examples engineers can pattern-match during review.

Avoid

return ok(new ErrorPayload("failed")); // 200 with error

Prefer

return httpResponse(500, Map.of("error", "internal_error"));

Bad

return ok(Map.of("error","x"))

Good

return response(400, Map.of("error","invalid_request"))

From the same buckets as this rule.

Critical
Check consent and role-based authorization before returning ePHI
Handlers must verify the requester’s role and a valid consent/relationship (e.g., care team assignment) before disclosing ePHI; include Purpose-Of-Use in the decision and audit the outcome.
compliance-hipaasecurity-hardening+2
Critical
Children's data: verify age and parental consent
If data subject is a child/adolescent, require age verification and parental/legal guardian consent prior to processing; deny processing otherwise and do not store the payload.
compliance-lgpdapi-conventions+1
Critical
Disallow public ingress without explicit allowlist
For Ingress/Service of type LoadBalancer, require host/path allowlist and TLS; forbid 0.0.0.0/0 exposure without WAF or Auth.
infra-as-codesecurity-hardening+1