Tweet
Tweet

Slide 1

Slide 1 text

Continuous Automation Nathen Harvey VP, Community Development @nathenharvey

Slide 2

Slide 2 text

Hello! Nathen Harvey VP, Community Development Chef Software, Inc. @nathenharvey .

Slide 3

Slide 3 text

@nathenharvey Annapolis Tech Community Local resources, meetups, and people

Slide 4

Slide 4 text

@nathenharvey http://launchannapolis.org/

Slide 5

Slide 5 text

@nathenharvey https://www.meetup.com/launchannapolis/

Slide 6

Slide 6 text

@nathenharvey https://www.meetup.com/LAUNCH-Annapolis-Dev-Talks

Slide 7

Slide 7 text

@nathenharvey @LaunchAnnapolis

Slide 8

Slide 8 text

@nathenharvey https://www.meetup.com/Annapolis-Hacking-Infosec-Meetup

Slide 9

Slide 9 text

@nathenharvey https://www.meetup.com/Annapolis-Code-Coffee/

Slide 10

Slide 10 text

@nathenharvey Annapolis Suburbs Washington, DC & Baltimore

Slide 11

Slide 11 text

@nathenharvey Meet Online • http://www.dctechslack.com/ • http://baltimoretech-slack.herokuapp.com/

Slide 12

Slide 12 text

@nathenharvey https://www.meetup.com/devopsdc/

Slide 13

Slide 13 text

@nathenharvey https://www.meetup.com/BaltimoreDevOps/

Slide 14

Slide 14 text

@nathenharvey DevOpsDays https://www.devopsdays.org/

Slide 15

Slide 15 text

@nathenharvey Introductions •  Hiring? •  Looking for work? •  Attending or speaking at a conference? •  Something we all should know? •  Favorite color?

Slide 16

Slide 16 text

Continuous Automation Nathen Harvey VP, Community Development @nathenharvey

Slide 17

Slide 17 text

@nathenharvey Scale

Slide 18

Slide 18 text

@nathenharvey @nathenharvey

Slide 19

Slide 19 text

@nathenharvey @nathenharvey

Slide 20

Slide 20 text

@nathenharvey Software success metrics SPEED Measure of rate of software change EFFICIENCY Measure of effectiveness of software change RISK Measure of quality of software change @nathenharvey

Slide 21

Slide 21 text

@nathenharvey Software success metrics are at odds Improving on one metric can negatively impact the others SPEED EFFICIENCY RISK A focus on increasing speed to meet business requirements... ...can introduce more errors into the environment... ...and open up security holes faster than teams can react.

Slide 22

Slide 22 text

@nathenharvey UBIQUITOUS WORKFLOW AUTOMATION @nathenharvey

Slide 23

Slide 23 text

@nathenharvey Code @nathenharvey

Slide 24

Slide 24 text

@nathenharvey

Slide 25

Slide 25 text

@nathenharvey The journey to continuous automation Three steps to improvement across all dimensions of software success Detect Correct Automate 1. Detect Gain visibility and develop baselines 2. Correct Remediate priority issues 3. Automate Continuously detect & correct

Slide 26

Slide 26 text

@nathenharvey 55% Step one: Detect Gain visibility into current status to satisfy audits and drive decision-making of organizations do compliance assessments inconsistently or not at all. Apply policies and gain a complete view across the fleet ▪  Accurately assess risk ▪  Prioritize remediation actions ▪  Maintain audit readiness ▪  Create and adjust policies ” Continuous visibility means that you enter into audits knowing the outcome. Jon Williams, NIU ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

Slide 27

Slide 27 text

@nathenharvey ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Step two: Correct Remediate issues to improve performance and security ▪  Prioritize actions based on impact ▪  Improve application performance ▪  Close security holes ▪  Prove policy compliance Web & Media Giant Can patch 250,000 nodes within 6 hours of a patch being made available Develop, test, and deploy remediation to address issues across the fleet ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ of organizations need days or longer to remediate issues. 58%

Slide 28

Slide 28 text

@nathenharvey 59% Step three: Automate Deploy applications faster and manage risk continuously ▪  Increase speed while reducing risk ▪  Improve software change efficiency ▪  Maintain security and compliance ▪  Align DevOps and InfoSec Every resource and app in HPC environment automatically qualified as compliant with FDA standards before deployment ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ of organizations do not assess for compliance until code is running in production. Deploy applications with confidence

Slide 29

Slide 29 text

@nathenharvey @nathenharvey Step One: Detect ? ? ? ? ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Detect Correct Automate

Slide 30

Slide 30 text

@nathenharvey @nathenharvey Step Two: Correct ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Detect Correct Automate ? ? ? ?

Slide 31

Slide 31 text

@nathenharvey @nathenharvey Step Three: Automate ? ? ? ? ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ Detect Correct Automate

Slide 32

Slide 32 text

@nathenharvey A single platform to Detect, Correct, and Automate Chef Automate enables the entire journey Detect ▪  Test against industry benchmarks ▪  Report and address audit needs Correct ▪  Close detect/correct loop in one platform ▪  Develop baselines for automation Automate ▪  Detect and correct before production ▪  Single language across DevOps, InfoSec Chef Automate is a single platform to support the entire journey

Slide 33

Slide 33 text

@nathenharvey Chef can help you achieve Continuous Automation Follow a proven path Automate by treating as code Achieve measurable outcomes

Slide 34

Slide 34 text

@nathenharvey

Slide 35

Slide 35 text

@nathenharvey https://chefconf.chef.io/ @nathenharvey

Slide 36

Slide 36 text

Thank You! Nathen Harvey VP, Community Development Chef Software, Inc. @nathenharvey .