As mentioned in the post "Best practice network design" (which you can read here), one of the tools a network administrator is required to have to securely manage servers is a jump server. A
jump server is installed in a partitioned section of the network and
access is provided to this server using a policy based network path. The
jump server is then the only network device that has network level
access to the administrative consoles of servers. This prevents these
consoles from being accessible to anyone on the internal network were
only application level access is provided. Administrators gain access to
the jump server using signed certificates which provides a high level
of trust and authentication. The normal server challenge methods are
then also applied on the server consoles.
There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg
Comments
Post a Comment