03-22-2018, 06:47 PM
Are you aware of what will happen to your application if it runs on port 80?! You will need to implement your own security to handle all of the scanning and probing that will be directed at that port. One of the benefits of IIS is that you can manage IP address restrictions and Request Filtering.
Port 80 will be scanned /probed every hour of every day. You will need to capture and monitor that traffic. If you don't, you will encounter performance issues for legitimate users.
Running on another port, such as 8080, will attract less traffic, but it still should be monitored. Once a port is open security becomes the responsibility of the application on that port. Running on the default port should not be taken lightly.
I've studied this over several years, and have the data to confirm it. I have a security layer that gets baked into each IW application to manage this problem. On any given day 30% of the traffic comes from probes and bots. Without rejecting that traffic false sessions will be created that live until your timeout kicks in. That can result in wasted resources and bad user experiences.
Port 80 will be scanned /probed every hour of every day. You will need to capture and monitor that traffic. If you don't, you will encounter performance issues for legitimate users.
Running on another port, such as 8080, will attract less traffic, but it still should be monitored. Once a port is open security becomes the responsibility of the application on that port. Running on the default port should not be taken lightly.
I've studied this over several years, and have the data to confirm it. I have a security layer that gets baked into each IW application to manage this problem. On any given day 30% of the traffic comes from probes and bots. Without rejecting that traffic false sessions will be created that live until your timeout kicks in. That can result in wasted resources and bad user experiences.