Uploaded byJustin Erdman
The Agile SOC @SANS SOC Summit 2017
The document discusses adopting an Agile approach to security operations. It describes Agile as an iterative software development methodology based on principles of collaboration and adaptation. Two common Agile frameworks are then explained - Scrum, which uses sprints, daily standups and retrospectives; and Kanban, which focuses on visualizing and limiting work in progress. Challenges of shifting to Agile are noted, such as cultural changes and maintaining business as usual, but benefits include improved workflow, predictability and resilience to change. Resources for implementing Agile using tools like Jira are also provided.
More Related Content
Similar to The Agile SOC @SANS SOC Summit 2017
The Agile SOC @SANS SOC Summit 2017
- 1. The Agile SoC Getthe most from your security team
- 2. About me I amJustin Erdman Security Engineer @ Cybereason Unapologetic Blue Teamer justin.erdman@cybereason.com Twitter: @elorionsec
- 3. Agenda ✓ What isit? ✓ Origin Story ✓ Why Agile? ✓ Core Principles / Elements ✓ The Real World ✓ Challenges ✓ Getting Started
- 4. ““Agile is notjust a methodology, but a set of principles and philosophy.” - Pearl Zhu
- 5. Agile…Huh? ✓ Set ofprinciples for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams ✓ Advocates adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change
- 6. In the Beginning… ✓1950’s – IBM started using iterative & incremental software development methods ✓ 1970’s - Evolutionary project management & adaptive software development ✓ 1990’s - Rapid application development, extreme programming, scrum ✓ 2001 - The Manifesto for Agile Software Development
- 7. The Skinny Responding tochange Following a plan Rapid iterations Big-Bang campaigns Testing & data VS Opinions & conventions Many small experiments A few large bets Individuals & interactions One size fits all Collaboration Silos & hierarchies
- 8. The Flavors DuJour ✓ Scrum ✓ Kanban
- 9. Scrum! ✓ Iterative &incremental process for structuring work ✓ Leverages commitment as change agent ✓ Face-to-face communication / close online collaboration ✓ Gamification of work
- 10. Scrum-ptious ✓ Small teamspending a short time building small things ✓ Time boxed & cross-functional teams ✓ Prioritized product backlog ✓ Three roles - product owner, scrummaster, & team ✓ Team velocity based ✓ No new items mid-sprint ✓ Scrum board reset every iteration ✓ Work only on those items that fit into the iteration ✓ Daily stand-ups
- 11. Roles & Ceremonies ✓Roles Product Owner ScrumMaster Team ✓ Ceremonies Sprint Planning Daily Stand-up Sprint Review Sprint Retrospective
- 12. The Quick &Dirty On Scrum ✓ Product owner creates a prioritized list ✓ team selects top item(s) from backlog ✓ Sprint (2-4 weeks) — team meets each day to assess progress ✓ Scrummaster keeps the team focused ✓ Hand work to customer / show to a stakeholder ✓ Sprint review & retrospective ✓ Rinse & repeat
- 13.
- 14. Kanban! ✓ Based on3 basic principles Visualize what you do today (workflow) Limit the amount of work in progress (WIP) Enhance flow ✓ Plan – Do – Study – Adapt (PDSA) approach
- 15. You Can Kanban ✓Work split into pieces ✓ Limited in progress items for a specific workflow ✓ Not timed boxed ✓ No prescribed roles ✓ New items can be added anytime within the pre-decided limit ✓ Board not reset & can be changed by anyone on team ✓ Story points & velocity not used ✓ No prescribed product backlog ✓ Daily stand-ups common
- 16.
- 17. Our Story Welcome toour crazy world
- 18. Change…Why? ✓ Better organizationof process improvements ✓ Prioritization of high impact items ✓ Increased work throughput & (some) predictability ✓ Easier to track planned & handle unplanned work ✓ Better resilience to changes ✓ Minimized planning & coordination ✓ Greater ability to gauge growth over time
- 19. You like StickyNotes…Right? ✓ Sprint zero 100% sticky notes ✓ No speed record attempts….yet ✓ Brain training ✓ Gamification of work ✓ Work to establish realistic team velocity ✓ Reinforce team mentality
- 20. Evolution ✓ Sticky Notesto Jira ✓ More realistic in sprint velocity ✓ Honest & direct team communication / feedback ✓ Full recognition of importance of ceremonies ✓ Less “I” & a whole lot more “team” ✓ Ask for help
- 21.
- 22.
- 23.
- 24.
- 25. Challenges & Setbacks ✓Moving to Scrum calls for a culture shift ✓ Establishing a groove – training is necessary ✓ Makes it difficult not to be a team player ✓ Breaking down classic silos ✓ Accountability ✓ Distraction from BAU – Discipline!
- 26. Resources / Tools ✓Tools Jira Trello ServiceNow – Visual Tasks Boards VersionOne ✓ http://www2.cprime.com/Agile-Impeditments-Webinar ✓ https://www.cprime.com/resources/what-is-agile-what-is-scrum ✓ https://www.atlassian.com/agile/how-to-do-scrum-with-jira- software
- 27. thanks! Any questions? You canfind me at justin.erdman@cybereason.com Twitter: @elorionsec