s_streichsbier

3 ms·

1. 1.▲
   The Rise of AI Security Engineers(thoughtson.ai)

   2 points by s_streichsbier 2y ago|0 comments
2. 2.▲
   NET Security Resources(github.com)

   3 points by s_streichsbier 8y ago|0 comments
3. 3.▲
   Awesome Python Security Resources(github.com)

   8 points by s_streichsbier 8y ago|0 comments
4. 4.▲
   by s_streichsbier 8y ago

   Famous last words ;) While leveraginvg serverless gives a lot of benefits in terms of hardening and infrastructure setup, all the traditional application security issues (e.g. OWASP TOP 10) like SQL injection can still apply.
5. 5.▲
   by s_streichsbier 8y ago

   I think for API consumption one important consideration is keeping API keys secure. Besides that, most of the modern issues I have seen are related to authentication and access control. Regarding reverse engineering, I personally feel that
6. 6.▲
   by s_streichsbier 8y ago

   These are excellent suggestions Bucephalus. One note though, they mainly deal with the infrastructure/network/os level security. A simple SQL injection in the code would still be exploitable regardless of the countermeasures above
7. 7.▲
   by s_streichsbier 8y ago

   <3
8. 8.▲
   by s_streichsbier 8y ago

   Good one, I didn't know that one yet. For the dynamic scans, I can also suggest https://www.securityheaders.com and https://ssllabs.com/
9. 9.▲
   Ask HN: How are you securing your apps in 2019?

   30 points by s_streichsbier 8y ago|14 comments
10. 10.▲
    Awesome PHP Security – Security Related Resources for PHP(github.com)

    6 points by s_streichsbier 8y ago|0 comments