Security
Security.
What the platform does and does not do with your data, and how to tell us when something is wrong.
Data minimisation
Redflow holds the fields a job needs to decide and to post, and no more. Where a job carries personal data, such as payroll, the aggregation happens at the edge before anything is written to a stream, so the platform never receives the detail.
No inbound connection into the ERP
The pull worker and the adapter run inside your network. They open outbound connections to the Redflow instance and pull cleared work. Nothing outside your network opens a connection to Dynamics GP, your CIS or WAMS.
Audit trail
Every hold, approval, release, post and failure is a record with the time, the rule, and the person. The log is visible in the console and exportable.
Sign-in
Console accounts use a password and a time-based one-time code (TOTP). Access is by role, and roles are deny-by-default.
Approval notices leave through your SMTP relay. Redflow requires TLS on that connection and refuses to send without it.
Self-hosted by design
The self-hosted edition runs on a VM you own, under a TLS certificate you issue. See Deployment.
This website
redflow.us is a static site with no accounts and no cookies. The contact form is relayed by a small function that validates the input, stores it in a private encrypted bucket, and emails it to us. See Privacy.
Reporting a vulnerability
Email security@redflow.us. Include what you found and how to reproduce it. A person reads every report and replies. We ask that you give us time to fix before publishing, and we will credit you if you want that.
Questions for your security review?
Send them. We would rather answer them before the demo than after.