Welcome to our catalog of resources on how to succeed with web application security. If you want to be able to focus on what’s most important or productive, you need to develop your application with a strong culture of Test Driven Development and you need to have a Defense in Depth strategy that includes the:
- Business model – especially removing sensitive information that is not truly needed
- Technical controls in development
- The configuration and management of the deployment environment – the devops.
Choose from the videos below. These are not easy concepts, but by learning them and putting them in place within your organization, you will greatly reduce your exposure to information security threats and protect your customers.
The Big Picture
Defending Against Data Breaches, as a Practicing Ruby Developer
A 20 minute conference talk given at Rocky Mountain Ruby 2015.
What information do I need to secure?
Question: What information do we need to keep secure?
Answer: It’s about classifying the information. You can read more on Frank’s blog post on this Commercial Information Security Classification System.
Is Ruby on Rails secure?
Question: Is Ruby on Rails secure? What if I add SSL?
Answer: Security is not an on/off switch. You need to ask three questions whenever you are interested in determining the appropriate security level for anything.
- Secure against what?
- What is the worst thing that can happen?
- Compared to what alternative?
Sadly, there is no secure switch to make all the risks go away! One should not look for magic pixie dust, but understand that security is a process that includes all aspects of the business model, application development, and deployment management practices.
Does a UUID make a secure API token for an Android or iOS application’s API RESTful endpoints?
So you need to implement an API token for mobile applications to access your backend server. A common practice among Ruby on Rails or Sinatra developers is to use a UUID. But is this a good idea? Is it secure enough? Can I just store it in plaintext in the database?
No, it’s not and for the same reasons that you should never store passwords in plaintext in the database. But they do make for great random usernames and following the same pattern you would for securely hashing passwords, you can make a very secure API token system for your application.
How to reduce an app’s vulnerability surface area while maintaining usability
Question: How do you eliminate surface area at multiple levels? How do you balance it the need for security with the need for usability?
Answer: It’s best to remove sensitive information from the business model. At the times that one cannot do that, technical controls to segment the sensitive data in a defense in depth strategy.