Security overview

Tenant boundaries

Every account, campaign, connector, approval, agent run, and workspace snapshot is scoped to a tenant identifier enforced by authenticated server routes.

Identity and access

• Passwords are salted and derived with PBKDF2-SHA-256.
• Optional authenticator MFA protects sign-in with encrypted secrets, short-lived one-use challenges, and one-time recovery codes.
• Sessions are HttpOnly, Secure, SameSite cookies with expiration.
• Login attempts are rate limited and privileged routes require explicit roles.
• Invitations are single-use, hashed, seat-limited, revalidated against the current entitlement when accepted, and expire automatically.
• Deactivating a member also disables the account and revokes its active sessions.
• The scheduler removes expired sessions, challenges, reset artifacts, and stale rate-limit records while retaining durable audit history.

Agent governance

High-impact actions can require durable human approval. Runs, decisions, connector changes, and entitlement updates are recorded in the workspace audit trail. Dealer and platform policy boundaries remain authoritative over agent instructions.

When a trial expires or a workspace becomes inactive, scheduled policies are disabled and queued actions, approvals, and active runs are stopped before the scheduler can claim more work.

Billing and seats

Signed billing events are idempotent and reconciled against active accounts and outstanding invitations. A provider reduction revokes surplus invitations first. Active-seat overages preserve account access at the safe effective quantity while creating an operator review case.

Integration security

Inbound universal connectors use one-time displayed bearer credentials stored only as hashes. JSON format and payload size are validated, credentials can be rotated or revoked immediately, and inactive workspaces cannot ingest data. Until field mappings are approved, event storage retains delivery metadata and payload fingerprints rather than source records.

Outbound connector credentials are write-only, tenant-bound, and encrypted at rest with AES-GCM. They are decrypted only for an authorized validation or execution request and are never returned by the application API or workspace export.

Report a concern

Report suspected vulnerabilities or account compromise to security@vicimus.com. Include the affected URL, time, and a concise reproduction without sending live customer data.