Protect Your Software with These Nine Security Questions

Download Our Guide on Software Testing Strategies

Web Security Issue 1: Is It a Problem, If My API Documentation Is Visible?

Web Security Issue 2: Should You Protect Your Endpoint Parameters?

Why Is This Dangerous?

Download the Top QA Strategies Guide

Web Security Issue 3: Will My Application Be Safer, If I Use Authentication?

Why Is This Dangerous?

Web Security Issue 4: Do Small Web Applications Also Need Protection?

Why Is This Dangerous?

Web Security Issue 5: Do I Need to Validate All User Input?

Why Is This Dangerous?

Our Guide to QA Best Practices

Web Security Issue 6: Should I Let the User Upload Any File They Want?

Why Is This Dangerous?

Web Security Issue 7: Will HTTPS (HTTP over SSL) help?

Why Is This Dangerous?

Web Security Issue 8: What If My Users Never Log Out. Is That Dangerous?

Why Is This Dangerous?

Web Security Issue 9: Will IP Restriction Help?

Why Is This Dangerous?

Are We Doomed to Insecurity?

  • When a website asks for your personal information
  • Asking for your credit card (even if it says you won money)
  • Check if it uses HTTPS (For payments, it’s absolutely mandatory.)
  • Clicking on a button (even if the only option is OK) or link, if you are unsure about the intended action

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store