What We Do

You learned at our launch that we’re setting out to improve the experience users have with secure-communication tools. We told you that we want to work with the open source community, and that we’re committed to documenting our activities transparently. But what does this mean in practice – how will Ame, Trouble and I be spending our days?

It’s much easier to show than to tell, so I expect you’ll get a better feel for our work as we describe it here over time. For the moment, though, you can expect it to fall into three major buckets:

  • Direct collaboration: We partner with open-source software-development teams to support them in researching and improving the usability of their tools. We’re focusing at first on secure-communication tools that have an established user base, but also collaborate with teams building related or emerging tools. I’ll tell you more in future posts about what we look for in a partner, and also introduce the projects we’ve already started working with. If you have a tool that you’d like a hand with, get in touch!
  • Information sharing: We take our collaborative research and use it to build public resources that help everyone – developers, designers, researchers, users, and the community at large – better understand great user experiences and how to achieve them. We also work to raise the profile of high-quality usable-security designs and projects, both those that we participate in directly and those conducted by other organizations. We share this information freely here, and through our newsletter, Twitter stream, and conference talks. Stay tuned in the near term for a reading list that will help you get started thinking about usable security – and let us know about your favorite books and papers that you want to see included.
  • Mentorship and capacity building: We work to support usable-security practitioners of all stripes, including developers, designers, and researchers. We encourage promising junior practitioners and students in their efforts to learn, and to participate in designing trustworthy experiences. As part of this, we are partnering with the Open Technology Fund on the Secure Usability Fellowship program.

In addition to these formal activities, we also aspire to act as a hub for usable-security practitioners, and among the development, design, research, and user communities. Although we don’t provide funding for projects, we make it a point to know about different practitioners and activities in the space, and offer referrals when asked. So, although we’re still catching up on our backlog of email inquiries, we’re always interested in hearing from you if you’re doing work in this space. And, as always, we hope you’ll stay tuned to keep up with our activities!

Related

What We Do

You learned at our launch that we’re setting out to improve the experience users have with secure-communication tools. We told you that we want to work with the open source community, and that we’re committed to documenting our activities transparently. But what does this mean in practice – how will Ame, Trouble and I be spending our days? It’s much easier to show than to tell, so I expect you’ll get a better feel for our work as we describe it here over time.

All Your Base Are Belong To Gus

Hi, everyone! I’m Gus. I am pleased to be joining Simply Secure for a one-year fellowship. For the past year and change I worked for the Open Internet Tools Project, where I pioneered their work on security usability. OpenITP being an open source organization, I had the great joy of doing all my work in public, which means everything we did is still online and publicly available.

Niaje! Introducing Maina

hr { margin: 3em 0; } I’m Maina, and I'm excited to start out at as a Senior Fellow at Simply Secure. Prior to this fellowship, I conducted research at the Center for Advanced Security Research Darmstadt, and the Technische Universität Darmstadt. Using both quantitative and qualitative research methods, I focused on the usability of verification in Helios, an end-to-end verifiable, open-source, remote electronic voting system. Previously, I taught several undergraduate courses, including human computer interaction and computer security.