Designed In
Do your software developers feel responsibility for the security of the systems they build? If so, are they designing security in? One of the reasons this is difficult is that they are incentivized to demonstrate that the system does what it is supposed to do.
How often do we make sure it doesn't do what it is not supposed to do?
By the way, what is security? Can you and they even define it? How will you know it when you see it? How will you know you have done enough?
How do we instill deep, meaningful, incremental improvements to an organization's security posture? How do we convince our executives to spend enough on security? By the way, what's enough?
In this talk I will help give you a tangible set of steps to do just this.
About Brian Sletten
Brian Sletten is a liberal arts-educated software engineer with a focus on forward-leaning technologies. His experience has spanned many industries including retail, banking, online games, defense, finance, hospitality and health care. He has a B.S. in Computer Science from the College of William and Mary and lives in Auburn, CA. He focuses on web architecture, resource-oriented computing, social networking, the Semantic Web, AI/ML, data science, 3D graphics, visualization, scalable systems, security consulting and other technologies of the late 20th and early 21st Centuries. He is also a rabid reader, devoted foodie and has excellent taste in music. If pressed, he might tell you about his International Pop Recording career.
More About Brian »