HeartBeatAgents (vendor site)Verified

BL-CLM-37.

HeartBeatAgents — Security controls: Documented: AES-256 at rest, TLS 1.2+, per-organization container folder scoping, token-authenticated websockets, token scrubbing.

Claim visualization

Actual claim data

BL-CLM-37 / Relationship

Claim evidence map

HeartBeatAgents (vendor site)

HeartBeatAgents — Security controls: Documented: AES-256 at rest, TLS 1.2+, per-organization container folder scoping, token-authenticated websockets, token scrubbing.

SSO, RBAC, certifications and audit log content/retention not documented there.

Source: heartbeatagents.com/features/security ↗
Where in the source: Encryption; WebSocket Auth; Audit Logs
Source organization: HeartBeatAgents (vendor site)
Evidence type: Vendor documentation
Source date: Not shown on the source
Last verified: October 13, 2026
Approved wording: According to HeartBeatAgents (vendor site), documented: AES-256 at rest, TLS 1.2+, per-organization container folder scoping, token-authenticated websockets, token scrubbing.
Scope and caveats: SSO, RBAC, certifications and audit log content/retention not documented there.
Do not infer: Do not present documented controls as a certification, authorization or independent audit.

Cited onSelf-hosted AI agent platforms comparison ↗Papyrus vs heartbeatagents ↗

← All claimsRecord BL-CLM-37