v2026.05.30SecuritySecurityInfrastructure
Security update: API origin lockdown behind the managed edge
1 min read
Security work rarely gets a launch post, but you deserve to know it happens. This month we closed a whole class of attack surface.
What changed
- api.ziasign.com now sits exclusively behind our managed edge network. Requests that try to bypass the edge and reach the origin directly are rejected with a 403 — the origin verifies a private edge identity header on every request.
- Web Application Firewall (WAF) protection screens all traffic at the edge, before it ever reaches application code.
- Every service continues to enforce role-based authorization and per-user data isolation independently — the edge is a layer, not the only lock.
Housekeeping
We also removed the standalone document-generate route from the dashboard; generation now lives inside the composer where your context already is. Fewer surfaces, fewer surprises.
No action is needed on your side. If you integrate with our API, nothing changes — the public endpoints and contracts are identical.