DoD CIO Enterprise DevSecOps Reference Design - Summaryenables: correlated and centralized logs, container security, east/west traffic management, a zero-trust model, a whitelist, Role-Based Access Control (RBAC), continuous monitoring, signature-based the service mesh 6. Zero Trust down to the container level. Zero trust requires strict controls, never trust anything by default and always verify. Key aspects of zero trust at the container level0 码力 | 8 页 | 3.38 MB | 5 月前3
The DevOps Handbookonly about one-third were successful at improving the key metric!” iii. A/B testing helps reduce zero or negative value add features to the baseline that also increase maintenance costs and identify to testing failure – seems valid since better testing practices could have mitigated iii. In low-trust, command & control cultures, change control often results in worse outcomes d. POTENTIAL DANGERS0 码力 | 8 页 | 24.02 KB | 5 月前3
MITRE Defense Agile Acquisition Guide - Mar 2014develop predictable and routine meeting schedules to enhance coordination. Second, a culture of trust that spans the decision authority, developers, testing organization, acquirers, program management facilitate this model, but it must be further reinforced at the top. Leadership can signal that trust by empowering team members with decision-making authority based on clearly communicating a high- while continuing to focus on the intent. This requires the team to build relationships that promote trust, collaboration, transparency, and shared responsibility. The Government Accountability Office0 码力 | 74 页 | 3.57 MB | 5 月前3
The DevOps HandbookThird Way: The Principles of Continual Learning and Experimentation 37 i. culture of fear and low trust 1. workers who make mistakes are punished 2. those who make suggestions or point out problems are suppressing, even punishing, learning and improvement, perpetuating quality and safety problems ii. high-trust culture 1. we are all lifelong learners who must take risks in our daily work 2. we learn from our outcomes as a shared goal, regardless of where they reside in the organization. ii. Requires high-trust cultures, transparent prioritization, and sufficient slack in the systemiii. Toyota Kata, “…one cannot0 码力 | 8 页 | 22.57 KB | 5 月前3
Velocity Conference 2015Training by David Genn (IG) @david_genn Separate deployment from release Automate everything Trust your tests Conversations are way better than project proposals Start small, be brave quickly0 码力 | 4 页 | 176.79 KB | 5 月前3
The Goal - A Process of Ongoing Improvementdishes tonight. Record the amount that each of them deviates from the average. They all start at zero. If the roll of the die is a 4, 5, or 6 then record - respectively - a gain of .5, 1.5, or 2.5. And0 码力 | 6 页 | 100.81 KB | 5 月前3
The DevOps HandbookReboot 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 celebrating an acquisition0 码力 | 9 页 | 25.13 KB | 5 月前3
共 7 条
- 1













