Minimum Security for SaaS/PaaS
| Standards | What to do | Low Risk System | Medium Risk System | High Risk System | 
|---|---|---|---|---|
| Product Selection | Follow the Georgetown Cloud Services Requirements workflow | X | X | X | 
| Pre-implementation Planning | Follow the SaaS considerations checklist Follow the PaaS considerations checklist Follow the Cloud Services Security checklist | X | X | X | 
| Inventory and Asset Classification | 
 | X | X | X | 
| Credential and Key Management | 
 | X | X | X | 
| Encryption | Enable transport layer encryption TLS 1.1 or higher. | X | X | X | 
| Logging and Auditing | 
 | X | X | X | 
| Data Management | Contractually ensure that Georgetown data are purged upon termination of the agreement with accommodations as necessary to comply with any applicable regulatory obligations. | X | X | |
| Privileged Access Workstation (PAW) | Administration consoles should only be accessed through a PAW when logging in with an administrative account. Administrative accounts are defined as: 
 | X | X | |
| Backups | Back up application data at least weekly. Encrypt backup data in transit and at rest. | X | X | |
| Multi-Factor Authentication | Require Duo multi-factor authentication for all interactive user and administrator logins. | X | X | X | 
| Security, Privacy, and Legal Review | Prior to implementation, follow the Georgetown Cybersecurity and Data Risk Assessment process. | X | X | X | 
| Regulated Data Security Controls | 
 | X | 
 
      