OkzByte
OKZBYTE / SECURITY & TRUST CENTER

Explore how OkzByte approaches platform security, data protection, responsible disclosure, infrastructure resilience, and transparency across its technology ecosystem.

TRUST BOUNDARY
APPAPIDATAOPS
02 / APPLICATION SECURITY

Application Security

Application controls are assessed against the implementation visible in this repository—not against intended policy alone.

IN PROGRESS

Secure authentication and authorization

Admin password verification uses scrypt and an environment-provided identity; authorization coverage is not a complete RBAC implementation.

IN PROGRESS

Secure session management

Admin sessions use random tokens in memory with HttpOnly and SameSite cookies. Persistence, rotation, and multi-instance behavior are not verified.

VERIFIED

Input validation and output encoding

Public forms apply allow-lists, length checks, email checks, payload limits, and HTML character stripping.

IN PROGRESS

SQL injection and XSS defenses

Database queries shown use parameter placeholders; frontend/content security coverage requires broader testing.

IN PROGRESS

CSRF and origin protection

Origin checks exist on privacy and support submission paths; a complete endpoint-by-endpoint CSRF review is not verified.

IN PROGRESS

Rate limiting and abuse prevention

Several sensitive endpoints use in-memory IP-based rate limiting; distributed enforcement and bot controls are not verified.

IN PROGRESS

Dependencies and secure configuration

A lockfile and environment-based secret model exist; dependency scanning and deployment secret policy are not verified.

IN PROGRESS

Secrets and error handling

Secrets are read server-side and generic errors are returned to clients; logging and production secret rotation are not verified.

Production requirement

Complete an authenticated endpoint inventory, dependency scan, authorization review, secret-rotation procedure, and independent penetration test before changing any NOT VERIFIED status.