Row-level security isolation
Every customer's data is kept apart in the database itself. Each table that holds customer data has row-level security switched on and enforced, so a query only ever returns the rows of the organization it runs for.
Your awards, suppliers, costs and shipments are your business. These are the controls built into O2F today.
Every customer's data is kept apart in the database itself. Each table that holds customer data has row-level security switched on and enforced, so a query only ever returns the rows of the organization it runs for.
Each user has a role: admin, operations manager, department user or read-only. Department and read-only users see their own department's work, and read-only users cannot change anything. The database enforces the same rules.
The database and stored files are encrypted at rest. Connections to O2F use HTTPS, and the application's connection to the database uses TLS with the server's certificate verified.
O2F records changes and refused actions as audit events. The application can add events but cannot edit or delete them. Admins and operations managers can search the trail and export it.
Sign-in runs on Amazon Cognito. Passwords must be at least 12 characters and include upper-case and lower-case letters, numbers and symbols. Accounts are created by invitation only.
Subscriptions are paid on Stripe's own checkout and billing pages. O2F has no card form and never receives or stores card numbers.
O2F runs on Amazon Web Services in the US East (N. Virginia) region, us-east-1.
The database is backed up automatically with 7 days of retention, and it has deletion protection switched on.
To report a security issue, email info@a-defense.com.
Tell us what you fulfill and what you want to see. We will walk you through O2F from award to delivery.