DMZ with Ajax on client

2

My problem is this, I've been developing a Single-Page Application that will eventually be posted to a DMZ server. On the other side I will have a API that will receive the requests of my front , the problem is: my client will have a copy of the front on your machine, and when I make the request I will have to release my local network (where API ), making the concept of DMZ only 50% .

Has anyone ever had this problem? Any suggestion ?

    
asked by anonymous 07.12.2015 / 14:03

1 answer

2

By DMZ I understand that you have a network segment with only incoming connections and limitations to services that can be exploited as access vectors. Thus, a workable implementation follows the following model:

Where:

  • Requests are received in the DMZ by an API that acts as a broker / proxy;
  • This API implements a Messaging Queue template - MSMQ, ZeroMQ or similar;
  • The API sends service requests via MQ, and waits for a response status;
  • In the local network, also monitoring the same MQ, is a service;
  • Upon receiving a request, this service processes it; if necessary, sends a return status / payload;
  • The API processes the return and sends it to the client.
08.12.2015 / 22:16