Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Quantifying Outcomes - Managing Risk

Quantifying Outcomes - Managing Risk

Part 2 in a 4 part short-form interactive series

George Miranda

March 08, 2017
Tweet

More Decks by George Miranda

Other Decks in Technology

Transcript

  1. IT Performance 0 20 40 60 80 Low Medium High

    Overall Performance (1st Poll) 0 20 40 60 80 Low Medium High Speed Metrics (2nd Poll) 0 10 20 30 40 50 Low Medium High Efficiency Metrics (3rd Poll) 0 20 40 60 Low Medium High Risk Metrics (4th Poll) Source: Audience poll 'Digital transformation & the competitive edge'
  2. The impact of outperformance 5x Revenue Growth, 8x Profitability Growth,

    2x Shareholder Return Growth 4.3% 13.5 % 18.1 % 0.8% -1.8% 10.3% B2B digital leaders turn in stronger financial performance. Top-quartile digital B2B companies Rest of B2B sample Revenue growth, CAGR,2010-15 Operating profit (EBIT) Growth, CAGR, 2010-15 Return to shareholder (TRS) growth, CAGR, 2010-15 ~5X ~8X ~2X Firms with high performing IT organizations were twice as likely to exceed their profitability, market share, and productivity goals The State of DevOps, 2016 HIGH PERFORMING IT ORGANIZATIONS: ▪ 200x more frequent releases ▪ 24x faster at recovering from failures ▪ 3x lower change failure rate ▪ 255x shorter lead times No high velocity company has gotten there without automation as a foundation 2x
  3. Velocity: time from idea to ship Software success metrics Quantifying

    outcomes to deliver software at speed Deployment frequency Time from commit to deploy Mean time to resolve Time deploying remediation Change failure rate SPEED Measure of rate of software change EFFICIENCY Measure of effectiveness of software change RISK Measure of quality of software change Compliance audit frequency Idea Ship
  4. Speed Efficiency Risk Transformation Speed 50% Source: Audience poll 'Digital

    transformation & the competitive edge' Most important transformation concerns
  5. Speed Efficiency Risk Transformation Risk 8.3% Source: Audience poll 'Digital

    transformation & the competitive edge' Least important transformation concerns
  6. Equifax easily scans and maintains security policies with Chef Focus

    on Risk Measuring the quality of software change HIGH IT PERFORMERS MEDIUM IT PERFORMERS LOW IT PERFORMERS On-Demand Week - Month Month - 12 Months < 1 Hour Week - Month Month - 6 Months USE CASES INCLUDE: ▪ Compliance Automation ▪ Compliance Test Coverage COMPLIANCE AUDIT FREQUENCY TIME DEPLOYING REMEDIATION
  7. PART OF A PROCESS OF CONTINUOUS COMPLIANCE Scan for Compliance

    Build & Test Locally Build & Test CI/CD Remediate Verify A SIMPLE EXAMPLE OF AN INSPEC CIS RULE InSpec ▪ Translate compliance into Code ▪ Clearly express statements of policy ▪ Move risk to build/test from runtime ▪ Find issues early ▪ Write code quickly ▪ Run code anywhere ▪ Inspect machines, data and APIs ▪ Customize requirements with policy overlays Turn security and compliance into code control ‘cis-1.4.1’ do title ‘1.4.1 Enable SELinux in /etc/grub.conf’ desc ‘ Do not disable SELinux and enforcing in your GRUB configuration. These are important security features that prevent attackers from escalating their access to your systems. For reference see … ‘ impact 1.0 expect(grub_conf.param ‘selinux’).to_not eq ‘0’ expect(grub_conf.param ‘enforcing’).to_not eq ‘0’ end
  8. Equifax easily scans and maintains security policies with Chef Focus

    on Risk Measuring the quality of software change HIGH IT PERFORMERS MEDIUM IT PERFORMERS LOW IT PERFORMERS On-Demand Week - Month Month - 12 Months < 1 Hour Week - Month Month - 6 Months USE CASES INCLUDE: ▪ Server patching ▪ Remediating zero-day exploits COMPLIANCE AUDIT FREQUENCY TIME DEPLOYING REMEDIATION
  9. Chef ▪ Manages deployment and on-going automation ▪ Define reusable

    resources and infrastructure state as code ▪ Scale elegantly from one to tens of thousands of managed nodes across multiple complex environments ▪ Community, Certified Partner, and Chef supported content available for all common automation tasks Infrastructure automation and delivery at scale windows_feature ‘IIS-WebServerRole’ do action :install end windows_feature ‘IIS-ASPNET’ do action :install end iis_pool FooBarPool do runtime_version “4.0” action :add end package "apache" do action :install end template “/etc/httpd/https.conf” do source “httpd.conf.erb” mode 0075 owner “root” group “root” end service “apache2” do action :start done
  10. Velocity: time from idea to ship Software success metrics Quantifying

    outcomes to deliver software at speed Deployment frequency Time from commit to deploy Mean time to resolve Time deploying remediation Change failure rate SPEED Measure of rate of software change EFFICIENCY Measure of effectiveness of software change RISK Measure of quality of software change Compliance audit frequency Idea Ship
  11. Q&A George Miranda Technical Strategy Chef Software, Inc. @gmiranda23 .

    What challenges do you face in decreasing risk as you increase your speed?