DMZ layer for web server/presentation layer

I need help explaining to non security people why I want to require the webserver/presentation layer in a dmz. I’ve given options for a tier two (presentation/logic -> logic/data in zones) architecture and an three tier architecture (presentation -> logic -> data zones).

Their argument is that I should be fine with firewall -> F5 with ASM -> firewall -> Presentation/Logic/data layer all in one zone. Their argument is that this is a two tiered architecture so should count to meet my requirement. I’ve asked them to find me an industry standard document explaining security design this way and have been stonewalled — probably because there are not any.

I’m having difficulty explaining that the first thing a hacker from the internet touches should be dead ended and prevent north-south movement into the next zone. They want it in terms of architectural capabilities.

An ideas on how to explain a two tier application security design architecture in terms of architectural capabilities? Any other ideas would be helpful too.

Continue reading DMZ layer for web server/presentation layer

Azure Active Directory Connect Makes Cloud Single Sign-On Easy

Russell Smith outlines two new features of Azure Active Directory Connect, Seamless Single Sign-On and Pass-Through Authentication.

The post Azure Active Directory Connect Makes Cloud Single Sign-On Easy appeared first on Petri.

Continue reading Azure Active Directory Connect Makes Cloud Single Sign-On Easy

Moving GIT/SVN servers to internal network segment while still allowing external collaboration

Here is my situation:

I have a typical network setup, with DMZ and internal segment, with a VPN concentrator. Because we have external collaborators, the GIT/SVN servers are in the DMZ. Individual collaborators are given cre… Continue reading Moving GIT/SVN servers to internal network segment while still allowing external collaboration