Concerned about ever growing list of DevOps tools

1

• Concerned about ever growing list of DevOps
  tools?
• The list of functions and tools to perform end to
  end DevOps is increasing all the time. The
  following are list of some of the key functions
  and tools.
• Code Quality Tools SonarQube, FxCop, Checkstyle,
  Coverity Packaging Artifacts Management
  Nuget, Artifactory, VSTS Containerization
  Docker, Kubernetes, AKS, ECS1
• Infrastructure Kaiburr, Ansible, TerraForm,
  Cloud formation and JSON Database Lifecycle
  Management Redgate, Flyway, Liquibase, Datical
• Scripting Languages/Frameworks PowerShell, Ruby,
  Python, Groovy, Shell Scripting Test Automation
  Selenium, VSTS, Cucumber, Serverspec, Test
  Kitchen, RSpec Monitoring Datadog, cloudwatch,
  App insight, Splunk, New Relic, Sciencelogic
  Visualization Tableau, PowerBI
• ALM, Collaboration Tools JIRA, TFS, VSTS, Rally,
  SharePoint, Confluence, Slack Config Management
  Ansible ,Chef, Puppet and Powershell DSC
• Logging Splunk, OMS and ELK Unit Test Xunit,
  Junit and KarmaJS Release Orchestration Kaiburr
• The engineers are challenged with learning these
  tools and integrating them into their release
  processes while also focusing on the core product
  development.
• Engineering teams need the following -
• Ability to select the various tools that make up
  their tool chain.
• Create profiles for various tool chains and their
  configurations.
• Seamlessly apply these profiles for various
  application environments.
• All of the above are possible with tools like
  Kaiburr. Kaiburr unifies and simplifies the
  entire DevOps tool chain so product and
  engineering teams can rapidly implement CI-CD
  pipelines for their software products and
  applications. Product teams can now set up fully
  automated releases and CI-CD pipelines in weeks
  using Kaiburr and its orchestration platform.

2

• How to enable DevSecOps in your organization?
• The purpose and intent of DevSecOps is to build
  on the mindset that "everyone is responsible for
  security" with the goal of safely distributing
  security decisions at speed and scale to those
  who hold the highest level of context without
  sacrificing the safety required.
• Organizations have understood the need for
  continuous security not just in a production
  environment but starting from development and
  testing environments. Some of the key DevSecOps
  functions are listed below -
• Vulnerability Management scanner, e.g., Nessus,
  Rapid7
• Code analysis tools, e.g., Veracode, Checkmarx,
  Coverity, Black Duck
• Runtime Application Self Protection (RASP)
  tools, e.g., Immunio, Veracode
• Monitoring, compliance validation and reporting,
  e.g., evident.io
• CI security framework for automated testing,
  e.g., Gauntlt, OWASP ZAP
• Automation tool for acceptance testing, e.g.,
  Beaker (Puppet)
• Dynamic code analysis, e.g., Burpsuite
• Machine data analytics, e.g., Splunk
• Automation of security, e.g., Chef, Puppet,
  Ansible
• Security compliance reporting, e.g., Twistlock

3

• Data masking and redaction
• Vulnerability and pen testing platform, e.g.,
  Metasploit
• It is imperative to have the following -
• Ability to define security requirements at the
  organization level based on application type
• A plug and play mechanism to apply the security
  requirements for each application
• If the above two are not in place and available
  in a fully automated manner then it is extremely
  difficult for engineering teams to enable
  continuous security and keep up with the changing
  needs. This can become a very arduous task if
  not implemented with ease of definition and
  enforcement in mind.
• Kaiburr provides a simple, easy to use interface
  to select various DevSecOps tools, create
  different security profiles for various kinds of
  applications (like web app, data app) and apply
  them to CI-CD process of various applications
  seamlessly. Application teams can now implement
  DevSecOps in weeks instead of months of effort
  without tools like Kaiburr.
• Reach us at contact_at_kaiburr.com to know more
  about how we have enabled DevSecOps across
  different organizations.

4
(No Transcript)
5
(No Transcript)