Everyone is moving fast and needs to learn new things constantly. We're on call and seems also always on duty. We're trying to finish the iron man before training our mind and body. The results are exhaustion, anxiety and burnout. Let's check your awareness. Build your personal SIEM and learn how to read it.
Share your experience on Rubber Ducky, Pineapple and Co. Did they work as expected? Did they perfom well in pentesting or for security awareness trainings? Which code have you written for the device?
3
Votes
5
Votes
Writing a Context-keyed Payload Encoder in Metasploit
Vulnerabilities are often found by private bug hunters. Most companies don't offer a way to submit security related reports in an easy way. Instead the only way is to contact the customer support which is normally unable to handle the request.
Related topics are:
- Personal experience with bug reporting
- Defining a tolerated scope for private security testing
- Offering a simple way to submit a report
- Dealing with reports (Bounties, Disclosure, ...)
I will give a short intro to LangSec to answer the question: Why are parsers, unparsers, and theoretical computer science key to most of the vulnerabilities we see today?
I would love to discuss options and opinions how to get out of this software crises by discussing:
- use of tools
- does knowledge alone help
- new programming language features to prevent entire bug classes like Injections
The IETF OAuth Working Group is working towards a new Security Best Current Practice (BCP) RFC that aims to weed out insecure implementation patterns for OAuth 2.0. It based on lessons learned in practice and on new attacks found through formal security analyses of OAuth and OpenID Connect.