Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!

Difference between revisions of "File:On-Premise API to SaaS Reference Model (2021-05-03 DRAFT).jpg"

From wiki
Jump to navigation Jump to search
(→‎Narrative:: removed)
Line 1: Line 1:
 
== On-Premise API to SaaS Reference Model (2021-05-03 DRAFT) ==
 
== On-Premise API to SaaS Reference Model (2021-05-03 DRAFT) ==
−
 
−
==== Narrative: ====
 
 
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.
 
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.

Revision as of 09:50, 25 May 2021

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

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.

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeThumbnailDimensionsUserComment
current13:58, 17 May 2021Thumbnail for version as of 13:58, 17 May 2021757 × 635 (88 KB)Adam.desrosiers (talk | contribs)

You cannot overwrite this file.

The following page uses this file:

Retrieved from "https://wiki.gccollab.ca/index.php?title=File:On-Premise_API_to_SaaS_Reference_Model_(2021-05-03_DRAFT).jpg&oldid=47913"