Free Application Security Program
Securing your software, together
Getting started with application security or building your first application security program can be overwhelming, especially when most the the frameworks and guidance are designed for enterprises. OneHourAppSec aims to help you get started in a way that suits your size and budget.
Ready to get started?
Enjoying OneHourAppSec? Try out SafeStack
Sign up for a 14-day trial of our team plan and invite your whole team. No credit card required.
Previous Sprints
Sprint #1: Start where you are
Welcome to the first sprint of OneHourAppSec – we’re so thrilled to have you here with us, dedicating your time to application security. How good!
This sprint we will lay the foundations for the work ahead of us. Our sprint goal is two-fold
Sprint #2: How bad can it be
This sprint we come to terms with this and take the drama out of it by preparing for the (somewhat) inevitable by:
Understanding what we should do if something does go wrong (from a security perspective)
Understanding how to determine how serious an incident is in our context.
Sprint #3: Embracing laziness
This sprint, we will take a look at some of the repetitive, boring parts of keeping your applications secure and then show you ways to do less work:
Explore the jobs to be done in application security, how frequently they need to be done and what’s involved.
To find ways to automate common, appsec jobs and make our lives easier
Sprint #4: Securing your source code
This sprint we will take a look at some of the foundations of securing our source code:
Examine the ways in which source code can be vulnerable and what steps we can take to protect it
Review the source code security for a project and take steps to improve it
Sprint #5: Making good library choices
This sprint we take a look at how we choose new components, what the risks are and take some steps to make things safer:
Understanding why 3rd party components can pose a risk to our software supply chain
Examining a 3rd party library from a security perspective and learning what to look for.
Putting a lightweight process in for accepting new components into your stack.
Sprint #6: Looking after your libraries
This sprint we look at what happens to those libraries once we have them in place and what we need to do from a security perspective to keep them and us safe.
Understanding why 3rd party components can pose a risk to our software supply chain
Examining a 3rd party library from a security perspective and learning what to look for.
Putting a lightweight process in for accepting new components into your stack.