Off-roading With Test by Sylvia Killinen

At the fabulous, swash-buckling Ministry Of Testing, Bangalore,
we had had Sylvia Killinen present on Security Testing! You can
watch the presentation recording here:

I am sharing a few questions that I wanted to ask Sylvia (although
I was driving at the time the crowdcast happened, thanks much to
Aine for covering me!).

Please feel free to add your questions too so that Sylvia can answer
them!

Let’s create a secure world!

1 Like

Hi Sylvia,

Here are my questions:

  1. Key industry experts in Security and Security Testing

  2. How do we make sure that security is an integral part of the test planning, and not as an aside thought ?

  3. What books do you recommend on Security and Security Testing?

  4. What blogs do you recommend on Security and Security Testing?

  5. What social media handles do you recommend on Security and Security Testing?

  6. What Meetups / regular Webinars do you recommend on Security and Security Testing?

  7. For learning Security and Security Testing, is there a play-around application/website?

  8. What are the github/Open Source resources on Security and Security Testing?

  9. Is there a ‘Dashboard’ that you loved which alerts on threat happenings? Can you share the link?

  10. Can you share a link to a well-written Security Test Plan?

  11. Do you have a ‘bookmarks’ page of security related website URLs?

  12. Tools that you recommend for security testing?

  13. What would be your general approach on coming up with a security testing architecture/test planning?

I apologize for the broken links in this post - the filter would not permit me to have all the ones I wanted to add.

  1. Key experts: There aren’t a lot of dedicated, vocal security testers (yet!) but ordinary test practices can and do apply - keep talking with your favorite voices in testing, and apply what you already know to security topics! In addition, searching for security practitioners on any social media site will likely reveal some interesting writers.

  2. You can work with your AppSec team to define and test security requirements as early as possible. Some requirements are probably known even before development begins, and you can write broad test cases based on those, then tune them to specific projects.

  3. For web application security testing, I highly recommend The Web Application Hacker’s Handbook. Shostack’s Threat Modeling is an extremely useful guide to the practice as well.

  4. I highly recommend reading https://blog.grimm-co.com/ and Schneier on Security for interesting security content. I’m not aware of any blogs specifically about security testing.

  5. You can find me on Twitter, and there are many other testers available there also. @/maaretp, @/noahsussman, and @/lisacrispin come to mind.

  6. Sadly, I am not aware of any regular webinars on this topic! (Anyone?)

  7. You can play around in many websites and applications! I strongly recommend the challenges at overthewire(.)org (do them in the recommended order if this is all brand new) or, if you have a specific subject in mind, try searching for it on tryhackme(.)com/.

  8. The Open Web Application Security Project (owasp(.)org) maintains extensive repositories, documentation, and tooling, all open source.

  9. Sadly, there’s not - I like to watch various threat intelligence websites (such as BleepingComputer) to try and stay abreast of what’s happening in the world of information security.

  10. Sorry, no; all of the test plans I have worked on are confidential.

  11. I should really set one of these up.

  12. OWASP ZAP (Zed Attack Proxy) is one of my favorites. BurpSuite is another excellent proxy. In addition, you can set up a Kali Linux VM to explore a huge variety of hacking and testing tools.

  13. Hopefully the presentation answered this one - but in case it didn’t…

  • Threat model your application to find vulnerabilities at an architectural level.
  • If you are in a CI/CD process or otherwise do not have stable architecture, threat model individual data flows.
  • Prioritize the threats by risk.
  • Write and automate security test cases for the most critical threats first!