expected iv. Great Amazon Reboot of 2014 – 10% of Amazon EC2 servers had to reboot for Xen emergency security patch. At Netflix, zero downtime, no one actively working incidents. They were at a Hollywood party infrastructure, and environments 2. Deployment tools 3. Testing standards and tools, including security 4. Deployment pipeline tools 5. Monitoring and analysis tools 6. Tutorials and standards ii Technical Practices of Integrating Information Security, Change Management, and Compliance 1. Introduction a. Goal to simultaneously achieve Information Security goals and create high degree of assurance

and technologically advanced. That is the force for the future.” - Secretary Panetta, Defense Security Review, 5 Jan 12iii Foreword Department of Defense (DoD) program managers and executives have environment. This guide seeks to adapt proven principles of Agile development specifically to the DoD context. More and more federal acquisition programs have begun to integrate aspects of Agile development success lie outside the control of the government program manager and his team. In the government context, Agile represents a good development approach when customizing an existing system or commercial

Agile c. Myth—DevOps is incompatible with ITIL d. Myth—DevOps is Incompatible with Information Security and Compliance: e. Myth—DevOps Means Eliminating IT Operations, or “NoOps” f. Myth—DevOps is Just center in queues and making it visible, all stakeholders can more easily prioritize work in the context of global goals. ii. REDUCE BATCH SIZES1. Another key component to creating smooth and fast flow designed. b. automate as much of the quality checking typically performed by a QA or Information Security department as possible c. Gary Gruver observes, “It’s impossible for a developer to learn anything

5. Fatal – forces a termination iv. Examples of potentially significant events (Gartner’s GTP Security & Risk Management group) 1. Authentication/authorization decisions 2. System and data access tools rather than static 3. Graph business metrics with infrastructure metrics to provide deeper context iv. Overlaying other relevant information onto our metrics 1. All production deployments should or those relevant to production incidents 1. Bad pull requests – typically doesn’t have enough context for the reader, little documentation of the changes intended outcome, or explanation of the thought

vision, that they understand the business’s intent, and that they will make decisions within the context of that intent.  How will the team determine the specific requirements—that is, determine what AWS he was the CIO of US Citizenship and Immigration Service (part of the Department of Homeland Security), CIO of Intrax, and CEO of Auctiva. He has an MBA from Wharton, a BS in Computer Science from

aims at unifying software development (Dev), security (Sec) and operations (Ops). The main characteristic of DevSecOps is to automate, monitor, and apply security at all phases of the software lifecycle: DevSecOps, testing and security are shifted to the left through automated unit, functional, integration, and security testing - this is a key DevSecOps differentiator since security and functional capabilities continuous monitoring approach in parallel instead of waiting to apply each skill set sequentially.  Security risks of the underlying infrastructure must be measured and quantified, so that the total risks

Installations  Route Adds – requires heightened security access  Database Data Script Execution  Load Balancer Node Disablement  OS and Security Patching  Requesting access to technology specific

Agile Principles 0 Nick Tuck XP Prctices 1 Shawn Stumme Continuous Delivery 4 Josh Wade Cyber Security through Agile 2 Nick Tuck Maximizing Retrospectives 2 Ray Page Open Agile Topics 0 Jason Beranek 3 Josh Sagucio Collaborative Work Environments 3 Nick Tuck Assuring Quality 3 Josh Wade Cyber Security through Agile 2 Nick Tuck Maximizing Retrospectives 2 Nick Wenner Clean Code - Book Overview

automate tests to validate the “-ilities” that are important (availability, capacity, security, etc.) ii. Incorporate security hardening testing and evaluation m. PULL OUR ANDON CORD WHEN THE DEPLOYMENT PIPELINE

Tuck XP Prctices shawn stumme Continuous Delivery Josh Wade Cyber Security through Agile Mar 2014 Nick Tuck Maximizing Retrospectives Ray Page