Skip to main content

How do you explain to experts that a Database Serverdatabase server should not reside in the DMZ?

Our security experts, DBAsdatabase administrators, network team and infrastructure team are all saying it's okOK to have the DBdatabase server located in the DMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the DBdatabase server is outside the internal system. If it is inside our network, the hacker can then use the DBdatabase server to access other systems.

What they are saying is:

  1. Let's not put the middle-ware server behind a 2ndsecond firewall and the DBdatabase server behind a 3rdthird firewall.
  2. Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB'sdatabase's sensitive data, at least that's all they can get.

The 2ndsecond statement was actually said... verbatim.

Please note that this DB Serverdatabase server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer, and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

How do you explain to experts that a Database Server should not reside in the DMZ?

Our security experts, DBAs, network team and infrastructure team are all saying it's ok to have the DB server located in the DMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the DB server is outside the internal system. If it is inside our network, the hacker can then use the DB server to access other systems.

What they are saying is:

  1. Let's not put the middle-ware server behind a 2nd firewall and the DB server behind a 3rd firewall.
  2. Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB's sensitive data, at least that's all they can get.

The 2nd statement was actually said... verbatim.

Please note that this DB Server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

How do you explain to experts that a database server should not reside in the DMZ?

Our security experts, database administrators, network team and infrastructure team are all saying it's OK to have the database server located in the DMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the database server is outside the internal system. If it is inside our network, the hacker can then use the database server to access other systems.

What they are saying is:

  1. Let's not put the middle-ware server behind a second firewall and the database server behind a third firewall.
  2. Let's use just one firewall (the HTTP server's) in case a hacker wants to get our database's sensitive data, at least that's all they can get.

The second statement was actually said... verbatim.

Please note that this database server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer, and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

Our security experts, DBAs, network team and infrastructure team are all saying it's ok to have the DB server located in the DMZDMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the DB server is outside the internal system. If it is inside our network, the hacker can then use the DB server to access other systems.

What they are saying is:

  1. Let's not put the middle-ware server behind a 2nd firewall and the DB server behind a 3rd firewall.
  2. Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB's sensitive data, at least that's all they can get.

The 2nd statement was actually said... verbatim.

Please note that this DB Server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

Our security experts, DBAs, network team and infrastructure team are all saying it's ok to have the DB server located in the DMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the DB server is outside the internal system. If it is inside our network, the hacker can then use the DB server to access other systems.

What they are saying is:

  1. Let's not put the middle-ware server behind a 2nd firewall and the DB server behind a 3rd firewall.
  2. Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB's sensitive data, at least that's all they can get.

The 2nd statement was actually said... verbatim.

Please note that this DB Server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

Our security experts, DBAs, network team and infrastructure team are all saying it's ok to have the DB server located in the DMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the DB server is outside the internal system. If it is inside our network, the hacker can then use the DB server to access other systems.

What they are saying is:

  1. Let's not put the middle-ware server behind a 2nd firewall and the DB server behind a 3rd firewall.
  2. Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB's sensitive data, at least that's all they can get.

The 2nd statement was actually said... verbatim.

Please note that this DB Server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

Tweeted twitter.com/#!/StackSecurity/status/537987122733805568
deleted 8 characters in body; edited tags
Source Link
AviD
  • 73.6k
  • 24
  • 141
  • 222

Our security experts, DBAs, network team and infrastructure team are all saying it's ok to have the DB server located in the DMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the DB server is outside the internal system. If it is inside our network, the hacker can then use the DB server to access other systems.

What they are saying is:

1.

Let's not put the middle-ware server behind a 2nd firewall and the DB server behind a 3rd firewall.

Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB's sensitive data, at least that's all they can get.

  1. Let's not put the middle-ware server behind a 2nd firewall and the DB server behind a 3rd firewall.
  2. Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB's sensitive data, at least that's all they can get.

The 2nd statement was actually said... verbatim.

Please note that this DB Server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

Our security experts, DBAs, network team and infrastructure team are all saying it's ok to have the DB server located in the DMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the DB server is outside the internal system. If it is inside our network, the hacker can then use the DB server to access other systems.

What they are saying is:

1.

Let's not put the middle-ware server behind a 2nd firewall and the DB server behind a 3rd firewall.

Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB's sensitive data, at least that's all they can get.

The 2nd statement was actually said... verbatim.

Please note that this DB Server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

Our security experts, DBAs, network team and infrastructure team are all saying it's ok to have the DB server located in the DMZ along with the HTTP server and middle-ware server.

Their reason:

If the database server is compromised (because of an insecure middle tier), at least the DB server is outside the internal system. If it is inside our network, the hacker can then use the DB server to access other systems.

What they are saying is:

  1. Let's not put the middle-ware server behind a 2nd firewall and the DB server behind a 3rd firewall.
  2. Let's use just one firewall (the HTTP server's) in case a hacker wants to get our DB's sensitive data, at least that's all they can get.

The 2nd statement was actually said... verbatim.

Please note that this DB Server will hold sensitive information, including bank details.

Now, are these experts making any sense to you? I'm a software developer and I can't get their logic. It's like, "Put the jewelry box outside the house so that robbers won't bother getting in for the TV?"

Fixed spelling, and made a more readable format
Source Link
Loading
Source Link
bruce bana
  • 633
  • 1
  • 5
  • 7
Loading