IMPLEMENTED
Approval-gated writes
External write tools are classified separately and require explicit approval before execution.
SECURITY & CONTROL
Control before autonomy.
Kernolix is early-stage software. We do not claim certifications we do not have. This page shows the controls already implemented and the security work still required before broader production use.
K
AUDIT
APPROVAL
CSRF
POLICY
IMPLEMENTED TODAY
Concrete controls already in the codebase.
These are implementation facts, not compliance badges.
IMPLEMENTED
Operator audit trail
Run metadata, actions, statuses, model details, outputs, and errors can be persisted for review.
IMPLEMENTED
Web hardening
CSRF protection, secure session behavior, CSP, HSTS on HTTPS, frame blocking, content-type protection, and login throttling are part of the application baseline.
IMPLEMENTED
Password hashing
User credentials are stored with PHP password hashing rather than plaintext passwords.
SECURITY ROADMAP
What must be completed before we call the platform mature.
We expose the gap instead of hiding it behind generic “enterprise-grade” language.
IMPLEMENTEDOAuth token encryption at rest
New connector secrets are encrypted server-side with AES-256-GCM when KERNOLIX_APP_KEY is configured. Legacy plaintext records still require migration before production use.
IN PROGRESSWorkspace isolation tests
Tenant boundaries need automated negative tests for IDOR and cross-workspace access paths.
IN PROGRESSConnector permission minimization
Gmail OAuth uses state validation and reduced read/send scopes. Refresh, revocation, and least-privilege tests still need production verification for every connector.
LATERIndependent compliance program
SOC 2 / formal compliance work belongs after real customers and infrastructure maturity justify the cost.
EXECUTION POLICYExample run boundary
Public researchAUTO
Draft contentAUTO
Update CRMREVIEW
Send customer emailREVIEW
Separate thinking from side effects
A model can recommend an action without automatically receiving permission to perform it.
Fail closed on missing capability
If a connector is absent, the action stays blocked rather than being reported as successful.
Make status visible
Available, approval-required, connector-required, blocked, executed, and failed are explicit states.