|
Re: Security tool for monitoring HTTPS traffic?: msg#00116security.web-applications
lists AT dawes DOT za DOT net wrote: The organisation is providing a service on their web server, and consequently have a need/right to see the data in clear. In particular, they may wish to do multiple things with the data, such as performing IDS, tracking users, etc, apart from providing the service. Very good point. NIDS/NIDP, deep inspection firewalls, network based content management and rate limiting will all go the way of the dodo as applications increasingly all start looking like HTTPS unless the encryption border is in the network instead of each individual host. |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Controlling access to pdf/doc files: 00116, David Cameron |
|---|---|
| Next by Date: | Where do You Architect Security in An Application (Was HTTPS Security Moniting Tools): 00116, Mark Curphey |
| Previous by Thread: | Re: Security tool for monitoring HTTPS traffic?i: 00116, lists AT dawes DOT za DOT net |
| Next by Thread: | Where do You Architect Security in An Application (Was HTTPS Security Moniting Tools): 00116, Mark Curphey |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |