Database protection
- Saved payment credentials
- Encrypted; saved keys are hidden
- Account passwords
- One-way hashed
- Database table-file encryption
- {{ $databaseProtection['label'] }}
@if($databaseProtection['verified'])
· {{ $databaseProtection['encrypted_tables'] }} of {{ $databaseProtection['total_tables'] }} application tables verified
@endif
@if($databaseProtection['verified'])- Transaction-log encryption
- {{ $databaseProtection['log_encryption'] ? 'Enabled' : 'Not enabled' }}
- Temporary database storage encryption
- {{ $databaseProtection['temporary_encryption'] ? 'Enabled' : 'Not enabled' }}
@endif
Encrypting payment keys does not encrypt the rest of the database. Database-file encryption requires a database-server key manager and verification of existing tables. Logical exports, uploaded documents and backup copies need their own storage protection.