Gravity can be accessed as a web application via a web browser using https. To use any functionality, users must first login with their username and password or use a single sign-on functionality.
For enterprise deployments, Gravity supports LDAP and SAML protocols to prevent user credentials being stored in its internal database and to help enforce corporate security rules (e.g. group membership).
Gravity uses backend database to store metainformation, execution statistics (job runtimes, record counts etc.) and job status to assist with monitoring, development and troubleshooting.
This metainformation includes:
User privileges and security group configuration,
Project runtime settings and permissions,
Miscellaneous server configuration.
Gravity does not store any processed data of any kind.
Temporary Files and Storage
During execution, partial results may be stored on local hard drive in temporary directory.
Gravity does not store any data after executed job has been completed (regardless of whether the job execution was successful or not)
Further, we have auto delete policies in place to ensure no files are left behind
All data is kept on encrypted at rest storage.
All external communication is encrypted.
Users can setup their Sources/Destinations to use SSH Tunnels or SSL also.
Passwords and Secrets
All passwords and secrets are encrypted on top of encrypted storage.
User account passwords are stored salted and hashed and never as plaintext.
Gravity, upon request, can work with an organization to understand and satisfy their regulatory or IT security requirements. We have undergone numerous IT audits, code source audits, and QA testing audits to ensure compliance. We can help to help answer vendor questionnaires about audits, security, and compliance for on-boarding vendors.