Presentation from the Sydney AWS Security Meetup - August 10, 2017.
https://www.meetup.com/Sydney-AWS-Security-User-Group/events/239370748/
Automating Compliance with InSpec - AWS North SydneyMatt Ray
Automating Compliance with InSpec provides a concise summary of how InSpec can be used to automate compliance testing across operating systems and applications. InSpec uses a single language to test configuration across Linux, Windows, databases and cloud platforms. It can test infrastructure as code, servers, containers and APIs. InSpec is open source and supported by Chef.
DevOpsDays Singapore - Continuous Auditing with Compliance as CodeMatt Ray
This document discusses using Chef Automate to enable continuous compliance through a three step process of detecting issues, correcting problems, and automating compliance. It notes that many organizations currently assess compliance inconsistently or after deploying code to production. Chef Automate allows detecting and correcting issues across infrastructure in a single platform using the same language for both DevOps and InfoSec teams. This enables deploying applications with confidence while maintaining security and compliance.
Habitat is an open source application automation platform that allows development and operations teams to build, deploy, and manage any application on any infrastructure. It implements automation best practices like immutable infrastructure, declarative deployments, and configuration as code. Habitat provides tools for building packages, running services, and managing applications across platforms in a standardized way. The Habitat community is open source and supports many languages and platforms.
The document discusses remediating compliance issues by writing a remediation recipe on the target node to update the SSH version. It describes testing the recipe locally using Kitchen, verifying compliance with InSpec from the CLI, converging the recipe, and rescanning the node to ensure compliance. Key steps include generating a cookbook and server recipe for SSH, creating an SSH config template, updating the template, deploying locally, and re-running the compliance scan to show the issue is now resolved.
The document discusses Habitat, an open source tool for automating the packaging, deployment, and management of applications. It describes how Habitat packages applications and all of their dependencies into artifacts called "packages" that can run on any Linux system. It also explains how Habitat uses supervisors to deploy packages, form service groups, and provide update strategies and REST APIs for managing applications in a continuous delivery model.
This document provides an agenda for a Chef Hack Day event hosted by Trace3 on April 26, 2016. The agenda includes times for lunch, welcome/kick-off, hacking sessions, and demo/wrap-up periods throughout the day. Guidelines are also listed for the hack day projects, encouraging teams to track work, share demonstrations, ask for help, be open to learning, and have fun. Suggested hack day project ideas include using InSpec to verify CIS Benchmarks and scanning/remediating with Chef Compliance.
Chef Automate provides a full-stack collaboration platform to help organizations achieve DevOps success by managing infrastructure, containers, applications, and compliance through automation. It addresses barriers to DevOps adoption like disparate tooling and lack of skills/cultural adoption. New capabilities in Chef Automate and Compliance accelerate and de-risk adoption by providing automation, governance, and compliance as code.
The document describes a conference agenda for ChefConf. It includes workshops, keynotes, technical sessions, and social events. It also discusses challenges faced by organizations around manual processes, legacy systems, silos, and infrequent releases. Finally, it outlines how Chef's tools and practices around automation, dynamic infrastructure, DevOps workflows, and continuous delivery can help address these challenges.
This document summarizes a Chef Automate demo. It includes:
1) An example of an InSpec test to check the umask setting on a Linux system.
2) An overview of using infrastructure as code with Chef to install and configure Apache on Linux, explaining how to write code to install packages, configure templates, and manage services.
3) A description of the workflow for testing code changes, including linting, unit testing, provisioning, deployment, and functional testing before approval and delivery.
4) An overview of the Chef Automate subscription model including premium features, support, and access to compliance and infrastructure automation content.
Chef Delivery provides a unified workflow for software development with fixed stages and phases for approving and delivering code changes. It ensures high velocity, safety, and visibility through automation of infrastructure as code, testing, and deployment. The shared pipeline can be used across projects and teams.
Here are the steps to run a compliance scan:
1. Click the checkbox next to your node.
2. Select the "cis-3.1" profile from the dropdown menu.
3. Click the "Scan Now" button.
4. The scan will run and you'll see the status change to "Scanning".
5. Once complete, the status will change to "Compliant" or "Non-Compliant" and you can view the detailed results and any failures/warnings.
Let me know if you have any other questions!
Automating Compliance with InSpec - Chef Singapore MeetupMatt Ray
July 24, 2017 slides and demo for Automating Compliance with InSpec. The associated GitHub repository is here: https://github.com/mattray/inspec-workshop
This document introduces Jon Aykroyd, an automation engineer with over 10 years of experience in Linux systems administration and automation. It provides an overview of Jon's background and role in helping organizations transition to DevOps practices. The document also shares a case study of how introducing Chef automation tools helped a clothing retailer reduce time-to-deployment from 2 weeks to just 2 hours. It closes with some details about Jon's initial work helping his own organization transition to Chef from various other tools and scripts.
The document provides instructions for installing Chef Compliance as a standalone server. It includes steps to SSH into the server node, download and install the Chef Compliance package, use chef-compliance-ctl to configure the server, and launch the Compliance web UI. The group lab has participants complete these installation and initial configuration tasks together by SSHing into the provided server node, downloading the appropriate RPM package, installing it using rpm, and configuring the server and web UI through the browser.
InSpec is an open source testing framework for infrastructure with a human-readable language for specifying compliance, security, and other policy requirements. Easily integrate automated tests that check for advherence to policy into any stage of your deployment pipeline.
Compliance Automation with InSpec - Chef NYC Meetup - April 2017adamleff
Presented at the Chef NYC meetup on April 20, 2017, this presentation reviews how to automate compliance scanning and reporting with InSpec by Chef and wrapped up with a hands-on workshop.
This document discusses how Chef configuration management is used centrally at Sky Betting and Gaming to provide tools and services for developers to deploy applications. It describes how the Platform Services team started by "fixing disaster recovery" and introduced Chef. Key aspects of their process include using Chef configuration for infrastructure, applications, CI pipelines, and integration tests. The document also outlines their use of a tool called pscli, which acts as "glue" by pulling Docker images containing tools like ChefDK, Terraform, and Packer and executing commands in containers to perform tasks like generating cookbooks, running Kitchen tests, and applying Terraform configurations.
This document provides an overview and introduction to Chef Compliance. It describes the capabilities and value of Chef Compliance, how to configure the Chef Compliance server, perform scans, remediate issues, and schedule reports. It also discusses using InSpec to create and test Chef Compliance profiles. The objectives are to describe Chef Compliance, configure the server, perform scans, remediate issues, schedule reports, and use InSpec.
This document provides an overview of using Chef and Azure to build next-generation infrastructure. It discusses key Azure services, deploying a Chef server in Azure, integrating Chef with the Microsoft ecosystem, and migrating and automating workloads across on-premise, Azure, and hybrid environments. The lab guides users through deploying a Chef server in Azure, configuring it, and cloning a sample cookbook to manage infrastructure as code.
Chef Automate provides automation capabilities across infrastructure, applications, and compliance. It allows organizations to build, deploy, and manage applications and infrastructure with consistency and security. Chef Automate offers workflow automation to establish continuous delivery pipelines, visibility into operational events, and compliance automation to embed security and compliance checks into the software development lifecycle. This allows organizations to achieve compliance at high velocity alongside continuous delivery of code changes.
Adding Security and Compliance to Your Workflow with InSpecMandi Walls
This document provides an overview of InSpec, which is a tool for creating automated tests for compliance and security. InSpec allows users to write tests in a human-readable language to check systems for vulnerabilities or configuration issues. It can test infrastructure locally or remotely. Profiles can be created to package and share test suites. InSpec integrates with tools like Test Kitchen and can be included in development workflows to continuously test systems.
InSpec can be used to automate security and compliance testing by translating compliance policies into code. This allows organizations to find issues early in the development process and continuously test configurations as code is built, tested, and deployed. The document discusses adding nodes to scan from the Chef Compliance dashboard, running compliance scans using built-in profiles, and viewing scan results to identify compliant and non-compliant controls. It also provides instructions for running InSpec tests directly from the command line locally or against remote systems using SSH or Docker.
1. Habitat consists of several components including Habitat Studio for packaging applications, Habitat Plans for instructions to install applications, and Habitat Depot for uploading and downloading application packages.
2. The packaging process starts with creating a Plan which defines how to build an application from source code using Bash. The built package is then uploaded to the Depot.
3. At runtime, the Habitat Supervisor manages application behavior using the predefined Plan. It provides service discovery, deployment coordination, and a REST API for management.
The document discusses the internals and architecture of the Nginx web server. It covers Nginx's event-driven and non-blocking architecture, its use of memory pools and data structures like radix trees, how it processes HTTP requests through different phases, and how modules and extensions can be developed for Nginx. The document also provides an overview of Nginx's configuration, caching, and load balancing capabilities.
This document provides an introduction and overview of Chef Compliance capabilities and objectives. It describes how to perform scans with Chef Compliance, remediate compliance issues, and use InSpec to create and test compliance profiles. The document outlines the lab environment and steps to configure the Chef Compliance server, add nodes to scan, run compliance scans, view scan results, and remediate identified issues.
This document provides steps for writing your first cookbook in Chef to configure a web server node. It explains that a cookbook contains the components needed to define a scenario like installing and configuring an HTTPD server. The key steps are to create a cookbook, add a recipe, upload it to the Chef server, configure the node's run list, and run chef-client on the target node. The document walks through writing a sample cookbook recipe to install httpd, start the service, and copy an index.html file. It demonstrates uploading and testing the cookbook on a node.
Melbourne Chef Meetup: Automating Azure Compliance with InSpecMatt Ray
June 26, 2017 presentation. With the move to infrastructure as code and continuous integration/continuous delivery pipelines, it looked like releases would become more frequent and less problematic. Then the auditors showed up and made everyone stop what they were doing. How could this have been prevented? What if the audits were part of the process instead of a roadblock? What sort of visibility do we have into the state of our Azure infrastructure compliance? This talk will provide an overview of Chef's open-source InSpec project (https://inspec.io) and how you can build "Compliance as Code" into your Azure-based infrastructure.
DevSec Delight with Compliance as Code - Matt Ray - AgileNZ 2017AgileNZ Conference
For too long, audits and security reviews have been seen as resistant to the frequent release of software. Auditors require access to static systems and environments, which would seem to make continuous delivery impossible. Too frequently audits are a fire drill sampling of the current state and temporary fixes are put in place to appease the compliance audit without being integrated into future releases.
About Matt Ray:
Matt Ray is the Manager and Solutions Architect for Asia Pacific and Japan for Chef. He has worked in large enterprise software companies and founded his own startups in a wide variety of industries including banking, retail and government.
He has been active in open source communities for over two decades and has spoken at, and helped organise, many conferences and Meetups. He currently resides in Sydney, Australia after relocating from Austin, Texas. He podcasts at SoftwareDefinedTalk.com, blogs at LeastResistance.net and is @mattray on Twitter, IRC, GitHub and too many Slacks.
The document describes a conference agenda for ChefConf. It includes workshops, keynotes, technical sessions, and social events. It also discusses challenges faced by organizations around manual processes, legacy systems, silos, and infrequent releases. Finally, it outlines how Chef's tools and practices around automation, dynamic infrastructure, DevOps workflows, and continuous delivery can help address these challenges.
This document summarizes a Chef Automate demo. It includes:
1) An example of an InSpec test to check the umask setting on a Linux system.
2) An overview of using infrastructure as code with Chef to install and configure Apache on Linux, explaining how to write code to install packages, configure templates, and manage services.
3) A description of the workflow for testing code changes, including linting, unit testing, provisioning, deployment, and functional testing before approval and delivery.
4) An overview of the Chef Automate subscription model including premium features, support, and access to compliance and infrastructure automation content.
Chef Delivery provides a unified workflow for software development with fixed stages and phases for approving and delivering code changes. It ensures high velocity, safety, and visibility through automation of infrastructure as code, testing, and deployment. The shared pipeline can be used across projects and teams.
Here are the steps to run a compliance scan:
1. Click the checkbox next to your node.
2. Select the "cis-3.1" profile from the dropdown menu.
3. Click the "Scan Now" button.
4. The scan will run and you'll see the status change to "Scanning".
5. Once complete, the status will change to "Compliant" or "Non-Compliant" and you can view the detailed results and any failures/warnings.
Let me know if you have any other questions!
Automating Compliance with InSpec - Chef Singapore MeetupMatt Ray
July 24, 2017 slides and demo for Automating Compliance with InSpec. The associated GitHub repository is here: https://github.com/mattray/inspec-workshop
This document introduces Jon Aykroyd, an automation engineer with over 10 years of experience in Linux systems administration and automation. It provides an overview of Jon's background and role in helping organizations transition to DevOps practices. The document also shares a case study of how introducing Chef automation tools helped a clothing retailer reduce time-to-deployment from 2 weeks to just 2 hours. It closes with some details about Jon's initial work helping his own organization transition to Chef from various other tools and scripts.
The document provides instructions for installing Chef Compliance as a standalone server. It includes steps to SSH into the server node, download and install the Chef Compliance package, use chef-compliance-ctl to configure the server, and launch the Compliance web UI. The group lab has participants complete these installation and initial configuration tasks together by SSHing into the provided server node, downloading the appropriate RPM package, installing it using rpm, and configuring the server and web UI through the browser.
InSpec is an open source testing framework for infrastructure with a human-readable language for specifying compliance, security, and other policy requirements. Easily integrate automated tests that check for advherence to policy into any stage of your deployment pipeline.
Compliance Automation with InSpec - Chef NYC Meetup - April 2017adamleff
Presented at the Chef NYC meetup on April 20, 2017, this presentation reviews how to automate compliance scanning and reporting with InSpec by Chef and wrapped up with a hands-on workshop.
This document discusses how Chef configuration management is used centrally at Sky Betting and Gaming to provide tools and services for developers to deploy applications. It describes how the Platform Services team started by "fixing disaster recovery" and introduced Chef. Key aspects of their process include using Chef configuration for infrastructure, applications, CI pipelines, and integration tests. The document also outlines their use of a tool called pscli, which acts as "glue" by pulling Docker images containing tools like ChefDK, Terraform, and Packer and executing commands in containers to perform tasks like generating cookbooks, running Kitchen tests, and applying Terraform configurations.
This document provides an overview and introduction to Chef Compliance. It describes the capabilities and value of Chef Compliance, how to configure the Chef Compliance server, perform scans, remediate issues, and schedule reports. It also discusses using InSpec to create and test Chef Compliance profiles. The objectives are to describe Chef Compliance, configure the server, perform scans, remediate issues, schedule reports, and use InSpec.
This document provides an overview of using Chef and Azure to build next-generation infrastructure. It discusses key Azure services, deploying a Chef server in Azure, integrating Chef with the Microsoft ecosystem, and migrating and automating workloads across on-premise, Azure, and hybrid environments. The lab guides users through deploying a Chef server in Azure, configuring it, and cloning a sample cookbook to manage infrastructure as code.
Chef Automate provides automation capabilities across infrastructure, applications, and compliance. It allows organizations to build, deploy, and manage applications and infrastructure with consistency and security. Chef Automate offers workflow automation to establish continuous delivery pipelines, visibility into operational events, and compliance automation to embed security and compliance checks into the software development lifecycle. This allows organizations to achieve compliance at high velocity alongside continuous delivery of code changes.
Adding Security and Compliance to Your Workflow with InSpecMandi Walls
This document provides an overview of InSpec, which is a tool for creating automated tests for compliance and security. InSpec allows users to write tests in a human-readable language to check systems for vulnerabilities or configuration issues. It can test infrastructure locally or remotely. Profiles can be created to package and share test suites. InSpec integrates with tools like Test Kitchen and can be included in development workflows to continuously test systems.
InSpec can be used to automate security and compliance testing by translating compliance policies into code. This allows organizations to find issues early in the development process and continuously test configurations as code is built, tested, and deployed. The document discusses adding nodes to scan from the Chef Compliance dashboard, running compliance scans using built-in profiles, and viewing scan results to identify compliant and non-compliant controls. It also provides instructions for running InSpec tests directly from the command line locally or against remote systems using SSH or Docker.
1. Habitat consists of several components including Habitat Studio for packaging applications, Habitat Plans for instructions to install applications, and Habitat Depot for uploading and downloading application packages.
2. The packaging process starts with creating a Plan which defines how to build an application from source code using Bash. The built package is then uploaded to the Depot.
3. At runtime, the Habitat Supervisor manages application behavior using the predefined Plan. It provides service discovery, deployment coordination, and a REST API for management.
The document discusses the internals and architecture of the Nginx web server. It covers Nginx's event-driven and non-blocking architecture, its use of memory pools and data structures like radix trees, how it processes HTTP requests through different phases, and how modules and extensions can be developed for Nginx. The document also provides an overview of Nginx's configuration, caching, and load balancing capabilities.
This document provides an introduction and overview of Chef Compliance capabilities and objectives. It describes how to perform scans with Chef Compliance, remediate compliance issues, and use InSpec to create and test compliance profiles. The document outlines the lab environment and steps to configure the Chef Compliance server, add nodes to scan, run compliance scans, view scan results, and remediate identified issues.
This document provides steps for writing your first cookbook in Chef to configure a web server node. It explains that a cookbook contains the components needed to define a scenario like installing and configuring an HTTPD server. The key steps are to create a cookbook, add a recipe, upload it to the Chef server, configure the node's run list, and run chef-client on the target node. The document walks through writing a sample cookbook recipe to install httpd, start the service, and copy an index.html file. It demonstrates uploading and testing the cookbook on a node.
Melbourne Chef Meetup: Automating Azure Compliance with InSpecMatt Ray
June 26, 2017 presentation. With the move to infrastructure as code and continuous integration/continuous delivery pipelines, it looked like releases would become more frequent and less problematic. Then the auditors showed up and made everyone stop what they were doing. How could this have been prevented? What if the audits were part of the process instead of a roadblock? What sort of visibility do we have into the state of our Azure infrastructure compliance? This talk will provide an overview of Chef's open-source InSpec project (https://inspec.io) and how you can build "Compliance as Code" into your Azure-based infrastructure.
DevSec Delight with Compliance as Code - Matt Ray - AgileNZ 2017AgileNZ Conference
For too long, audits and security reviews have been seen as resistant to the frequent release of software. Auditors require access to static systems and environments, which would seem to make continuous delivery impossible. Too frequently audits are a fire drill sampling of the current state and temporary fixes are put in place to appease the compliance audit without being integrated into future releases.
About Matt Ray:
Matt Ray is the Manager and Solutions Architect for Asia Pacific and Japan for Chef. He has worked in large enterprise software companies and founded his own startups in a wide variety of industries including banking, retail and government.
He has been active in open source communities for over two decades and has spoken at, and helped organise, many conferences and Meetups. He currently resides in Sydney, Australia after relocating from Austin, Texas. He podcasts at SoftwareDefinedTalk.com, blogs at LeastResistance.net and is @mattray on Twitter, IRC, GitHub and too many Slacks.
Melbourne Infracoders: Compliance as Code with InSpecMatt Ray
Presentation to the Melbourne Infrastructure Coders Meetup November 8, 2016. Overview of InSpec (https://inspec.io) and the idea of "Compliance as Code"
http://www.meetup.com/Infrastructure-Coders/events/233990769/
Compliance Automation with InSpec
InSpec is an open source testing framework for infrastructure with a human- and machine-readable language for specifying compliance, security, and policy requirements. Using a combination of command-line and remote-execution tools, InSpec can help you keep your infrastructure aligned with security and compliance guidelines on an ongoing basis, rather than waiting for and then remediating from arduous annual audits. InSpec’s flexibility makes it a key tool choice for incorporating security into a complete continuous delivery workflow, reducing the risk of new features and releases breaking established host-based security guidelines. This talk covers the basics of working with InSpec, writing tests to reflect your organization’s security guidelines, and managing InSpec as part of a high-velocity workflow.
Chef Automate - Infracoders Canberra August 8, 2017Matt Ray
Slides from the overview and demo of Chef Automate from Canberra Infracoders.
https://www.meetup.com/Infrastructure-Coders-Canberra/events/241775704/
Compliance as Code with InSpec - DevOps Melbourne 2017Matt Ray
DevOps Melbourne Meetup March 28, 2017
PCI and auditors slowing you down? Compliance and security are the next steps in building your software-defined infrastructure. Chef's open-source project InSpec (https://inspec.io) and audit cookbooks provide an accessible pattern for building compliance into your continuous delivery pipelines.
Infrastructure and Compliance Delight with Chef AutomateMatt Ray
The document discusses Chef Automate, a platform for continuous automation, infrastructure automation, compliance automation, and application automation. It describes how Chef Automate can help increase development speed, improve efficiency, and decrease risk by defining infrastructure, applications, and compliance rules as code. It provides an example workflow of how Chef Automate can enable the continuous compliance process of scanning for compliance, building and testing locally and in CI/CD, remediating issues, and verifying compliance. Finally, it summarizes how Chef Automate supports the entire journey from detecting compliance issues to correcting them to automating continuous detection and correction.
Compliance as Code: Velocity with Security - Fraser Pollock, ChefAlert Logic
This document discusses mapping compliance documents to InSpec controls for auditing infrastructure. It provides an example of mapping a compliance control related to setting the SSH protocol to version 2. It demonstrates implementing this control in InSpec by defining a title, description, and test to check the SSH configuration file. It also shows how to run the InSpec control locally and remotely on infrastructure to automate compliance testing.
Chef Automate - Wellington DevOps August 2, 2017Matt Ray
Chef Automate is a platform that provides continuous automation for infrastructure, compliance, and applications. It allows users to define infrastructure, compliance policies, and application configuration as code. It also provides workflows to collaborate, build, deploy, manage, and secure automation through an integrated platform. Chef Automate utilizes open source automation engines and works with technology partners and AWS OpsWorks to provide these capabilities at scale across environments.
Presentation from Cloud Expo Asia Hong Kong covering the rationale for "Compliance as Code" and how InSpec may be applied to servers, cloud platforms, and much more to keep track of your compliance everywhere.
This document discusses challenges faced by organizations in managing their infrastructure and applications, and how Chef and related tools can help address those challenges. It outlines Chef's approach of treating infrastructure as code and using automation to enable continuous delivery of infrastructure and applications. This allows for faster innovation, better quality/compliance, and rapid time to value. Key aspects covered include infrastructure as code, automation of the development stack, enabling DevOps workflows, and integrating security and compliance into the software delivery pipeline.
Presentation to the Perth MS Cloud Computing User Group on November 14, 2017. Covered off on how Chef, InSpec, Habitat and Chef Automate work with Windows, Azure and the Microsoft ecosystem.
You've heard about Continuous Integration and Continuous Deilvery but how do you get code from your machine to production in a rapid, repeatable manner? Let a build pipeline do the work for you! Sam Brown will walk through the how, the when and the why of the various aspects of a Contiuous Delivery build pipeline and how you can get started tomorrow implementing changes to realize build automation. This talk will start with an example pipeline and go into depth with each section detailing the pros and cons of different steps and why you should include them in your build process.
Delivering High-Availability Web Services with NGINX Plus on AWSNGINX, Inc.
Over 1/3 of websites running on Amazon Web Services (AWS) are delivered and accelerated using NGINX. In this webinar Nginx and Amazon explain how to get started with NGINX Plus on AWS and how to further increase performance and availability of large, dynamic, cloud-based applications integrating with critical AWS services.
DevOps, Continuous Integration & Deployment on AWS discusses practices for software development on AWS including DevOps, continuous integration, continuous delivery, and continuous deployment. It provides an overview of AWS services that can be used at different stages of the software development lifecycle such as CodeCommit for source control, CodePipeline for release automation, and CodeDeploy for deployment. National Novel Writing Month (NaNoWriMo) maintains its websites and services on AWS to support its annual writing challenge. It migrated to AWS to improve uptime and scalability. Its future goals include porting older sites to Rails, using Amazon SES for email, load balancing with ELB, implementing auto scaling, and using services like CodeDeploy, SNS
Cfengine presentation at the RMLL 2010 in Bordeaux. This presentation focuses on the reasons for configuration management, and how Cfengine addresses this need.
Using Chef InSpec for Infrastructure SecurityMandi Walls
This document provides an overview of Chef InSpec and how it can be used for infrastructure security assurance. Chef InSpec allows users to create tests for security and compliance related to infrastructure and then run those tests on systems locally or remotely. The document demonstrates how to use Chef InSpec to check for compliance with a security baseline, remediate any issues found using Chef infrastructure automation, and then re-check compliance.
- What's Software Deployment
- A Minimal Python Web Application
- Trouble Shoot
- Interface between Web Server and Application
- Standardization/Automation/Monitoring/Availability
Open Source Summit NA 2024: Open Source Cloud Costs - OpenCost's Impact on En...Matt Ray
Discover how a leading enterprise achieved visibility into their cloud costs with the CNCF project OpenCost. OpenCost models current and historical Kubernetes cloud spend and resource allocation by service, deployment, namespace, labels, and much more. This data provides transparency for cloud bills and can be used as the basis for optimizing your Kubernetes deployments based on cost allocation. This session delves into the real-world journey of implementing OpenCost for tracking cloud costs and how they optimized their infrastructure with this information. We’ll start with an introduction to OpenCost, its capabilities, and how to get started as a user and as a contributor. Then we’ll explore the challenges faced, lessons learned, and the tangible impact observed. From initial deployment to ongoing management, learn how OpenCost empowered the enterprise to make data-driven decisions, avoid cost overruns, and streamline their cloud budgeting. Join us for practical insights, success stories, and actionable steps to harness the power of OpenCost in your enterprise.
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
KubeCon EU 2024 Lightning Talk
Understanding the cost and efficiency of Kubernetes on public clouds is essential once you start expanding your infrastructure with real production workloads. The FinOps Certified Solution and CNCF Sandbox OpenCost project monitors cloud costs and models current and historical Kubernetes cloud spend and resource allocation by service, deployment, namespace, labels, and much more. This data provides transparency for cloud bills and can be used as the basis for optimizing your Kubernetes deployments based on cost allocation. This quick introduction to OpenCost will start your foundation for monitoring and Kubernetes and cloud costs.
SCaLE 20X: Kubernetes Cloud Cost Monitoring with OpenCost & Optimization Stra...Matt Ray
Understanding the cost and efficiency of Kubernetes on public clouds is essential once you start expanding your infrastructure with real production workloads. The CNCF Sandbox OpenCost project and specification models current and historical Kubernetes cloud spend and resource allocation by service, deployment, namespace, labels, and much more. This data provides transparency for cloud bills and can be used as the basis for optimizing your Kubernetes deployments based on cost allocation. Optimizing Kubernetes for cost and performance is an ongoing iterative process that starts with applications and works through the entire stack.
HashiTalks 2020 - Chef Tools & Terraform: Better TogetherMatt Ray
This document discusses how Chef and Terraform can be used together for infrastructure automation and compliance. It provides overviews of Chef Infra, Chef Habitat, Chef InSpec, and how each integrates with Terraform. Key points include the Chef Provisioner and Provider for Terraform, the Habitat Provisioner, using Kitchen-Terraform for testing, and InSpec-Iggy for generating compliance profiles from Terraform configs. The document emphasizes that these tools can work better together for provisioning, deploying applications, and verifying infrastructure and security compliance as code.
EmacsConf 2019: Interactive Remote Debugging and Development with TRAMP ModeMatt Ray
Emacs’ TRAMP Mode allows for remotely editing files and using Emacs Shell Mode with remote systems. This session walked through the basics of using TRAMP Mode with the Free Software tools Vagrant, Chef, InSpec, and the interactive Ruby debugging shell Pry. The speaker notes are included along with the demo notes. The YouTube recording of the talk is available here: https://youtu.be/4pHid-kTBHw
Wellington DevOps: Bringing Your Applications into the Future with HabitatMatt Ray
This document discusses Habitat, an open source application automation platform from Chef that allows teams to build, deploy, and manage any application in any environment. Habitat addresses challenges like modernizing legacy applications to run in cloud-native environments and accelerating adoption of platforms like Kubernetes. It achieves application portability by separating platform-independent and dependent components and packaging applications immutably. Customers like a large automaker and agribusiness have used Habitat to modernize legacy apps and optimize their platform adoption efforts.
DevOps Days Singapore 2018 Ignite - Bringing Your Applications into the Futur...Matt Ray
Ignite talks are 20 slides auto-advancing every 15 seconds. This session attempts to share the value of migrating existing applications from legacy to modern platforms.
Cloud Expo Asia 20181010 - Bringing Your Applications into the Future with Ha...Matt Ray
What are we going to do about all these legacy applications? Kubernetes, Docker or Server Core? With Habitat it doesn’t matter anymore! As companies make the transition from traditional IT infrastructure to cloud-native container platforms packaging, deploying and managing applications becomes the focus for developers and operators. Having a consistent approach to managing dependencies and building applications brings stability to CI/CD pipelines and frees developers to prioritize on features. Automated, repeatable builds with immutable artifacts and consistent management of any application on any platform allow operators to focus on stability and speed. Chef's Habitat project brings all of this together in an open source automation platform that enables modern application teams to build, deploy, and run any application in any environment - from traditional data-centers to containerized microservices. This presentation provided an overview of the benefits of Habitat and a live demo of applications being built and deployed on traditional operating systems across Docker and Kubernetes, seamlessly.
Opening keynote for DevOpsDays Jakarta. I attempted to tie the themes of DevOps to a timeline of when they received increasing focus. Books on the subjects provided a convenient way to mark those times.
https://www.devopsdays.org/events/2018-jakarta/program/matt-ray/
DevOps Talks Melbourne 2018: Whales, Cats and KubernetesMatt Ray
Kubernetes, Docker or VMs? With Habitat it doesn’t matter anymore! As companies make the transition from traditional IT infrastructure to cloud-native container platforms packaging, deploying and managing applications becomes the focus for developers and operators. Having a consistent approach to managing dependencies and building applications brings stability to CI/CD pipelines and frees developers to prioritize on features. Automated, repeatable builds with immutable artefacts and consistent management of any application on any platform allow operators to focus on stability and speed. Meet Habitat! This session will provide an overview of the benefits of Habitat and a live demo of applications being built and deployed on traditional operating systems across Docker and Kubernetes, seamlessly.
An overview of Chef Automate and the various resources for Chef, InSpec and Habitat for Azure and Microsoft's other products. Presented September 20, 2017 at Tank Stream Labs.
Automating Applications with Habitat - Sydney Cloud Native MeetupMatt Ray
Habitat is an open source tool for automating the build, deployment, and management of applications. It defines a standard lifecycle for applications that includes building, deploying, running, and managing applications and their dependencies. Habitat packages applications and dependencies together, and uses supervisors to manage applications in production. It aims to simplify and standardize the delivery of developer services by automating common tasks like configuration, service discovery, and clustering across different runtime environments.
Compliance as Code: Shifting Compliance Left in Continuous DeliveryMatt Ray
This document discusses shifting compliance left into continuous delivery pipelines using compliance as code. It describes integrating security and compliance checks into regular development processes through automation. Compliance policies and rules are expressed as testable code that can be checked alongside infrastructure and application code in CI/CD pipelines. This allows organizations to more quickly detect and fix compliance issues while accelerating development cycles.
Brisbane AWS Meetup: OpsWorks for Chef AutomateMatt Ray
June 28, 2017 presentation at the Brisbane AWS Meetup.
OpsWorks for Chef Automate is a service directly available from AWS, managed by Chef as a joint offering.
Chef presentation from the CC Dojo #3 Agile & DevOps Bootcamp in Tokyo on December 12, 2016.
https://connpass.com/event/46308/
AWS Sydney North User Group, October 25, 2016. http://www.meetup.com/Amazon-Web-Services-Sydney-North-User-Group/events/234184228/
This session provided an introduction and live demo of Habitat. The process of moving applications from build to Docker and then published to ECR and running on ECS were demonstrated.
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/
HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar.
Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten.
In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich
- Zugriff auf die Konsole
- Auffinden und Interpretieren von Protokolldateien
- Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS)
- Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien
- Nutzung der Client Clocking-Funktion
DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock
Building 10x Organizations with Modern Productivity Metrics
10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, ‘The Coding War Games.’
Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method we invent for the delivery of products, whether physical or virtual, we reinvent productivity philosophies to go alongside them.
But which of these approaches actually work? DORA? SPACE? DevEx? What should we invest in and create urgency behind today, so that we don’t find ourselves having the same discussion again in a decade?
Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.
Impelsys provided a robust testing solution, leveraging a risk-based and requirement-mapped approach to validate ICU Connect and CritiXpert. A well-defined test suite was developed to assess data communication, clinical data collection, transformation, and visualization across integrated devices.
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc
Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency.
This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data.
Attendees will learn:
- Consumer awareness around data brokers and what consumers are doing to limit data collection
- How businesses assess third-party vendors and their consent management operations
- Where business preparedness needs improvement
- What these trends mean for the future of privacy governance and public trust
This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.
This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat
The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.
Procurement Insights Cost To Value Guide.pptxJon Hansen
Procurement Insights integrated Historic Procurement Industry Archives, serves as a powerful complement — not a competitor — to other procurement industry firms. It fills critical gaps in depth, agility, and contextual insight that most traditional analyst and association models overlook.
Learn more about this value- driven proprietary service offering here.
#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada
Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex
Toradex brings robust Linux support to SMARC (Smart Mobility Architecture), ensuring high performance and long-term reliability for embedded applications. Here’s how:
• Optimized Torizon OS & Yocto Support – Toradex provides Torizon OS, a Debian-based easy-to-use platform, and Yocto BSPs for customized Linux images on SMARC modules.
• Seamless Integration with i.MX 8M Plus and i.MX 95 – Toradex SMARC solutions leverage NXP’s i.MX 8 M Plus and i.MX 95 SoCs, delivering power efficiency and AI-ready performance.
• Secure and Reliable – With Secure Boot, over-the-air (OTA) updates, and LTS kernel support, Toradex ensures industrial-grade security and longevity.
• Containerized Workflows for AI & IoT – Support for Docker, ROS, and real-time Linux enables scalable AI, ML, and IoT applications.
• Strong Ecosystem & Developer Support – Toradex offers comprehensive documentation, developer tools, and dedicated support, accelerating time-to-market.
With Toradex’s Linux support for SMARC, developers get a scalable, secure, and high-performance solution for industrial, medical, and AI-driven applications.
Do you have a specific project or application in mind where you're considering SMARC? We can help with Free Compatibility Check and help you with quick time-to-market
For more information: https://www.toradex.com/computer-on-modules/smarc-arm-family
Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55
We’re bringing the TDX energy to our community with 2 power-packed sessions:
🛠️ Workshop: MuleSoft for Agentforce
Explore the new version of our hands-on workshop featuring the latest Topic Center and API Catalog updates.
📄 Talk: Power Up Document Processing
Dive into smart automation with MuleSoft IDP, NLP, and Einstein AI for intelligent document workflows.
Massive Power Outage Hits Spain, Portugal, and France: Causes, Impact, and On...Aqusag Technologies
In late April 2025, a significant portion of Europe, particularly Spain, Portugal, and parts of southern France, experienced widespread, rolling power outages that continue to affect millions of residents, businesses, and infrastructure systems.
Semantic Cultivators : The Critical Future Role to Enable AIartmondano
By 2026, AI agents will consume 10x more enterprise data than humans, but with none of the contextual understanding that prevents catastrophic misinterpretations.
AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB
I started my online journey with several hosting services before stumbling upon Ai EngineHost. At first, the idea of paying one fee and getting lifetime access seemed too good to pass up. The platform is built on reliable US-based servers, ensuring your projects run at high speeds and remain safe. Let me take you step by step through its benefits and features as I explain why this hosting solution is a perfect fit for digital entrepreneurs.
Artificial Intelligence is providing benefits in many areas of work within the heritage sector, from image analysis, to ideas generation, and new research tools. However, it is more critical than ever for people, with analogue intelligence, to ensure the integrity and ethical use of AI. Including real people can improve the use of AI by identifying potential biases, cross-checking results, refining workflows, and providing contextual relevance to AI-driven results.
News about the impact of AI often paints a rosy picture. In practice, there are many potential pitfalls. This presentation discusses these issues and looks at the role of analogue intelligence and analogue interfaces in providing the best results to our audiences. How do we deal with factually incorrect results? How do we get content generated that better reflects the diversity of our communities? What roles are there for physical, in-person experiences in the digital world?
6. SSH Control
"SSH supports two different protocol
versions.The original version, SSHv1, was
subject to a number of security issues.
Please use SSHv2 instead to avoid
these."
8. Whip up a one-liner!
grep "^Protocol" /etc/ssh/sshd_config | sed 's/Protocol //'
9. Apache Server Information Leakage
• Description
This Directive Controls wheather Server response field is sent back to clients includes a description of Generic OSType of the
Server.
This allows attackers to identify web servers details greatly and increases the efficiency of any attack,as security vulnerabilities are
dependent upon specific software versions.
• How toTest
In order to test for ServerToken configuration, one should check the Apache configuration file.
• Misconfiguration
ServerTokens Full
• Remediation
Configure the ServerTokens directive in the Apache configuration to value of Prod or ProductOnly.This tells Apache to only
return "Apache" in the Server header, returned on every page request.
ServerTokens Prod
or
ServerTokens ProductOnly
https://www.owasp.org/index.php/SCG_WS_Apache
10. More grep and sed!
grep "^ServerTokens" /etc/httpd/conf/httpd.conf | sed 's/ServerTokens //'
19. Key Trends
• While individual rule compliance
is up, testing of security systems
is down
• Sustainability is low. Fewer than
a third of companies were found
to be still fully compliant less
than a year after successful
validation.
21. Shell Scripts
grep "^Protocol" /etc/ssh/sshd_config | sed 's/Protocol //'
grep "^ServerTokens" /etc/httpd/conf/httpd.conf | sed 's/ServerTokens //'
47. InSpec
> inspec exec test.rb
Test a machine remotely via SSH
> inspec exec test.rb -i identity.key -t ssh://[email protected]
Test your machine locally
> inspec exec test.rb -t winrm://[email protected] --password super
Test Docker Container
> inspec exec test.rb -t docker://5cc8837bb6a8
Test a machine remotely via WinRM
AGENTLESS
48. Operating System & Application Coverage
• Microsoft Windows
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux Enterprise Server
• Oracle Enterprise Linux
• AIX
• HP-UX
• Solaris
• VMware ESXi
• MySQL
• Oracle
• PostgreSQL
• Tomcat
• SQL Server
• IIS
• HTTP request
53. The Chef Automate Platform
Continuous Automation for High Velocity IT
Workflow • Local development • Integration • Tooling (APIs & SDKs)
COLLABORATE
▪ Package
▪ Test
▪ Approve
BUILD
▪ Provision
▪ Configure
▪ Execute
▪ Update
DEPLOY
▪ Secure
▪ Comply
▪ Audit
▪ Measure
▪ Log
MANAGE
Infrastructure Automation Compliance AutomationApplication Automation
OSS AUTOMATION ENGINES
Increase Speed
▪ Package infrastructure and app
configuration as code
▪ Continuously automate
infrastructure and app updates
Improve Efficiency
▪ Define and execute standard
workflows and automation
▪ Audit and measure effectiveness of
automation
Decrease Risk
▪ Define compliance rules as code
▪ Deliver continuous compliance as
part of standard workflow
54. AWS OpsWorks for Chef Automate
Native Amazon Service
Managed Chef Server
▪ Utilizes RDS and other native
services
▪ May be externally accessible
AWS Native
▪ Auto Scaling in your VPC
▪ Automatic backups and upgrades
OpsWorks Stacks
▪ New name for previous version of
OpsWorks
● Partnership between Amazon and Chef, jointly
developed and maintained
● Fully managed AWS service with frequent updates
● Fully compatible with open source Chef
● Amazon is your support and billing
● All Chef Automate features will be supported
○ Visibility and Workflow today
○ Compliance soon
○ Currently Northern Virginia, Oregon & Ireland
with more planned