Security and records¶

RiskVault protects records through server-side authorization, workflow checks, version checks, audit history, and configurable storage controls.

Server-side authorization¶

Hiding a button is not the security boundary. Sensitive requests are checked again on the server for your claim, record-specific access, assignment where relevant, and the current workflow state.

Confidential risks require specific access. Users without it do not receive those risks in lists, Details pages, or supported APIs.

Deleting and restoring risks¶

Normal deletion is a soft delete: the risk is hidden from ordinary views but retained and restorable by authorized users.

Deletion is blocked when:

• the risk has never reached Closed, Rejected, or Archived;
• the general retention period has not elapsed;
• any legal hold is active.

An active hold with Delete automatically when this hold ends can eventually trigger a permanent purge after all applicable holds expire with that setting. The risk, comments, relationships, workflow history, and attachments are then unrecoverable.

Version protection¶

Risk and asset saves include a version check. If another person changes the record first, your stale update is rejected rather than overwriting their work. Reload, compare, and reapply the intended change.

Files and file encryption¶

Files use the configured cloud storage. A customer-managed AWS KMS key can provide encryption; otherwise protection depends on the storage bucket's default encryption. Optional malware scanning and file-type limits are managed separately.

AI and data privacy¶

MCP external connections use delegated user access and return only Public and Internal data after all applicable exclusions. See What MCP is.

The separate in-app writing assistant uses the endpoint configured by the organization. Review its hosting, logging, and network protections. Always check generated text before saving it.

Auditability¶

The application audit log records security- and business-significant actions such as access changes, configuration changes, imports, exports, and integration administration. Each risk also has workflow and activity history. Administrators can forward the broader audit log to a SIEM.