devopsy.kinsta.cloud

Tag: tripwire

  • Tripwire for DevOps SaaS Debuts – The first dynamic container vulnerability assessment service for the DevOps Pipeline

    Now generally available, Tripwire’s DevOps SaaS provides security assessments as part of the continuous integration/continuous deployment (CI/CD) pipeline

    PORTLAND, Ore. – August 08, 2018 – Tripwire, Inc., a leading global provider of security and compliance solutions for enterprises and industrial organizations, today announced the debut of Tripwire® for DevOps. After pre-releasing DevOps capabilities in an early access program earlier this year, Tripwire has launched Tripwire for DevOps as a generally available software-as-a-service (SaaS) solution.  Tripwire for DevOps integrates security assessments into the DevOps life cycle and toolchain, providing visibility into the security state of underlying application infrastructure throughout the pipeline.

    Complementing application and source code analysis tools, Tripwire for DevOps assesses container images and container registries for vulnerabilities, with additional features, such as the ability to assess configurations for compliance with security policies, in near-term release. It integrates with the CI/CD pipeline to ensure components meet security standards as they move through build and deploy DevOps stages.

    “As organizations move their application and service deployment to a DevOps model, it’s vital that they integrate security into the actual process,” said Tim Erlin, vice president of product management and strategy at Tripwire. “In addition to securing custom code, businesses need to ensure that the application infrastructure and inherited code remain secure throughout the life cycle. We’re excited to introduce a solution that embodies what’s been referred to as ‘DevSecOps,’ true integration of security into the DevOps workflow.”

    Tripwire for DevOps fully automates the assessment of container images in the CI/CD pipeline and can dynamically test live instances of application containers in an isolated, cloud-based sandbox. It can be used to establish quality gates at each stage to fail builds that don’t meet defined security standards. It can also be used to simply monitor and assess repositories, providing visibility of potential risk without interfering with the roll-out process.

    In a report, Gartner analysts said, “Traditional application security testing relies on heavyweight, one-time gating inspections, typically performed during testing, taking days if not weeks and requiring security professionals to perform them. This won’t work and it won’t scale for DevSecOps. DevOps emphasizes continuous feedback and improved automation. Security needs to adopt and support a mindset where security starts at the very beginning of the service creation, throughout the DevOps processes, and is continuous, automated and improves with each subsequent iteration.”[1]

    Simplifying deployment and set-up, Tripwire for DevOps is a fully self-contained SaaS solution that features:

    • Integration with popular DevOps CI/CD build tools, including Jenkins, & TeamCity, with additional tools coming soon.
    • Compatibility with all Docker v2 repositories for container assessment.
    • A complete REST API and command line interface for DevOps engineers to write custom integrations.

    For more information please visit: https://www.tripwire.com/products/tripwire-for-devops

    About Tripwire

    Tripwire is a leading provider of integrity assurance solutions that improve security, compliance and IT operations in enterprises, industrial organizations, service providers and government agencies. Tripwire solutions are based on high-fidelity asset visibility and deep endpoint intelligence combined with business context; together, these solutions integrate and automate security and IT operations. Tripwire’s enterprise-class portfolio includes file integrity monitoring, configuration management, asset discovery, vulnerability management and log collection that supports all widely used industry-standard frameworks.

    Learn more at https://www.tripwire.com/get security news, trends and insights at www.tripwire.com/blog, or follow us on Twitter @TripwireInc.

  • Tripwire Debuts Early Access Program for Container Analyzer Service

    Security solution expands vulnerability visibility across DevOps life cycle

    PORTLAND, Ore. – April 16, 2018 – Tripwire, Inc., a leading global provider of security and compliance solutions for enterprises and industrial organizations, today announced the debut of its Container Analyzer Service. This DevOps solution for scanning vulnerabilities in the build phase is now available for beta customers.

    The early access program for Tripwire’s Container Analyzer Service now embeds security at the beginning of the DevOps process. During the build phase, it can be used to perform complete vulnerability analysis of Docker images, systematically approving images or preventing further use of them.

    “With the new Container Analyzer Service, Tripwire helps address security needs throughout the entire DevOps life cycle – from build to production,” said Tim Erlin, vice president of product management and strategy at Tripwire. “It’s critical that security controls work at the speed of DevOps, and we’re excited to provide security teams with the tools that help them address the continuous and rapid release of new applications and services.”

    Images are built earlier in the DevOps process and are the basis for building a container – a runtime instance of an image. The Container Analyzer Service combines with continuous integration (CI) and continuous deployment (CD) tools to perform vulnerability scanning at each layer of the Docker image.

    This new capability builds upon Tripwire’s existing capabilities for scanning online, offline and non-running Docker containers later in the DevOps life cycle. Scanning for vulnerabilities throughout the life cycle is important as change happens frequently and rapidly through the DevOps process.

    In addition to delivering this enhanced visibility into vulnerabilities, Tripwire also provides integration with the DevOps toolchain for initiating scans, securing the build pipeline infrastructure, and monitoring for changes throughout the continuous deployment life cycle.

    To learn more about the early access program for Tripwire’s Container Analyzer Service, please visit: https://www.tripwire.com/solutions/container-security/container-analyzer-service/

    About Tripwire

    Tripwire is a leading provider of integrity assurance solutions that improve security, compliance and IT operations for enterprises, industrial organizations, service providers and government agencies. Tripwire solutions are based on high-fidelity asset visibility and deep endpoint intelligence combined with business context; together, these solutions integrate and automate security and IT operations. Tripwire’s enterprise-class portfolio includes file integrity monitoring, configuration management, asset discovery, vulnerability management and log collection that supports all widely used industry-standard frameworks.

    Learn more at www.tripwire.com get security news, trends and insights at www.tripwire.com/blog, or follow us on Twitter @TripwireInc.

    Contact:

    Tripwire, Inc.

    Ray Lapena, +1 714-624-8862

    PR Manager

    rlapena@tripwire.com

     

  • Busting The 4 Biggest DevOps Security Myths

    Busting The 4 Biggest DevOps Security Myths

    Last month when the IT security world convened in San Francisco for the annual RSA confab, a number of security experts tackled DevOps in talks that covered the crossover between continuous improvement and risk management. Among them was a lively panel mythbusting some of the most prevalent misconceptions about DevOps held by the security community.

    Moderated by Dwayne Melancon of Tripwire, the panel was made up of Josh Corman, CTO of Sonatype, Nick Galbreath, vice president of engineering at IPONWEB, Gene Kim, author of The Phoenix Project, and David Mortman chief security architect and distinguished engineer for Dell Enstratius, all of them security professionals and very active DevOps evangelists. The banter backed-and-forthed between the participants, with four myths bubbling to the surface as particular highlights from the discussion.

    Myth #1: DevOps Pace Will Leave Security In The Dust

    One of the most prevalent myths about DevOps within the security community is that the rapid deploys of the approach will throw all risk management precautions to the wind and leave security practices behind as a result. Quite the contrary, panelists argued. They believe that DevOps patterns make it more possible than ever to bake security practices into IT processes more than before, when it is frequently bolted on “at the end of the caboose,” as Galbreath puts it.

    “You’re not throwing out your current security system,” he said. “What you’re doing is removing a lot of the junk work that eats up so much time and keeps people underwater. You’re really enabling different teams to all improve security together.”

    As Corman explained, security people say all the time that complexity is the enemy of security.

    “It also happens to be the enemy of stability,” he said. “That is the reason DevOps people come willingly with open arms to the security community.”

    Not to mention, Kim added, “because you can’t be highly available and have stuff coming continuously through the pipeline if it is not secure.

    Myth #2: DevOps Destroys Compliance And Control Frameworks

    This myth came up during the audience Q&A portion of the panel, where one audience member from the financial industry wondered at how possible it would be to institute DevOps in a highly regulated industry. According to Mortman, as seemingly chaotic and fast-and-furious as the DevOps pace can seem to the uninitiated, it is actually far more process-oriented than people realize.

    “People say ‘Oh, there’s no process to this.’ But it is actually very process oriented,” he said. “It’s just not very bureaucracy-oriented. There’s not a lot of paperwork. In its very guts, it is very service-oriented and very delivery-oriented.”

    As he puts it, every compliance framework in the planet says you need to log, audit and approve changes. But none of them stipulate a workflow where each change has to be approved one at a time.

    “The workflow can be ‘Please approve the following list of actions that I can do without notifying you first,’” he explained, “and as long as you have an audit trail showing that that has been done properly, I have yet to meet an auditor who will not buy into that.”

    Myth #3: DevOps Gives Developers Too Much Power

    Many dyed-in-the-wool security pros fear DevOps because they believe it is a cowboy environment that gives developers too much power.

    “I’ll be honest, when i first started observing DevOps patterns, developers doing their own deploys seemed immoral to me; irresponsible, reckless, just shouldn’t be done,” Kim said. “No sane person would want to be associated with that, right?”

    The thing was, after Kim dove in and also did a benchmark study with Tripwire several years ago across 4,000 organizations, he found that when comparing groups where ops did the deploys to those where developers shepherded code through deploys, change success rates and mean time to repair were not adversely affected, and in fact, “it is often considered indispensible that developers take code all the way through the deployment pipeline and you know they are getting great outcomes.”

    And from a security controls perspective, the truth is that in a DevOps situation developers “are not logging individually into each server and SSH’ing the code up, untarring it and installing it,” Mortman said. Instead these actions are being done by automated systems.

    “They’re actually going to give you much better timestamps, much more accuracy, and more consistent results and visibility than a manual process being done by someone in ops,” Mortman said. “So, actually, you’re getting better change management out of that system than you are in other situations.”

    Myth #4: DevOps Cuts Important Testing

    One discussion point also brought up during audience Q&A was the possibility that DevOps would somehow excise important testing functionality from the IT process. The panel quickly put that one to bed.

    “You can do bad testing in any model,” Corman said. “If DevOps starts eliminating any kind of testing, its a bad DevOps program. I think that’s orthogonal to some of the benefits or opportunities of DevOps.”

    Kim pointed to Google as an example of how testing fits into the DevOps methodology.

    “So, Google does about 5,500 code commits per day, they have about 15,000 software engineers, and 75 million hours of testing is run each day,” he said. “You can’t get that massive amount of deployment frequencies without a tremendous amount of testing.”