From the Blogosphere
Rugged DevOps | @DevOpsSummit #DevOps #Microservices #ContinuousDelivery
Critical reading for DevOps or DevOpsSec
By: Derek Weeks
Mar. 18, 2016 07:00 PM
"The big problems are where people don't realize they have one in the first place." - Edward Deming, patron saint of DevOps.
Clarity on a Big Problem
Manually reviewing every component you desire to download and use is out of the question... nobody has the time or resources for that. To do it right, would require dedicating 2 - 4 hours of research per component - and your organization consumes thousands of unique components each year.
There is an easier (and free) way to understand if your repository contains components with known security vulnerability or license risks. Every one of the 60,000 active Nexus repository manager installations out there comes with a feature called the Repository Health Check. If you have a big problem, the health check will let you know; if your repo is free of vulnerable and risky components, you will learn that too.
Guarding the Front Door, The House, and Back Door
Protecting the Inside - We often say that components age like milk and not wine. Yes, we all understand that a component that is good today, may go bad tomorrow. Therefore, you can continue to use the Repository Health Check reports to automatically audit your repositories for any changes over time.
Protecting the Back - Additionally, for those of you utilizing staging repositories in your configurations, Nexus Firewall can help analyze your release candidates. The staging suite (available in the commercial version of Nexus Repository) allows an organization to create a temporary staging repository and to manage the promotion of components from a staging repository to a release repository. This ability to create an isolated, release candidate repository that can be discarded or promoted makes it possible to support the decisions that go into certifying a release. This enables you to better control the exact set of binaries that will ultimately be released.
When coupled with the Nexus Firewall solution, every component in the staging repository can be assessed for known security vulnerabilities, outdated/undesirable versions, or risky licenses. Used in this manner, Nexus Firewall not only protects your front door upon initial download of the components, it also guards your back door prior to releases going out.
Solving Big Problems
We all have a software supply chain that feeds components into our repository managers and application development lifecycles. With better visibility to the components we are using, we can all deliver better software, even faster.
While this story covers only one aspect of Rugged DevOps, there is much more to be learned about the subject. One of the best papers I have read recently comes from Amy DeMartine and Kurt Bittner at Forrester Research, entitled "The Seven Habits Of Rugged DevOps: Strengthen Cybersecurity Using DevOps Culture, Organization, Process, And Automation" (registration is required to download, but it's worth it).
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week