A systematic approach to replacing old technologies and applications with new can save you time and money, improve continuity of operations, and allow you to keep up with your competitors.
By Frank Oelschlager
I often work with clients that have dated technologies and infrastructures, stuff that was modern and based on (mostly) good decisions, say 10-15 years ago. Even if there has been continuous investment in revising and updating the tech (which often is not the case), it eventually reaches a point that it just needs to be replaced in order to meet the needs of the business going forward.
The reality is that we now operate technology in an ubiquitously connected environment, from employees and contractors to customers, partners, and even frenemies. Supporting this capability in a reliable and secure manner requires a modern technology infrastructure and set of capabilities that are just too complex or expensive to deliver using older technology and architectural models.
By Rob Giseburt
This is the third part of a series about using SSH with bastion hosts. You may wish to read the other parts if you haven’t already:
SSH Connection Multiplexing
If you might be opening multiple connections through the bastion host, either to a single machine or to multiple machines, it’s possible to use “connection multiplexing” to share the same connection to the bastion host as a transport to many ssh connections. This saves both resources and time establishing new connections. For a more in-depth discussion of connection multiplexing, look here.
By Rob Giseburt
A Bastion host is a special purpose computer on a network specifically designed and configured to withstand attacks. The computer generally hosts a single application, for example a proxy server, and all other services are removed or limited to reduce the threat to the computer. It is hardened in this manner primarily due to its location and purpose, which is either on the outside of the firewall or in the DMZ and usually involves access from untrusted networks or computers.
By Alden Hart
CTO and Managing Director
Recently I gave a talk to a group of CTOs about Agile development, something the development shops I’ve worked in have been doing one way or another since before Agile got labeled and got its own Manifesto. It was going to be difficult to bring something to this group that they didn’t already know, so I did a lot of research beforehand.
The literature review dusted off some real gems. For one, the term “Scrum” was first used by a couple of Japanese authors to describe the way Toyota designed cars – circa 1986. But before that was Frederick Brooks’ The Mythical Man-Month which contains a wealth of best practices (1975), and before that Kelly Johnson’s 14 Rules and Practices from the Lockheed Skunkworks. That’s how they iterated supersonic hardware in the 1950’s.