Changes

On-Premise API to SaaS Reference Model (2021-05-03 DRAFT)

On-Premise API to SaaS Reference Model (2021-05-03 DRAFT)

[[file:On-Premise API to SaaS Reference Model (2021-05-03 DRAFT) |tumb|100px|This model depicts Protected B outbound data from on-premise/Data Centre to a SaaS (Software as a Service). As a best practice, it is recommended to secure this flow via API Management (e.g. API Gateway, reverse proxy). SCED (Secure Cloud Enablement Defense) is not required as a security control for this flow.

[[file:On-Premise API to SaaS Reference Model (2021-05-03 DRAFT).jpg |tumb|100px|This model depicts Protected B outbound data from on-premise/Data Centre to a SaaS (Software as a Service). As a best practice, it is recommended to secure this flow via API Management (e.g. API Gateway, reverse proxy). SCED (Secure Cloud Enablement Defense) is not required as a security control for this flow.

The model also depicts that SCED CASB (Cloud Security Access Broker) is required as a security control for GC End Users to access Protected B data in a SaaS (Departmental or GC-wide). A CASB agent needs to be installed on a GC Managed Device to identify the user as a GC End User. This means GC End Users must access Protected B data on a SaaS via a GC Managed Device.]]

The model also depicts that SCED CASB (Cloud Security Access Broker) is required as a security control for GC End Users to access Protected B data in a SaaS (Departmental or GC-wide). A CASB agent needs to be installed on a GC Managed Device to identify the user as a GC End User. This means GC End Users must access Protected B data on a SaaS via a GC Managed Device.]]