Security
Security claims you can check against the code.
SignalForge holds credentials for your most sensitive systems, so this page is specific. Anything not done yet says so.
Implemented
In the platform today.
Credential encryption at rest
Every connector credential sits in a dedicated secret store, encrypted with AES-256-CBC and HMAC-SHA256 via ASP.NET Core Data Protection. No API returns it.
Encryption in transit
TLS 1.2 and 1.3 only at the edge, with HSTS, a Content-Security-Policy and access logs that never record bearer tokens.
Four-layer authorization
Short-lived JWTs, feature permissions, per-resource access lists and field-level security. An unparseable row filter refuses the query rather than widening access.
SSO, MFA and SCIM
Entra ID or any SAML 2.0 or OIDC provider, with optional enforced SSO. TOTP and FIDO2 MFA for local accounts. SCIM 2.0 provisioning.
Tenant isolation
Each tenant has its own signing keys, secret key ring and hostname. Shared cells isolate rows per tenant; Enterprise can run fully dedicated.
Audit logging
Administrative and data actions are logged with actor, action, entity, IP and time. Audit logs are kept 365 days by default.
Signed exports
On Enterprise, an export can carry an ES256 signature over its SHA-256 and what it is. Anyone can check it in the browser or offline against your published key; the key is yours or generated for you, and a retired key still verifies what it signed.
Outbound-only on-prem collection
The worker agent connects outbound over WebSocket: no inbound rules, no VPN. Its tokens use a separate audience and are refused on user endpoints.
Hardened request paths
SSRF guards on outbound HTTP, read-only validation of user SQL, sandboxed AI prompts, and per-tenant, per-tier rate limits at the edge.
Tested adversarially
More than 1,000 automated tests, many probing auth boundaries. A 2026 internal audit found 28 issues: 24 are fixed and verified, the rest tracked to closure.
Not yet
Honestly not done yet.
Certifications: none claimed.
SignalForge has not achieved SOC 2, ISO 27001, HIPAA, FedRAMP or any other formal certification. Its compliance module helps you produce evidence about your systems; it is not a certification of SignalForge. This page will say plainly if and when one is achieved.
Org-wide retention policy
PlannedPer-data-source archive and purge rules exist today. Org-wide defaults and legal-hold-style controls are planned.
Responsible disclosure
Report a vulnerability in this site or the platform privately to [email protected] and give us reasonable time to fix it. We read every report, take no legal action against good-faith research, and credit reporters who want it.
A formal policy with scope and safe-harbor terms will be published with general availability.
Security questions before you buy? Talk to us.