text
stringlengths
0
1.49k
• Availability of resources for learning and practicing InfoSec skills, such as vulnerable virtual machines and challenge platforms
• Capture the Flag (CTF) games as a way to learn about security
• Bridging the gap between information security and development worlds
• Challenges in cross-pollination between security and development teams
• The importance of teaching security basics to developers, rather than relying on security experts
• Making security easier for developers by simplifying complex concepts or automating security checks
• Code security is nearly impossible to achieve unless it's extremely simple
• Basic security measures include patching libraries, input validation, and output encoding
• Key points:
+ Patching: keeping libraries up-to-date
+ Input validation: using a whitelist over a blacklist
+ Output encoding: preventing cross-site scripting
• Additional important considerations:
+ Hardcoded credentials in API keys
+ Authentication and authorization
+ Encrypting data at rest and in transit
• Blind SQL injection attacks
• Automation and education as key to DevSecOps
• SQLmap and NoSQLmap tools for automated vulnerability detection
• DevSecOps concept and its focus on integration of developers, operations, and security teams
• Polarization in cybersecurity terminology (red team vs. blue team)
• The OWASP Top 10 list of most common web application vulnerabilities
• Security scanners and tools for code analysis
• OWASP top 10 resources for secure coding practices
• Go-specific OWASP book on GitHub
• Red teaming concepts and simulated attack methodology
• Terms: red team/blue team vs. white hat/black hat/grey hat distinctions
• Book recommendations: "Black Hat Go" and SD Elements software security requirements checker
• The concept of "chaotic neutral" and the gray area between good and bad intentions
• Hacktivism and the evolution of freelance security researchers to bug bounty programs
• Bug bounty programs as a way for organizations to encourage vulnerability reporting in a legal manner
• Concerns around the potential for organizations to take legal action against individuals participating in bug bounty programs
• Discussion about attending GopherCon and personal commitments (marriage and giving birth) being considered acceptable excuses for missing the conference
• Kubernetes 1.8 and 1.9 releases
• ARM64 support in Go applications
• Concurrent maps implemented in standard library
• Go 1.8 now available in App Engine beta
• GoRef package for invocation tracking and performance analysis
• Upcoming conferences: GopherCon, GothamGo, DotGo, Golang UK, and GopherCon Brazil
• #GopherConOrBust Twitter hashtag to encourage conference preparations
• Brian Ketelsen's new job at an unnamed company (announced as Amazon Whole Foods in a later statement)
• Discussion of Goman and other tools to generate man pages for open-source projects
• Request for a tool to automatically generate Bash and Zsh completions
• Shoutouts:
• Aaron Hnatiw's use of Visual Studio Code and its Go plugin
• Erik St. Martin's #FreeSoftwareFriday feature: K8GUARD, a Kubernetes monitoring tool
• Discussion of editors and IDEs, including Visual Studio Code, Gogland, Vim, and their respective plugins
• End of conversation
**Erik St. Martin:** Welcome back everybody to another episode of GoTime. We had a little bit of a long break there (two weeks), but we are back. On the show today we have myself, Erik St. Martin, Brian Ketelsen is also here...
**Brian Ketelsen:** Hello!
**Erik St. Martin:** And Carlisia Pinto.
**Carlisia Thompson:** Hi there!
**Erik St. Martin:** And our special guest for today actually gets to blend two worlds for us, both Go and information security. Please welcome to the show Aaron Hnatiw.
**Aaron Hnatiw:** Hey, everyone!
**Erik St. Martin:** For anybody who may not be familiar with you, do you wanna give a brief background, maybe how you got into security and how you transitioned into Go, and a little bit of how that fits into your current role?
**Aaron Hnatiw:** Sure. Starting out in security - I never really got into the industry early on; it was a little bit later when I was in university. I originally went to school for criminology and I was on the path to becoming a federal police officer, but when I was at school I ended up meeting a guy who was into hac...
I worked at a firewall company, and just kind of found my way through different roles, like system administrator, network engineer, developer, with the ultimate goal of getting into security. I ended up starting my own security consulting company after a couple years of doing those other jobs. That went really well; it...
Then I ended up getting approached by the company that I work for now, and I had the opportunity with them to do security consulting as well. The big draw for me was that the people that worked there were all really smart and they knew a lot about security, so I knew I could learn a lot from them... And not only that, ...
\[03:41\] So I got into consulting that way, and eventually found my way, after doing that for a few years -- I really enjoyed it, but I found that I was getting to a point where I needed to get more coverage than depth. I was doing a lot of the same stuff over and over again, and it was interesting, but I wanted more....
As far as Go, what got me interested in Go was I have a friend who's name is Thomas Shadwell; he's a senior security engineer over at Twitch, and I think everyone knows Twitch is a pretty big proponent of Go... So he uses it every day in his job, and he loved using it; he's really, really good at it, he's a super smart...
Sort of building some open source tools, contributing to projects... I actually started using it as the scripting language almost for my pentesting work. Python is kind of the most common one now, but I started using Go on a regular basis... I just picked it up and started using it more and more, and to this day I real...
**Carlisia Thompson:** I wanna pick up on one thread... You mentioned that you were using Go to teach, yeah? Two related questions - how did it go teaching Go? Did the students find it easier, did they complain, did they have praises for it? How did that go? And how do you think Go compares with Python for security rel...
**Aaron Hnatiw:** To answer the first question as far as how it went teaching it - teaching it was good. I was teaching developers; they were a group of third-year programmers, so they had some of the basics; I think they had done a lot of work in Python before, Java as well, so they had some of the basics and fundamen...
I think the one that I used in the course was [The Go Programming Language by Donovan/Kernighan](https://www.amazon.com/Programming-Language-Addison-Wesley-Professional-Computing/dp/0134190440). Now I think both Brian and Erik have both put out a [book](https://www.manning.com/books/go-in-action) as well... There's so ...
I gave them something interesting to work on... This is how I've always approached learning a language - finding a project to build on, and I think by doing that with them, it made it a little bit easier for them. I wouldn't say it was super easy for them to pick up, but having those resources and then being able to an...
The second question was how it compares to using something like Python for InfoSec...
**Erik St. Martin:** \[08:07\] I'd like to hear that from a more generic perspective, because a lot of InfoSec people use Python, and I think a lot of that is they can do things like HTTP servers and things like that significantly easier, and I think the standard library that Go provides makes a lot of that easier. So ...
**Aaron Hnatiw:** There's no doubt that Python right now in most cases is the easier choice and the better choice because there is a ton of libraries out there right now that support Python for security. But the thing is Go is getting to the place where there's more support for that... A lot of the work that I've done ...
Right now I would say it is more difficult for most things, because you have to really do it almost from scratch, you have to do it from a much lower level, but it's not impossible, and I think once you get the basics and once you start to learn what's available to you in the standard library, then it becomes easier.
**Carlisia Thompson:** So you're saying that part of the difficulty is having to write things from scratch, but it's more difficult because people are not aware of the functionality in the standard library? Because it's such a common thing for Go developers to want to always build things from scratch, and they find tha...
**Aaron Hnatiw:** Yeah, if you're coming from a developer's standpoint, I would say it's a lot more fun to do that. You get to understand the language a lot more. That's one of the things that I've benefitted from in writing Go - I've gotten to understand how it works at a much lower level, because I'm diving into the ...
[Beautiful Soup](https://en.wikipedia.org/wiki/Beautiful_Soup_(HTML_parser)) was one that was made in Python (it was pretty big) for scraping web content. I know that recently there was an [open source version of that in Go](https://github.com/anaskhan96/soup) that I looked at. There's a major package called [Scapy](ht...
\[12:19\] To answer your question, it's hard because of the lack of libraries, because not a lot of people come from a development background, but if you do come from a development background, it's awesome and you'll learn a lot doing it, and you just get better over time. It's the same with anything.
**Carlisia Thompson:** That makes total sense.