Security Gateway - Revision history

Tom: /* References */

2023-07-26T00:28:54Z

‎References

Tom: /* Secure Web Gateway */

2023-03-21T22:37:54Z

‎Secure Web Gateway

Tom: /* No Gateway */

2023-03-04T17:31:49Z

‎No Gateway

Tom: /* No Gateway */

2023-03-04T17:30:28Z

‎No Gateway

Tom: /* Secure Access Service Edge */

2023-03-04T17:26:29Z

‎Secure Access Service Edge

Tom: /* Secure Access Service Edge */

2023-03-04T17:24:21Z

‎Secure Access Service Edge

Tom: /* No Gateway */

2023-03-04T17:23:49Z

‎No Gateway

Tom: /* Solutions */

2023-03-04T01:00:25Z

‎Solutions

Tom at 19:24, 3 March 2023

2023-03-03T19:24:01Z

Tom: Created page with "==Full Title or Meme== The Security Gateway is a Firewall interposed between two networks to allow only protected traffic to pass from one security zone to another. =..."

2023-03-03T19:20:28Z

Created page with "==Full Title or Meme== The Security Gateway is a Firewall interposed between two networks to allow only protected traffic to pass from one security zone to another. =..."

New page

==Full Title or Meme==
The [[Security Gateway]] is a [[Firewall]] interposed between two networks to allow only protected traffic to pass from one security zone to another.

==References==

[[Category: Glossary]]
[[Category: Network]]

← Older revision		Revision as of 00:28, 26 July 2023
Line 23:		Line 23:

	[[Category: Glossary]]		[[Category: Glossary]]
−	[[Category: ~~Network~~]]	+	[[Category: Networking]]

← Older revision		Revision as of 22:37, 21 March 2023
Line 15:		Line 15:

	===Secure Web Gateway===		===Secure Web Gateway===
		+	There is little difference between a Secure Gateway and a Firewall there than the hype.

	===Zero Trust Network Access===		===Zero Trust Network Access===

@@ Line 9: / Line 9: @@
 ===No Gateway===
-At its extreme a [[Zero Trust Architecture]] should assume that there is no such thing as a [[Security Gateway]]. But there are attacks that can be mitigated at a gateway. Several gateways stacked together like an onion can limit different attacks and some result in good security. It is unlikely that a [[Zero Trust Architecture]], by itself, can ever be considered to be a workable solution.
+At its extreme a [[Zero Trust Architecture]] should assume that there is no such thing as a [[Security Gateway]]. But there are attacks that can be mitigated at a gateway. Several gateways stacked together like an onion can block different attacks and so result in good security at the center of the onion. It is unlikely that a [[Zero Trust Architecture]], by itself, can ever be considered to be a workable solution.
 ===Secure Access Service Edge===

← Older revision		Revision as of 17:30, 4 March 2023
Line 9:		Line 9:

	===No Gateway===		===No Gateway===
		+	At its extreme a [[Zero Trust Architecture]] should assume that there is no such thing as a [[Security Gateway]]. But there are attacks that can be mitigated at a gateway. Several gateways stacked together like an onion can limit different attacks and some result in good security. It is unlikely that a [[Zero Trust Architecture]], by itself, can ever be considered to be a workable solution.

	===Secure Access Service Edge===		===Secure Access Service Edge===

@@ Line 11: / Line 11: @@
 ===Secure Access Service Edge===
-SASE is promoted by cloud providers as a way to encourage cloud solutions.<ref>Rich Korn ''Think of SASE as a Framework - Not a Checklist'' https://vmblog.com/archive/2022/07/18/think-of-sase-as-a-framework-not-a-checklist.aspx#.ZADtKh_MKry</ref> It does encourage thinking operationally about the total problem, but is really just a continuation of Firewall thinking which gives the impression of better security but limits the security to edge protection. The following items can be considered to be point solutions in a SASE.
+SASE is promoted by cloud providers as a way to encourage cloud solutions.<ref>Rich Korn ''Think of SASE as a Framework - Not a Checklist'' (2022-07-18) https://vmblog.com/archive/2022/07/18/think-of-sase-as-a-framework-not-a-checklist.aspx#.ZADtKh_MKry</ref> It does encourage thinking operationally about the total problem, but is really just a continuation of Firewall thinking which gives the impression of better security but limits the security to edge protection. The following items can be considered to be point solutions in a SASE.
 ===Secure Web Gateway===

← Older revision		Revision as of 17:23, 4 March 2023
Line 9:		Line 9:

	===No Gateway===		===No Gateway===
		+
		+	==Secure Access Service Edge==
		+	SASE is promoted by cloud providers as a way to encourage cloud solutions.<ref>Rich Korn ''Think of SASE as a Framework - Not a Checklist'' https://vmblog.com/archive/2022/07/18/think-of-sase-as-a-framework-not-a-checklist.aspx#.ZADtKh_MKry</ref> It does encourage thinking operationally about the total problem, but is really just a continuation of Firewall thinking which gives the impression of better security but limits the security to edge protection. The following items can be considered to be point solutions in a SASE.

	===Secure Web Gateway===		===Secure Web Gateway===

@@ Line 6: / Line 6: @@
 ==Solutions==
 ===No Gateway===
@@ Line 13: / Line 14: @@
 ===Zero Trust Network Access===
 This is a false hope
 ==References==

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
 The [[Security Gateway]] is a [[Firewall]] interposed between two networks to allow only protected traffic to pass from one security zone to another.
 ==References==