For security reasons, we will not be able to use IIS on our local machines. I am sure many of you have faced the same problem, so how did you solve it? These are the options we are looking for:
-
Create a VLAN which is different from the network for development. This will allow us to use any software including IIS, which we want. One loss is testing web services with external organizations, which can be removed using the stubs.
-
Do not use VLAN and use only ASP.NET Development Server which is Visual Studio, and then that code is being employed on the development server. This loss is not being able to replicate the environment of production during local development. Apart from this, at least one developer needs IIS for GIS development, so he could not develop locally.
Thank you for the comments or suggestions!
Create local VM using virtual PC. Do not give that virtual machine a network connection.
Edit: Note that it is possible to access the virtual machine on a network safely in two ways:
-
Share the hard drive on the settings of the virtual machine and the network share. Only one person can use virtual machines at one time. I can remove this limit using a previously undisclosed disk, but it is not supported.
-
Use a server-based virtual machine solution such as VMWare if your company is not already doing so, it costs money and resources to install it . The advantage of this is that everyone can see the machine in one go.
Note that in both of these solutions, users are reaching VM directly, not connecting it. Therefore, the machine is not actually killing the network and thus there is no way to hack VM in the VM without first getting access to a VM host machine (such as through a share in # 1) Compared to the external website, more like a remote desktop, but the remote desktop lets you leave the machine to be removed in the computer's ability to see the computer directly, so it The trunk is not safe as it is.
TataLogy: It is not possible for the machine to provide the facility of other machines, as long as access to those machines (direct or indirectly), therefore, if you have a VMI IIS Is running and behaving as an external web server, but it is not able to reach the computer on your network, so you are participating in an interconnected requirements. Some roundabouts are making security checks by any move involved in sending traffic, but more secure holes in security checkpoints (though do not have a circle with hackers perspective).
Technically both # 1 and # 2 also make VM accessible on the network, but the virtual machine does not see the network (instead, VM sees the host network network).
Comments
Post a Comment