Encrypt sensitive risk data at rest
Protect the data behind your GRC program with AES-256 encryption, so sensitive text can only ever be read or changed through SimpleRisk itself.
Why it matters
Your risk data is sensitive by definition
A GRC program collects exactly the information an attacker would want: your weaknesses, your controls, and precisely where they fall short.
If that data sits unencrypted in a database, then anyone who reaches the database, an insider, a backup, a misconfiguration, reaches your entire risk posture along with it.
What it does
Protect the data behind your program
The Encrypted Database Extra encrypts sensitive fields with AES-256 before they are ever stored, so the data can only be read or changed through SimpleRisk, never straight from the database.
- AES-256 encryption. A random key encrypts sensitive fields before they reach the database.
- Protected at rest. Nobody can read or modify the data outside the application.
- Built for regulated data. A proven safeguard for sensitive information at rest.
How it works
Up and running in three steps
Enable encryption
Turn on the Extra to generate a random AES-256 key.
Encrypt on write
Sensitive fields are encrypted before they ever reach the database.
Read through the app
Data is only decrypted inside SimpleRisk, never straight from the database.
Built for compliance
Helps satisfy data-at-rest mandates
A common requirement for teams that answer to:
PCI DSS
Protect stored cardholder data.
HIPAA
Safeguard sensitive health data.
FIPS
Meet federal encryption requirements.
Protect data at rest
Start a free trial or book a demo to see database encryption in action.
Start a free trial