API Security & Compliance

Enterprise-grade security standards protecting every endpoint, payload, and data exchange across the Aevum Zenth ecosystem.

System Operational

SOC 2 Type II Certified

TLS 1.3 Enforced

🔐

Authentication

Multi-layered access control with zero-trust architecture.

API Keys (X-API-Key header)
OAuth 2.0 Authorization Code Flow
JWT RS256 with 15-min expiration
mTLS for Enterprise endpoints

🛡️

Threat Mitigation

Automated defense against injection, DDoS, and abuse.

OWASP Top 10 compliance
Rate limiting & request throttling
IP allowlisting & geo-fencing
Automated anomaly detection

🔍

Auditing & Logging

Immutable request trails for compliance and forensics.

End-to-end request tracing
PII redaction in logs
90-day retention (configurable)
Real-time alerting on anomalies

Authentication & Authorization

Note: All API requests must include valid credentials. Unauthenticated or malformed requests will receive a 401 Unauthorized response.

Aevum Zenth supports multiple authentication methods depending on your integration tier. Production workloads require OAuth 2.0 or mTLS.

example-auth.curl

curl -X POST https://api.aevumzenth.com/v3/data/ingest \
  -H "Authorization: Bearer eyJhbGciOiJSUzI1NiIs..." \
  -H "X-Api-Key: azk_live_9f8e7d6c5b4a3210" \
  -H "Content-Type: application/json" \
  -d '{"stream":"sensor_network_eu","payload":[...']}'

auth-response.json

{
  "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6...",
  "token_type": "Bearer",
  "expires_in": 900,
  "scope": "read:analytics write:streaming admin:org",
  "refresh_token": "dGhpcyBpcyBhIHJlZnJlc2ggdG9rZW4..."
}

Data Encryption & Key Management

Warning: TLS 1.2 and lower are deprecated. All connections must use TLS 1.3. Certificates issued before 2023-01-01 will be rejected.

All data in transit is encrypted via TLS 1.3 with AES-256-GCM cipher suites. At-rest encryption uses AES-256 with keys rotated every 90 days and managed through FIPS 140-2 Level 3 Hardware Security Modules (HSMs).

Rate Limiting & Quotas

API access is governed by tier-based rate limits to ensure stability and fairness. Limits are enforced at the edge and return 429 Too Many Requests when exceeded.

Tier	Requests / Min	Burst Allowance	Dedicated IP
Developer	600	100	No
Scale	3,000	500	Optional
Enterprise	Custom (10k–100k+)	Configurable	Yes
Gov/Defense	Custom + mTLS	Air-gapped options	Yes

Retry logic should implement exponential backoff. Response headers include X-RateLimit-Limit, X-RateLimit-Remaining, and Retry-After.

Compliance & Certifications

🏛️

SOC 2 Type IIAnnually audited

🌍

ISO 27001:2022InfoSec Management

🇪🇺

GDPR CompliantData subject rights

🔒

CCPA / CPRACalifornia privacy

🏥

HIPAA EligibleBAA available

🛡️

FedRAMP ReadyMod Level 2 in progress

Full audit reports are available upon request for Enterprise and Government contracts. Security questionnaires can be completed via our Vendor Portal.

Vulnerability Disclosure Program (VDP)

We prioritize responsible disclosure. If you discover a security vulnerability in Aevum Zenth APIs, infrastructure, or related services, please report it to:

report@security.aevumzenth.com

PGP Key ID: 0xA1B2C3D4E5F67890
Key Server: keys.openpgp.org
PGP Public Key: https://aevumzenth.com/security/pgp-key.asc

Acknowledgment within 24 hours
30-day coordinated disclosure window
Bounty program for critical/remote code execution findings
No litigation for good-faith security research