Security & Compliance
CyberTax security architecture is designed for controlled RMF operations with tenant isolation, role-scoped access, auditable activity records, and explainable AI-assisted scoring.
Encryption Practices
Data In Transit
- TLS 1.2+ enforced at ingress with HTTPS-only access patterns.
- HSTS and secure header controls are included in deployment baseline configuration.
Data At Rest
- Artifact storage supports server-side encryption policies.
- Production database encryption-at-rest is expected through platform-managed controls.
Audit Logging & Tenant Isolation
Audit Logging
- Assessment actions, role governance updates, scoring events, and authorization actions are logged.
- Administrative and authentication events are queryable from system audit views.
- AI invocation logs retain model ID, latency, fallback status, and error context when applicable.
Tenant Isolation
- Organization-scoped access checks are enforced on assessment and artifact routes.
- Cross-tenant object access is blocked by API-level authorization checks.
- Role membership is resolved per organization to prevent privilege leakage across tenants.
AI Guardrails & Validation Methodology
- Deterministic AI scoring settings and schema validation for every model response.
- Reasoning and missing-elements outputs are persisted for assessor traceability.
- Fallback heuristic scoring is used when model invocation or output validation fails.
- Prompt content remains internal; user-facing APIs return only scored outcomes and rationale.
Identity Provider Support
| Provider | Supported Pattern |
|---|---|
| OIDC | Issuer-based federation with client credential and redirect URI validation. |
| SAML 2.0 | Metadata-driven SSO configuration with signing/encryption certificate support. |
| LDAP | Directory-backed authentication with bind/base DN, filters, and TLS options. |
System Update & Patching Process
- Build and dependency updates are validated through CI (backend tests, frontend type/build checks).
- Container images are rebuilt and deployed through controlled promotion workflow.
- Post-deployment verification confirms API readiness, scoring behavior, and core workflow integrity.
- Patch cycles and release changes are documented in release notes for operator review.