Patch Management
Margaret Lee & Ajay Sridhar
October 2020
Speakers
2
Ajay Sridhar
Sr. Solutions Engineer
Puppet, Inc.
Margaret Lee
Product Manager
Puppet, Inc.
3
What many organizations struggle with...
Different teams can all have their own way to patch
systems
Lack of process control
Many tools for patching and securing infrastructure
across disparate Operating Systems
Toolchain Sprawl
We are all human. Manual processes increase the room for error
Manual and error prone processes
Separate views for each operating system
Lack of visibility across the estate
4
Bring visibility and understand
compliance of your infrastructure
Visibility
Secure your infrastructure with
Puppet Enterprise
Secure
Bring process control to your
patching and security workflow
Patch
Puppet Enterprise will help you...
The average time to
patch is 102 days
- Ponemon Institute Report (2018)
6
Typical Patching Workflow
Teams review
available patches
Coordinate with system
owners to agree on
update schedule
Create necessary
ticketing and get
change approvals
Apply patches
Validate that patch
was applied
successfully
Several hours
to several days
Multiple days
Weeks
Hours, with
multiple
stakeholders
Several hours
Timeframes for each step are approximations. Amount of time required will vary between companies.
Patch Management from the PE Console
7
Current State
● Everyone needs to patch their systems on a regular basis.
● Need to know what needs to be patched and where
● Different tools required for each operating system
● Complex workflow coordination across multiple teams
What gets eliminated
● Manual, error prone processes
● Complex workflows coordinated across multiple teams
● Time consuming
● Lack of visibility into what patches are available and what systems need
patching
Keeping your infrastructure secure with Puppet
Manage tool
sprawl...
• Puppet Enterprise can patch Windows and
*nix platforms independently
• Track compliance
• Simplifying your patching process by reducing
the number of moving parts
8
PUPPET PRESENTATION TEMPLATE - ASSET LIBRARY9
Demo
Why use Puppet
Enterprise for
Patching?
• Leverage your existing investment in PE
• Improve patching success rates with automation
• Simplify your patching workflow
• One product all you platforms
• Compliance and audit
• Improve patch cycle time
• Security and RBAC capabilities
10
11
Looking ahead
1
2
3
Usability Improvements - Make it easy
for non Puppet admins to do patching.
Workflow Improvements - Address more
complex use cases
Reporting - Compliance and execution
reporting
Q&A
Save the date! 19 Nov 2020
● 3 events in one day: APAC, EMEA, Americas
● Multiple tracks for Puppet users and IT leaders, hands-on
workshops, networking, and more
https://puppet.com/puppetize/
Thank you!

Simplified Patch Management with Puppet - Oct. 2020

  • 1.
    Patch Management Margaret Lee& Ajay Sridhar October 2020
  • 2.
    Speakers 2 Ajay Sridhar Sr. SolutionsEngineer Puppet, Inc. Margaret Lee Product Manager Puppet, Inc.
  • 3.
    3 What many organizationsstruggle with... Different teams can all have their own way to patch systems Lack of process control Many tools for patching and securing infrastructure across disparate Operating Systems Toolchain Sprawl We are all human. Manual processes increase the room for error Manual and error prone processes Separate views for each operating system Lack of visibility across the estate
  • 4.
    4 Bring visibility andunderstand compliance of your infrastructure Visibility Secure your infrastructure with Puppet Enterprise Secure Bring process control to your patching and security workflow Patch Puppet Enterprise will help you...
  • 5.
    The average timeto patch is 102 days - Ponemon Institute Report (2018)
  • 6.
    6 Typical Patching Workflow Teamsreview available patches Coordinate with system owners to agree on update schedule Create necessary ticketing and get change approvals Apply patches Validate that patch was applied successfully Several hours to several days Multiple days Weeks Hours, with multiple stakeholders Several hours Timeframes for each step are approximations. Amount of time required will vary between companies.
  • 7.
    Patch Management fromthe PE Console 7 Current State ● Everyone needs to patch their systems on a regular basis. ● Need to know what needs to be patched and where ● Different tools required for each operating system ● Complex workflow coordination across multiple teams What gets eliminated ● Manual, error prone processes ● Complex workflows coordinated across multiple teams ● Time consuming ● Lack of visibility into what patches are available and what systems need patching Keeping your infrastructure secure with Puppet
  • 8.
    Manage tool sprawl... • PuppetEnterprise can patch Windows and *nix platforms independently • Track compliance • Simplifying your patching process by reducing the number of moving parts 8
  • 9.
    PUPPET PRESENTATION TEMPLATE- ASSET LIBRARY9 Demo
  • 10.
    Why use Puppet Enterprisefor Patching? • Leverage your existing investment in PE • Improve patching success rates with automation • Simplify your patching workflow • One product all you platforms • Compliance and audit • Improve patch cycle time • Security and RBAC capabilities 10
  • 11.
    11 Looking ahead 1 2 3 Usability Improvements- Make it easy for non Puppet admins to do patching. Workflow Improvements - Address more complex use cases Reporting - Compliance and execution reporting
  • 12.
  • 13.
    Save the date!19 Nov 2020 ● 3 events in one day: APAC, EMEA, Americas ● Multiple tracks for Puppet users and IT leaders, hands-on workshops, networking, and more https://puppet.com/puppetize/
  • 14.