InfoWorld recently published “10 dumb security mistakes sys admins make” by Fahmida Y. Rashid. In that article, Rashid outlines “10 common security blunders made by sys admins and other IT staff.

In reading it, we quickly saw that the Kubisys Platform actually prevents three of these pressing issues. Let’s consider each issue and how our Platform eradicates the problem at its core.

How Our Test Environment Solution Prevents “Leaving Troubleshooting Tasks in Place”

Rashid writes, “When troubleshooting, you perform various tricks and experiments to find and fix the problem. As you make these attempts, you tend to bypass the usual processes. The problem comes when you fix the problem and move on to the next fire. Admins in a hurry may forget and leave things in disarray — and open to potential abuse …. When troubleshooting, keep track of what you do as you go, so that afterward you can restore configurations to their original settings — except for the changes you really needed to make.”

The Kubisys Platform offers developers and QA testers a fast way to spin up accurate test environments with full configuration data. Troubleshooting can be done within the test environment instead of subjecting the production environment to risky behavior or “leaving things in disarray.”

How the Kubisys Platform Prevents “Failing to Keep Track of Log Files”

Rashid writes, “The last thing you want to do is leave debugging on and generate log files containing information that may be useful to attackers. As a best practice, always keep track of what logs are created and know what kind of information is in them.”

Kubisys Platform test environments allow users to enable logging at varying levels of granularity across multiple servers in order to identify potential issues. Based on those logs, administrators can take corrective action which could be considered too risky to do on production. Once the problem is resolved, the fixes can then be implemented in production. Since the logs are generated within the Kubisys environment, no production settings are touched. Consequently, when the problem is resolved, the troubled application environment can be released, removing the potential for erroneous settings to be left on or propagated to production. Furthermore, using the Kubisys Platform lessens the need for production server resources like storage and memory set aside for debugging needs.

How Kubisys Test Environments Prevent “Being Lax About Patches”

Rashid writes, “Too many servers are compromised not because of a zero-day exploit, but because a year-old patch was never installed. Even if it’s a critical server, a little downtime as part of a scheduled maintenance window is far better than losing hours and days because attackers successfully compromised the box …. In real life, patching can be a political quagmire. If a manager who outranks you prevents a system from being patched, make sure everyone understands the risks of failing to do so.”

Failing to patch can result in an avalanche of negative outcomes, from downtime to lost revenue to overtime. By deploying a Kubisys Test Environment—which can be used for both on-premise, cloud and hybrid workflows—a developer or QA tester can test a patch before applying the patch to production. In other words, they’ll be able to witness whether a patch will negatively affect a legacy system within a secure environment that’s firewalled from production. This is also helpful in showing “a manager who outranks you” how disastrous going without a patch could be for the company.

IT security is an ever-growing concern for CEOs, CIOs, developers, and IT staff, but with a test environment tool like the Kubisys Platform, those concerns can be significantly decreased—if not prevented altogether.

Share This