Timeline for Safety of exposing an internal web application to the internet using a reverse proxy in the DMZ
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 12, 2015 at 15:36 | vote | accept | RobSiklos | ||
| May 12, 2015 at 15:16 | comment | added | RobSiklos | @k1DBLITZ Correct. | |
| May 12, 2015 at 15:15 | comment | added | k1DBLITZ | So would it be out of the question to have this site behind a VPN portal, or restrict access to allowed network segments? | |
| May 12, 2015 at 15:10 | comment | added | RobSiklos | It could be either. For random clients they would get logged on automatically by the back-end (anonymous user). For known users, they will authenticate either by providing credentials (over HTTPS) or single-sign-on (also done automatically by the back end). | |
| May 12, 2015 at 15:06 | comment | added | k1DBLITZ | +1 for the Skeletor avatar. Will the users of this system be predefined? In other words, will this application be used by random internet clients, or will it primarily be used by other businesses? | |
| May 12, 2015 at 14:42 | answer | added | Stephane | timeline score: 4 | |
| May 12, 2015 at 14:21 | review | First posts | |||
| May 12, 2015 at 14:22 | |||||
| May 12, 2015 at 14:20 | history | asked | RobSiklos | CC BY-SA 3.0 |