Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Insecurity in Information Technology - USENIX Enigma Edition

277 views

Published on

A lot is expected of software developers these days; they are expected to be experts in everything despite very little training. Throw in the IT security team (often with little-to-no knowledge of how to build software) telling developers what to do and how to do it, and the situation is further strained. This silo-filled, tension-laced situation, coupled with short deadlines and mounting pressure from management, often leads to stress, anxiety and less-than-ideal reactions from developers and security people alike. This talk will explain how people's personal insecurities can be brought out by leadership decisions in the way we manage our application security programs, and how this can lead to real-life vulnerabilities in software and other IT products. This is not a soft talk about "feelings", this is a talk about creating programs, governance and policies that ensure security throughout the entire SDLC. No more laying blame and pointing fingers, it's time to put our egos aside and focus on building high-quality software that is secure. The cause and effect of insecurities and other behavioural influencers, as well as several detailed and specific solutions will be presented that can be implemented at your own place of work, immediately. No more ambiguity or uncertainty from now on, only crystal clear expectations.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Insecurity in Information Technology - USENIX Enigma Edition

  1. 1. Insecurity in Information Technology Tanya Janca Tanya.Janca@owasp.org OWASP Ottawa Chapter Leader OWASP DevSlop Project Leader @SheHacksPurple
  2. 2. All of this creates the feeling of insecurity about people’s jobs and how to do them well. This leads to predictably negative behaviour.
  3. 3. Deviant Behaviour
  4. 4. Moral Disengagement
  5. 5. Reduced Job Involvement
  6. 6. Risk Taking Behaviour
  7. 7. Reduction of Organizational Citizenship Behavior (positive workplace activity and involvement)
  8. 8. All of this negative behavior leads to insecure software.
  9. 9. The Plan: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  10. 10. The Plan: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  11. 11. The Plan: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  12. 12. The Plan: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  13. 13. The Plan: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  14. 14. Start Security Earlier! Requirements Design Code Testing Release Push Left!
  15. 15. Break security testing into smaller pieces
  16. 16. 1
  17. 17. 1
  18. 18. Job Shadowing
  19. 19. 2Give Developers Security Tools!
  20. 20. OWASP: Your new BFF!!! The Open Web Application Security Project
  21. 21. 2
  22. 22. 2
  23. 23. In Summary: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  24. 24. In Summary: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  25. 25. In Summary: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  26. 26. In Summary: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  27. 27. In Summary: 1. Support dev and sec team with processes, training, and resources so they can confidently get the job done. 2. Initiate and then maintain culture change.
  28. 28. ANY QUESTIONS?OWASP Ottawa Chapter Leader OWASP DevSlop Project Leader @SheHacksPurple Tanya Janca Tanya.Janca@owasp.org

×